How to Transfer SEO During a Website Redesign

Knowing how to transfer SEO during a website redesign is not optional, it is the difference between launching a better site and destroying years of organic rankings overnight.

SEO does not migrate automatically. Every ranking signal must be deliberately moved.

Most website owners discover this the hard way: traffic drops after launch, then the investigation begins.

The good news is that with a documented process, you can protect and even improve your SEO through a complete redesign.

Key Takeaways

• SEO transfer is deliberate: Rankings, authority, and keyword targeting must be explicitly migrated through redirects, on-page transfer, and content preservation.
• Link equity moves via 301s: Properly implemented 301 redirects pass the majority of ranking power from old URLs to new ones.
• On-page elements need manual migration: Title tags, meta descriptions, schema markup, and alt text must be explicitly copied, they do not carry over by default.
• Content is an SEO asset: Cutting or rewriting pages that rank is one of the fastest ways to destroy organic traffic during a redesign.
• Verify on staging first: Never assume a CMS migration handled SEO elements correctly, verify with a full crawl before launch.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

What "Transferring SEO" Actually Means

SEO transfer means deliberately moving every ranking signal from your old site to your new one. It is a parallel project workstream, not a byproduct of the redesign itself.

Understanding the full scope prevents teams from treating SEO as an afterthought applied after the build is complete.

Link Equity and Domain Authority

• Domain authority stays: Authority is attached to the domain name, not individual pages, it does not disappear when you redesign.
• Domain changes add risk: Changing your domain or moving to a subdomain requires additional steps beyond a standard page-level redesign process.
• Authority does not auto-transfer: Inbound links pointing to specific old URLs must be redirected to maintain their ranking contribution.
• Authority builds over time: New pages without inbound links start with no link equity and must earn it through redirects or new external links.

Page-Level Ranking Signals

• Inbound links are page-specific: External sites link to individual URLs, those links lose value if the URL disappears without a redirect in place.
• On-page signals are transferable: Title tags, H1s, keyword density, and structured data can all be preserved or improved during migration.
• Engagement data is not portable: Click-through rate and dwell time signals reset after a redesign, regardless of how carefully you migrate other elements.

Content and Keyword Targeting

• Keyword targeting lives in your copy: Title tags, headings, and body text on ranking pages carry explicit keyword signals that must be preserved.
• Rewrites destroy existing rankings: Replacing ranked page copy with new content removes the signals that earned the position in the first place.
• Improvements are safe after stabilisation: Wait until rankings stabilise post-launch before optimizing copy further on high-value pages.

Technical SEO Configuration

• Canonicals must be reconfigured: Every page on the new site needs a self-referencing canonical tag that is correctly set in the new CMS.
• robots.txt must be updated: A staging site often blocks all crawlers, verify this file is corrected on launch day before anything else.
• Structured data must be re-added: Schema markup lives in code and is stripped during CMS migrations unless explicitly rebuilt.

See our complete SEO redesign overview for the full context behind each of these elements.

Step 1, Audit and Document Everything Before You Change Anything

Before a single page changes, you need a complete record of what exists. Start with keyword mapping before redesign to document which pages currently rank for which terms.

This pre-redesign documentation is your comparison baseline. Without it, you cannot verify that the transfer was successful.

Full Site Crawl Export

• Use Screaming Frog or Sitebulb: Export every URL with status code, title tag, meta description, H1, canonical, and word count.
• Save the export immediately: This master reference document is what you compare against after launch to identify any missing elements.
• Include internal link counts: Pages with high internal link equity require special care during URL restructuring or consolidation.

Organic Performance Mapping

• Export GSC performance data: Pull every query with impressions, clicks, and average position for the past 12 months.
• Map queries to specific pages: Connect each URL to its best-performing keywords using a spreadsheet VLOOKUP or pivot table.
• Create a priority tier list: Pages generating the most organic traffic become P1, they require the most careful handling throughout migration.

Backlink Profile Export

• Export from Ahrefs or Semrush: Pull every inbound link with the destination URL, linking domain, and domain authority rating.
• Flag high-authority inbound links: URLs receiving links from high-authority external domains need exact destination mapping in the redirect plan.
• Check for link clusters: Multiple inbound links pointing to one URL mean that page's redirect is among the most critical in the entire plan.

Step 2, Transfer Link Equity via 301 Redirects

