My server is configured correctly. (Server default virtual host file goes to correct ip)
I’m getting mixed content errors for images:
Mixed Content: The page at ‘https://www.p a r a d i s e f o u n d t o u r s.com/’ was loaded over HTTPS, but requested an insecure image ‘http://www.p a r a d i s e f o u n d t o u r s.com/images/p a r a d i s e_f o u n d_t o u r s_logo_272x90.png’. This content should also be served over HTTPS.
NOTE: remove spaces in domain name if you want to view it.
any ideas?
You need
a) specify your explicit domain is https in your wp-config.php file
b) setup 301 redirect in your htaccess file to redirect all http requests to https
c) edit your WP dbase to replace all instances o internally added images embdeed into posts to change domain from http to https.
Will that affect my indexed pages in Google? They are 200+ indexed pages in there as www. ?
While I got you Chris, here’s my .htaccess file in the public_html directory. I’m thinking of removing the block to index sitemaps.
Do you see any other trouble with this? Thanks
RewriteCond %{HTTP_USER_AGENT} libwww-perl.*
RewriteRule .* ? [F,L]
RewriteCond %{HTTP_HOST} ^50\.28\.106\.21
RewriteRule (.*) http://www.mydomain.com/$1 [R=301,L]
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
# PROTECT WPCONFIG
<files wp-config.php>
order allow,deny
deny from all
</files>
# Enable Leverage Browser Caching
<IfModule mod_rewrite.c>
ExpiresActive On
# Favicon (cannot be renamed)
ExpiresByType image/x-icon "access plus 1 week"
# Media: images, video, audio
ExpiresByType audio/ogg "access plus 1 month"
ExpiresByType image/gif "access plus 1 month"
ExpiresByType image/jpeg "access plus 1 month"
ExpiresByType image/png "access plus 1 month"
ExpiresByType video/mp4 "access plus 1 month"
ExpiresByType video/ogg "access plus 1 month"
ExpiresByType video/webm "access plus 1 month"
# CSS and JavaScript
ExpiresByType application/x-javascript "access plus 1 week"
ExpiresByType text/css "access plus 1 week"
ExpiresByType text/javascript "access plus 1 week"
# Webfonts
ExpiresByType application/vnd.ms-fontobject "access plus 1 month"
ExpiresByType application/x-font-ttf "access plus 1 month"
ExpiresByType application/x-font-woff "access plus 1 month"
ExpiresByType font/opentype "access plus 1 month"
ExpiresByType image/svg+xml "access plus 1 month"
</IfModule>
# End Leverage Browser Caching
# TYPES FIX
AddType text/css .css
AddType text/javascript .js
# Enable GZIP Compression
SetOutputFilter DEFLATE
AddOutputFilterByType DEFLATE text/html text/css text/plain text/xml text/javascript application/x-javascript application/x-httpd-php
BrowserMatch ^Mozilla/4 gzip-only-text/html
BrowserMatch ^Mozilla/4\.0[678] no-gzip
BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
BrowserMatch \bMSI[E] !no-gzip !gzip-only-text/html
SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip
Header append Vary User-Agent env=!dont-vary
# End GZIP Compression
# DISABLE DIRECTORY BROWSING
Options All -Indexes
# PROTECT HTACCESS
<files ~ "^.*\.([Hh][Tt][Aa])">
order allow,deny
deny from all
satisfy all
</files>
# DISABLE SITEMAP INDEXING BY GOOGLE AND OTHERS
<IfModule mod_rewrite.c>
<Files ~ "^(post-sitemap.xml|category-sitemap.xml|sitemap_index.xml)\.xml$">
Header set X-Robots-Tag "noindex"
</Files>
</IfModule>
# FORBID COMMENT SPAMMERS ACCESS TO YOUR wp-comments-post.php FILE
# This is a better approach to blocking Comment Spammers so that you do not
# accidentally block good traffic to your website. You can add additional
# Comment Spammer IP addresses on a case by case basis below.
# Searchable Database of known Comment Spammers http://www.stopforumspam.com/
# BLACKLISTED USER AGENTS
SetEnvIfNoCase User-Agent "Acunetix" keep_out
SetEnvIfNoCase User-Agent "FHscan" keep_out
SetEnvIfNoCase User-Agent "Baiduspider" keep_out
SetEnvIfNoCase User-Agent "Yandex" keep_out
<Limit GET POST PUT>
order allow,deny
allow from all
deny from env=keep_out
</Limit>
# END BLACKLISTED USER AGENTS
Ummmmm….
why would you deny access to your sitemap ?
Purpose of the sitemap is so search engines can read it to index your site. Unless you allow it, then it serves no purpose.
If all your pages are https as default, if properly set as site level and your wp-config.php then ALL pages will have proper canonical URL of https://pagename
The 301 redirect tells Google things have moved permanently so you won’t have 2 copies of the same pages being loaded or if they are, only the https is the “canonical” (official) version — that’s the point of that.
You should read the Google guide to moving to https if you have not already as it’s very step by step on what you need to do including updating your listing in webmaster tools (search console).
Thanks Chris. Will remove:
# DISABLE SITEMAP INDEXING BY GOOGLE AND OTHERS
<IfModule mod_rewrite.c>
<Files ~ "^(post-sitemap.xml|category-sitemap.xml|sitemap_index.xml)\.xml$">
Header set X-Robots-Tag "noindex"
</Files>
</IfModule>
I was under the impression that this would keep the sitemap from being indexed in the engine, yet still be followed.
One last question that wasn’t answered. Will that affect my indexed pages in Google? They are 200+ indexed pages in there as www. ?
Cheers Chris!
yoast has already generated my sitemap (post-sitemap.xml) with all my posts being https in it. So I’m nervous what will happen with my indexed pages in google already as http and not https.
Hi,
You could use a 301 redirect to fix the old http urls, look for a plugin or guides like this on the web – http://designmodo.com/wordpress-https/
Thank you!
Right — as I noted you need to do a sitewide 301 redirect in your htaccess file — this tells Google the “NEW” location of an existing page has moved/changed
http://site/page >> new canonical = https://site/page
Google sees that *and* your sitemap you should be submitting from your webmaster tools account (!!), and “knows” what the new page is.
Again — you need to tell Google your site has changed from http to https in your webmaster tools account — see their HOW to.
You need to create new site in your account with https, submit your https sitemap, and then make sure the http site fully redirects to https — this tells Google to use the https version in your account vs the http version.
Ok, I’m all moved over from http to https. Hired a great developer off elance who delivered fast and perfect. anyone needs his name just hollar.
All looks good. yoast site maps, google analytics, updated google webmaster tools..etc. Hope I got it all.
https://p a r a d i s e f o u n d t o u r s (dot) c o m
