Blog
 » 

Webflow

 » 
SEO Checklist for a Website Redesign

SEO Checklist for a Website Redesign

A complete SEO checklist for a website redesign — pre-launch, during build, and post-launch tasks to protect rankings and traffic.

Daniel Moreno

By 

Daniel Moreno

Updated on

Jul 10, 2026

.

Jesus Vargas

Reviewed by 

Jesus Vargas

Founder

Why Trust Our Content

SEO Checklist for a Website Redesign

An seo checklist for website redesign is the difference between a traffic bump and a traffic collapse.

Without structured SEO tasks across all three phases, the most common outcome is losing the rankings that took years to build.

Most SEO damage during redesigns is preventable. Dropped pages, broken redirects, and accidental noindex tags all occur because no one ran a systematic check at each phase. The checklist is what prevents that.

 

Key Takeaways

  • Three phases, one checklist: Pre-redesign, during-build, and post-launch tasks each have distinct SEO requirements that must be tracked separately.
  • Baselines are foundational: Without a crawl export and GSC baseline before launch, verifying that any SEO element was preserved correctly is impossible.
  • Redirects are a project in themselves: A redirect map for a site with hundreds of URLs is a significant deliverable; underestimating it is the single most common SEO error in redesigns.
  • Staging must be blocked from indexing: An indexable staging environment creates duplicate content and can contaminate the live site's search presence.
  • Post-launch monitoring is required: The 90 days after launch are when most SEO issues surface; monitoring is a defined phase, not optional activity.

 

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.

 

Phase 1: Pre-Redesign SEO Audit Checklist

The complete SEO redesign guide begins before any design work starts. Every Phase 1 task documents the current state so you can verify what was preserved, improved, or accidentally lost after launch.

Skipping Phase 1 is the single most common SEO mistake in a redesign. You cannot confirm whether rankings were protected if you did not document them before the project began.

 

Crawl and Export the Current Site

A full crawl export is the migration source of truth.

  • Full URL list: Every URL on the current site, including pagination, tag pages, category pages, and media files, exported with HTTP status codes.
  • On-page SEO elements: Title tags, meta descriptions, H1s, canonical tags, and alt text for every crawled page, exported for comparison after launch.
  • Word count and internal link data: Pages with substantial content and strong internal link equity are the highest-risk pages if their URLs change without redirects.
  • Crawl tool: Screaming Frog, Sitebulb, or equivalent tool used to produce a complete, structured export that can be cross-referenced during QA.

 

Export Organic Performance Data

Pull the top-traffic and top-impression pages from Google Search Console.

Cross-reference with GA4 conversion data to identify the 30 to 50 pages that represent the highest SEO risk if their content, URL, or structure changes without proper handling.

 

Export Backlink Profile

Use Ahrefs or Semrush to export all pages with inbound backlinks, noting the referring domain count and anchor text for each.

These pages must be preserved with their current URL or redirected to the most relevant equivalent on the new site.

 

Document Current Keyword Rankings

Record current rankings for all target keywords using Google Search Console or a rank tracker.

This baseline is what you compare against at 30, 60, and 90 days post-launch to confirm whether rankings were preserved or recovered.

 

Phase 1: Keyword Mapping and URL Planning

Keyword mapping for redesign ensures the new site architecture is built around search intent, not just internal organizational logic or visual hierarchy.

Every URL decision in the new site has SEO implications. Locking these decisions before design begins prevents the expensive cascade of changes that occur when URL structure is revised mid-project.

 

Build a Keyword Map Before the Sitemap

Assign primary and secondary target keywords to every page in the new site before the sitemap is finalized.

This prevents pages with ranking equity from being cut, consolidated, or moved to a URL that loses their existing authority.

  • Keyword-to-page assignment: Every page gets one primary keyword and up to three secondary keywords, documented in a shared spreadsheet that the sitemap references.
  • Equity-bearing page protection: Any page currently ranking for a target keyword is flagged in the keyword map and protected from consolidation or URL change without a redirect.
  • New page identification: Keywords with search volume and no currently ranking page are flagged as new page opportunities, so they can be planned and briefed during the content phase.

 

Finalize URL Structure Before Design Begins

URL structure decisions must be locked before wireframing starts. Mid-project URL changes cascade into navigation, sitemaps, redirect maps, and internal link updates.

Every change made after the sitemap is signed off costs significantly more time than making the decision correctly upfront.

 