301 redirects are the primary mechanism for transferring link equity from old URLs to new ones. Research consistently reports that 301 redirects pass 90 to 99% of ranking power to the destination URL.

Implement redirects correctly and thoroughly, every missed redirect is lost link equity. Review our guide to redirect implementation for SEO before building your redirect map.

Build a Complete Redirect Map

• Use a spreadsheet with three columns: Old URL, new URL, and a priority flag based on organic traffic and inbound link value.
• Cover all URL types: Include paginated pages, category pages, tag archives, and media file URLs that have inbound links.
• Flag every changed URL: Any URL that changes during the redesign, even slightly, requires a row in the redirect map.

Implement 301 (Not 302) Redirects

• 301 means permanent: Search engines treat 301 redirects as permanent signals, reliably passing link equity to the destination URL.
• 302 means temporary: A 302 redirect tells crawlers the move is temporary, causing them to retain the old URL as the canonical version instead.
• Verify redirect type in your CMS: Many CMS plugins default to 302, check your implementation method explicitly outputs the correct status code.

Verify No Redirect Chains Exist

• A chain is three or more hops: URL A redirecting to B, which redirects to C, dilutes the link equity passed at each step of the chain.
• Use Screaming Frog to audit chains: Run a crawl of your redirect map file and flag any URL that resolves through more than one redirect step.
• Resolve all chains before launch: Flatten every chain to a single direct redirect from the old URL to the final destination URL.

Step 3, Transfer On-Page SEO Elements

To maintain rankings during build, every on-page element on ranking pages must be explicitly migrated, not recreated from scratch or left as placeholder copy.

This is the section of SEO transfer that gets skipped most frequently during CMS migrations, and it is responsible for the majority of post-launch ranking losses.

Migrate Title Tags and Meta Descriptions

• Copy them exactly first: For pages preserving their URL, carry over the exact existing title tag and meta description before the site launches.
• Optimize after stabilisation: Wait until rankings re-stabilise post-launch before testing improvements to title tags on P1 pages.
• Verify in a post-launch crawl: Run a crawl within 24 hours of launch and compare title tags against your pre-redesign crawl export.

Preserve Heading Structure and Body Copy

• H1s must be text, not images: Heading text embedded in graphic files or hero images is invisible to search engines, verify all H1s are live HTML text.
• Check for placeholder copy: Redesigns often launch with "Lorem ipsum" or draft copy on interior pages, these pages lose all keyword signals immediately.
• Preserve word count on P1 pages: Pages that rank often rank partly because of content depth, do not cut content length without assessing ranking risk first.

Re-Implement Schema Markup

• Schema does not transfer automatically: Structured data in the old site's code is stripped during CMS migration unless explicitly rebuilt in the new platform.
• Prioritize schema types with rich results: Review, FAQ, LocalBusiness, Article, and Product schema can generate rich result appearances that directly improve CTR.
• Validate using Google's Rich Results Test: After re-implementing schema, validate each type to confirm it is correctly structured and error-free.

Transfer Image Alt Text

• Alt text is an SEO element: Image alt text contributes to both image search visibility and on-page keyword relevance for key product and service images.
• Audit after image re-upload: Alt text is frequently lost when images are re-uploaded to a new CMS, verify it was transferred, not just the image file.
• Check infographics and portfolio images: These high-traffic image types are the most likely to rank in image search and the most likely to lose alt text during migration.

Step 4, Handle Canonical Tags and Duplicate Content Risks

Duplicate content risks are highest during the transition period when the old and new sites may briefly be accessible simultaneously. Address canonical tags during migration before any public traffic reaches the new site.

A single canonical configuration error can cause Google to index the wrong version of your content for months.

Set Self-Referencing Canonicals on All Pages

• Every indexable page needs a canonical: A self-referencing canonical tag tells Google that this URL is the preferred version of this content.
• Verify in the CMS settings, not just templates: Many CMS platforms auto-generate canonicals but do so incorrectly for paginated or filtered pages.
• Confirm canonical matches the primary URL: If your site loads on both www and non-www, canonicals must consistently point to the preferred version.

Manage URL Parameter Issues

