SEO Preservation.

Most business owners don't find out their website migration hurt their SEO until three months after it happened — when the phone gets quieter and a Search Console check reveals a 40% drop in impressions that started the week the new site launched. By then, recovery is a longer road than prevention would have been.

This guide is the prevention. It covers what to document, what to protect, what to implement at launch, and what to monitor afterward. We've run migrations for Tucson businesses across every industry — dental practices, contractors, law firms, med spas — and the checklist in this guide is built from what has actually mattered in those projects. Twenty-eight questions. Six sections. No filler.

01Why SEO preservation matters more than you think.

1.1How common is ranking loss after a redesign or migration?

Very common. In our experience, the majority of businesses that go through a website migration without a dedicated SEO preservation plan experience measurable ranking loss in the first 60–90 days. The losses are usually in two categories: pages that moved URL without a redirect, and ranking signals that were embedded in content that was rewritten, merged, or removed. The smaller the business's existing backlink profile, the slower the recovery — because there's less authority to absorb the losses.

1.2What specifically does a business "lose" when rankings drop?

Real dollars — not abstract metrics. If a local HVAC company in Tucson ranks number three for "AC repair Tucson" and loses that ranking, they lose the 15–25 qualified visitors per day that position was driving. At a 5% conversion rate, that's one to two leads per day. At an average job value of $400, that's $400–$800 per day in potential revenue per search term. Business owners who think of SEO in terms of "rankings" don't feel the loss the same way as those who've translated it to lead flow and revenue. Translate it.

1.3What are the most common causes of post-migration ranking loss?

In order of frequency: (1) URL changes without 301 redirects — the single most destructive oversight. (2) Content reduction — rewriting a 1,200-word ranking page as a 300-word summary. (3) Structured data removal — old site had schema, new site doesn't. (4) Core Web Vitals regression — moving from a fast custom-coded site to a slow page-builder site. (5) Internal link structure changes — the new architecture doesn't pass authority through the site the same way. (6) Canonical tag errors — duplicate content signals from staging environments or www/non-www mismatches.

1.4Should SEO preservation be a line item in the project scope?

Yes — explicitly. If the redesign proposal doesn't mention redirects, pre-migration auditing, or post-launch monitoring, those things aren't being done. Add them to the scope in writing before signing. The work involved — an export of current URLs, a traffic analysis, a redirect map, a schema rebuild checklist, and 60 days of post-launch monitoring — is 8–15 hours of additional work. On a $6,000 redesign, it's the cheapest insurance you can buy.

1.5What if my current site has very little SEO equity — does preservation still matter?

Yes, for a reason that's often missed: the redesign is supposed to build SEO equity, not just preserve it. If you launch a new site on a broken redirect foundation, every piece of content you add over the next two years will be building on a compromised structure. It's much harder to fix redirect architecture retroactively than to do it right at launch. Preservation isn't just about protecting what you have — it's about launching on solid ground.

02The pre-migration audit — what to document first.

2.1What does a pre-migration audit cover?

A thorough pre-migration audit covers: a complete crawl of every URL on the current site (Screaming Frog is the standard tool); a Google Search Console export of every page's impression and click data for the last 12 months; a Google Analytics export of top pages by organic sessions; an Ahrefs or SEMrush export of every page with inbound backlinks; and a manual review of the pages that rank in positions 1–20 for commercial terms. The output is a prioritized list of pages that cannot be broken — ranked by their current SEO value.

2.2How do I know which pages are most important to protect?

Three signals identify high-value pages: organic traffic (pages driving more than 50 sessions per month from search deserve special attention); ranking position (any page in positions 1–10 for a commercial query is an asset); and inbound links (any page with two or more external links pointing at it has link equity that moves with the redirect). A page can rank without traffic if its impressions are high but CTR is low — that's often a title tag fix, not a deprecation candidate.

2.3What's the difference between pages to preserve versus pages to improve?

A preserve decision means: keep the URL the same if possible, keep the core content, update the design around it. An improve decision means: the page is ranking but the content is thin or outdated, so we'll rewrite it substantially while keeping the URL and the topical signal. A deprecate decision means: the page has zero traffic, zero rankings, and no inbound links — it can be removed or merged. Most well-managed sites have a mix of all three. The mistake is treating every page as a redesign candidate when some are ranking machines in an ugly wrapper.

2.4How should the pre-migration audit influence the new site architecture?

Directly. The new URL structure should be designed around preserving the best-performing patterns of the old site, not starting from scratch. If your existing site has service pages at /services/[service-name]/ that rank well, the new site should use the same or nearly-the-same pattern. If the old site had a blog at /blog/ with ranking posts, /blog/ stays. Changing URL patterns forces more redirects and creates more risk. The audit tells you what to protect; the architecture reflects that protection.

