httpdocs 301 SSL redirects are dropping pages from search engine.

You can check if the redirect is set correctly with https://www.redirect-checker.org/.

After enabling the redirect, search engines will start indexing the new URLs: with https.

You should update search console and Google Analytics accordingly, see also:
https://really-simple-ssl.com/how-to-setup-google-analytics-and-google-search-consolewebmaster-tools/

The htaccess 301 redirect in its current form is used in the plugin for five years now, on millions of websites.

It is however possible that on some servers the server configuration is adjusted in such a way that standard htaccess redirects don’t work as expected. In that case, we recommend to use the php redirect.

If you want you can post the contents of your htaccess file here and we can take a look.

ok

• This reply was modified 1 year, 12 months ago by Zeliha Canderengul.
• This reply was modified 1 year, 12 months ago by Zeliha Canderengul.
• This reply was modified 1 year, 12 months ago by Zeliha Canderengul.

#Begin Really Simple Security
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on [NC]
RewriteCond %{REQUEST_URI} !wp-content\/cache\/(all|wpfc-mobile-cache)
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
</IfModule>
#End Really Simple Security

# BEGIN WordPress
# Headers Security Advanced & HSTS WP – 5.0.06
<IfModule mod_headers.c>
Header always set Strict-Transport-Security “max-age=63072000; includeSubDomains; preload” “expr=%{HTTPS} == ‘on’”
Header always set X-XSS-Protection “1; mode=block”
Header always set X-Content-Type-Options “nosniff”
Header always set Referrer-Policy “strict-origin-when-cross-origin”
Header always set Expect-CT “max-age=7776000, enforce”
Header set Access-Control-Allow-Origin “null”
Header set Access-Control-Allow-Methods “GET,PUT,POST,DELETE”
Header set Access-Control-Allow-Headers “Content-Type, Authorization”
Header set X-Content-Security-Policy “img-src *; media-src * data:;”
Header always set Content-Security-Policy “report-uri https://www.resimsin.com&#8221;
Header always set X-Frame-Options “SAMEORIGIN”
Header always set Permissions-Policy “accelerometer=(), autoplay=(), camera=(), fullscreen=*, geolocation=(self), gyroscope=(), microphone=(), payment=*”
Header set X-Permitted-Cross-Domain-Policies “none”
</IfModule>
# END Headers Security Advanced & HSTS WP

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

• This reply was modified 1 year, 12 months ago by Zeliha Canderengul.

my website is in Hostgator.

Rogier Lankhorst (@rogierlankhorst)

@zelihacanderengul there is nothing wrong with the .htaccess redirect. I also checked your redirect to https, this works fine: there’s a 301 permanent redirect on it.

It does not seem likely this redirect is an issue. More likely it is a configuration issue in search console, or something like that. But you can set it to php redirect if that gives better results for you.

As a side note: you have currently:
Header always set X-XSS-Protection “1; mode=block”

It is best practice to use
Header always set X-XSS-Protection “0”

For more information on this, see https://really-simple-ssl.com/definition/what-is-xxss-protection/

The above codes are what happens when I add htaccess for 301 SSL. I do not use these codes until the problem is solved. So for now I am using PHP 301 SSL redirect. We could be mistaken because an htaccess 301 SSL redirect is not active when you check my website. I will remove PHP SSL redirect and activate htaccess 301 SSL redirect until you respond to me so that you can do the test better. And I will wait for you to do a test. I hope we can fix the error if any.

@zelihacanderengul as your php redirect seems to handle the redirect fine, I would recommend to leave it as it is.

ok thnk u