How to Remove a Sitemap From Google Search Console

A sitemap plays an important role in helping Google discover and crawl the pages on your website. However, there are times when you might need to remove an existing sitemap from Google Search Console—such as when the file is outdated, contains incorrect URLs, or you’ve restructured your site. An unchecked sitemap can confuse crawling and affect your content’s appearance in search results.

What is a Sitemap?

A sitemap is a file, usually in XML format, that lists your website’s important pages so search engines like Google can easily discover and crawl them. It acts as a roadmap, guiding crawlers to the right URLs and ensuring no key content is missed.

There are two main types of sitemaps:

• XML Sitemap: A file that includes URLs of your site and metadata such as the last modification date.
• Sitemap Index: A master file referencing multiple smaller sitemaps, often used for larger websites.

By keeping sitemaps up to date, you help Google maintain an accurate view of your site’s structure. On the other hand, if a sitemap becomes outdated or contains broken links, it’s usually better to fix and resubmit it, and to remove it only when the file itself is no longer needed.

When to Remove a Sitemap

Not every sitemap needs to be removed, but there are specific cases when it becomes necessary. Common situations include:

• Outdated sitemap: The file references URLs that no longer exist or have been redirected.
  
• Incorrect submission: A wrong or duplicate sitemap was accidentally added to Google Search Console.
  
• Restructured website: After a site migration or major redesign, the old sitemap may no longer reflect your site’s structure.
  
• Testing or temporary files: Sometimes developers submit test sitemaps that should be cleaned up later.
  

👉 If your sitemap is valid and up to date, there’s no need to remove it. Updating or replacing the file is often better than deleting it completely.

Steps to Remove a Sitemap From Google Search Console

Step 1: Log in to Google Search Console

To begin, sign in to your Google Search Console account. Make sure you have access to the correct property (domain or URL prefix) where the sitemap is submitted.

If you manage multiple websites, double-check that you’ve selected the right property from the dropdown list. This ensures you don’t accidentally change the wrong site.

Step 2: Go to the Sitemaps Section

Once inside the correct property, look at the left-hand menu in Google Search Console. From there, click on “Sitemaps” under the Indexing section.

This will open the Sitemaps report, where you can see all the sitemaps you’ve submitted, their status, last read date, and any errors detected by Google.

Step 3: Select the Submitted Sitemap

In the Sitemaps report, you’ll see a list of all the sitemaps you’ve submitted for your property. Locate the sitemap you want to remove.

Check carefully to ensure you’ve selected the correct one, especially if multiple sitemaps or indexes are listed. Removing the wrong sitemap could disrupt Google’s ability to crawl important pages on your site.

Step 4: Remove the Sitemap

After selecting the sitemap you want to remove, click on the three-dot menu (⋮) next to it. From the options provided, choose Remove sitemap.

Google Search Console will then delete the sitemap entry from your property. Keep in mind that this action only removes the sitemap submission — it does not delete the actual sitemap file from your server. If you no longer need the file, delete or update it directly on your website.

Stop Google Fetching the Old File (404/410)

Removing the submission in Search Console does not stop Google from requesting the file. This step complements that removal rather than replacing it: by making the old sitemap URL return a 404 (Not Found) or 410 (Gone) status code, you tell Google the file no longer exists.

• 404 Response: Tells Google the file cannot be found.
  
• 410 Response: More strongly indicates that the file has been permanently removed.

Over time, Google stops relying on the missing file, but the entry can stay in the Sitemaps report with a Couldn't fetch status until you remove it there too. This method is especially useful if you’ve permanently retired a sitemap and want to ensure search engines stop requesting it.

After Removal Verification

Once you’ve removed a sitemap, confirming that the changes have taken effect is important. Head back to the Sitemaps report in Google Search Console and check the list of submitted sitemaps. The one you removed should no longer appear.

Additionally, you can use the URL Inspection tool to check specific pages and ensure Google is still crawling your site correctly. Monitor the Page indexing report to verify that important URLs remain indexed without issues.

What Happens After You Remove a Sitemap

Many site owners expect removal to have a bigger effect than it does. Here is what actually changes, and what does not:

Changes	Does not change
The sitemap disappears from the Sitemaps report	Pages already in Google's index stay indexed
You stop seeing errors and stats for that file	The sitemap file stays live on your server
The file no longer counts as a submission from you	Google may still know the URL and fetch it occasionally

If you want Google to forget an old sitemap completely, run this short checklist once:

