Website Redesign SEO Checklist

A same-URL website redesign SEO checklist — what to preserve (titles, H1s, internal links, schema, alt text), how to crawl-diff staging vs. live, and how to plan a rollback.

First published: Jul 2, 2026 · Last updated: Jul 25, 2026 · Advanced
demand #3 in Site Migrations#193 in Technical SEO#267 on the site
AIAuthored byAI v2

A website redesign in this checklist's sense keeps the same domain and the same URLs — only the templates, visual design, CMS theme, and on-page presentation change. That makes it feel safer than a migration, but John Mueller has said you'll potentially see more fluctuation from a redesign than from a straight domain move, because new templates silently rewrite the on-page elements that were earning your rankings. So the checklist is: benchmark the current site with a full crawl, identify the pages you must not touch carelessly (Top pages + Best by links), preserve titles, meta descriptions, H1s, internal links and anchor text, schema, canonical tags, and alt text through the template swap, crawl-diff staging vs. live before launch (and confirm schema/titles render server-side, not client-side only), keep the new theme's hero images and web fonts from wrecking Core Web Vitals, and have a rollback threshold and a backup ready before launch — not improvised after. If any URLs, the domain, or the platform's data structure also change, that's a migration, not a redesign.

TL;DR — A redesign in scope here is a same-domain, same-URL change to templates, visual design, CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. theme, or on-page presentation — nothing else. If URLs, the domain, or the platform’s data structure change too, it’s a migration; use the website migration checklist instead (tripwire: did any URL change?). Redesigns feel lower-risk than migrations, but Mueller has said the opposite can be true — you’ll potentially see more fluctuation from a redesign than from a straight domain move, because templates silently control your titles, H1sAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about., internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them., schema, and alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search.. The checklist: (1) benchmark with a full pre-redesign crawl and flag your Top pages + Best by links; (2) preserve titles, meta descriptionsThe meta description is an HTML head tag — `<meta name=\"description\" content=\"…\">` — that suggests a short summary of the page for the search snippet. It's not a Google ranking factor, and Google rewrites it the majority of the time, but a good one can still lift click-through., H1s/heading hierarchy, internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them. + anchor textAnchor text is the visible, clickable text of a hyperlink. It tells readers what they'll find on the other end and gives search engines context about the linked page., schema, canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content., and alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search.; (3) hold content parity — don’t let a “streamlined” redesign cut ranking content; (4) protect Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. from heavier hero images, web fonts, and animations (never lazy-load the LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good. image); (5) crawl-diff staging vs. live and confirm schema/titles render server-side, not client-side only; (6) launch with staging blocks removed, sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. resubmitted, IndexNowIndexNow is an open push protocol that lets you instantly tell participating search engines (Bing, Yandex, Naver, Seznam, and Yep) which URLs you've added, changed, or removed via a simple HTTP request — and one submission is shared across all of them. Google does not use it. pinged; (7) monitor with a pre-defined rollback threshold and a backup ready before launch.

Evidence for this claim Google can use title elements, prominent visual titles, and headings to generate title links. Scope: Preserving meaningful titles and headings during template changes. Confidence: high · Verified: Google Search Central: Title links Evidence for this claim Google recommends monitoring Core Web Vitals and improving page experience without treating any single signal as a complete ranking guarantee. Scope: Google page-experience guidance. Confidence: high · Verified: Google Search Central: Page experience

Redesign vs. migration — the scope line, drawn hard

This checklist covers exactly one thing: a redesign that keeps the same domain and the same URLs, and changes only the templates, visual design, CMS/theme, and on-page presentation. That’s it.

If the project also changes URLs, the domain, or the platform’s underlying data structure — even alongside the visual refresh — it stops being a same-URL redesign and becomes a migrationA site migration is any significant change to a website's URL structure, domain, platform, protocol, or hosting that can affect how search engines crawl, index, and rank it. The risk scales with how much you change at once., which needs a 301-redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. map and the website migration checklist’s whole apparatus. The tripwire is one question: did any URL change? If the answer is yes for even a handful of pages, treat those as a migration.

This distinction is a real advantage, because most redesign guides blur it — they’ll warn that “CMS migrations can break URL structuresURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly.” in the middle of a “redesign” guide, which just confuses which checklist you actually need. Ahrefs’ own risk list even names “Broken redirects: redirects leading to non-existing or inaccessible pages” as a redesign risk — which is really a sign the redesign quietly became a migration. Catch that early and route it to the right process.

