Website redesign SEO checklist: how to redesign without losing rankings

To redesign a website without losing rankings, map every old URL to its new URL, use server-side 301 redirects, keep them for at least a year, and benchmark crawl data, rankings and Core Web Vitals before launch so you can compare afterward. Google says to keep redirects "generally at least 1 year".

Most redesign SEO checklists are written from experience alone. This one is built on Google Search Central's own site-move and redirect documentation, quoted where it matters, and split by the one question that changes the risk most: are your URLs changing? Work through it in three phases (before launch, launch day and the 90 days after), then keep the rollback plan ready.

Does a website redesign hurt SEO?

A redesign hurts SEO when it breaks one of the signals Google already relies on. The usual causes are:

• URL changes without redirects. Old URLs return 404 errors, and the links pointing at them stop counting.
• Removed or thinned content. Pages that ranked are merged, cut or replaced with shorter copy.
• Broken internal links. New navigation drops links to important pages, so they get crawled less.
• Rendering problems. Content that only appears after client-side JavaScript runs may be indexed late or incompletely.
• Slower pages. Heavier images, scripts and fonts push Core Web Vitals from good to poor.
• Leftover staging settings. A "noindex" tag or a blocking robots.txt rule copied from staging can de-index a whole site.

None of these is inevitable. Each one has a check below.

What's the difference between a redesign that changes URLs and one that doesn't?

Google publishes two separate guides, and they carry different risks.

If you can keep your URLs, do. A redesign on the same URLs removes the biggest source of risk. If URLs must change, Google advises: "We recommend moving all URLs on your site simultaneously instead of moving one section at a time."

What should you do before launch?

Most migration damage is decided before launch day. Work through this list on staging.

1. Crawl and benchmark the live site. Export every indexable URL, its title, meta description, canonical, status code and word count. Save rankings, organic landing-page traffic and conversions for the last 12 months.
2. Build a content inventory. Mark each page keep, merge, rewrite or remove. Never remove a page that earns traffic or links without a redirect target.
3. Create the URL map. One row per old URL, pointing to the closest new equivalent, not the home page.
4. Write redirect rules. "Use server side permanent redirects," Google says: a 301 or 308. Its redirects guide explains that for permanent redirects "the indexing pipeline uses the redirect as a signal", while for temporary ones it "doesn't use the redirect as a signal". Avoid JavaScript redirects: "Only use JavaScript redirects if you can't do server-side or meta refresh redirects."
5. Remove chains. Point each old URL straight at its final destination. Seomator says redirect chains fail on 24.3% of the sites it audits.
6. Block staging properly. Use password protection or noindex on staging, and write down every setting that must change at launch.
7. Update internal links. Point navigation, footers and in-content links at the new URLs directly, not through redirects.
8. Check canonicals and hreflang. Every canonical should point to a live, indexable new URL. Update hreflang pairs on multilingual sites.
9. Carry over structured data. Rebuild Organization, Product, Article, FAQ and Breadcrumb schema in the new templates and validate it.
10. Set a Core Web Vitals budget. Google's Web Vitals thresholds are LCP "within 2.5 seconds", INP "200 milliseconds or less" and CLS of "0.1", measured at "the 75th percentile of page loads". Test the new templates against them.
11. Check AI crawler access. Decide which AI crawlers your robots.txt allows, and make sure key answers are in plain HTML, not hidden behind scripts or tabs.

Core Web Vitals regressions are common. The HTTP Archive's Web Almanac 2024 found good Core Web Vitals on 43% of mobile sites and 54% of desktop sites, and "59% of mobile pages achieved a good LCP score". A heavier redesign can easily move you into the failing group.

What should you check on launch day?

Launch in a quiet traffic window with developers and an SEO lead available.

