Website redesign SEO launch checklist

A working system for preserving useful URLs, proving the new site is ready, and watching the right signals after release.

A web designer and young client reviewing a website redesign together at a laptop.

Use this before a redesign replaces URLs, templates, navigation, tracking or hosting.

Direct answer

A safe redesign launch is a controlled site change: inventory the old site, decide an outcome for each meaningful URL, test direct redirects and indexability on the release candidate, then monitor errors and search signals after launch. A design approval alone cannot verify those conditions.

Methodology, checked 6 November 2026: reviewed current Google Search Central, Google Search Console and web.dev documentation; the current source and preview; and current search-result content for this topic. Existing results commonly offer a checklist or map. This system adds a decision record, evidence limits, a day-30 timeline, failure triage and a copyable worksheet. No original client outcomes, rankings, backlink data or case studies were available.

Planning a redesign? Start with the launch system. Explore the launch system.

What does an SEO launch system do?

An SEO launch system gives founders, developers and agencies one release record. It separates URL decisions from tests of the replacement site, then separates those tests from post-launch observation. That makes ownership, evidence and next actions clear when a redesign changes search behaviour.

  1. Preserve: record old URLs, purpose and evidence.
  2. Decide: assign each meaningful URL one action.
  3. Prove: test the release against acceptance checks.
  4. Observe: monitor the released site and prioritise evidence.

Google recommends planning a move, using permanent server-side redirects for permanent changes, avoiding chains and monitoring after release. [1] [2]

How do you decide where each old page should go?

Start with what visitors came to do. Keep a page that still serves them, send it to a close replacement when one exists, combine pages only when the new page answers the same need, and retire pages with no useful destination. Record the reason for each choice before building redirects.

Choose the right next step for each old page
What changed?Your decisionWhat visitors should experienceRecord before launch
A close replacement existsSend visitors directly to itThe new page answers the same needOld address, new address and final response
Several pages now become oneCombine only if the new page serves the same needsEach useful old page leads straight to the combined pageWhy the new page is a suitable match
The page and address stayKeep itThe page still opens and points to itself as the main versionPage response, main address, title and key content
The page is no longer usefulRetire itA clear removed-page response, with no forced homepage detourReason for removal and links that need updating
A campaign has endedChoose a related destination only when it helps visitorsA direct route to genuinely relevant informationCampaign context and destination choice
Two pages repeat the same contentChoose one main pageVisitors and internal links point to that pageWhich page stays and why

Google treats redirects as a strong signal for the preferred page and advises avoiding chains and irrelevant destinations. [1] [2]

Need the launch system implemented? See technical improvements.

What should you check before the new site goes live?

Test the working site you are about to release. Check that important pages still have a home, old links lead to useful new pages, Google can access the public site, and forms and measurement work. Save the page address or test result so the team can see what passed and what still needs attention.

Keep important pages

  • List the pages visitors and customers rely on.
  • Give each useful old page a clear next step.
  • Make sure the new navigation helps people find them.

Make the site public

  • Check public pages open normally.
  • Remove the private preview block when the launch is ready.
  • Allow search engines to reach the pages you want found.

Test old links

  • Send changed addresses directly to their closest new match.
  • Remove detours, loops and irrelevant homepage redirects.
  • Try the important old addresses after launch.

Set the preferred page address

  • Check each page points to its intended main address.
  • Make that address match the sitemap and links on the site.
  • Check duplicate versions resolve consistently.

Check links around the site

  • Update navigation and page links to the final addresses.
  • Remove links to old pages that no longer exist.
  • Make key service and contact pages easy to reach.

Make page details agree

  • Match each page title, description and main heading to its purpose.
  • Make sure structured information matches what visitors see.
  • Check page dates and details before release.

Test enquiries and measurement

  • Send a test enquiry using the approved process.
  • Check the key enquiry or booking event is recorded.
  • Confirm consent choices behave as intended.

Check speed on real devices

  • Try representative pages on a phone and computer.
  • Look for oversized images or content that jumps as it loads.
  • Record whether a result is a lab test or visitor data.

Check the full visitor journey

  • Use the site with a keyboard.
  • Check headings, page landmarks and image descriptions.
  • Make sure forms explain how to fix an error.

Google explains page access, preferred addresses and sitemaps as separate checks. Web.dev describes Core Web Vitals as measures of user experience. A pass helps confirm what was tested; it cannot promise rankings or business results. [3] [4] [5] [6]

What should you check on launch day and afterwards?

The first month gives you time to spot problems and respond carefully. Check key pages and customer journeys as soon as the site goes live, then review errors and search data as it arrives. Compare results with a saved pre-launch baseline, allowing for delays in search and reporting tools.

  1. Two weeks to three days before: finish page decisions, test important old links, review the new site and try enquiry forms.
  2. The day before: confirm who is responsible, how to reach the person managing launch and which pages need an immediate check.
  3. Launch day: open the home page, main services and enquiry journey. Test a sample of old links, the sitemap and search access.
  4. Days 1 to 3: look for broken pages, redirect problems, failed forms and missing measurement.
  5. Days 7 to 14: review which pages search engines can find, any reported errors and changes in key landing pages.
  6. Days 15 to 30: review the trend, resolve open items and record what changed before making further major updates.