Identify Content Gaps That Need New Pages

Keyword research will reveal high-opportunity topics not covered by the current site.

These new pages need to be planned and briefed before the content strategy is finalized, so the information architecture and page templates support them from the start.

 

Phase 2: During-Build SEO Checklist

Maintain SEO during build by running every technical SEO verification task on the staging environment before any client review is scheduled.

The staging phase is the last opportunity to catch and fix SEO errors before they affect the live site.

Errors found after launch cost significantly more to address because they may have already caused ranking drops.

 

Block Staging From Indexing

Confirm that the staging site's robots.txt disallows all crawlers and that no staging URLs appear in Google Search Console.

  • Robots.txt verification: Manually check the staging robots.txt file to confirm the global disallow rule is in place before any external preview links are shared.
  • Password protection: Add HTTP authentication to the staging environment as a secondary barrier, particularly for high-profile redesigns where preview links may be shared broadly.
  • GSC check: Verify that no staging domain appears in Google Search Console. If it does, request removal immediately and confirm the disallow rule is active.

 

Migrate All On-Page SEO Elements

Verify that every page has its title tag, meta description, H1, alt text, and schema markup correctly migrated from the old site.

Spot-check at least 10% of pages manually; do not rely solely on a programmatic comparison for high-risk pages.

 

Verify Internal Link Structure

Run a crawl of the staging site to confirm all pages are internally linked, no orphaned pages exist, and descriptive anchor text is used on all key internal links.

 

Implement and Test All 301 Redirects

Confirm that every changed URL has a 301 redirect in place, test a representative sample manually, and run a crawl to identify any redirect chains or loops before launch.

 

Phase 2: Redirect Checklist

301 redirect implementation steps are the highest-risk SEO task in any redesign. Redirect errors are the most common cause of post-launch ranking drops and the most difficult to recover from once the site is live.

A complete redirect map built before launch is a significant deliverable. Treating it as a minor technical task is the mistake that causes the most preventable SEO damage.

 

Complete Redirect Map Built and Reviewed

The redirect map must cover all old URLs, not just the homepage and main service pages.

Pagination pages, category archive pages, tag pages, and media file URLs all need to be included if they carry inbound links or ranking equity.

  • Source of truth: The redirect map is built from the full crawl export and backlink export completed in Phase 1. Any URL not in those exports that carries ranking equity is a gap that needs to be identified and closed.
  • Destination page relevance: Each redirect should point to the most topically relevant new page, not the homepage. Homepage-all redirects are a common shortcut that consistently produces ranking drops.
  • Redirect map review process: Both the SEO lead and a developer should review the redirect map before implementation to catch mapping errors before they are pushed to the live server.

 

No Redirect Chains Present

Audit for redirect chains using Screaming Frog's redirect chain report. Every redirect should resolve in a single hop.

Chains (A redirects to B which redirects to C) dilute link equity and slow page load, both of which negatively affect rankings.

 

Backlink-Destination Pages Manually Verified

Pages with inbound backlinks require manual verification. Confirm that each redirect lands on the most relevant new page, not just a close approximation.

High-value backlinks pointing to redirected pages lose a portion of their link equity with every additional hop.

 

Phase 3: Pre-Launch Final Verification Checklist

Common redesign SEO mistakes almost always appear at the transition from staging to production. The pre-launch checklist is specifically designed to catch the errors that consistently occur at this transition.

Run every item on this checklist in the hours before launch, not the day after. Post-launch fixes for these errors require additional crawl time from Google that you cannot accelerate.

 

robots.txt Configured Correctly for Production

Confirm that the production robots.txt allows Googlebot to crawl all indexable pages and does not carry over any staging disallow rules.

  • Manual review: Open the production robots.txt file at domain.com/robots.txt and read it. Do not rely on an automated check alone.
  • Staging rules removed: Any disallow rules that were applied to staging must be explicitly removed from the production version before launch.
  • No over-blocking: Confirm that the robots.txt does not accidentally disallow CSS, JavaScript, or image files that Googlebot needs to render pages correctly.

 

XML Sitemap Updated and Submitted

Confirm that the sitemap contains only indexable URLs (no noindex pages, no redirected URLs, no 404s) and that it has been submitted to Google Search Console before or immediately after launch.

 

Noindex Tags Removed From All Production Pages

Run a crawl of the live site immediately after launch and filter for noindex tags.

Forgetting to remove staging noindex tags from the production build is one of the most common SEO errors in redesigns and one of the most damaging.

 