2.5What technical baseline should be documented before any changes go live?

Document: current Core Web Vitals scores (LCP, CLS, FID/INP) on both mobile and desktop for your top 10 pages; current canonical tag configuration; current robots.txt and any crawl directives; all structured data markup present on each page type; XML sitemap structure; and any hreflang or international targeting configurations if applicable. This baseline is your comparison point post-launch. Without it, you can't tell whether a performance change after launch is from the redesign or from something else.

03Redirects — the foundation of a safe migration.

3.1What is a 301 redirect and why does it matter for SEO?

A 301 redirect is a server instruction that tells browsers and search engines: "this page has permanently moved to this new URL." When Google follows a 301 redirect, it transfers approximately 90–99% of the original page's ranking signals to the new URL. Without a redirect, those signals stay attached to a URL that now returns a 404 — and they decay. The inbound links, the crawl history, the user signals — all of it. A clean redirect map means virtually none of that is lost.

3.2How do I build a redirect map?

Start with the full URL crawl from the pre-migration audit. For each URL, determine: (1) Does it have a direct equivalent on the new site? If yes, map it one-to-one. (2) Has it been merged with another page? Map it to the URL that absorbed it. (3) Has it been deprecated entirely? Map it to the most topically relevant parent page, or to the homepage as a last resort. Never redirect to the homepage by default — that dilutes the signal. The output is a spreadsheet with two columns: old URL, new URL. Implement those as server-side 301 redirects before launch.

3.3Are there types of redirects I should avoid?

Yes. Redirect chains — where URL A redirects to URL B, which redirects to URL C — lose link equity at each hop and slow page load. After launch, audit for chains and consolidate them. JavaScript-based redirects (meta refresh, JS window.location) are read by Google but are slower and less reliable than server-side 301s — avoid them for SEO-critical pages. Temporary 302 redirects should never be used for permanent moves — they don't transfer ranking signals the same way, and many SEOs treat them as sending zero equity.

3.4What should I do with pages that have no equivalent on the new site?

For pages with inbound links or traffic, find the closest topically relevant page on the new site and redirect there. A page about "Tucson bathroom remodel services" that no longer exists should redirect to the general "remodeling services" page, not the homepage. For pages with no traffic, no links, and no ranking value — they can return a 404 or redirect to the closest category parent. Document every 404 decision in the redirect map so you can revisit if you see unexpected traffic losses in Search Console post-launch.

04Content, structure, and on-page signals.

4.1Can I rewrite my existing page content during a redesign without hurting rankings?

Yes — carefully. Rewrites that improve the depth, accuracy, and usefulness of existing content while preserving the primary keyword focus typically maintain or improve rankings over 60–90 days. Rewrites that reduce word count significantly, change the topical focus, or remove supporting information that searchers need tend to hurt rankings. The safe rule: make the content better and more complete, not shorter and more polished. Google rewards depth on commercial service pages. A 1,500-word page that fully answers what someone searching "Tucson HVAC installation cost" wants to know will outrank a 400-word summary written for design aesthetics.

4.2What on-page elements carry the most ranking weight?