• Remove noindex and staging blocks. Check the live robots.txt and the meta robots tag on key templates.
• Test redirects. Run the full old-URL list through a crawler and confirm every row returns one 301 or 308 to a 200 page.
• Submit the sitemap. "Submit the new sitemap in Search Console," Google says. Keep the old sitemap available for a short time so Google finds the redirects.
• Verify Search Console. Make sure the property covers the new URLs or domain, and use the Change of Address tool only if the domain changed. Google is clear: "You only need this tool when moving from one domain or subdomain to another."
• Check analytics and tags. Confirm the analytics tag, conversion events, consent banner and any ad pixels fire on the new templates.
• Spot-check top pages. Inspect your 20 highest-traffic pages for content, titles, canonicals and schema.

If you deploy through a CI/CD pipeline, add the redirect test and a robots check as automated steps. Our DevOps consulting team sets these up so a launch cannot ship with staging settings.

What should you monitor for 90 days after launch?

Compare against the same period last year, not just last month, so seasonality does not hide a real loss.

How long does SEO recovery take after a migration?

Google says it "can take a few weeks or more" for new URLs to appear. Independent data is more sobering, but it measures a harder case. Search Engine Journal's study by Dan Taylor looked at 892 domain migrations and found that "On average, it took 523 days" for organic traffic to recover, and "17% … didn't see organic traffic return to the same levels after 1,000 days."

Those are domain migrations, where every URL and the domain itself change at once. A redesign that keeps the same domain and most URLs usually carries less risk. The lesson still applies: plan as if recovery could be slow, and do not stack other big changes (a new domain, a CMS switch and a content cull) into the same launch unless you must.

What does a rollback plan look like?

A rollback plan is a written decision, made before launch, about when and how you would revert.

1. Keep the old site deployable for at least the first few weeks, with its database and media.
2. Define triggers. For example: key pages de-indexed, a large share of redirects failing, or conversions falling sharply with no seasonal explanation.
3. Decide who calls it. One named owner, with the SEO lead and developer consulted.
4. Prefer a fix to a full revert. Most launch problems (noindex, missing redirects, broken tags) can be fixed in hours. A full rollback is a last resort, because it means changing URLs twice.
5. Log every change so you can tell which fix moved which metric.

What should a redirect map include?

A redirect map is the single most valuable document in a migration. Keep it as a shared spreadsheet with these columns:

Sort by traffic and links, so the most valuable URLs are checked first.

Which tools do you need for a redesign migration?

You do not need an expensive tool stack, but you do need the right data before and after launch.

• Google Search Console: indexing, sitemaps, Core Web Vitals field data and the Change of Address tool for domain moves.
• A site crawler: to export every URL before launch, then crawl the old URL list after launch and confirm each redirect resolves in a single hop.
• Web analytics: organic landing pages, conversions and year-on-year comparisons for your most valuable templates.
• A performance tool: lab tests such as Lighthouse or PageSpeed Insights during development, and field data from real users after launch.
• A backlink tool: to find old URLs with external links, so they get the most careful redirect targets.
• A rank tracker: for a fixed list of priority keywords, tracked from at least a month before launch.

Common redesign SEO mistakes

• Redirecting every old URL to the home page instead of the closest match.
• Launching with the staging noindex tag or robots.txt block still in place.
• Dropping text from category and service pages to make the design cleaner.
• Changing title tags and headings on every page at once, so you cannot tell what caused a drop.
• Removing the old redirect rules a few months after launch.

Each of these is cheap to prevent and slow to recover from.

How can Elgrith protect your rankings during a redesign?

Elgrith has delivered 1,000+ projects for 250+ clients since 2015, from our New Delhi headquarters and client centers in New York, London and Shanghai. Our flagship build is Kenerate AI, an all-in-one AI image and video studio designed and engineered by Elgrith. On a website redesign, we build the URL map and redirect rules before design starts, and our technical SEO team runs the launch-day checks and 90-day monitoring. Budgeting first? Read how much a website redesign costs in 2026. Book a call or start a project.