Submitting Your First Sitemap in Google Search Console

You've shipped. Your site is live. Now Google needs to find it.

A sitemap is the fastest way to tell Google what pages exist on your domain. Without one, you're waiting for Googlebot to stumble across your content through backlinks or internal navigation. With one, you're handing Google a map.

This guide walks you through generating, submitting, and monitoring your sitemap in Google Search Console in under 15 minutes. You'll see crawl activity within 48 hours.

Prerequisites: What You Need Before You Start

Before you submit anything, confirm you have these three things in place.

A live domain. Your site must be publicly accessible at a real domain (not localhost, not an IP address). Google can't crawl what the internet can't reach.

Google Search Console access. You need a Google account and verified ownership of your domain in Google Search Console. If you haven't verified your domain yet, do that first. Verification takes 5 minutes via DNS record, HTML file, or Google Analytics. Google's verification process is straightforward—pick the method that matches your hosting setup.

A sitemap file. Most modern platforms generate sitemaps automatically. If you're on WordPress, Shopify, Webflow, Next.js, or any other framework, your sitemap likely already exists at /sitemap.xml or /sitemap-index.xml. If you built a custom site, you'll need to generate one. We'll cover both scenarios below.

If you're unsure whether your site has a sitemap, open a browser tab and visit yoursite.com/sitemap.xml. If you see XML code, you're done with step one. If you see a 404, jump to the "Generating Your Sitemap" section.