In rough priority order for a local service business: the title tag (the single most important on-page ranking signal); the H1 (should match the title tag's core intent); the first 100 words of body copy (where topical relevance is established for crawlers); internal links from high-authority pages to this page; the URL slug (should contain the primary keyword, once); and image alt text (matters for image search and as a secondary topical signal). Meta descriptions don't directly affect rankings but affect click-through rate significantly — write them to sell the click.

4.3How important is internal linking in SEO preservation?

Very. Internal links pass authority through a site — from high-traffic pages to the pages you most want to rank. If your homepage links to your five core service pages, those pages rank better than service pages buried in a navigation dropdown. In a redesign, audit the old internal link structure and replicate the authority flow in the new site. New sites often start with a clean navigation that inadvertently cuts off the internal link paths that were supporting key ranking pages. Map the old structure; preserve the intent.

4.4What happens to structured data (schema) in a migration?

It disappears — unless you explicitly rebuild it. Structured data is not a page design element; it's markup in the page's HTML or in a JSON-LD script block. Unless the agency working on the redesign has a specific structured data implementation plan, the new site will launch without schema. For local businesses, losing LocalBusiness schema, Service schema, and FAQPage schema removes rich result eligibility and weakens local pack signals. Schema should be rebuilt from scratch for every page type — not copied verbatim from the old site, because the new site's structure may have changed.

4.5Should I change my domain name during a redesign?

Only if the current domain name has a genuine business problem — it's confusing, it's wrong, the business has rebranded. A domain change is an additional migration layer on top of a URL migration: you're now asking Google to transfer every signal from the old domain to a new one, through redirects, over a period that typically takes three to nine months to fully resolve. If you do change domains, you must submit the new domain to Google Search Console, implement sitewide 301 redirects from the old domain, and inform any major referring sites. Domain changes don't fail — but they cost time that a URL-only migration doesn't.

05Post-launch monitoring and recovery.

5.1What should I monitor immediately after a new site launches?

First 48 hours: verify that all redirects are returning 301 status codes (not 302 or 404); confirm the new site is indexed in Google Search Console (submit the new sitemap immediately); verify canonical tags are pointing to the correct URLs; check that robots.txt is not blocking search engine crawlers (a common staging-to-production oversight). First two weeks: monitor Search Console for crawl errors, coverage issues, and any pages returning 404 that shouldn't be. Weeks two through eight: track ranking positions for your 20 most important commercial queries weekly.

5.2How long should I expect rankings to be unstable after a migration?

Some fluctuation in the first two to four weeks is normal — Google is re-crawling and re-evaluating the site after the structural change. For a well-executed migration (redirects in place, content preserved, schema rebuilt), rankings typically stabilize by week six. A site that shows sustained decline past week eight has a structural problem — usually broken redirects, missing content, or a Core Web Vitals regression — that needs diagnosis and remediation. Don't wait until week twelve to investigate.

5.3What are the first things to check when rankings drop post-launch?

In order: (1) Search Console Coverage report — are the ranking pages indexed? (2) Redirect check — do the old URLs 301 to the correct new URLs? (3) Page-level content comparison — did the rewrite reduce keyword relevance or word count significantly? (4) Core Web Vitals comparison — is the new site slower than the old one on mobile? (5) Canonical tags — are any pages accidentally canonicalizing to a different URL? (6) Structured data — does the new site have the schema that the old site had? Address these in order before concluding the drop is algorithmic.

5.4How do I recover rankings that were lost in a migration?

Start by identifying exactly which pages lost rankings and by how much, using the pre-migration baseline. For each lost page: fix any redirect chain issues; restore any content that was reduced substantially; rebuild any missing schema; and check internal link pointing. Once the technical issues are resolved, rankings typically begin recovering within four to eight weeks. The recovery timeline depends on how long the broken state existed — a page that 404'd for eight weeks has lost more equity than one that 404'd for eight days. Fix fast.

5.5Is there a point of no return — SEO damage that can't be recovered?

Not usually, but the timeline of recovery scales with the severity and duration of the problem. Redirects implemented a week after launch lose less than redirects implemented six months after. A domain that has lost its inbound links (because webmasters updated their links to the new URL and the old redirects were removed) loses those links permanently unless individual outreach is done. Backlinks lost to a 404 over a long period may or may not be recoverable. The honest answer is that most migration damage is fully recoverable with proper remediation — but early intervention is always better than late.

06Hiring signals — who handles migrations well.

6.1What should I ask an agency about their SEO migration process?

These four questions reveal the most: "Do you complete a pre-migration traffic and rankings audit before building the new site?" "Do you build a redirect map, and is that included in the project scope?" "What's your process for rebuilding structured data on the new site?" "How do you monitor rankings after launch, and for how long?" An agency that can answer all four specifically and without hesitation has real experience with SEO migration. Vague answers — "we use best practices," "we handle all the SEO stuff" — mean they're improvising.

6.2Are there portfolio questions I should ask about past migration projects?

Yes. Ask if they can share before-and-after Search Console data from any redesign project in their portfolio. A well-handled migration shows stable or improved impressions and clicks after launch. A poorly handled one shows a clear drop. If an agency can't or won't share this data — even in anonymized form — they may not have it. Agencies that measure their migrations have the data. Agencies that don't measure haven't been looking.

6.3Should SEO migration be handled by the web design firm or an SEO firm?

Ideally, both are involved — or the web design firm has strong in-house SEO knowledge. The web design firm controls the redirect implementation, the URL structure, the on-page elements, and the structured data. An external SEO firm can provide the pre-migration audit, the redirect map review, and the post-launch monitoring. If you're working with a web design firm that doesn't have SEO experience, hire an SEO consultant to oversee the migration specifically — it's worth $500–$1,500 in consulting fees to protect years of organic growth.

6.4What's in the contract that protects me if rankings drop after a migration?

Most agencies won't guarantee rankings — and you shouldn't expect them to, because ranking outcomes are partially outside any agency's control. What you can and should negotiate: a defined post-launch monitoring period (30–60 days at minimum); a clear remediation clause specifying what the agency will do at no additional charge if technical migration errors (broken redirects, missing schema, indexing failures) cause measurable ranking loss; and documentation deliverables (redirect map, pre-migration baseline, structured data implementation list) that give you the tools to work with any future agency. Don't sign a scope without those three elements.