Proper 301 in Place but Old Site Still Indexed In Google

[kchandler]

So i have stumbled across an interesting issue with a new SEO client. They just recently launched a new website and implemented a proper 301 redirect strategy at the page level for the new website domain. What is interesting is that the new website is now indexed in Google BUT the old website domain is also still indexed in Google? I even checked the Google Cached date and it shows the new website with a cache date of today.

The redirect strategy has been in place for about 30 days. Any thoughts or suggestions on how to get the old domain un-indexed in Google and get all authority passed to the new website?

[DougRoberts]

How big is the site in question? How many pages are there to de-index?

What does Google Webmaster Tools tell you about the old domain? Does it show pages being removed from the index over time?

If you do a site:{old domain} query, can you see that the number of results being returned is gradually decreasing?

How have you implemented the redirects?

Have you submitted a change of address request in Webmaster Tools?

On the new website, have you submitted a sitemap fom the old website as well as the new one?

What does the backlink profile on the old domain look like? Can you start to get authoritative links to the old site updated? What about any embedded internal links in your content - have they also been updated?

More guidance from Google here:

Webmasters Tools Help: Move a site with URL changes

[DonnaDuncan]

It could just be me kchandler, but I've seen it take as long as 8 months for old pages to get purged from Google's index, redirected or not. The redirect and indexing are independent of one another.

[customerparadigm.com]

Kyle -

Sorry this is so puzzling.  The only other thing I could think of is that perhaps the older pages still somehow exist and/or are being served by the server?  For example, the .htaccess file might have the /old-page.php redirecting to the /new-page.php... but somehow the old-page.php is still accessible?  I'd also look at caching, too? For example, our site, www.CustomerParadigm.com uses varnish for caching, so if we make a change to the site, we need to clear out that page or the change won't be reflected publicly.

Hope this helps?

-- Jeff

[kchandler]

Hi Jeff, thank you for the quick response, it is truly appreciated

Unfortunately i am not able to publicly release their URL in forums due to part of our contract. However i can provide some feedback to your ideas.

• Different web servers - the website is the same and on the same hosting platform, they just updated their branding and along with that their domain name
• WWW. vs non-WWW. - I did a quick check and it looks like both versions of the old domain properly 301 redirect no matter what the subdomain. I am checking that both with my Chrome developer tools as well s checkmyheaders.com.
• Robots.txt on old server - as it related to my first bullet, it is technically the same website and server the the robots.txt is the same for the new website just reflecting the new domain.

Are there any other things that i could look at for a sanity check? I have never seen a website not get de-indexed after a 301 redirect. Do you think i would need to submit something to Google Webmaster Tools for the old URLs/domains?

Regards, Kyle

[customerparadigm.com]

Without seeing the new and old sites, my first impression is that this might have been caused by having the older site on a different server; the newer site might be on a newer, different Web server.  If this is the case, and the older server is still online, I'd check your DNS zone files to make sure that the older site isn't somehow still accessible?  I've seen cases where there's two A records for the www. version of a domain; not ideal, but it can cause issues.  I'd also set the robot.txt file on the older server / older site to no-index / no-follow.

Hope this helps?

Thanks,

• Jeff