The single most common reason a website redesign disappoints is not the design itself. It is what happens to organic search traffic in the three months after launch. Get this wrong and you can quietly lose half a year of marketing investment in a single weekend. We have seen it happen — and we have been called in to fix it twice in 2025.
Here is the checklist we run on every Neurabit redesign. It is unromantic and slightly tedious, which is exactly the point.
Before you touch a single page
Crawl the old site and lock the snapshot
Screaming Frog is the boring tool of choice. We crawl the entire production site, export the full URL inventory with HTTP status, title tag, meta description, H1, indexability flag and canonical URL. That file becomes the source of truth for the rest of the project. Anyone who edits content on the old site after this snapshot date raises a flag.
Pull the last twelve months of search data
From Search Console: which pages drove clicks, on which queries, with what click-through rate. Sort by clicks, descending. The top fifty pages usually account for somewhere between 70% and 90% of organic traffic. These are your protected URLs — the ones that need to land somewhere sensible on the new site even if the URL changes.
Build the redirect map early
Before any design happens, we map each old URL to its new equivalent. Most go to a direct counterpart. A handful go to a section parent. A small number go to a content-rolled-up page. None go to the homepage as a lazy default — that is the single most common mistake we see in inherited builds.
While the new site is being built
Hold structured data parity
If the old site had Organization, LocalBusiness, Product or FAQPage schema in production, the new site has to ship with the same coverage on day one. Lose this and you can lose rich-result eligibility before Google even crawls your new pages.
Preserve internal anchor text
The anchor text on internal links is a quiet ranking signal. We try to maintain it on the new site where the content allows. Where the new content does not naturally support the old anchor text, we let it change — but we document the change.
Plan your noindex carefully
Staging sites should always be password-protected, not noindexed. We have seen production sites accidentally ship with leftover staging robots.txt directives more than once. Production noindex on the wrong page is the easiest way to delete six months of rankings overnight.
The good redesign protects the rankings on Monday morning. The great redesign improves them by Friday.
The week of launch
Test redirects in staging
Run the redirect map through a tool like httpstatus.io against the staging environment. Every old URL should return a 301 to its mapped destination. Every redirect chain should be at most one hop deep. Anything 302 or 307 in the production map gets fixed before launch.
Submit the new sitemap immediately
Sitemap.xml updated and resubmitted in Search Console within an hour of launch. Old sitemap deleted. Property settings checked. Any new properties (mobile, country) added.
Watch the crawl rate
Search Console's Crawl Stats report tells you how Google is reacting. A healthy redesign sees crawl rate spike for two to three weeks as Google works through the new URLs, then settle to roughly the old baseline. If crawl rate craters, something is wrong — usually a server-side issue or an accidental robots.txt block.
The first ninety days after launch
For the first ninety days, organic traffic on individual pages will jitter. Some pages will gain immediately. Others will dip for two to four weeks while Google re-evaluates. Aggregate site-wide organic traffic should be within plus-or-minus 10% of the prior baseline by week six. Anything worse than that is worth a closer look.
We track three numbers on a daily basis for the first month, then weekly through to day ninety: total organic sessions, organic sessions on the top-fifty protected pages, and total impressions in Search Console. If two of those three are trending up, the migration is healthy.
Most websites we redesign actually gain organic traffic in the first ninety days because the new build is faster, more crawlable and better structured. But that is the upside scenario. The point of the checklist above is to make sure the downside scenario does not happen — that a redesign never loses you measurable revenue.
Planning a redesign? We run the full migration audit as part of every Neurabit website project — and as a standalone service for clients working with another agency. Get in touch.