Google advises site owners to monitor traffic, indexing and errors after a site move. Its URL Inspection tool reports on an individual page; it cannot confirm the whole site. [1] [7]

What does each redesign check prove, and what does it not prove?

A release check is evidence about one condition at one time. It can show a redirect, tag or event behaved as expected when tested. It cannot prove future rankings, traffic, enquiries, full indexing or AI citations. Writing the limit beside the check stops teams from over-reading a pass.

Evidence limits: use this wording in release notes
CheckWhat it provesWhat it does not prove
Priority redirectTested request reaches recorded final destination.Every historic URL works or search processed it.
Canonical tagPage publishes that canonical signal.Google always selects that URL.
Sitemap entryURL is offered for discovery.URL is crawled, indexed or ranked.
URL InspectionSearch Console shows current information for that URL.Whole-site health or future crawl timing.
Analytics eventTested journey sent an expected event.All visitors convert or measurement is complete everywhere.
Lab performance runPage met recorded synthetic conditions.Every visitor’s field experience.

How do you triage common redesign failures?

Start with the observable symptom and test the narrowest condition first. Do not treat every traffic change as a redirect problem or every missing page as a ranking problem. This decision tree directs first investigation; it does not replace server, Search Console or analytics evidence.

  1. Traffic drop?
    Check measurement first. Then compare affected landing pages, dates, redirects, indexability and release changes with baseline.
  2. 404 on old URL?
    Find its matrix row. Add or fix a direct redirect if close replacement exists; otherwise confirm retirement and remove new internal links.
  3. Wrong canonical?
    Correct it, then align internal links and sitemap with intended clean URL.
  4. Blocked or missing page?
    Check status, robots controls, noindex, authentication and canonical. Inspect individual URL where eligible.
  5. Lost internal links?
    Crawl the release, prioritise links into important pages, then update to final URLs.
  6. Missing conversion tracking?
    Repeat journey with approved consent state; record environment, time and result before changing tags.

What can you use to keep the redesign on track?

Use this simple record to keep page decisions, launch checks and follow-up actions together. Start with the pages that matter most to customers. Add an owner and a result as the team works, so you can see what is ready, what needs attention and who is taking the next step.

Three short records. One calmer launch.

Use the cards below in a project ticket, spreadsheet or launch meeting. Fill them with your site’s real pages and test results.

01

Decide where each old page goes

Start with one row per important old address.

Old page
Address visitors use today
New page
Closest useful destination
Decision
Keep, redirect, combine or retire
Why
What the visitor needs and why this choice fits
Owner
Person responsible for checking it
Example

/services/old-name → /services/new-name
Decision: Redirect
Why: The new page offers the same service.

02

Know what is ready to launch

For each check, write down the page or journey you tested.

Check
Old link, page address, form or key journey
Expected
What should happen
Result
What happened when tested
Evidence
Link, screenshot or dated note
Status
Ready, needs work or not checked
Example

Check: Main service enquiry
Expected: Form sends successfully
Result: Received test confirmation
Status: Ready

03

Keep an eye on the first month

Record changes and give every follow-up a clear owner.

Date
When you checked
What changed?
The issue or result you noticed
Pages affected
Addresses to review
Next step
The action agreed
Owner and due date
Who will follow up and when
Example

Date: Day 2
What changed? A priority old link returns an error
Next step: Check its redirect
Owner: Project lead · Due: Today

These examples show how to fill in the record. Replace them with your own URLs, test evidence and launch owners.

What do launch teams ask about redirects and rankings?

These are the follow-up questions that come up once the redirect map is written. The answers below cover how long to keep redirects, whether rankings can move after launch, when the Change of Address tool applies and when a temporary redirect is the wrong choice. Each answer comes from Google Search Central guidance.

How long should I keep redirects in place?

Google's guidance is to keep redirects for as long as possible, generally at least one year. It also suggests that, from users' perspective, redirects could be kept indefinitely. Both points apply to the old addresses listed in your redirect matrix.

Will search rankings dip after a redesign?

Google says that with any significant change to a site, you may see ranking fluctuations while it recrawls and reindexes the site. It also says rankings will settle down over time. The guidance does not give a timeframe for either point.

Do I need the Change of Address tool for my redesign?

Only if the move is from one domain or subdomain to another. Google says you do not need it for HTTP to HTTPS moves, for switching between www and non-www on the same domain, or for moving paths within the same domain.

Should I use a temporary redirect while the new design settles?

Only if the change is temporary. Google recommends a permanent server-side redirect for a permanent URL change whenever possible, and says the 301 and 308 status codes mean a page has permanently moved. Use a temporary redirect only to send users to a different page temporarily.

Primary sources

  1. Site moves and migrations with URL changes, Google Search Central. Checked 6 November 2026.
  2. Redirects and Google Search, Google Search Central. Checked 6 November 2026.
  3. Canonicalization, Google Search Central. Checked 6 November 2026.
  4. Robots meta tag specifications, Google Search Central. Checked 6 November 2026.
  5. Sitemaps overview, Google Search Central. Checked 6 November 2026.
  6. Web Vitals, web.dev. Checked 6 November 2026.
  7. URL Inspection tool, Google Search Console Help. Checked 6 November 2026.
ClaroSi logo
ClaroSi

At ClaroSi, we run evidence-led website and search reviews for Irish startups, solo founders and small businesses. Read about the approach.