Generating Your Sitemap (If You Don't Have One Yet)

Most platforms handle this automatically. Here's what to check for your setup.

WordPress: Install Yoast SEO or Rank Math. Both generate sitemaps by default. Once installed, your sitemap appears at yoursite.com/sitemap.xml. No additional configuration needed.

Shopify: Your sitemap is automatically generated and lives at yoursite.myshopify.com/sitemap.xml. Shopify handles this for you. No action required.

Webflow: Webflow generates sitemaps automatically. Access it at yoursite.webflow.io/sitemap.xml (or your custom domain equivalent).

Next.js or static site generators: You'll likely need to generate a sitemap programmatically. The simplest approach is using a package like next-sitemap for Next.js or sitemap-generator for static builds. Install, configure to point to your domain, run the build, and your sitemap appears in your public folder.

If you're on a custom stack without automatic sitemap generation, use a free tool like XML-Sitemaps.com. Enter your domain, let it crawl your site, download the generated sitemap.xml file, and upload it to your root directory via FTP or your hosting control panel.

Google's official documentation on building and submitting a sitemap covers XML format requirements in detail if you need to hand-code one. For most founders, though, automated generation is faster and less error-prone.

Step 1: Open Google Search Console and Select Your Property

Go to Google Search Console and sign in with the Google account you used to verify your domain.

You'll see a list of verified properties on the left sidebar. Click the property that matches your domain. If you only have one domain verified, it will be pre-selected.

If you see a dropdown arrow next to your domain name, click it to confirm you're in the correct property. You might have both example.com and www.example.com as separate properties in GSC. Submit your sitemap to both if they're set up as separate properties. Most modern sites use one canonical property (usually with www), but verify your setup to be sure.

Once you've selected the correct property, you're ready to move to the next step.

Step 2: Navigate to the Sitemap Section

On the left sidebar, scroll down and click "Sitemaps" under the "Index" section. You'll see a page titled "Sitemaps" with a button labeled "Add a new sitemap" in the top right.

If you've never submitted a sitemap before, this section will be empty. That's normal. You're about to fix that.

Click "Add a new sitemap."

Step 3: Enter Your Sitemap URL

A text field will appear asking you to enter your sitemap URL. This is where precision matters.

Enter the full URL to your sitemap file. For most sites, this is:

https://yoursite.com/sitemap.xml

Replace yoursite.com with your actual domain. Include the https:// protocol. If your site uses www, include it: https://www.yoursite.com/sitemap.xml.

If you have a sitemap index file (common on large sites with multiple sitemaps), the URL might be:

https://yoursite.com/sitemap-index.xml

If you're unsure which URL to use, open a new browser tab and visit https://yoursite.com/sitemap.xml. If you see XML content with <urlset> or <sitemapindex> tags, you've found the right URL. If you see a 404, check your sitemap file location or regenerate it using the steps above.

Paste the correct URL into the text field and click "Submit."

Step 4: Confirm Submission

Google will process your submission in real-time. You'll see one of three outcomes:

Success. A green checkmark appears next to your sitemap URL with the status "Success." Your sitemap has been accepted and queued for crawling. This is what you want to see.

Couldn't fetch. A red error appears saying Google couldn't fetch your sitemap. This usually means:

The URL is incorrect (typo or wrong path)
Your site isn't publicly accessible
Your hosting provider is blocking Googlebot
Your sitemap file doesn't exist at that location

Double-check the URL. Visit it in your browser to confirm it returns XML, not a 404. If it's accessible to you but Google can't reach it, contact your hosting provider to whitelist Googlebot's IP range.

Couldn't parse. Google fetched the file but couldn't read it. This means your sitemap XML is malformed. Common issues include:

Missing XML declaration at the top (<?xml version="1.0" encoding="UTF-8"?>)
Incorrect namespace declarations
Invalid URL encoding (special characters not properly escaped)

If you used an automated tool or plugin to generate your sitemap, regenerate it and try again. If you hand-coded it, validate it against Google's sitemap format spec or use an online XML validator.

Once you see the green success message, your sitemap is submitted. You're done with the technical work.

What Happens in the First 48 Hours

After submission, Googlebot begins crawling the URLs listed in your sitemap. You won't see immediate ranking changes—that comes later, after Google indexes your pages and evaluates their relevance.

Here's what you can expect to see in Google Search Console over the next two days:

Within 1-4 hours: Googlebot starts fetching your sitemap and begins crawling the URLs you listed. You'll see activity in the "Coverage" report under the "Index" section. Some URLs will show as "Discovered – currently not indexed" or "Crawled – currently not indexed." This is normal. Crawling and indexing happen in stages.

Within 24 hours: Google has crawled most of your URLs. The Coverage report updates to show how many pages were crawled, how many are indexed, and any crawl errors encountered. If you have 50 pages, expect 40-50 of them to show crawl activity within 24 hours. Larger sites (100+ pages) may take longer, but Googlebot prioritizes sitemapped URLs.

Within 48 hours: You'll see a significant portion of your pages in the "Indexed" section of the Coverage report. Not all pages will be indexed immediately—Google evaluates quality, uniqueness, and relevance before adding pages to its index. Pages that are thin, duplicate, or low-quality may stay in "Crawled – currently not indexed" status for weeks or longer.

Check your Coverage report daily for the first week. Look for any error categories that appear repeatedly. Common issues include:

Crawl errors: Usually DNS issues or temporary server problems. Rare on stable hosting.
Redirect errors: Pages that redirect to other URLs. Check if these are intentional.
Noindex: Pages you've marked with <meta name="robots" content="noindex">. These won't be indexed and shouldn't be in your sitemap.
Soft 404: Pages that return a 200 status but have little or no content. Thin pages Google doesn't deem indexable.

Most of these resolve on their own as Google re-crawls. If you see a persistent error affecting more than 5% of your pages, investigate and fix the root cause.

Pro Tip: Monitor Crawl Stats

Google Search Console has a "Crawl stats" report (under "Settings") that shows how much of your site Googlebot is crawling daily. After sitemap submission, you'll see a spike in crawl requests.

If you submit a sitemap with 100 URLs and see only 5-10 crawl requests in the stats, Google may not have discovered your sitemap yet. Wait 24 hours and check again. If crawl activity remains flat after 48 hours, verify your sitemap was actually submitted successfully (check the Sitemaps section for the green checkmark).

Crawl stats also help you understand if your site's crawl budget is being wasted on low-value pages. If Googlebot is spending time crawling admin pages, login pages, or duplicate content, you can exclude those URLs from your sitemap or add a robots.txt rule to prevent crawling.

Common Mistakes to Avoid

Submitting a sitemap with broken links. Every URL in your sitemap should return a 200 status code. If 30% of your URLs return 404s, Google marks them as "not found" and stops crawling them. Before submitting, test a sample of URLs from your sitemap in your browser or use a tool like Screaming Frog to validate them. This takes 10 minutes and saves you weeks of crawl waste.

Including noindex pages in your sitemap. If a page has <meta name="robots" content="noindex">, don't include it in your sitemap. Google will crawl it, see the noindex tag, and skip indexing it anyway. This wastes crawl budget. Remove noindex pages from your sitemap or remove the noindex tag. Pick one.

Forgetting to submit to both www and non-www versions. If you have your domain set up as both example.com and www.example.com in GSC as separate properties, submit your sitemap to both. Google treats them as separate domains. Submitting to only one means the other property won't get crawl signals from your sitemap.

Submitting a sitemap with thousands of low-quality pages. If your site has auto-generated pages with thin content (like tag pages with 2-3 posts each, or user-generated pages with minimal text), consider excluding them from your sitemap. Focus Googlebot's crawl budget on your high-value content. You can always add these pages back later if they gain traction.

Not updating your sitemap when you publish new content. If you publish a new blog post, it won't appear in your sitemap automatically (unless your CMS regenerates it). Most modern platforms regenerate sitemaps on each new publish, but verify this is happening. You can check by visiting /sitemap.xml a few hours after publishing a new page. If the new URL isn't there, your sitemap generation is broken.

Integrating Sitemap Submission Into Your SEO Workflow

Submitting a sitemap is a one-time task, but monitoring it should be part of your weekly SEO routine. If you're following the first 100 days of SEO playbook for founders, sitemap submission happens in week one, right after your domain audit and before you start content creation.

For busy founders shipping in week one, sitemap submission takes 10 minutes and unblocks everything else. You can't get organic visibility without indexing, and you can't get indexed without a sitemap (or backlinks, but that's slower).

If you're running a 30-day SEO sprint, submit your sitemap on day one. Spend the next 29 days creating content and building backlinks while Googlebot crawls and indexes your pages in the background. By day 30, you'll have indexed pages ready to rank.

For Shopify store owners, sitemap submission is part of the technical audit. Shopify generates sitemaps automatically, so you're just confirming it exists and submitting it to GSC. This takes 5 minutes and is non-negotiable before you start product page optimization.

If you're turning Notion public pages into ranked content, you'll need to generate a sitemap for your Notion pages (Notion doesn't do this automatically) and submit it to GSC. This ensures your Notion content gets crawled and indexed.

Automating Sitemap Updates

Once your sitemap is submitted, you need it to stay fresh. Every time you publish new content, your sitemap should update automatically.

WordPress: Yoast and Rank Math update sitemaps on every new post publish. No action needed.

Shopify: Shopify regenerates sitemaps in real-time. New products appear in the sitemap within minutes of publishing.

Next.js: If you're using next-sitemap, regenerate your sitemap as part of your build process. Every time you deploy, the sitemap updates. This is automatic if you've configured it correctly.

Custom sites: If you're using a custom stack, set up a cron job to regenerate your sitemap daily or weekly. This ensures new pages are discoverable by Google within 24 hours of publishing.

If your sitemap isn't updating automatically, Google will only crawl the URLs that were in it at submission time. New content you publish won't appear in your sitemap, and Googlebot won't find it until it discovers backlinks or internal navigation.

Verifying Your Sitemap Is Working

After 48 hours, check these three things to confirm your sitemap submission is working:

1. Check the Sitemaps report in GSC. Go to Sitemaps and look for your submitted URL. You should see:

A green checkmark next to "Submitted sitemap"
The date and time of submission
The number of URLs in your sitemap
The number of URLs indexed from your sitemap

If your sitemap shows 100 URLs but only 20 are indexed, investigate why. Common reasons include:

Pages are noindexed
Pages are canonicalized to other URLs
Pages have duplicate content
Pages are low-quality or thin

2. Check the Coverage report. Go to Coverage and look at the breakdown:

"Valid" or "Indexed": Pages Google has indexed
"Crawled – currently not indexed": Pages Google crawled but didn't index
"Excluded": Pages you've excluded via robots.txt or noindex tags
"Error": Pages with crawl errors

You want to see the majority of your pages in "Valid" or "Indexed." If more than 20% are in "Crawled – currently not indexed," your pages may be too thin or duplicate.

3. Check the URL Inspection tool. Pick a few URLs from your sitemap and inspect them individually. In GSC, search for a URL and click "Inspect URL." You'll see:

Whether the page is indexed
Whether Google can render it (important for JavaScript-heavy sites)
Any crawl or indexing issues
The canonical URL (if different from what you submitted)

If a page shows "Discovered – currently not indexed" in the URL Inspection tool, Google found it but hasn't indexed it yet. Wait a few more days. If it still shows this status after a week, the page likely has an issue preventing indexing (thin content, noindex tag, canonicalization, etc.).

What Comes After Sitemap Submission

Getting your pages indexed is step one. Ranking them is step two.

After your sitemap is submitted and your pages are indexed, focus on:

Content creation. Write content that targets keywords your audience is searching for. Use a keyword roadmap to prioritize which pages to create first. Don't wait for perfect indexing before you start writing—submit your sitemap and begin content work in parallel.

Backlink building. Indexed pages don't rank without authority signals. Backlinks are the primary authority signal Google uses. Reach out to relevant sites, publications, and communities to link to your content. This is slow but necessary.

On-page optimization. Make sure your indexed pages have proper title tags, meta descriptions, heading hierarchy, and internal linking. These don't move the ranking needle alone, but they compound over time.

Technical health. Monitor your crawl stats, fix broken links, and ensure your site loads fast. Technical issues don't prevent indexing, but they slow crawling and hurt rankings.

If you're optimizing a Shopify store, Bubble app, or Framer site, these platforms have platform-specific optimization steps beyond sitemap submission. Follow the platform-specific guides after you've submitted your sitemap.

Sitemap Submission for Multi-Site Setups

If you have multiple domains (e.g., a main site and a blog subdomain, or multiple regional versions), submit a sitemap for each domain separately in GSC.

If you have a single domain with thousands of pages, you can break your sitemap into multiple files using a sitemap index. A sitemap index is a file that lists other sitemaps. For example:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://yoursite.com/sitemap-posts.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://yoursite.com/sitemap-products.xml</loc>
  </sitemap>
</sitemapindex>

Submit the index file (usually at /sitemap-index.xml) to GSC. Google will crawl both child sitemaps and index all URLs from both files.

Most modern platforms handle this automatically if you have more than 50,000 URLs. WordPress, Shopify, and Next.js all generate sitemap indexes by default on large sites.

Troubleshooting: When Sitemap Submission Fails

If you're seeing errors after submission, here's how to fix them.

"Couldn't fetch sitemap." Google can't reach your sitemap URL. Verify:

The URL is correct and accessible in your browser
Your hosting provider isn't blocking Googlebot
Your site's SSL certificate is valid (HTTPS errors prevent crawling)
Your robots.txt isn't blocking the sitemap path

"Couldn't parse sitemap." Your XML is malformed. Validate it using an online XML validator or regenerate it using your platform's built-in tool.

"Sitemap index file contains invalid sitemap location." One of the URLs in your sitemap index is malformed or inaccessible. Check each child sitemap URL to ensure it returns valid XML.

"Large number of pages not indexed." This is normal initially. Google indexes pages gradually. If 80% of your pages are still "not indexed" after 2 weeks, investigate:

Are pages noindexed?
Do pages have duplicate content?
Are pages too thin (under 300 words)?
Are pages behind a login?

Fix the root cause (remove noindex tags, add unique content, expand thin pages) and resubmit your sitemap.

Key Takeaways

Submitting your first sitemap takes 10 minutes and unblocks organic visibility for your entire site. Here's what you need to do:

Verify your sitemap exists. Visit /sitemap.xml on your domain. If it doesn't exist, generate one using your platform's built-in tool or a free generator.
Open Google Search Console and select your property. You must have verified domain ownership first.
Navigate to Sitemaps and click "Add a new sitemap." Enter your sitemap URL (usually https://yoursite.com/sitemap.xml) and submit.
Wait for the green checkmark. This confirms Google accepted your sitemap.
Monitor Coverage and Crawl Stats for 48 hours. You'll see Googlebot crawling your URLs and indexing your pages. This is normal and expected.
Keep your sitemap updated. Most modern platforms do this automatically, but verify that new content appears in your sitemap within 24 hours of publishing.
Focus on content and backlinks next. Indexing is table stakes. Ranking requires quality content and authority signals.

If you're shipping a new product or launching a startup, sitemap submission should happen before you do anything else in SEO. It's the fastest way to get Google's attention and start building organic visibility from day one. Within 48 hours, you'll have indexed pages. Within 30 days, you'll have ranked pages (if your content is good). Within 90 days, you'll have meaningful organic traffic.

Start with the sitemap. Everything else follows.