Analytics and Conversion Tracking Verified

Confirm that GA4 is firing on all pages, that key conversion events (form submissions, calls, purchases) are tracking correctly, and that all UTM parameters pass through the site without being stripped.

 

Phase 3: Post-Launch SEO Audit Checklist

Post-launch SEO audit steps form a structured 90-day monitoring framework that catches issues before they compound into significant ranking losses.

Most SEO issues that surface in the 90 days after a redesign are detectable and fixable if monitoring begins on launch day. Issues that go undetected for weeks are significantly harder to recover from.

 

Week 1: Crawl the Live Site and Fix Critical Errors

Crawl the live site within 24 hours of launch. Prioritize 404 errors and redirect chains. Any critical error identified in Week 1 should be resolved within 48 hours before Google's crawl reflects the broken state.

  • 404 error prioritization: 404s on pages with inbound backlinks are the highest priority. These represent lost link equity that can be recovered immediately with a correct redirect.
  • Redirect chain resolution: Any redirect chain identified in the live crawl should be collapsed to a single hop as quickly as possible.
  • Form and conversion verification: Confirm that all contact forms, checkout flows, and conversion tracking are functioning correctly on the live domain.

 

Weeks 2 to 4: Monitor GSC Coverage and Index Status

Watch Google Search Console for coverage errors, compare the indexed page count against the expected count, and submit individual priority pages for indexing if they have not appeared within 14 days of launch.

 

Days 30 to 90: Track Rankings and Traffic vs. Baseline

Compare organic traffic, impressions, and keyword rankings against the pre-launch baseline documented in Phase 1.

Use a combination of GSC data and crawl analyzis to diagnose specific page-level drops rather than treating all ranking changes as a single problem.

 

Conclusion

This SEO checklist only works when it starts before design begins. Tasks left to post-launch are damage control, not protection.

Every item skipped in Phase 1 or Phase 2 becomes a harder problem to fix after launch.

Run through the Phase 1 tasks against your current site this week. The data you collect now is the foundation for every SEO decision in the redesign and the baseline against which you measure success.

 

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.

 

LOW/CODE Agency Runs Through This Checklist on Every Redesign We Build

Protecting organic rankings through a redesign requires process, not just awareness of what can go wrong.

LOW/CODE Agency is a strategic product team, not a dev shop, and our integrated SEO process runs through every item on this checklist across every redesign we deliver.

We treat SEO protection as an engineering responsibility, not an afterthought. Every redirect is mapped, every staging environment is locked, and every post-launch crawl is scheduled before the project begins.

  • Pre-launch SEO audit: Full crawl export, GSC baseline, backlink export, and keyword ranking documentation before any design work starts.
  • Keyword mapping and URL planning: Keyword-to-page assignments and URL structure locked before wireframing begins.
  • Staging SEO verification: On-page element migration, internal link audit, redirect implementation, and noindex verification on staging before client preview.
  • Redirect map as a deliverable: Complete redirect map built from crawl data, reviewed for chains and destination relevance, and tested before launch.
  • Pre-launch final checks: robots.txt, XML sitemap, noindex removal, and analytics verification completed in the hours before DNS cutover.
  • Post-launch monitoring framework: Week 1 crawl, GSC coverage monitoring, and 90-day ranking comparison against pre-launch baselines.
  • SEO-safe platform builds: Webflow, WordPress, and headless builds configured with SEO best practices as default, not optional additions.

Our SEO-safe website redesign process has been applied across 450+ products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku. Start with a scoping call

Last updated on 

July 10, 2026

.

Daniel Moreno

Daniel Moreno

 - 

Web Developer

Daniel is a Web Developer at LOW/CODE Agency who has been building websites in Webflow since 2022. With a background in graphic design, he turns the design team's concepts into fast, responsive sites

Custom Automation Solutions

Save Hours Every Week

We automate your daily operations, save you 100+ hours a month, and position your business to scale effortlessly.

FAQs

Watch the full conversation between Jesus Vargas and Kristin Kenzie

Honest talk on no-code myths, AI realities, pricing mistakes, and what 330+ apps taught us.
We’re making this video available to our close network first! Drop your email and see it instantly.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Why customers trust us for no-code development

Expertise
We’ve built 330+ amazing projects with no-code.
Process
Our process-oriented approach ensures a stress-free experience.
Support
With a 30+ strong team, we’ll support your business growth.