Why “just a redesign” is riskier than it sounds

The instinct is that a redesign is the safe cousin of a migration: the URLs don’t move, so what could go wrong? John Mueller’s answer is the load-bearing point of this whole article:

“You’ll potentially see more fluctuations from the redesign / revamp than from the domain name change. Moving things 1:1 from one domain to another is – for the most part – a non-issue.”

A 1:1 domain move is mechanical and reversible: same content, same structure, new address, redirects carry it. A redesign is not mechanical — it rewrites the actual pages. As Mueller put it, “Moving between CMSs, rebuilding a site, restructuring it: changing URLs, significantly changing the design, changing the internal linkingLinks between pages on the same site., all of those things can significantly impact a site’s performance in search (and it can go up too, it’s not always down — you can do things to improve SEO after all).” The design and internal-linking changes are exactly what a redesign touches — and exactly what a domain move leaves alone.

Phase 1 — Pre-redesign benchmarking

You cannot verify preservation without a “before” to compare against. Build it first.

  • Full crawl of the current live site. Export titles, meta descriptionsThe meta description is an HTML head tag — `<meta name=\"description\" content=\"…\">` — that suggests a short summary of the page for the search snippet. It's not a Google ranking factor, and Google rewrites it the majority of the time, but a good one can still lift click-through., H1s and the full heading structure, canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content., hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others., structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding., internal links and their anchor textAnchor text is the visible, clickable text of a hyperlink. It tells readers what they'll find on the other end and gives search engines context about the linked page., status codes, and indexability directives. This export is the baseline for the staging-vs-live diff later — it is the single most useful artifact in the whole project.
  • Identify the pages you must not touch carelessly. Don’t rely on memory. Ahrefs’ own redesign guidance names the exact technique: “use two reports in Ahrefs’ Site Explorer: Top pages and Best by links.” Top pages sorts by organic trafficVisitors from unpaid search results — it compounds without ad spend.; Best by links sorts by external and internal links, which catches pages that don’t yet rank top-100 but carry real link equity a redesign shouldn’t quietly delete. Flag every one of these as protected.
  • Snapshot the reference set. Keep the exported titles, metas, H1s, schema, and canonicals somewhere the redesign team can check their work against — not just in your head.

Phase 2 — What must be preserved (the core checklist)

Each of these has a verification method, not just a “remember to keep it.” Templates control all of them, so a template swap is where they die.

  • Exact URLs. The tripwire again: if any URL changed, that page is a migration. In a true redesign every URL stays byte-for-byte identical.
  • Title tagsThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim.. Verify old vs. new via the crawl diff, not by eyeballing a few pages. A new template can prepend or append brand strings, truncate, or auto-generate titles differently across thousands of pages at once.
  • Meta descriptions. Same — diff them. New templates frequently drop custom meta descriptions and fall back to an auto-generated excerpt.
  • H1s and heading hierarchy. Watch for a new page builder that defaults the H1 to the raw page title instead of your curated H1, or demotes your old H1 to an H2. Diff the heading structure, don’t assume it survived.
  • Internal link structure and anchor text. This is the most commonly broken element, because nav, breadcrumbsBreadcrumbs are a secondary navigation trail (Home > Category > Page) that shows where a page sits in a site's hierarchy. They create internal links that pass PageRank, and when marked up with BreadcrumbList structured data they can drive the path Google shows in desktop search results., footers, and related-content modules are entirely template-driven — and templates are what you’re replacing. A redesigned nav can drop the deep links that were passing authority to your best pages. Preserve descriptive anchor text too; Search Engine Land’s guide stresses “descriptive anchor text that tells both users and crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. what they’ll find when they click.”
  • Structured data / schema. Two checks, not one: that the schema still exists after the template swap, and that it renders server-side (see Phase 5’s JS trap). A timely accuracy note: don’t build the redesign’s schema plan around FAQPage rich results — Google retired that feature, and “This feature will no longer appear in Google Search starting May 7, 2026.” A template redesign is exactly the kind of event (alongside CMS updates and schema-plugin swaps) that warrants a full structured-data re-audit, since any one of them can silently break markup across hundreds of pages.
  • Canonical tags. Confirm self-referencing canonicals survived the swap. A new template that hard-codes a canonical, or points every page at the homepage, is a classic redesign regression.
  • Image alt text. Redesigns routinely re-crop, re-format, and re-host images through a new CDN or media library — and lose the alt attributes in the process. Google’s guidance is worth keeping in view here: “The most important attribute when it comes to providing more metadata for an image is the alt text (text that describes an image), which also improves accessibility for people who can’t see images on web pages, including users who use screen readers or have low-bandwidth connections.” Preserve the alt text you already had; don’t let a rushed “SEO-ify the new copy” pass stuff keywords into it — “Avoid filling alt attributes with keywords (also known as keyword stuffing) as it results in a negative user experience and may cause your site to be seen as spam.”