• Parameters create duplicate URLs: Sorting filters, pagination parameters, and session IDs generate multiple URLs with identical or near-identical content.
• Use canonical tags to nominate the master: The canonical on every parameter variation should point to the clean, parameter-free version of the page.
• Alternatively, disallow parameters in GSC: Google Search Console's URL Parameters tool can instruct Google to ignore specified parameters entirely.

Handle the Transition Period if Running Sites in Parallel

• Do not let both sites be fully indexed: If running old and new sites simultaneously during QA, add a noindex to the new site or block it via robots.txt until launch.
• Remove blocking immediately at launch: The single most common technical launch error is forgetting to remove staging-environment noindex tags when going live.
• Set old-to-new canonicals if needed: If the old site remains live briefly after launch, add canonical tags on old pages pointing to the corresponding new URL.

Step 5, Verify the Transfer Was Successful

Use our SEO transfer verification checklist as a structured reference for the post-launch audit process. Verification is not optional, it is the final phase of the SEO transfer project.

Missing this step means problems that are catchable on day one can compound into ranking losses that take months to recover.

Post-Launch Crawl Verification

• Crawl the live site within 24 hours: Compare the live crawl export against your pre-launch baseline to identify any missing title tags or broken canonicals.
• Check for unexpected noindex tags: Verify that no staging-environment noindex or robots.txt blocks were accidentally carried into the live site.
• Flag all 4xx and 5xx errors immediately: Any URLs returning errors are lost ranking signals that must be redirected or resolved on launch day, not later.

Submit Sitemap and Monitor GSC Coverage

• Submit the updated XML sitemap: Go to Google Search Console and submit the new sitemap URL under the Coverage section immediately after launch.
• Monitor for excluded or errored pages: GSC's Coverage report will identify pages that were indexed before but are now excluded, redirected, or returning errors.
• Request indexing on P1 pages manually: Use the URL Inspection tool to manually request indexing for your highest-priority pages after launch.

Compare Rankings at 30, 60, and 90 Days

• Set a pre-redesign baseline: Export all keyword rankings before launch so you have a direct comparison point at each post-launch milestone.
• Investigate drops of 3 or more positions: A 3-position drop on a high-traffic keyword warrants investigation, it may indicate a redirect miss or on-page element loss.
• Allow 90 days for full stabilisation: Some rankings fluctuate for 6 to 8 weeks after a major site change as Google re-crawls and re-evaluates the new structure.

Conclusion

SEO transfer is not something your CMS handles automatically. It is a project workstream, planned before the redesign begins, executed in parallel with development, and verified independently after launch.

Every team that treats it as an afterthought learns this the hard way.

Start today by running a Screaming Frog crawl of your current site and saving the export.

Without that baseline file, your SEO transfer plan has no starting point. The crawl takes less than an hour, the ranking recovery from skipping it can take months.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

LOW/CODE Agency Treats SEO Transfer as a Core Redesign Deliverable

At LOW/CODE Agency, SEO protection is not a bolt-on service, it is a documented workstream in every redesign project we run. We treat it as a deliverable with its own checklist and sign-off gate.

We are a strategic product team, not a dev shop. Every redesign engagement includes a pre-launch audit, a complete redirect map, on-page element transfer verification, and a 90-day post-launch monitoring plan.

Our clients do not find out about SEO problems six months after launch.

• Pre-Redesign SEO Audit: We crawl and document every existing ranking signal before a single design decision is made on your project.
• Keyword Mapping and Architecture: We map every target keyword to a specific page before the sitemap is finalized, protecting existing rankings from structural damage.
• Complete Redirect Map Build: We build and verify a full redirect map covering every URL change before the site goes live for any audience.
• On-Page Element Migration: We verify that every P1 and P2 page has its correct title tag, H1, schema markup, and alt text transferred to the new build.
• Canonical and Technical Audit: We run a full technical SEO audit on staging and again within 24 hours of launch to catch configuration errors before they compound.
• Post-Launch Ranking Monitoring: We track keyword rankings at 30, 60, and 90 days against the pre-redesign baseline and investigate any significant movement.
• GSC Setup and Sitemap Submission: We handle sitemap submission, coverage monitoring, and manual indexing requests on priority pages immediately after launch.

Our clients include Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku, and we have delivered 450+ digital products with a zero-tolerance approach to post-launch SEO drops.

Start with a scoping call to see how we would protect your rankings through a redesign, or explore our SEO-safe redesign services to understand what a fully managed migration looks like.