302 redirect used, submit old sitemap?

[Theo-NL]

The website of a partner of mine was recently migrated to a new platform. Even though the content on the pages mostly stayed the same, both the HTML source (divs, meta data, headers, etc.) and URLs (removed index.php, removed capitalization, etc) changed heavily. Unfortunately, the URLs of ALL forum posts (150K+) were redirected using a 302 redirect, which was only recently discovered and swiftly changed to a 301 after the discovery. Several other important content pages (150+) weren't redirected at all at first, but most now have a 301 redirect as well. The 302 redirects and 404 content pages had been live for over 2 weeks at that point, and judging by the consistent day/day drop in organic traffic, I'm guessing Google didn't like the way this migration went.

My best guess would be that Google is currently treating all these content pages as 'new' (after all, the source code changed 50%+, most of the meta data changed, the URL changed, and a 302 redirect was used). On top of that, the large number of 404's they've encountered (40K+) probably also fueled their belief of a now non-worthy-of-traffic website.

Given that some of these pages had been online for almost a decade, I would love Google to see that these pages are actually new versions of the old page, and therefore pass on any link juice & authority. I had the idea of submitting a sitemap containing the most important URLs of the old website (as harvested from the Top Visited Pages from Google Analytics, because no old sitemap was ever generated...), thereby re-pointing Google to all these old pages, but presenting them with a nice 301 redirect this time instead, hopefully causing them to regain their rankings. To your best knowledge, would that help the problems I've outlined above? Could it hurt?

Any other tips are welcome as well.

[GeoffKenyon]

Hi There,

As the other people have said here, 2 weeks isn't very long for Google to sort this out, though I know it feels like a really long time. While Google and Bing say they will treat 302's as 301's if they think it's a mistake, but I haven't really seen this happen.

Whenever I do a URL migration, I always submit a sitemap with the old URLs to help Google pick up the 301's faster. In your situation, I'd definitely submit an xml sitemap of as many old URLs as you can find to help Google pick up the updated redirects ASAP. Do you have any old files that you could pull URLs from (I know you don't have an old xml sitemap, but maybe a csv or something like that)?

Good luck!

[Kurt_Steinbrueck]

You're right that the search engines are treating the new pages like...well...new pages.  It has nothing to do with how much code has changed and everything to do with the fact that they simply have new URLs.

I agree with Alan.  Two weeks isn't a terribly long time.  Obviously, it's best to have all your ducks in a row from the start, but I think there's good chance that just from setting up the proper redirects for the pages the site should now transfer, though it may take few weeks and you may not get completely back to where you were.

As far as submitting the sitemap for all the old pages, I'm not sure what that would do.  It's possible it may do exactly what you want, basically tell Google about all the redirects, but then again, Google may think it's a bit odd putting up a sitemap to redirected pages.

[AlanMosley]

My guess is the large number of 404's was wasting your link juice(100%), also you will lose something from all the 301's (approx 15%),

as for the source code changing I would not worry about change itself. as long as the code has no problems. It a change in content that is the concern.

some other points,

2 weeks is not a long time for things to sort themselves out with this many pages.

You don't need to 301 redirect all the pages, just the ones that had external links.

Also just for interest, Bing treats a 302(temp) that has been in place for a long time as a 301, likewise a 301(permanent) that keeps changing is treated as a 302. Maybe google does the same, I don't know.

I would fix all the 404s and wait