Phase 3 — Content parity

A redesign is a magnet for “let’s clean this up” — and that’s where rankings quietly bleed out. Ahrefs is direct: “Redesigns often include some kind of content pruning or simply arbitrary deleting of older content” — but “it’s crucial that you keep the pages that are already ranking high.”

The subtle version isn’t deleting whole pages — it’s a copywriting refresh that reworks titles, H1s, and body copy. “changing keywords can alter the page’s relevance for corresponding queries.” A product page ranking for “kick scooter for kids” can lose that ranking if a copy refresh edits that exact phrase out of the title, H1, or body — even though the URL and everything structural stayed the same. Use your Phase 1 Top pages / Best by links list as the “do not rewrite carelessly” list.

The rule of thumb from the same source: “expanding or reducing content should be done with the intent to serve user needs better, provide more value, or clarify existing information” — not just to look cleaner or more modern. And the same care applies to links: “changing/cutting a few internal links shouldn’t do any harm, but you need to be tactical about it.”

Phase 4 — Core Web Vitals impact of the new design

New themes routinely introduce heavier assets. Ahrefs’ guidance: “don’t overuse heavy graphics, animations, and video. Again, make sure to pre-test the staging site for CWV,” and “Testing your site for Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. (CWV) and mobile friendliness before it goes live is the best way to ensure that your new site will comply with Google’s page experience guidelines.” The three redesign-specific offenders:

  • Hero images (LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good.). A big new hero is usually the Largest Contentful Paint element. Serve it in a modern format, compress it, and hint its priority with fetchpriority="high". Above all, never lazy-load it. New themes and page builders love to apply blanket loading="lazy" to every image — including the hero — and Google is blunt about the cost: “Never lazy-load your LCP image, as that will always lead to unnecessary resource load delay.”
  • Web fonts. A rebrand’s new typography often adds render-blocking font loads. Preload the critical fonts and set font-display so text stays visible during load — per web.dev, “If you set a font-display value of anything other than auto or block, then text will always be visible during load.”
  • Animations and heavy JS. Scroll effects, sliders, and animation libraries add main-thread work that hurts responsiveness. Test the staging build for CWV before launch — see the web performance cluster for the metrics and fixes.

Phase 5 — Staging audit: crawl staging vs. live and diff

This is the single most mechanically useful phase. A visual QA pass will not catch a stripped meta description, a broken canonical, or schema that only renders after JavaScript runs. A structured crawl diff will.

  • Crawl the staging site and diff it against the Phase 1 baseline. Compare, field by field: titles, meta descriptions, H1s and heading structure, canonical tags, hreflang, structured data, internal link counts and anchor text, status codes, and indexability directives (meta robots and robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere.). Every unexpected difference is a bug to fix before launch.
  • The JS-renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. trap. Redesigns built on a new frontend framework (React, Vue, Next.js and friends) commonly render titles and schema client-side only. Search Engine Land names this exact failure: “Ensure schema and meta tagsMeta tags are HTML elements in a page's head that pass metadata about the page to search engines and browsers. For SEO only a few matter — the title element, the meta description, and the robots meta tag — while meta keywords and most others are ignored. render server-side, not just client-side. If Google’s crawler sees empty title tags because JavaScript hasn’t loaded yet, you’re in trouble.” Verify with the URL Inspection toolA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version.’s rendered HTML or the Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test — not just view-source — so you’re seeing what the crawler actually gets.
  • Keep staging out of the index — with noindex, not a robots.txt block. Google’s site move without URL changes guidance applies to a redesign staging site: “Allow for public testing with a temporary hostname for your new infrastructure” and, to keep it out of the index, “add the noindex robots rule to the HTML or the HTTP headers of your pages.” That doc does not recommend a robots.txt disallow for this — and for good reason: Google’s own indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. guidance warns that “for the noindex rule to be effective, the page or resource must not be blocked by a robots.txt file… If the page is blocked by a robots.txt file… the crawler will never see the noindex rule, and the page can still appear in search results, for example if other pages link to it.” Combining noindex and a robots.txt disallow on the same staging site is the trap, not the safeguard — it silently disables the noindex you think is protecting you. Use noindex alone to keep staging out of the index; if you also want to stop it from being crawled or found at all, put it behind HTTP authentication or an IP allowlist instead of robots.txt. Remove the noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed. (and any HTTP auth) at launch — a staging block left live is one of the most common causes of a post-launch traffic collapse.
