Indexing HTTPS pages by default

Hello!

My original domain is http://SpokanePlanner.com

My hosting service is SiteGround.

In early August I installed Let’s Encrypt’s SSL service courtesy of their partnership with SiteGround. My organic visitation has held steady and even increased a few ticks since moving to SSL. However, Google Search Console is no longer indexing my pages, which worries me. My basic question is how do I get Google (and other search engines) to index the https pages over http?

Thank you in advance for any advice or direction you might have for me!

Mike

3 Likes

I’m not quite sure about indexing the https pages over http, but I can say the following will really help:

  • :white_check_mark: Make certain you’re forwarding http to https for ALL of your indexed content
  • :white_check_mark: Make certain that you are not serving any “mixed content” on ANY of your pages (i.e. no content from http sources) (https://www.missingpadlock.com)
  • :question:Add a rel="canonical" tag to every unique page to indicate its proper address and ensure your are only serving from that address in terms of using https protocol and the correct (sub)domain (https://moz.com/learn/seo/canonicalization)
  • :white_check_mark: Add a sitemap.xml file to the root of your site containing the canonical addresses of the primary pages you want indexed (https://www.sitemaps.org)
  • :ballot_box_with_check: Add a robots.txt file to the root of your site containing at least a sitemap line (e.g. Sitemap: https://spokaneplanner.com/sitemap.xml) (https://www.robotstxt.org)

https://spokaneplanner.com/sitemap.xml -> https://spokaneplanner.com/sitemap_index.xml :

XML Sitemap

Generated by YoastSEO, this is an XML Sitemap, meant for consumption by search engines.

You can find more information about XML sitemaps on sitemaps.org.

This XML Sitemap Index file contains 5 sitemaps.

SitemapLast Modifiedhttp://spokaneplanner.com/post-sitemap.xml2020-09-04 16:31 +00:00http://spokaneplanner.com/page-sitemap.xml2020-07-03 16:16 +00:00http://spokaneplanner.com/category-sitemap.xml2020-09-04 16:31 +00:00http://spokaneplanner.com/post_tag-sitemap.xml2020-09-04 16:31 +00:00http://spokaneplanner.com/post_format-sitemap.xml2019-01-21 05:27 +00:00


https://spokaneplanner.com/robots.txt :

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

edit: @JuergenAuer appears to have confirmed the first two items for you. His tool can give you a tremendous amount of insight into your website. I’ve confirmed the fourth item for you.

3 Likes

Hi @SpokanePlanner

checking your domain you have already redirects http -> https - see https://check-your-website.server-daten.de/?q=spokaneplanner.com#url-checks

That

may be expected. You have to add the https url to the Google search console. The old http version is removed and not longer indexed.

So that’s not a problem, it’s a feature of the Google Search console. http goes down, the new added https goes up.

Add the https version.

PS: Now the check is ready, you have a very good Grade B: Correct redirects, one destination (non www is preferred), no mixed content, no Chrome warnings. So it’s only a problem of the Google Search console. Check the result, some minor things (Cookies) you may fix.

PS: OT:

Writing things that are already implemented doesn’t help.

4 Likes

I didn’t check if they were all fully implemented. Doing so could take considerable time for me. Did you spider the entire content that quickly? :astonished:

3 Likes

@JuergenAuer

Somewhat off-topic:

First off, thanks for making such a powerful tool.

I understand I’m currently missing some icon and font files. New website turnup and haven’t finalized icon design or font selection yet.

I also understand I’m missing the HSTS header, which I want to add and brings me to my concern.

This could just be my own lack of understanding, but I believe your tool may be indicating that I should use multiple 301 redirects instead of a single 301 redirect.

  • I have a single 301 redirect:
    http://www.openacme.org/ -> https://openacme.org/

  • I am getting this message from your tool:
    Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That’s fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like “RewriteEngine on” + “RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]” (two rows, without the "). Don’t add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.

2 Likes

Gentlemen,

Thank you so much for the feedback. It is much appreciated! I love simple solutions. Thanks again. I’m heading over to Search Console to fidget with it now.

Mike

4 Likes

Don’t forget to submit the link to your sitemap in Google Search Console! For whatever reason it doesn’t seem to automatically detect it.

https://spokaneplanner.com/sitemap_index.xml

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.