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! 




From the folks who brought you High Rankings!

- - - - -

Redesign Troubleshooting Help

  • Please log in to reply
1 reply to this topic

#1 CNCARex


    HR 1

  • Members
  • Pip
  • 2 posts
  • Location:Schaumburg, IL

Posted 29 August 2013 - 10:50 AM

We launched a redesign at the end of May and soon after, our website was de-indexed from Google. Here are the changes that I implemented so far to try to fix this issue:
1) 301 redirect chain - We changed all our URLs and implemented 301 redirects. However, these are multiple redirects meaning 1 URL redirects to a second and then a 3rd. I was told that this could confuse Google.
For example: [http:]//site.tld 301s to [http:] www site.tld 301s to [https:] www site.tld
We wrote a rule for each variation of the URL and now there is only a one to one 301 redirect and this was validated.
2) Canonical tags did not match URL - We created the new website in a CMS where the CMS generated non-SEO friendly URLs. We applied 301 redirects to those CMS URLs, but when we enable canonical tags within the CMS, it uses the original CMS URL and not the URL of the page, so the canonical URL didn't match the page. For now, I disabled canonical tags until I can figure out a way to manually insert canonical tag code in the pages without using the CMS canonical tag feature.
After doing these two fixes our website still doesn't seem like it is able to get re-indexed by Google even when I submit the sitemap in Google Webmaster Tools...the sitemap doesn't get indexed?
Questions...there are two more concerns that I am hoping can be answered in this forum:
3) Cache-Control = private : I saw from [a tool] that our cache-control is set to private. Is this affecting us being indexed and should this be set to public?
4) Load Balancer - Our old website was not on a load balancer, but our new website is. When I look in our analytics at servers, I noticed that the site is being picked up on one server and then another server at different times. Is Google seeing the same thing and is the load balancer confusing Google?
I'm not sure what else could be an issue with us not being indexed. Maybe its just a waiting game where after I implemented the 1 & 2 change I just have to wait or does 3 & 4 or other issues also need to be addressed in order to get re-indexed?
I hope someone can help me.

Edited by Jill, 30 August 2013 - 09:16 AM.

#2 chrishirst


    A not so moderate moderator.

  • Moderator
  • 7,718 posts
  • Location:Blackpool UK

Posted 30 August 2013 - 04:56 AM


3) Cache-Control = private : I saw from URIvalet.com that our cache-control is set to private. Is this affecting us being indexed and should this be set to public?

Nope! Cache-control http-equiv meta directives are for caching HTTP proxies and browsers caching NOT search engines. Google caching the URLs is NOT HTTP caching that is intended for actually serving the documents on request to user agents.


Google's document cache is purely there as a 'convenience' to Google's users should the actual URL be inaccessible at the time of the query.

It is only updated when Google's system has determine the document has been substantially changed NOT when or if the "Expire" period is reached

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.