TIP Crawl the redesigned staging output before launch

A redesign can preserve every URL while dropping search-visible template output. This raw-HTML crawl is a baseline; rendered behavior, analytics, and Search Console need separate parity checks.

Run a scoped staging crawl with my free Scout Site Audit Free Free

  1. Crawl equivalent staging and live sections with the same page cap and exclusions.
  2. Compare titles, canonicals, headings, links, image metadata, and indexability by template.
  3. Fix parity losses, rerun the crawl, and complete rendered and performance checks before launch.
The scope and blind spots matter as much as the score when this becomes a launch gate.

The sample report has an 82 out of 100 raw-HTML score, crawled 24 of 31 discovered URLs, labels the crawl partial, reports two missing-title warnings, and states that rendered JavaScript and AI checks were not evaluated.

Phase 6 — Launch day

  • Remove every staging block. Double-check no noindex, no robots.txt Disallow: /, no HTTP auth left on the production site.
  • Resubmit your sitemap in Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. so recrawling of the changed templates starts promptly.
  • Bing: submit changed URLs via IndexNow. Bing’s own IndexNow FAQ is narrower than some redesign guides suggest — it says to publish only URLs that actually changed, not a blanket historical resubmission. A same-URL redesign does change the on-page content of essentially every URL (new titles, headings, markup), so submitting your full URL list is a defensible read of that rule, not a documented Bing “redesign trigger” — treat it as reasonable practice, not a cited exception. Spot-check with Bing’s URL Inspection tool that Bing sees the new content, and Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility.’ recommendations/SEO reports as a lightweight Bing-side technical check.
  • If the redesign also brought new hosting or a CDN: lower DNS TTL ahead of the switch, and check firewall / DoS protection isn’t blocking crawlers — Google’s caution transfers directly: “Check your firewall configuration or denial of service (DoS) protection. Make sure it does not block GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer.’s ability to reach the DNS or the hosting provider’s servers.” Expect a temporary crawl-rate dip right after launch.
  • Bing’s own migration guidance on log monitoring generalizes to any large content change: “Log files are critical…and must be monitored on a daily basis once the actual website migration has been initiated for a period of at least three months.”

Phase 7 — Post-launch monitoring and rollback

Don’t improvise this during a panic. Decide the plan before you launch.

  • Crawl-diff the live site against the Phase 1 baseline immediately after launch — the same comparison as staging, now against what actually shipped. When a page drops, this diff tells you which on-page element regressed instead of leaving you guessing.
  • Watch GSC — Page Indexing (Coverage) for new exclusions, and Performance filtered to your Phase 1 top pages, which are the ones a regression will hurt most and fastest.
  • Define a rollback threshold in advance. Competitors say “do some SEO debugging,” which is useless mid-crisis. Instead: pick a specific drop (traffic or rankings on the protected pages) sustained over a specific window that flips you from “wait and diagnose” to “revert now.” A clear, sustained drop isolated by the crawl diff to a specific broken element is a rollback trigger; day-one noise is not.
  • Keep a full backup and a rollback path ready before launch, not after. Ahrefs’ framing: “A backup ensures you can restore the original site if anything goes wrong.” A hosting-level snapshot or a plugin like UpdraftPlus for WordPress does the job — the point is that the safety net exists before you need it.

For the broader migration-type taxonomy (domain moves, HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.', replatforms, and the rest), the Site MigrationsA site migration is any significant change to a website's URL structure, domain, platform, protocol, or hosting that can affect how search engines crawl, index, and rank it. The risk scales with how much you change at once. hub is the companion to this checklist — and if any URLs are changing, its website migration checklist is the one you actually want.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.