When a site has just been redesigned, submitting a fresh sitemap is how you tell search engines that the old map no longer matches the territory. What changed is rarely just the paintwork: URLs move, pages merge, and menus get rebuilt. Who needs to act is whoever owns the launch, whether that is you, a developer, or an agency, and when matters too, because the submission should happen on launch day, not weeks later when traffic has already dipped.
Why does this step get skipped so often? Because a redesign feels finished when the pages look right in a browser, yet crawlers still follow the structure they learned before. Where the confusion shows up first is usually in coverage reports, where brand-new pages sit undiscovered while removed pages keep getting requested. How you submit the sitemap correctly, and how you clean it up before you submit, is the difference between a smooth relaunch and a slow, puzzling slide in visibility.
A sitemap is a promise about which URLs exist and matter. A redesign breaks it quietly: a file generated months ago cannot know about a new product section, a renamed category, or a checkout that moved. Even a visual refresh can change templates and pagination enough to leave the old file describing a site that no longer exists.
The risk is wasted time and mixed signals during the window when you watch rankings most anxiously. A stale sitemap sends crawlers to redirects and dead ends, while the pages you care about wait behind them.
Together, they mean the safest assumption after any redesign is that your previous sitemap is history, not a reference.
Submitting a flawed file quickly is worse than submitting a clean file a day later. Regenerate it from the live site so it reflects pages that resolve today, rebuilding it with an XML sitemap generator and reviewing the output by hand.
Open a sample of URLs from every part of the site. Check that each loads without a redirect, shows the intended content, and carries a self-referencing canonical tag.
Keep the sitemap focused on pages you genuinely want indexed. That means excluding URLs blocked in robots.txt, pages with a noindex tag, duplicate parameter versions, and anything behind a login. It also means resisting the temptation to pad the file with low-value pages just to make the site look bigger, a habit that drifts toward the kind of manipulative practice described in Google's spam policies documentation.
With a clean file ready, submission is simple. In Google Search Console, open the Sitemaps report for the correct property, enter the address, and submit. Use the property matching the live site, including protocol and host.
Do the same in Bing Webmaster Tools, since the engines do not share submissions. Then add the sitemap line to robots.txt as a permanent signpost for any crawler.
For more background reading on keeping search engines informed as your site evolves, the guides collected on the Seovaro blog cover the wider habits that support a healthy, crawlable site.
List only new URLs in the sitemap, but give every old address with links or rankings a permanent redirect to the closest matching new page.
Submission is a request, not a receipt. A day or two later, return to the report and read the status. Success with a discovered count close to your submission is what you want; a far lower count points to blocked or redirected URLs in the file.
Next, watch coverage reports for two weeks. New pages should move from discovered to indexed, and old URLs should drop away as redirects are processed. A growing error spike means you should crawl the site yourself.
Teams that relaunch smoothly treat the sitemap as a launch checklist item with an owner and a deadline. Note who regenerated the file, when it was submitted, and what the first status report said.
Ready to rebuild your file before you submit it? Try the XML Sitemap Generator mentioned above, run through the cleanup checks in this guide, and give search engines a map that finally matches the site your visitors see.
Submit it as soon as the new site is live at its real address. A sitemap pointing to pages that are not reachable yet will collect errors, while waiting weeks leaves crawlers working from an outdated picture of your site.
If the old file still exists at the same address and has been regenerated, there is nothing extra to remove. If you changed the sitemap location, delete or redirect the old file and submit the new address so engines are not reading two conflicting versions.
Search engines often fetch a submitted sitemap within hours, but indexing the discovered pages can take days or a few weeks depending on the size of the site and how much changed. Watch the reports rather than expecting an instant ranking change.
No. A sitemap announces new URLs, while redirects transfer visitors and link signals from old ones. A careful relaunch always uses both together, and skipping redirects is one of the most expensive redesign mistakes a site can make.
