Jump to content

  • Log in with Facebook Log in with Twitter Log In with Google      Sign In   
  • Create Account

Subscribe to HRA Now!

 



Are you a Google Analytics enthusiast?

Share and download Custom Google Analytics Reports, dashboards and advanced segments--for FREE! 

 



 

 www.CustomReportSharing.com 

From the folks who brought you High Rankings!



Photo
- - - - -

I Believe Both Http & Https Versions Of Website Are Appearing In S


  • Please log in to reply
5 replies to this topic

#1 ttw

ttw

    HR 5

  • Active Members
  • PipPipPipPipPip
  • 395 posts
  • Location:San Mateo, California

Posted 05 February 2015 - 09:51 AM

A new client switched to https from http for the entire website and we believe there are a number of issues with the way in which it was done.  

 

1)  When we do a "site: " we see some pages returned showing www.company.com and some results showing https://www.company.com/products/

 

.:   I believe that when Google shows only www.company.com in its results for a URL that it is showing the "http" version.

 

.:  These results tell me that Google  is indexing both non secure and secure pages from the site.  I have not seen a case where Google is showing the same page in both secure and non-secure.  It looks like Google is seeing both URLs and selecting the URL they prefer to show based on their algo.

 

.:  When I look at the source for what I believe is a non-secure page, they have the canonical tag going to the non-secure page.   Conversely when I look at the URL of a secure page, their canonical is going to its secure version.

 

.:  When we run a ScreamingFrog report we see both secure and non-secure pages showing up.  GWMTs page count is way out and only showing about 10% of the sites' pages.

 

 

I believe the best course of action is to change the existing rel canonical tags for the non secured webpages to their corresponding secured https versions.  In addition they should redirect all http traffic to https inside their .htaccess file located in the root directory.

 

Will this solve our problem ?

 

 

 



#2 Jill

Jill

    Recovering SEO

  • Admin
  • 33,244 posts

Posted 05 February 2015 - 09:53 AM

How long ago was the switch made? It takes quite some time for Google to sort stuff out. The answer is likely to do nothing.

#3 ttw

ttw

    HR 5

  • Active Members
  • PipPipPipPipPip
  • 395 posts
  • Location:San Mateo, California

Posted 05 February 2015 - 09:54 AM

Good morning Jill! 

 

They told me they made the change last summer (August).



#4 Jill

Jill

    Recovering SEO

  • Admin
  • 33,244 posts

Posted 05 February 2015 - 10:05 AM

Then yeah, this:

 

I believe the best course of action is to change the existing rel canonical tags for the non secured webpages to their corresponding secured https versions.  In addition they should redirect all http traffic to https inside their .htaccess file located in the root directory.

 

 

...sounds like a good solution to me. (But I've been outta the loop for over a year, so take this with a grain of salt!)



#5 qwerty

qwerty

    HR 10

  • Moderator
  • 8,695 posts
  • Location:Somerville, MA

Posted 06 February 2015 - 07:20 AM

If you have proper 301s in place, the bot will never reach the non-secure pages, so it will never see the rel-canonical tag indicating that the secure page is canonical. If you don't already have the redirects set up, I think that's what you need to do. You should also make sure all of your internal links (if they're using absolute URLs) point to the https version of each page.



#6 ttw

ttw

    HR 5

  • Active Members
  • PipPipPipPipPip
  • 395 posts
  • Location:San Mateo, California

Posted 10 February 2015 - 04:02 PM

Thanks very much Qwerty.  Sounds like the best approach.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

We are now a read-only forum.
 
No new posts or registrations allowed.