Webflow Sitemap Checklist for Redesigns and Migrations

Author : Muhammad Aamir Ijaz | Published On : 18 Nov 2026

A redesign changes URLs, page counts, and site structure all at once. Your Webflow sitemap has to keep pace, or Google may keep visiting old addresses while your new pages wait. If you want the background first, read this guide to Webflow sitemaps and crawl efficiency, then use the checklist below before your next relaunch.

Why a Redesign Puts Your Webflow Sitemap at Risk

Redesigns rename slugs, merge thin pages, and retire old ones. Each change can leave a gap between what your sitemap says and what your site actually serves.

Webflow's auto-generated sitemap updates every time you publish. That helps, but it only reflects what exists. It cannot know which old URLs you meant to retire or redirect.

If you pasted in a custom file earlier, the risk grows. Nothing updates that file for you, so it keeps listing old addresses until someone edits it by hand.

Before Launch: Map Every URL

Planning prevents most post-launch cleanup. Work through these steps while the new site is still in progress:

  1. List every live URL on the current site.

  2. Mark each one as keep, merge, or retire.

  3. Write the new address for every page you keep or merge.

  4. Plan a 301 redirect for each address that changes.

  5. Note which pages should stay out of the sitemap, such as thank-you pages.

Treat your Webflow sitemap as the official list of the new site. Every address on it should match a page in your plan, and every planned page should appear on it, apart from the exclusions you noted.

Keep this list in a shared sheet. Your developer, writer, and SEO lead can all check it, and you will use it again on launch day.

Protect Staging While You Build

Your staging site should not compete with your live one. Webflow includes a setting that stops its default subdomain from being indexed, so confirm it is on while you build. Share the staging link only with your team and reviewers.

Before launch, review the indexing setting on every page. Nothing marked noindex for staging should stay that way on a page that is meant to rank.

Launch Day: Confirm Your Webflow Sitemap Is Right

Right after you publish, open yoursite.com/sitemap.xml on the live domain and check these points:

  • The file loads without errors

  • New pages appear in the list

  • Retired pages do not appear

  • Listed URLs open directly, with no redirect

  • Auto-generate is on, unless you chose a custom file on purpose

If a page is missing, check its page-level setting first, then confirm the page is published.

Then submit the file in Google Search Console. Google's guide to building and submitting a sitemap explains the submission process in plain steps. A submitted sitemap helps Google find your pages, but it does not promise indexing.

After Launch: Let Search Console Show What Changed

Open the Sitemaps report and check whether Google read the file without errors. Compare the number of discovered URLs with the page count you expect from your URL list.

Next, scan the Page indexing report. Pages marked as redirects or not found often point to old addresses that survived somewhere, such as a custom sitemap or an internal link. Fix the source, then recheck in a few days.

Give Google time to recrawl. Large changes rarely settle overnight, so review the reports on a regular schedule instead of reacting to a single day's numbers.

Three Redesign Mistakes to Avoid

  • Leaving an old custom sitemap pasted in after the URLs change

  • Listing redirected addresses instead of final destinations

  • Forgetting a noindex setting from staging on a page that should rank

Each one is easy to miss and easy to fix once you know where to look.

Final Thoughts

A redesign is the moment your Webflow sitemap matters most. Map your URLs before launch, confirm the file on launch day, and let Search Console guide your cleanup afterward. Do those three things and Google meets your new site with fewer old addresses in the way