How to Submit a Sitemap to Google: Step-by-Step
Submitting your sitemap to Google Search Console is the most reliable way to ensure Googlebot discovers every page on your site — not just the ones it stumbles upon through links. The process takes under five minutes, but doing it correctly and monitoring it afterward makes a real difference in how quickly new content gets indexed. Follow these steps in order to submit, verify, and maintain a healthy sitemap in Search Console.
Step 1: Verify your sitemap exists and is valid
Before submitting, open yoursite.com/sitemap.xml in your browser. If it displays XML content, it exists. If you get a 404, your sitemap has not been generated yet - check your CMS or sitemap plugin settings. Validate the XML format at validator.w3.org. Your sitemap should not show any validation errors.
Step 2: Set up Google Search Console if you have not already
Go to search.google.com/search-console and add your site as a property. Choose Domain property for full coverage across HTTP, HTTPS, www, and non-www. Verify ownership via DNS TXT record (add it at your domain registrar), HTML file upload, or meta tag in your site head. Domain property requires DNS verification.
Step 3: Navigate to Sitemaps
In Google Search Console, select your property from the dropdown. In the left sidebar, click Indexing, then Sitemaps. This shows all previously submitted sitemaps and their status.
Step 4: Enter your sitemap URL and submit
In the 'Add a new sitemap' field, enter the path to your sitemap - just the path after your domain, like sitemap.xml or sitemap_index.xml. Do not include the full domain - Search Console already knows it. Click Submit.
Step 5: Verify the submission was successful
After submitting, your sitemap should appear in the list with status Success. It shows the date last read, number of URLs discovered, and number of URLs indexed. If the status shows an error instead, click on the sitemap entry to see the specific error message.
Step 6: Monitor ongoing sitemap health
Check your Sitemaps report weekly for the first month after submission. Watch for: status changing from Success to error, a significant drop in URLs indexed vs discovered (may indicate quality issues), and warnings about specific URLs. If you update your site significantly, click the sitemap entry and use the Resubmit option to prompt Google to re-read your sitemap immediately.
Step 7: Use a sitemap index for large sites
If your site has more than a few hundred pages or multiple content types, use a sitemap index file instead of a single sitemap. A sitemap index is an XML file that lists multiple child sitemaps — for example, one for blog posts, one for product pages, one for categories. Submit only the sitemap index URL to Search Console. Each child sitemap can contain up to 50,000 URLs. This structure makes it easier to identify which section of your site has indexing problems and lets Google prioritize crawling by sitemap.
Step 8: Confirm which URLs Google actually indexed
After submitting, the Sitemaps report shows 'URLs discovered' but that number does not equal indexed pages. Use the Pages report in Search Console (Indexing then Pages) to see how many pages are actually indexed. Filter by 'Indexed, not submitted in sitemap' to find pages Google found but you have not included — these may need to be added. Filter by 'Submitted and indexed' to confirm your most important pages are in the index.
Step 9: Keep your sitemap up to date automatically
Static sitemaps go stale fast. Use a CMS plugin (Yoast, Rank Math, or All in One SEO for WordPress; or your framework's built-in generation) to auto-generate your sitemap so new pages appear immediately. For Next.js, use app/sitemap.ts to dynamically generate it. Avoid manually-maintained sitemaps unless your site rarely changes — a stale sitemap containing deleted pages wastes crawl budget and creates errors in Search Console that dilute signal from legitimate issues.
Step 10: Do not include low-value or non-canonical URLs
Your sitemap should be a curated list of the pages you most want Google to index, not an exhaustive dump of every URL your server can serve. Exclude paginated archive pages beyond page 1, faceted navigation URLs, internal search result pages, tag or category pages with thin content, and any page with a noindex tag. A leaner sitemap with high-quality URLs signals confidence to Google and improves the ratio of submitted URLs that actually get indexed.
Step 11: Resubmit after major site migrations
After a domain migration, HTTPS switch, URL restructure, or platform change, submit your new sitemap immediately in Search Console on the new property. Also use the Change of Address tool in Search Console if you migrated to a new domain — this tells Google to transfer your ranking signals. Do not delete your old Search Console property for at least 6 months after a migration. Monitor the new property's Sitemaps report daily for the first two weeks to catch crawl errors early.