A sitemap strategy for site moves requires updating your XML files to reflect the final destination of all migrated URLs. When you move domains, you must inform Google of the change by submitting a new sitemap that contains the current, live URLs on the new domain while keeping the old sitemap active during the transition. This allows Googlebot to discover the new structure and process the redirect signals efficiently, ensuring that your search presence remains stable throughout the migration period.
Why is your sitemap critical during a site move?
A sitemap acts as a map for search engines, highlighting the pages you want crawled and indexed. During a domain move, the sitemap becomes the primary tool to help Google identify the new site structure. If you leave the old sitemap pointing to non-existent pages or ignore the new one, you delay the indexing process and risk losing the visibility gained by your original domain.
Think of the sitemap as an invitation to the search engine to visit your new architecture. When you change domains, Googlebot relies on these files to understand the new landscape. Without a clear map, the engine might continue to visit old URLs, which creates unnecessary traffic on your legacy infrastructure and slows down the discovery of your updated content.
In a typical account migration, we often see that sites failing to update their sitemaps suffer from fragmented indexation. If the old sitemap is deleted too soon or the new one is not submitted, Googlebot may wander through the site blindly. This leads to a dip in crawl efficiency, as the engine struggles to associate the authority of old pages with their new canonical counterparts.
How should you structure sitemaps when merging domains?
When merging domains, the priority is to provide a clean, updated list of URLs. Avoid including URLs that result in 301 redirects within the new sitemap, as this sends conflicting signals to Google. Instead, focus on providing a list of canonical URLs that are live on the destination domain.
A common mistake is maintaining a cluttered sitemap that includes both old and new URLs. You should strip out any URL that returns a 301 or 302 status code. Only pages that return a 200 OK status belong in your primary XML sitemap. This keeps the crawl budget focused on the content you want to rank.
- Create a new XML sitemap containing only the live, canonical URLs of the new site.
- Remove all URLs that are currently being redirected from the new sitemap.
- Submit the new sitemap through Google Search Console using the account for the new domain.
- Keep the old sitemap accessible on the old domain until Google has processed all redirects.
What are the common pitfalls in sitemap management?
Many teams assume that simply setting up redirects is enough, but neglecting the sitemap causes issues. If you include old URLs in your new sitemap, you force Google to crawl pages that already redirect, wasting your crawl budget. Furthermore, failing to verify the new domain in Search Console prevents you from tracking how Googlebot interacts with your newly submitted sitemap.
Another error is the failure to update the robots.txt file to point to the new sitemap location. If you move your site, Googlebot will check the robots.txt file on the old domain first. If that file does not inform the engine about the new sitemap’s location, you effectively hide your new content.
Prepare a URL mapping from the current URLs to their corresponding new format.
Google Search Central
How Alien Road applies this sitemap strategy
At Alien Road, we follow a strict protocol for site moves to minimize traffic loss. We begin by auditing the existing sitemap to identify pages with the highest authority. During the migration, we generate separate sitemaps for different content types, such as product pages and blog posts, to monitor indexing progress on a granular level. We then monitor the crawl stats in Search Console to ensure Googlebot is focusing on the new URLs.
For example, when we move an e-commerce site, we map high-traffic categories individually. By creating segmented XML files, we can see exactly which parts of the site Googlebot is struggling to process. If a specific product category shows low indexation, we immediately adjust our internal linking strategy and resubmit the sitemap.
- Audit the existing domain to identify high-performing content.
- Map every URL to its new location to prevent 404 errors.
- Submit the new XML sitemap immediately after the site goes live.
- Monitor Google Search Console for crawl errors or indexing delays.
How can you verify the migration success?
Verification requires constant observation of the URL Inspection tool. After submitting your sitemap, check the ‘Sitemaps’ report in Search Console. If you see ‘Success’ status, it means Google has read the file. If you see errors, address them immediately to prevent indexing gaps.
We also check the ‘Index’ report for a sudden spike in 404 errors. While some errors are expected during the first few days of a move, a consistent increase indicates that your 301 redirects are not correctly mapped. Ensure that you have a comprehensive list of every old URL and its corresponding destination.
What steps should you take this week?
You should verify that your new domain is fully set up in Google Search Console by Wednesday. Once the domain is confirmed, audit your current sitemap file to ensure every entry points to a live page on the new server. Remove any legacy URLs that no longer exist or that have been combined with other pages. Finally, submit the new sitemap and monitor the ‘Coverage’ report to verify that Google is finding the new content.