1. [Home](https://www.void-agency.com/)
2. [Insights](https://www.void-agency.com/insights)
3. Website Redesign SEO Migration Evidence Pack

Website Migration16 min readJuly 17, 2026

# Treat a website redesign as an evidence migration, not a visual launch

An acceptance contract for redesigns that change URLs, templates, tracking, or conversion paths without losing search or lead evidence.

Written by**Sulayman Bowles**Field note 08

Redesign / evidence migration

OLD STATES**/service-a/guide-b/contact**

NEW STATES**Canonical routeMapped evidenceMeasured lead pathMap every valuable old state to a defensible new state**Inventory · redirect · acceptance

Website redesign migration

8

Evidence sections

10

Linked references

In this field note
1. 01Classify the change before choosing the checklist
2. 02Capture a baseline that can answer what changed
3. 03Map every valuable old state to one defensible new state
4. 04Turn requirements into an acceptance contract
5. 05Preserve the chain from landing page to accepted lead
6. 06Launch with fast technical checks and slower outcome checks
7. 07Use predefined thresholds without pretending the future is deterministic
8. 08Run a redesign SEO and enquiry-handoff acceptance test
9. RSource ledger

A redesign can improve a website while still damaging the evidence a business uses to earn and evaluate demand. The risk is not limited to rankings. URL changes can break discovery paths, template changes can remove indexable content, analytics changes can split historical comparisons, and new forms can stop carrying the fields that connect an inquiry to its source. A launch that looks correct in a browser can therefore be commercially worse and diagnostically opaque.

The safer operating model is an evidence migration. Before launch, document what the current site exposes to search engines, what people can accomplish, and what the measurement stack records. Then translate each important state into an acceptance condition for the new site. This article provides that contract for owners, developers, SEO teams, and measurement leads. It does not promise that traffic will remain flat; Google explicitly notes that site moves can cause temporary fluctuations while systems recrawl and reindex. It does make preventable losses visible before they become a post-launch argument.

The search-specific controls below are Google-first because the cited migration guidance comes from Google. They do not replace accessibility, security, privacy, legal, performance, browser-compatibility, content, or general quality assurance. Those disciplines need their own release gates.

Short answer

Protect a redesign by inventorying every valuable URL, search template, conversion path, and measurement field before launch; mapping each old state to a testable destination; and requiring evidence for redirects, canonical signals, rendered content, analytics events, and CRM lead continuity. Separate hosting changes from URL changes, define owners and rollback thresholds in advance, and monitor search, behavior, and accepted leads together. A redesign is ready when the migration evidence passes—not when the new interface merely looks finished.

Section 01

## Classify the change before choosing the checklist

“Redesign” is too broad to be a technical plan. A reskin that keeps URLs, rendered copy, navigation, and tracking intact has a different risk profile from a domain move, a framework replacement, or a rewrite that consolidates service pages. Start by listing what actually changes: domain, protocol, hostname, path, query handling, renderer, information architecture, structured data, analytics property, consent behavior, forms, phone tracking, and CRM handoff. Avoid stacking a domain, URL, CMS, design, analytics-property, and consent-platform change into one launch when they can be sequenced and observed independently.

Migration class determines the evidence required before launch

| Change class | Primary failure mode | Minimum proof |
| --- | --- | --- |
| Visual or component redesign | Important copy, links, metadata, or events disappear inside new templates | Rendered-page comparison plus interaction and event tests |
| Content or information-architecture change | Useful intent, internal paths, and evidence are removed or merged into weak destinations | Old-to-new intent map, editorial review, internal-link graph, and conversion-path acceptance |
| CMS or framework replacement | Server output, routing, status codes, metadata, or rendering semantics change | Raw and rendered template contract, error-route tests, asset access, and deployment parity |
| Hosting or infrastructure move | Crawl failures, DNS errors, blocked assets, or capacity collapse under recrawl | Staged load checks, lowered DNS TTL, old-host access, crawl controls, logs, and production response monitoring |
| URL or domain move | Old demand lands on errors or weak destinations while signals fragment | Complete URL map, server-side redirects, old and new Search Console properties, Change of Address where applicable, and old/new sitemap controls |
| Analytics or form-stack change | Historical comparison breaks or inquiries lose acquisition context | Versioned event-and-lead data contract, parallel validation, lead-record checks, and reconciliation; preserve the existing GA property unless a separate business requirement justifies replacement |

Evidence boundary

Official Google documentation explains how Search processes redirects, canonical signals, recrawling, and site moves. It does not certify a business’s redirect map, CRM setup, or acceptable traffic variance. The acceptance thresholds in this guide are operating decisions, not Google requirements.

Platform behavior and documentation can change. The source guidance here was reviewed on July 18, 2026; recheck current Search and analytics documentation before a live migration.

Section 02

## Capture a baseline that can answer what changed

A baseline is not a screenshot of total sessions. It is a dated, reproducible record at the grain where migration failures occur. Export Search Console performance by page and query for a representative pre-launch window, preserving filters, row limits, anonymized-query gaps, and the fact that visible or exported rows are not a complete census. Record indexed and submitted URLs, crawl the full known URL union, and preserve responses, metadata, directives, schema, internal links, rendered body text, XML sitemaps, and robots. The point is enough bounded evidence to distinguish seasonality from a missing page or broken template.

Measurement needs its own baseline. Document landing-page sessions, form starts and completions, tracked calls, bookings, and accepted leads by the dimensions the business actually uses. Preserve the identifiers and fields that cross systems: client or session identifiers where policy permits, lead ID, event timestamp, landing page, referrer, campaign parameters, consent state, phone pool, form name, location, service, and CRM status. Record known gaps such as offline calls with no digital session or legacy forms that omit a lead ID. Unknown attribution should remain unknown rather than being redistributed into a preferred channel.

### Baseline evidence package

- Dated URL inventory from crawl, sitemap, analytics landing pages, Search Console pages, and server logs where available
- Page-and-query Search Console export with the exact date range and filters preserved
- Rendered HTML evidence for representative home, service, location, article, conversion, and error templates
- Analytics event dictionary with parameters, triggers, destinations, and current observed counts
- Sample lead records showing which acquisition fields survive the form, call, booking, and CRM handoff
- Known anomalies, seasonal factors, active campaigns, and tracking limitations written beside the baseline

Section 03

## Map every valuable old state to one defensible new state

Build the URL map from evidence, not from the new navigation alone. Union the crawl, sitemaps, indexed pages, landing pages, backlinks if available, and URLs that produced impressions, conversions, or accepted leads. For each old URL, assign an intentional outcome: unchanged, redirected to a close replacement, consolidated into a broader resource, or removed with an appropriate not-found or gone response. A blanket redirect to the home page hides planning gaps and creates a poor destination for both users and crawlers.

Google supports direct permanent server-side 301 or 308 redirects as a strong signal that a destination should become canonical, but redirects are only one signal. The destination should also return a successful response, declare a self-consistent canonical when appropriate, remain crawlable, appear in internal links and the new sitemap, and fulfill the old page’s purpose. Redirect chains, loops, mixed protocol targets, and irrelevant destinations weaken the contract even when the final page eventually loads.

### Resolve each old URL in this order

1. Keep the URL when its purpose and canonical identity remain intact.
2. Choose the closest useful destination when a true replacement exists.
3. Create a dedicated replacement when the old page earned material search demand or leads and no current page satisfies it.
4. Return an honest removal response when the content has no replacement and should not remain indexed.
5. Update internal links, canonicals, hreflang if used, structured data, sitemaps, campaigns, and external profiles to reference the final URL directly.

Section 04

## Turn requirements into an acceptance contract

A checklist says that someone looked. An acceptance contract defines the population, denominator, assertion, threshold, evidence location, environment, build identifier, owner, due time, and disposition for every condition. It prevents the common launch-day negotiation in which missing metadata is called minor, broken analytics is deferred, and no one knows whether a redirect sample represents the full map. Each condition should be machine-testable where practical and manually reviewed where meaning matters.

Example redesign acceptance contract

| Control | Population / denominator | Assertion / threshold | Evidence / environment / build | Owner / disposition |
| --- | --- | --- | --- | --- |
| Old-to-new URL outcomes | All known URLs; priority subset named | 100% priority and stated map resolve as approved; zero loops or unintended chains | Release-candidate URL report with timestamp and build ID | Technical lead; block on priority failure |
| Rendered template contract | Every priority template plus declared sample | Required copy, links, canonicals, directives, status, and schema present | Raw/rendered captures from release candidate | SEO and frontend; block critical omissions |
| Analytics and SPA events | Every critical initial load and logical route fixture | Exactly one pageview with final page_location, page_title, and page_referrer; conversions fire once under approved consent | Debugger and network record tied to build | Measurement lead; block duplicates or missing context |
| CRM continuity | Form, call, booking, and vendor test matrix | Each test creates one governed record with required operational fields and a pseudonymous reconciliation key | Sanitized CRM records and handoff logs | Revenue operations; block lost inquiries |
| Production parity | Priority URL and conversion set after launch | No new critical blocks, server errors, canonical conflicts, or orphaned destinations | Production crawl, logs, synthetic tests, release ID | Launch owner; fix, roll forward, or rollback |

Use representative template tests during development, then run full URL-map checks and all critical conversion contracts against the release candidate. Include non-HTML assets that carry search or customer value—images, PDFs, feeds, scripts, styles, and downloads—in the migration inventory. A crawler cannot judge replacement meaning, and a manual reviewer cannot reliably find loops across thousands of rows. Preserve machine and manual evidence with build identifiers.

Section 05

## Preserve the chain from landing page to accepted lead

A redesigned form often changes more than its appearance. Write a versioned event-and-lead data contract for each conversion path: business definition, user action, event name, parameter name and type, allowed values, privacy class, consent dependency, analytics destination, server or vendor handoff, CRM field, pseudonymous reconciliation key, final business status, owner, retention, and validation evidence. Test successful and unsuccessful submissions, duplicate clicks, validation errors, consent states, mobile layouts, call-tracking swaps, cross-domain journeys, and SPA route changes.

Do not use analytics conversions as a substitute for lead records. Analytics can show that an event was observed; the CRM can show whether an inquiry was accepted, qualified, won, duplicated, spam, or unreachable. Reconcile the systems at a documented cadence using lead IDs or another governed key where possible. Expect legitimate differences caused by consent, blocked scripts, cross-device behavior, phone calls, and processing rules. The goal is an explainable bridge, not artificially identical totals.

### Measurement release checks

- Existing campaign and referral parameters survive redirects and do not leak into canonical URLs
- Initial loads and SPA logical routes each produce exactly one pageview with the correct final page_location, page_title, and page_referrer
- Cross-domain journeys preserve approved session continuity without leaking identifiers into URLs
- Critical events fire once, carry the intended page and form context, and respect the approved consent state
- Test inquiries appear in the correct CRM pipeline with a durable lead ID and required acquisition fields
- Call, booking, chat, and embedded-form vendors still use the intended domains, webhooks, and notification recipients
- Dashboards identify the deployment date and do not splice incompatible definitions into one trend without annotation
- Browser console errors, failed network requests, CSP violations, and client-rendering failures are captured in production observability

Privacy and identifier gate

Do not place raw personal information or direct CRM identifiers in URLs, titles, referrers, analytics event parameters, browser storage, or vendor payloads. A CRM lead ID is an operational identifier; a browser-safe pseudonymous analytics key is a different, governed field.

Document purpose, consent or other authority, access, retention, and deletion for each identifier. If the handoff cannot meet that contract, preserve aggregate reconciliation and leave the person-level connection absent.

Section 06

## Launch with fast technical checks and slower outcome checks

Immediately after deployment, verify DNS and certificates if changed, critical responses, robots access, old and new sitemaps, canonical targets, redirects, rendered templates, non-HTML assets, structured data, browser and network errors, analytics collection, and real test leads. For a domain move, verify all relevant old and new Search Console properties—including protocol, www/non-www, and affected subdomains—and submit Change of Address where required. Do not use Change of Address for an HTTPS-only move. Keep direct 301/308 redirects for at least one year and retain the old host, ownership, and logs until old traffic is zero through the approved observation window.

Monitor at several clocks. Minutes and hours are appropriate for server errors, form failures, accidental noindex directives, and redirect defects. Days are more useful for crawl discovery, indexed-page patterns, landing-page behavior, and event reconciliation. Weeks may be needed to interpret page-and-query performance without overreacting to ordinary volatility. Compare like-for-like days and annotate campaigns, holidays, outages, and releases. Report priority URL groups and accepted leads, not only sitewide averages that can conceal a failed service line.

### Escalation sequence

1. Confirm the observation is real across the source system and not a dashboard, filter, consent, or latency artifact.
2. Localize the change by URL group, query group, device, geography, template, event, and deployment.
3. Check the migration contract for failed responses, redirects, canonicals, rendering, internal links, or measurement fields.
4. Fix the narrow defect, record the release, and re-run the same acceptance evidence.
5. Escalate to a wider remediation only when the localized evidence supports it.

Section 07

## Use predefined thresholds without pretending the future is deterministic

A useful launch plan defines hard go/no-go gates before pressure arrives. Failed critical forms, blocked priority pages, unresolved redirect-map defects, an accidental noindex, broken production rendering, or missing acquisition fields stop launch. After deployment, those failures can justify rollback only when a tested rollback exists. Stateful changes—submitted leads, changed DNS, new URLs discovered, cache state, or third-party writes—may require recovery or roll-forward instead of reversal. Search fluctuation alone usually requires diagnosis first.

Set thresholds in the business’s own units and label them as internal controls: for example, zero tolerance for failed critical forms, an agreed maximum number of unmapped priority URLs, and a review trigger for sustained loss in accepted leads from a defined page group. Do not borrow universal percentage promises from case studies. Traffic, query mix, demand, and lead quality differ. The contract should force a response to strong evidence while allowing enough time for normal processing and noise.

Close the migration only when the URL map and critical conversion matrix are resolved, the old-host retirement rule is satisfied, Search Console and sitemap monitoring show no unexplained priority failures, measurement reconciles within its approved coverage bounds, accepted-lead paths pass, and every exception has an owner and disposition. A launch date is not a closeout condition.

Decision rule

Fix confirmed technical defects immediately. Investigate search and lead changes at the smallest useful grain. Roll back only when the expected benefit exceeds the additional migration cost, stateful side effects have a recovery plan, and the rollback path has itself passed redirect, rendering, measurement, and lead-capture tests.

The practical win is not a no-loss guarantee. It is knowing which state changed, which requirement failed, who owns the fix, and whether the business outcome recovered after the fix.

Section 08

## Run a redesign SEO and enquiry-handoff acceptance test

A redesign test needs three kinds of evidence: the old URL reaches the approved destination, the destination retains its required answer and working form, and the same test enquiry appears in the intended downstream systems. A successful redirect and a thank-you page leave the last question open.

This runnable example uses two temporary local HTTP servers and fixed sample data. We checked actual responses and native browser submissions on November 18, 2026 (America/Chicago). One server represents the redesigned site; the other provides separate event and enquiry receipts. These are authored systems, with no GA4, real CRM, email or production connection.

- [Download the runnable launch example and instructions](https://www.void-agency.com/downloads/redesign-launch-acceptance-fixture.zip)
- [Read the launch-test Node source](https://www.void-agency.com/downloads/redesign-launch-acceptance-fixture.mjs)
- [Read the launch-test instructions](https://www.void-agency.com/downloads/redesign-launch-acceptance-README.txt)

With Node.js 22 or later, extract the ZIP and run node redesign-launch-acceptance-fixture.mjs from its folder. It needs no packages, account or target URL. The output keeps acknowledgements and independent receipt reads in separate fields, then closes both servers.

### Actual observations from the owned local launch sample

1. Redirect and canonical: /drain-cleaning.html returns 301 directly to /services/drain-cleaning, which returns 200. The sample campaign and test ID survive the redirect; the canonical omits the query. These checks pass in both modes.
2. Required answer and control: The destination's required answer matches the retained authored baseline. The distinct boiler-repair control stays 200 and self-canonical. This bounded content check passes in both modes.
3. Form and delivery acknowledgement: The form returns 303 to a 200 thank-you page. Both downstream requests receive HTTP 202 acknowledgements in both modes. The interface can therefore look successful before receipts are confirmed.
4. Independent event receipt: The broken receipt reader returns 200 with no matching event. After repair it returns one event matching the test ID, service, campaign and landing path.
5. Independent enquiry receipt: The broken reader returns 503: the enquiry state is unavailable, not zero. After repair it returns 200 with one matching recorded sample enquiry.
6. Repeated submission: Submitting the same test token twice leaves one event and one enquiry record in the repaired in-memory stores during this server run.

Read the acceptance decision

The broken state is blocked for this local sample: the event is absent from an available reader and the enquiry receipt is unavailable. A 503 does not establish that the enquiry was lost. The repaired state passes these stated local checks after matching receipts are observed.

The sample covers one changed route, a required-answer comparison, one unchanged control and one form handoff. Qualification, attribution, revenue and Google indexing require their own later records. The in-memory stores disappear when the servers close.

### Repeat the check in a browser, then on your release candidate

1. Run node redesign-launch-acceptance-fixture.mjs --serve broken. Open the printed local URL, submit the fixed sample enquiry, then follow both independent receipt links from the thank-you page. Forms also work with JavaScript off.
2. Stop that server and repeat with --serve repaired. Compare the matching test key and acquisition fields. Each run stops automatically after two minutes; ports and test IDs can change.
3. For your project, use the approved URL map and required-content contract. Name the deployment, destination analytics property, operational system, test key, expected fields and checking owner before submitting the approved test. Record the actual receipt states in the migration ledger's conversion_test and validation fields; leave unavailable evidence unresolved.
4. Verify the exact event in the intended analytics property and the test enquiry in the destination system, then repeat the critical paths on production. Google's Measurement Protocol validation server checks event structure; validation requests do not populate reports. Its implementation guide separately calls for checking the property with Realtime or DebugView. These two documents were checked November 18; earlier source cutoffs elsewhere in this guide remain.

- [Use the existing 30-point migration checklist and blank URL ledger](https://www.void-agency.com/tools/redesign-migration-checklist)
- [Define the fields and outcomes in the lead-attribution chain](https://www.void-agency.com/insights/local-service-business-lead-attribution)
- [Read Google's event-validation limits](https://developers.google.com/analytics/devguides/collection/protocol/ga4/validating-events)
- [Verify events in the intended GA4 property](https://developers.google.com/analytics/devguides/collection/protocol/ga4/verify-implementation)

Primary and authoritative references

## Source ledger

These sources support the operating guidance above. Platform behavior and documentation can change, so volatile implementation details should be rechecked before a rollout.

1. [Site moves with URL changes](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) — Google Search Central. Official process for URL-changing moves, redirect mapping, testing, and expected processing fluctuations.
2. [Changing your hosting location](https://developers.google.com/search/docs/crawling-indexing/site-move-no-url-changes) — Google Search Central. Official guidance for infrastructure moves that keep public URLs unchanged.
3. [Redirects and Google Search](https://developers.google.com/search/docs/crawling-indexing/301-redirects) — Google Search Central. Official redirect methods and their use as canonicalization signals.
4. [Canonicalization](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) — Google Search Central. Official explanation of canonical signals and consistency across redirects, sitemaps, and links.
5. [Debugging drops in Google Search traffic](https://developers.google.com/search/docs/monitor-debug/debugging-search-traffic-drops) — Google Search Central. Official diagnostic framing for technical, algorithmic, seasonal, and reporting causes.
6. [Ask Google to recrawl your URLs](https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl) — Google Search Central. Official limits and expected timing for recrawl requests and sitemap discovery.
7. [Common tasks in the Performance report](https://support.google.com/webmasters/answer/17010961) — Google Search Console Help. Official guidance for examining Search performance by query, page, device, country, and date.
8. [Lead acquisition report](https://support.google.com/analytics/answer/16376749) — Google Analytics Help. Official GA4 lead-stage reporting context used to distinguish platform events from operational lead outcomes.
9. [Validate Measurement Protocol events](https://developers.google.com/analytics/devguides/collection/protocol/ga4/validating-events) — Google Analytics. Checked November 18, 2026 for the difference between schema validation, successful HTTP responses and events appearing in reports.
10. [Verify Measurement Protocol implementation](https://developers.google.com/analytics/devguides/collection/protocol/ga4/verify-implementation) — Google Analytics. Checked November 18, 2026 for verification in the intended property with Realtime or DebugView; the owned example is not a GA4 integration.

Implementation

## The practical next step

Before approving a redesign release, ask for one artifact: an approved, release-linked migration acceptance report with a named owner that connects the URL map, rendered-template tests, analytics evidence, and CRM test leads to the exact deployment candidate. If that report cannot be produced, the project is still in development.

[Run the worked SEO and enquiry-handoff launch test](https://www.void-agency.com/insights/website-redesign-seo-measurement-migration#worked-launch-sample)[Use the migration checklist and blank URL ledger](https://www.void-agency.com/tools/redesign-migration-checklist)[Use the 35-check technical SEO release gate before launch](https://www.void-agency.com/tools/technical-seo-audit-checklist)[Plan a website development engagement around measurable release evidence](https://www.void-agency.com/services/website-development)[Protect analytics and lead-system continuity during the migration](https://www.void-agency.com/services/measurement-data-systems)[Build the lead attribution contract before changing forms or analytics](https://www.void-agency.com/insights/local-service-business-lead-attribution)

## Related service pages

[AI, website, and SEO systems for service businesses in Austin](https://www.void-agency.com/smbs)

### More Field Notes

## Related Reading

Technical SEO

### Googlebot’s 2 MB HTML Limit: A Byte-Level Audit

Test what Googlebot can fetch before the 2 MB cutoff and whether critical metadata, links, content, ...

[Read more](https://www.void-agency.com/insights/googlebot-2mb-html-limit-audit)Technical SEO

### SPA Core Web Vitals in Chrome 151: Soft Navigations

New browser support makes route-transition performance more observable, but teams still need feature...

Read more Technical

### Why Website Speed Drains Lead Conversion

Core Web Vitals affect search visibility and conversion. Here is how to make image-rich service page...

Read more

---
Source: https://www.void-agency.com/insights/website-redesign-seo-measurement-migration · VOID Agency
