Yes, you should submit a new sitemap after redesigning your website. A redesign usually changes URLs, or adds and removes pages, and the sitemap is how you tell Google the new set of URLs to crawl. Submitting a fresh one speeds up rediscovery of the new site, so the new URLs get found and indexed faster than if you waited for Google to stumble on them. The process is short: generate an accurate sitemap of the live new URLs, submit it in Search Console, and remove the old one. The important caveat is that a sitemap is a hint, not a fix. It helps Google find the new pages, but it does not replace the 301 redirects that actually preserve rankings for changed URLs. WPBuildAI inventories the new site’s URLs so your sitemap is complete and matches what actually exists.

Submit it, then watch a second surface as well: Google launched Search Generative AI performance reports in Search Console on 3 June 2026, which shows which of the redesigned URLs are actually appearing inside AI Overviews and AI Mode as the new sitemap is processed.

Why the sitemap matters after a redesign

A sitemap is a list of the URLs you want crawled, and after a redesign that list has changed. New pages exist, some old ones are gone, and many addresses may have changed shape. Submitting an updated sitemap, as Google describes in its sitemaps overview, points the crawler at the current set so it does not waste time on URLs that no longer exist and finds the new ones sooner. This matters most right after launch, when Google’s picture of your site is still the old one. The sitemap accelerates the correction.

Generate a fresh, accurate sitemap

The value of the sitemap depends on its accuracy. It should list the live URLs that actually exist on the new site, and nothing else: no leftover old URLs, no staging addresses, no pages that 404. A sitemap full of stale entries wastes crawl budget and muddies rediscovery. So generate it from the real, current URL set, which means inventorying the new site rather than reusing the old sitemap, the same discipline as finding all URLs. An accurate sitemap is a clean signal; a stale one is noise.

Submit it in Search Console

Submitting is straightforward. In Search Console, add the new sitemap’s URL under the Sitemaps report, and remove or replace the old sitemap entry so Google is not still reading an outdated list. Google then fetches the sitemap and uses it to schedule crawling. There is no need to repeatedly resubmit; once it is registered, Google rechecks it. For a site that changed domain, submit the sitemap on the new domain’s property and pair it with the Change of Address tool, part of the site move process.

Do not rely on the sitemap to fix redirects

This is the part people get wrong: a sitemap is not a substitute for redirects. Submitting the new URLs tells Google what exists now, but it does nothing for the old URLs that changed. Those still need 301 redirects to pass their rankings to the new pages, per Google’s redirects guidance; without them, the old URLs 404 regardless of how good your new sitemap is. The traffic stakes are real, since traffic concentrates on a few URLs per the Ahrefs study. So treat the sitemap and the redirect map as two separate jobs: the sitemap helps discovery, the redirects preserve equity.

What to watch after submitting

After submitting, watch how Google processes it. In Search Console, the Sitemaps report shows how many submitted URLs were discovered and indexed, and the Pages report shows indexing status. You want indexed pages to climb toward the new total, and the 404 count to stay low, fixing any that appear, as in fixing 404 errors. If the sitemap shows many URLs submitted but few indexed, check that those URLs are not blocked, redirected, or thin. The sitemap turns the recrawl from passive waiting into something you can monitor.

A worked example

A site rebuilt on a new platform changed about a third of its URLs. At launch, the team generated a sitemap from the live new URLs only, with no stale entries, and submitted it in Search Console, removing the old sitemap. Crucially, they also applied 301 redirects for the changed URLs, treating that as a separate task. Over the next two weeks, the Sitemaps report showed the new URLs being discovered and indexed, and the redirects carried the rankings across. Submitting the sitemap sped up rediscovery; the redirects preserved the equity. Neither would have been enough alone, but together the transition was fast and clean.

Common mistakes

  • Not submitting a new sitemap, leaving Google to rediscover the site slowly.
  • Submitting a sitemap full of old or 404ing URLs.
  • Treating the sitemap as a substitute for 301 redirects.
  • Leaving the old sitemap registered alongside the new one.
  • Submitting but never checking how many URLs actually get indexed.

Key points to remember

Yes, submit a new sitemap after a redesign, because it tells Google the new set of URLs and speeds rediscovery of the rebuilt site. Generate it from the live URLs only, submit it in Search Console, and remove the old one. But remember it is a hint, not a fix: it does not replace the 301 redirects that preserve rankings for changed URLs, so treat the sitemap and the redirect map as two jobs. Then watch the Sitemaps and Pages reports as Google recrawls. WPBuildAI inventories the new site’s URLs so your sitemap is complete and matches what exists. Send your site URL for a free URL inventory.

Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.