1. Remove the sitemap in Search Console (the steps above).
2. Delete the file from the server, or make its URL return a 404 or 410.
3. Open yourdomain.com/robots.txt and delete any Sitemap: line that still points to the old file, leaving only the current sitemap URL. Our free robots.txt tester shows what the file currently declares.
4. Check the Sitemaps report a week later to confirm the entry has not returned.

Fix or Remove? What Google Actually Reads in a Sitemap

Before you remove a sitemap for being "outdated", it helps to know how little of it Google uses. Google reads the URL (loc) and the last-modified date (lastmod). It ignores priority and changefreq entirely, so wrong values there are no reason to remove anything.

The lastmod value matters, but only while it is accurate. Google has said it stops trusting the date when a site sets it to the current time on every crawl or updates it without a real content change. So if your sitemap's problem is bad dates, duplicate URLs or redirected pages, fix the generator (plugin settings, excluded post types, canonical URLs) and resubmit the same address. Removal is for sitemaps whose URL itself is wrong, duplicated or no longer in use.

Replacing a Sitemap After Switching Plugins or Platforms

The most common reason to remove a sitemap is that its address changed. Typical cases:

• Switching SEO plugins. Yoast SEO and Rank Math both use /sitemap_index.xml, but All in One SEO uses /sitemap.xml and WordPress core uses /wp-sitemap.xml. After switching, open the new URL in your browser, submit it, then remove the old one.
• Moving to HTTPS or a new domain. Submit the new sitemap in the property for the new address. Keep the old property so you can watch the redirects being processed.
• Moving to Shopify. Shopify generates /sitemap.xml automatically for every store; you cannot edit or delete it from the store, so submit that address and remove the old WordPress entry once it shows Success.
• Blogger and other hosted platforms. Blogger also serves /sitemap.xml (and /sitemap-pages.xml for static pages). Hosted platforms generally publish one fixed sitemap URL, so the removal always happens on the Search Console side only.
• Rebuilding the site. If the new build uses a different sitemap URL, submit it first and remove the old entry only once the new one shows Success.

Submitting the new sitemap before removing the old one avoids a gap where Search Console shows no sitemap at all.

Why a Removed Sitemap Keeps Coming Back

If a sitemap you removed reappears in the report, check these causes:

• Another user submitted it. Look at Settings, Users and permissions to see who else has access, including agencies or former developers.
• A connected tool re-submitted it. Some SEO tools and plugins linked to Search Console can submit sitemaps automatically. Check their settings.
• It is still declared in robots.txt. Google discovers sitemaps from the Sitemap line in robots.txt, which is step 3 of the checklist above.

Once you have found and fixed the source, remove the sitemap again and check the report a week later. If it has not returned, the cleanup worked. Keep a short note of which sitemaps should be listed, so anyone managing the property knows the correct setup.

Conclusion

Removing a sitemap from Google Search Console is simple, but it should only be done when the file is outdated, incorrect, or no longer needed. By following the proper steps, verifying the removal, and keeping your sitemaps updated, you ensure that Google always has the most accurate picture of your website structure, which helps maintain healthy crawling and indexing.

Frequently asked questions

Will removing a sitemap deindex my pages?

No. Removing a sitemap from Search Console does not remove any page from Google's index. Google keeps indexed URLs and continues to find pages through internal links and other sources. The only change is that Google stops reporting on that sitemap. To remove specific pages from search, use a noindex tag, a 404 or 410 status, or the Removals tool.

Should I remove my sitemap if it shows errors?

Usually no. It is better to fix the file and resubmit it than to remove it. Errors in the Sitemaps report often come from a few bad URLs, a wrong domain version or a temporary fetch problem. Correct the sitemap on your site, then submit the same URL again so Google re-reads it. Remove it only if the URL itself is wrong or obsolete.

Can I remove a sitemap from a Domain property?

Yes. The Sitemaps report works the same way in Domain and URL-prefix properties. Open the property, go to Indexing and then Sitemaps, click the sitemap and choose Remove sitemap from the three-dot menu. You need full owner or full user permission. Restricted users can view the report but cannot add or remove sitemaps.

Does Google use the priority and changefreq values in my sitemap?

No. Google reads the URL and the lastmod date and ignores priority and changefreq. It only trusts lastmod when the date is accurate, so a sitemap that stamps every URL with the current time on each crawl teaches Google to disregard it. If your sitemap is "outdated" because of wrong dates, fixing the generator is better than removing the file.