XML Sitemap Generator: Free Tool + Complete Guide (2026) Meta

The One File That Decides Whether Google Finds Your Pages

You spend hours writing blog posts. You optimize titles. You fix your Core Web Vitals. You build links.

Then you wait.

Three weeks later, half your content still isn’t indexed.

This is one of the most common — and most preventable — problems in SEO. And in most cases, the fix takes under ten minutes.

The issue isn’t your content quality. It’s not your keyword research. It’s something far simpler: Google never found the pages in the first place.

Search engines crawl the web by following links. They start from pages they already know, hop to new ones, and gradually map out your site. But if a page is buried deep in your site structure — or if you launched it recently — Google might not stumble across it for weeks.

That’s exactly what a sitemap solves.

An XML sitemap is a file that lists every URL on your website. It tells Google: here are all my pages, here’s when I updated them, here’s what matters most. Instead of crawling blindly, Google follows your map.

The result: faster indexation, broader coverage, and more of your content appearing in search results.

This guide covers everything — what sitemaps are, how they work, how to generate one for any platform, and how to fix the errors that quietly kill your rankings.

Part 1: What Is an XML Sitemap and Why Does It Matter?

The Plain-English Explanation

An XML sitemap is a simple text file, formatted in XML code, that lists the pages on your website. You place it at yoursite.com/sitemap.xml — a location Google checks automatically when it visits your domain.

When Google finds your sitemap, it uses it as a crawling guide. Instead of relying purely on link-following to discover pages, it reads your sitemap and knows exactly what exists on your site.

Here’s what a basic sitemap looks like:

xml

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://yoursite.com/</loc>
    <lastmod>2026-04-01</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://yoursite.com/blog/seo-guide</loc>
    <lastmod>2026-03-15</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>

Each entry tells Google four things:

<loc> — The exact URL of the page
<lastmod> — When you last updated it
<changefreq> — How often it typically changes
<priority> — How important this page is relative to others on your site (0.0 to 1.0)

That’s the entire concept. A list of pages with metadata. Simple in theory, powerful in practice.

Does Google Actually Need a Sitemap?

No. Google can index a site without one.

But here’s the critical word: efficiently.

Without a sitemap, Google discovers your pages by following links. If your internal linking is strong and your site is well-established, this works reasonably well. But it has real limitations:

New pages don’t get found for weeks
Deep pages (3+ clicks from homepage) often get missed entirely
Pages with few internal links get crawled infrequently
After a site redesign, Google may not notice updated URLs quickly

With a sitemap, these problems largely disappear. Google sees all your pages, knows when they were updated, and can prioritize its crawling accordingly.

Google itself states in its documentation: “Using a Sitemap helps Google discover and crawl your site’s pages more efficiently and comprehensively.”

The practical impact: sites with proper sitemaps get new content indexed within 24–48 hours. Without a sitemap, the same content often waits two to four weeks.

In a competitive niche, four weeks is the difference between ranking first on a trending topic — and ranking after ten other sites that moved faster.

How Sitemaps Improve Search Visibility (The Real Mechanism)

A common misconception: sitemaps boost rankings directly.

They don’t. Google doesn’t look at your sitemap and rank you higher because it exists.

What sitemaps do is fix the conditions that prevent ranking:

1. More pages indexed = more keywords ranking If 30% of your content isn’t indexed, you’re missing 30% of your potential organic traffic. Those pages can’t rank for anything because Google doesn’t know they exist.

2. Faster indexation = faster ranking Content indexed today can start ranking this week. Content indexed in three weeks starts ranking in a month. Early rankings compound — older rankings build authority faster.

3. Better crawl budget utilization = priority pages crawled more often Google allocates a crawl budget to each site — a limit on how many pages it crawls per day. Without a sitemap, Google wastes budget crawling low-value pages. With a sitemap and proper priority settings, Google focuses its crawl on your most important content.

These three effects together produce the visibility improvements that site owners attribute to sitemaps. The mechanism is indirect, but the outcome is real.

Part 2: The XML Sitemap Framework — What to Include, What to Exclude

Pages That Belong in Your Sitemap

Not every page should appear in your sitemap. Including the wrong pages doesn’t just waste crawl budget — it actively dilutes the signal you’re sending Google about what matters on your site.

Include:

Homepage — Always. Priority 1.0.
Service and category pages — Your core navigation pages. Priority 0.8–0.9.
Blog posts and articles — Published, indexable content. Priority 0.6–0.8.
Product pages — For e-commerce sites. Priority 0.7–0.8.
Landing pages — Campaign pages you want indexed. Priority 0.7.
About, Contact, and key utility pages — Priority 0.5.

Exclude:

Login and account pages (/login, /dashboard, /account)
Search results pages (/search?q=...)
Admin and backend pages (/wp-admin, /admin)
Pages blocked by robots.txt (contradicting robots.txt with your sitemap creates confusion)
Duplicate content pages or URL parameter variations (?utm_source=email, ?ref=twitter)
Pages with a noindex meta tag (if you’ve told Google not to index it, don’t include it in your sitemap)
Soft 404 pages and thin content pages

The goal is a clean sitemap that tells Google: every URL in this file is worth crawling. If Google repeatedly finds low-quality or duplicate pages in your sitemap, it learns to trust your sitemap less over time.

The Priority System — Used Correctly

Priority is a hint, not a command. Google uses it as one signal among many. But used thoughtfully, it helps Google understand your site’s hierarchy.

Priority	Use For
1.0	Homepage
0.8–0.9	Main service pages, category pages, top-performing content
0.6–0.7	Regular blog posts, product pages, resource pages
0.5	Utility pages (About, Contact, FAQ)
0.3–0.4	Archive pages, older content with lower value

The critical mistake to avoid: marking every page as 1.0. If everything is “most important,” nothing is. Google’s crawlers are sophisticated enough to recognize inflated priorities, and they largely ignore them. Be honest about your hierarchy.

Update Frequency — Be Accurate, Not Optimistic

The changefreq attribute tells Google how often a page typically changes. Google treats this as a hint, not a schedule — it tracks actual change history and adjusts accordingly.

Value	Use For
`daily`	News sites, frequently updated feeds
`weekly`	Active blogs, regularly updated pages
`monthly`	Standard blog posts, product pages
`yearly`	About page, Privacy Policy, static content
`never`	Archived content that won’t change

If you mark a page as weekly but never update it, Google notices the discrepancy and stops trusting your frequency hints. Accuracy here builds long-term crawl credibility.

Part 3: How to Generate an XML Sitemap — Every Method Explained

Method 1: WordPress (The Easiest Setup)

WordPress doesn’t generate a sitemap by default, but the major SEO plugins handle this automatically and keep it updated.

Using Yoast SEO:

Install and activate Yoast SEO from your plugin directory
Go to Yoast SEO → Settings → Site features
Confirm “XML sitemaps” is toggled on
Your sitemap is live at yoursite.com/sitemap_index.xml

Yoast creates a sitemap index that references separate sitemaps for posts, pages, categories, and custom post types. Every time you publish new content, Yoast updates the sitemap automatically.

Using Rank Math:

Install Rank Math
Go to Rank Math → Sitemap Settings
Enable “Sitemap” in the modules
Configure which content types to include
Sitemap available at yoursite.com/sitemap_index.xml

Using All in One SEO:

Install All in One SEO
Navigate to All in One SEO → Sitemaps
Enable XML Sitemap
Configure settings and save

All three plugins produce sitemaps that meet Google’s specifications and update automatically. For most WordPress users, this is a two-minute setup with zero ongoing maintenance.

Method 2: Shopify

Shopify generates a sitemap automatically. You don’t need to do anything.

Your sitemap is at: yourstore.myshopify.com/sitemap.xml

Or if you have a custom domain: yourstore.com/sitemap.xml

Shopify’s sitemap automatically includes all published products, collections, pages, and blog posts. It updates whenever you add or remove content.

The only action you need to take: submit this URL to Google Search Console. Shopify generates the file — you just need to tell Google where it is.

Limitation: Shopify offers limited sitemap customization. You can’t manually adjust priorities or exclude individual pages through the dashboard. For stores with specific SEO requirements, third-party apps like “Sitemap & NoIndex Manager” extend this functionality.

Method 3: Wix

Wix automatically generates and maintains your sitemap.

Your sitemap is at: yoursite.wixsite.com/sitemap.xml or yourcustomdomain.com/sitemap.xml

Wix handles generation, updates, and even submits to Google automatically through its SEO setup. If you’ve completed Wix’s SEO Setup Checklist, your sitemap is likely already submitted.

To verify: visit your sitemap URL directly. If it loads an XML file listing your pages, it’s working.

Method 4: Blogger

Blogger also auto-generates sitemaps.

Your sitemap: yourblog.blogspot.com/sitemap.xml

One important limitation with Blogger: the auto-generated sitemap only includes your most recent 500 posts. If your blog has more than 500 posts, you need to submit additional sitemaps to Google Search Console that cover older content:

yourblog.blogspot.com/sitemap.xml?startIndex=1 (posts 1–500)
yourblog.blogspot.com/sitemap.xml?startIndex=501 (posts 501–1000)
yourblog.blogspot.com/sitemap.xml?startIndex=1001 (posts 1001–1500)

Submit each URL separately in Google Search Console.

Method 5: Custom-Built Websites

If your site isn’t built on a CMS with automatic sitemap generation, you have two solid options.

Option A: Online Sitemap Generator (For sites under 500 pages)

Visit a free XML sitemap generator tool
Enter your domain name
Configure crawl depth, priority settings, and change frequency
The tool crawls your site and generates sitemap.xml
Download the file
Upload it to your server’s root directory via FTP or your hosting file manager

The entire process takes 10–15 minutes.

Option B: Screaming Frog SEO Spider (For larger or complex sites)

Screaming Frog is the professional standard for technical SEO work. The free version crawls up to 500 URLs.

Download and install Screaming Frog
Enter your domain and run a crawl
Go to Sitemaps → XML Sitemap
Configure settings
Export sitemap.xml
Upload to server root

Screaming Frog gives you full control over what’s included, priority settings, and URL filtering — essential for larger sites.

Method 6: Manual Creation (Only for Very Small Sites)

If your site has fewer than 20 pages and you’re comfortable with XML, you can write a sitemap by hand. Use the format shown in Part 1 of this guide, save the file as sitemap.xml, and upload it to your root directory.

This is not recommended for most people. Generators are faster, more accurate, and don’t introduce syntax errors that break crawling.

Part 4: How to Submit Your Sitemap to Google Search Console

Generating a sitemap is only half the job. Google will eventually find it on its own — but submitting it directly through Google Search Console triggers crawling immediately and gives you monitoring data that’s invaluable for diagnosing issues.

Step-by-step:

Go to Google Search Console and sign in
Select your property (your website)
In the left sidebar, click Sitemaps (under the Index section)
In the “Add a new sitemap” field, enter your sitemap URL — typically sitemap.xml or sitemap_index.xml
Click Submit

Google will begin crawling your sitemap within 24 hours. After a few days, the Sitemaps report will show:

How many URLs were submitted
How many were indexed
Any errors or warnings

Also add your sitemap to robots.txt:

Open your robots.txt file (located at yoursite.com/robots.txt) and add this line:

Sitemap: https://yoursite.com/sitemap.xml

This ensures any crawler — not just Google — can automatically discover your sitemap without manual submission.

Submitting to Bing:

Google Search Console covers Google. For Bing (which also powers Yahoo search results), go to Bing Webmaster Tools, add your site, and submit your sitemap URL under the Sitemaps section.

Part 5: The 40 Questions Website Owners Ask About Sitemaps

Section A: Foundations

Q1: Do I actually need a sitemap if my site is small?

Yes — even for small sites. The common belief is that sitemaps only matter for large sites with thousands of pages. This is wrong.

A small site with 20 pages can still have pages that Google misses — especially if those pages aren’t well-linked internally. A sitemap guarantees that every page gets submitted for crawling, regardless of how deeply buried it is.

The setup takes five minutes. The benefit is permanent. There’s no scenario where having a sitemap hurts you.

Q2: How do I create an XML sitemap from scratch?

The fastest approach depends on your platform:

WordPress: Install Yoast SEO or Rank Math. Sitemap is generated automatically in minutes.
Shopify, Wix, Blogger: Already generated. Visit yourdomain.com/sitemap.xml to confirm.
Custom site: Use an online XML sitemap generator tool. Enter your domain, configure settings, download the file, upload to your root directory.
Manual (under 20 pages): Write the XML by hand using the format in Part 1. Not recommended for most users.

For 95% of website owners, a plugin or generator is the right choice. Manual creation introduces syntax errors that silently break crawling.

Q3: Where should my sitemap be located on my server?

Your sitemap must be in your root directory: yoursite.com/sitemap.xml

This is the standard location Google checks automatically. If you place it anywhere else, you’ll need to explicitly tell Google where to find it through Search Console or robots.txt — and some crawlers may miss it entirely.

Correct:

yoursite.com/sitemap.xml
yoursite.com/sitemap_index.xml (for sites using multiple sitemaps)

Wrong:

yoursite.com/blog/sitemap.xml
yoursite.com/files/sitemap.xml
yoursite.com/wp-content/sitemap.xml

For CMS platforms (WordPress, Shopify, Wix), the platform places the sitemap in the correct location automatically.

Q4: What is the maximum size for a sitemap?

Each sitemap file has a hard limit of 50,000 URLs and 50MB (uncompressed).

For most websites, a single sitemap file is sufficient. If your site exceeds either limit, you need to split the sitemap into multiple files and reference them through a sitemap index file.

Example sitemap index:

xml

<?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>
  <sitemap>
    <loc>https://yoursite.com/sitemap-pages.xml</loc>
  </sitemap>
</sitemapindex>

Submit the index file URL to Google Search Console. Google reads the index and crawls each referenced sitemap.

Q5: How often should I update my sitemap?

The answer depends on how frequently your content changes.

CMS sites (WordPress, Shopify, Wix): Your sitemap updates automatically every time you publish or edit content. No action required.
Daily publishers: Sitemap should update daily. Use a plugin or automated generation script.
Weekly publishers: Regenerate weekly. Set a calendar reminder.
Static sites with infrequent changes: Regenerate whenever you add or remove pages.

The most important rule: whenever you delete a page or change a URL permanently, update your sitemap immediately. Keeping dead URLs in your sitemap trains Google to trust your sitemap less over time.

Q6: Does having a sitemap improve my Google rankings?

Not directly. A sitemap file contains no keywords, no links, and no content that Google’s ranking algorithm evaluates.

What it does is remove the obstacles that prevent ranking. If your content isn’t indexed, it ranks for nothing. If new content takes four weeks to get indexed, competitors with faster indexation will rank first and build authority while you wait.

The practical impact of a properly implemented sitemap is that more of your content gets indexed and indexed faster — which translates to more pages appearing in search results, more keywords ranking, and more organic traffic. The mechanism is indirect, but the outcome is real and measurable.

Q7: What’s the difference between an XML sitemap and an HTML sitemap?

They serve completely different purposes.

An XML sitemap is written in machine-readable code. It’s for search engines, not humans. Users visiting your site never see it. Its purpose is to help crawlers discover and index your pages efficiently.

An HTML sitemap is a regular webpage on your site — a human-readable list of links organized by category or hierarchy. Its purpose is to help visitors navigate your site, especially on complex sites where the main navigation doesn’t expose all pages.

Best practice is to have both: the XML sitemap for Google, the HTML sitemap for your users. They’re not interchangeable, and having one doesn’t replace the need for the other.

Q8: Can I have more than one sitemap?

Yes — and for larger sites, you should.

Multiple sitemaps organized by content type is a common professional setup:

sitemap-posts.xml — All blog articles
sitemap-products.xml — All product pages
sitemap-pages.xml — Core website pages
sitemap-images.xml — Image sitemap for media-heavy sites

Each individual sitemap still follows the 50,000 URL / 50MB limit. A sitemap index file ties them all together, and you submit only the index URL to Google Search Console.

The benefit: cleaner organization, easier troubleshooting, and the ability to monitor indexation rates by content type through Search Console.

Q9: Should I use separate sitemaps for different content types?

For most small to medium sites: no. A single combined sitemap is simpler and equally effective.

Separate content-type sitemaps become genuinely useful when:

Your site has 10,000+ pages across different content categories
You want to monitor indexation rates separately for posts vs. products vs. pages
You have heavy image or video content that benefits from dedicated media sitemaps
You’re troubleshooting indexation issues and need to isolate problem areas

If you’re using WordPress with Yoast or Rank Math, separate sitemaps by content type are generated automatically as part of the sitemap index. You get the organizational benefit without any extra configuration.

Q10: What actually happens if my site doesn’t have a sitemap?

Google will still crawl your site — just less efficiently.

For a new site, missing a sitemap means Google may not discover it for weeks. For an established site with strong internal linking, the impact is smaller but still real: newly published pages take longer to get indexed, deep pages get missed, and crawl budget gets spent on lower-priority content.

The compounding effect is the real issue. If your competitors publish content today and get indexed within 24 hours, while your content waits three weeks — they’re building authority, accumulating links, and generating traffic while your equivalent content sits invisible. Over months and years, this indexation gap becomes a meaningful traffic gap.

Section B: Technical Deep Dive

Q11: How do I submit my sitemap to Google Search Console?

Go to search.google.com/search-console, select your property, click “Sitemaps” in the left menu, enter your sitemap URL, and click Submit.

Google typically begins crawling within 24 hours. Check the Sitemaps report after a few days to review your coverage data and identify any errors.

Also add your sitemap to robots.txt for automatic discovery by all crawlers:

Sitemap: https://yoursite.com/sitemap.xml

Q12: Should I submit my sitemap to Bing?

Yes, if search visibility beyond Google matters to you.

Bing powers both Bing Search and Yahoo Search. Submitting to Bing Webmaster Tools covers both. Visit bing.com/webmasters, add your site, and submit your sitemap URL under the Sitemaps section.

If your robots.txt file includes the Sitemap: directive, Bing’s crawler will also discover it automatically during its regular crawl of your robots.txt file.

Q13: What’s the relationship between my sitemap and robots.txt?

They work together but serve opposite functions.

robots.txt tells crawlers which pages to skip. A sitemap tells crawlers which pages to visit.

The critical rule: never include a URL in your sitemap that’s blocked by robots.txt. This creates a direct contradiction — you’re telling Google to crawl a page while simultaneously telling it not to. Google will report this as an error in Search Console and will not crawl the blocked page regardless of its inclusion in your sitemap.

Practical setup:

Use robots.txt to block admin pages, login pages, duplicate parameter URLs, and anything you don’t want indexed
Use your sitemap to include all canonical, indexable pages
Make sure there’s zero overlap between the two

Q14: How do image and video sitemaps work?

Standard XML sitemaps list web pages. Image and video sitemaps extend this to help Google discover and properly index media content.

Image sitemap format:

xml

<url>
  <loc>https://yoursite.com/blog/post-title</loc>
  <image:image>
    <image:loc>https://yoursite.com/images/featured-image.jpg</image:loc>
    <image:title>Descriptive image title</image:title>
    <image:caption>Brief description of what the image shows</image:caption>
  </image:image>
</url>

Image sitemaps improve your presence in Google Images search — meaningful if visual content is a traffic channel for your site. Video sitemaps work similarly and help video content appear in Google’s video search results.

For most sites, the easiest approach is using a plugin (Yoast SEO handles image sitemaps automatically) rather than building these manually.

Q15: How much does the priority setting actually matter?

Less than most people assume.

Google has stated publicly that priority values are treated as hints, not directives. Crawlers observe actual linking patterns, content quality, and historical crawl data. A page marked 1.0 in your sitemap but rarely linked to internally will still get crawled infrequently.

That said, priority settings are worth getting right. They contribute a small signal to crawl frequency decisions. More importantly, having accurate, honest priority settings (rather than inflating everything to 1.0) is a signal of sitemap quality — and Google’s internal systems do reward sitemaps that prove consistently reliable.

Mark what’s actually important to you. Use 1.0 only for your homepage or a handful of truly critical pages. Spread 0.7–0.8 across your main content. Use 0.5 for utility pages. This is more useful to Google than a flat priority structure.

Q16: What’s the difference between changefreq in my sitemap and when Google actually crawls?

Google ignores your changefreq value if it contradicts observed reality.

If you mark a page as weekly but the page hasn’t changed in eight months, Google’s systems notice the discrepancy. Over time, they’ll adjust their crawl frequency based on actual change history rather than your declared frequency.

Conversely, if you accurately declare monthly for a page that consistently changes monthly, Google comes to trust your declarations and can better allocate its crawl budget.

Accuracy matters more than optimism. Set changefreq to what actually happens, not what you wish would happen.

Q17: How do I handle duplicate URLs in my sitemap?

Don’t include them. Only the canonical version of a URL belongs in your sitemap.

Common sources of duplicate URLs to watch for:

Trailing slash variations: /blog/post and /blog/post/
UTM parameters: /page?utm_source=email
Session IDs: /page?sessionid=abc123
Print versions: /page?print=1
Pagination variations: /category?page=2

In addition to excluding duplicates from your sitemap, make sure you’re using canonical tags (<link rel="canonical">) on pages with multiple URL variations. This tells Google which version to index, complementing what your sitemap communicates.

Q18: Can a sitemap cover a subdomain?

Each subdomain needs its own sitemap.

If you run blog.yoursite.com separately from yoursite.com, they require separate sitemaps: blog.yoursite.com/sitemap.xml and yoursite.com/sitemap.xml. Submit each separately in Google Search Console under their respective properties.

You cannot include subdomain URLs in your main domain’s sitemap. Google’s sitemap protocol requires that all URLs in a sitemap must be on the same domain (or subdomain) as the sitemap file itself.

Q19: How does a sitemap affect crawl budget?

For most small to medium sites, crawl budget isn’t a concern — Google crawls them fully regardless. Crawl budget becomes a real issue for sites with tens of thousands of pages.

For large sites, a well-structured sitemap directly improves crawl budget efficiency. Without a sitemap, Google may spend a large portion of its daily crawl allocation on low-value pages (old pagination, parameter variations, thin archive pages). With a clean sitemap that excludes low-value URLs, Google focuses its crawl allocation on the pages that matter.

The practical recommendation for large sites: audit your sitemap regularly, remove low-value URLs, and let your sitemap guide Google toward your most important content.

Q20: Should I remove deleted pages from my sitemap?

Yes — and do it quickly.

When you permanently delete a page, it should return a 410 (Gone) or 404 (Not Found) status code. A URL in your sitemap that returns 404 when Google tries to crawl it is a sitemap error. Google Search Console will flag it, and repeated errors reduce Google’s trust in your sitemap overall.

Process for handling deleted pages:

Remove the URL from your sitemap
Ensure the old URL returns a proper 404 or 410 status
If the page moved to a new URL, set up a 301 redirect and add the new URL to your sitemap

For CMS sites, plugins handle deletion automatically. For manually managed sitemaps, build a habit of updating your sitemap every time you delete or move content.

Section C: Platform-Specific

Q21: Which WordPress plugin should I use for my sitemap?

All three major SEO plugins generate excellent sitemaps. The choice should be based on which plugin you’re already using for your broader SEO setup — there’s no benefit to running multiple plugins just for sitemaps.

Yoast SEO: Industry standard. Reliable, well-documented, generates a sitemap index with separate files for posts, pages, categories, and custom post types. Works out of the box with minimal configuration.

Rank Math: More feature-rich and slightly more configurable than Yoast. Generates the same quality of sitemap with more granular control over what gets included. Free version covers everything most sites need.

All in One SEO: Strong alternative with a clean interface. Comparable functionality to the other two.

For a new WordPress installation, Rank Math offers the best combination of features and control. For sites already using Yoast, there’s no meaningful reason to switch.

Q22: How do I set up a sitemap for a Shopify store?

You don’t need to. Shopify generates it automatically at yourstore.com/sitemap.xml.

Your job is to submit it to Google Search Console:

Log in to Google Search Console
Select your Shopify store property
Click Sitemaps
Enter sitemap.xml
Submit

Shopify’s sitemap automatically includes all published products, collections, blog posts, and standard pages. It updates whenever you make changes to your store.

For stores with complex SEO needs — hiding certain products from search, adding custom priority settings, managing large inventories — apps like “Sitemap & NoIndex Manager” or “SEO Manager” extend Shopify’s built-in functionality.

Q23: How do I set up sitemaps for Blogger?

Blogger generates your sitemap automatically at yourblog.blogspot.com/sitemap.xml.

If you’ve mapped a custom domain, it’s available at yourcustomdomain.com/sitemap.xml.

Important limitation for blogs with more than 500 posts: Blogger’s auto-generated sitemap only covers your 500 most recent posts. For larger blogs, submit multiple sitemaps to Google Search Console:

yourblog.com/sitemap.xml?startIndex=1
yourblog.com/sitemap.xml?startIndex=501
yourblog.com/sitemap.xml?startIndex=1001

Each covers a 500-post window. Submit all of them in Search Console to ensure complete coverage.

Q24: Does Wix handle sitemaps automatically?

Yes. Wix generates and maintains your sitemap at yoursite.com/sitemap.xml automatically.

If you completed Wix’s SEO Setup Checklist, your sitemap was likely submitted to Google during that process. To verify, visit your sitemap URL directly. If you see an XML file listing your pages, it’s active and working.

Wix automatically updates the sitemap when you publish or remove pages. No ongoing maintenance is required.

Q25: How do I generate a sitemap for a custom-built website?

Two reliable approaches:

Online generator (straightforward): Enter your domain into a free XML sitemap generator tool. The tool crawls your site, builds the sitemap file, and lets you download it. Upload the downloaded sitemap.xml to your server’s root directory via FTP or your hosting control panel.

Screaming Frog (professional approach): Download Screaming Frog SEO Spider (free up to 500 URLs). Run a crawl of your domain, then export an XML sitemap from the Sitemaps menu. This gives you full control over what gets included and how priorities are assigned.

After generating and uploading your sitemap, submit the URL to Google Search Console and add the Sitemap: line to your robots.txt file.

Q26: What’s the right approach for e-commerce sitemaps?

E-commerce sites have unique sitemap considerations because of the volume of product pages and the risk of including low-value URL variations.

What to include:

All published, in-stock product pages — Priority 0.8
All category and collection pages — Priority 0.7–0.8
Brand and filter landing pages (if they have unique, substantial content) — Priority 0.6
Core website pages — Priority 0.5

What to exclude:

Out-of-stock products with no content value
Faceted navigation and filter combinations (/shoes?color=red&size=10)
Sorting parameter variations (/products?sort=price_asc)
Cart, checkout, and account pages

For stores with 10,000+ products, separate sitemaps for products and categories improve both organization and troubleshooting capability. Most e-commerce platforms (Shopify, WooCommerce with Yoast) handle this separation automatically.

Q27: Can I generate a sitemap for a password-protected website?

Not through standard automated tools. Crawlers can’t access pages behind authentication walls, so any tool that works by crawling your site will only see your login page.

Practical solutions:

If using WordPress: Yoast SEO and Rank Math generate sitemaps by reading your database, not by crawling your site. They know all your pages regardless of password protection. Your sitemap will be accurate even on a protected site.

If on a custom build: Create the sitemap manually by listing all URLs in XML format. Or temporarily disable password protection, generate the sitemap with an online tool, then re-enable protection.

Important consideration: If your entire site is password-protected, Google can’t crawl or index it anyway. A sitemap won’t help until your content is publicly accessible.

Q28: How do I keep my sitemap updated when I publish new content?

CMS platforms handle this automatically. WordPress plugins (Yoast, Rank Math), Shopify, Wix, and Blogger all update sitemaps in real time when you publish.

For manually managed sitemaps, the responsible approach is to regenerate your sitemap every time you add or remove content, or at minimum monthly if you publish regularly. Set a calendar reminder — this is the kind of maintenance that’s easy to forget and costly when neglected.

Q29: How do I validate my sitemap and check for errors?

Google Search Console (most important): After submitting your sitemap, the Sitemaps report shows how many URLs were indexed, how many have errors, and what the specific error types are. This is the primary tool for ongoing monitoring.

Online XML Validators: Use a free XML sitemap validator tool to check your file for syntax errors before submitting. Upload your sitemap file or enter your sitemap URL. The validator checks for malformed XML, invalid URLs, missing required tags, and formatting issues.

Screaming Frog: The free version can analyze a submitted sitemap and identify URL-level issues including broken pages, redirect chains, and noindex conflicts.

Common errors to watch for:

URLs returning 404 or 301 status
Pages with noindex tags included in sitemap
URLs blocked by robots.txt
Malformed XML (missing closing tags, invalid characters)
Duplicate URLs

Q30: Do small websites actually benefit from sitemaps?

Yes — consistently.

The threshold myth (“sitemaps only matter above X pages”) persists because large sites see the most dramatic impact. But every site benefits from guaranteed page discovery and faster indexation.

A ten-page site might have all pages indexed without a sitemap. But a twenty-five-page site with a new blog section, several deep landing pages, and recent content is much more likely to have indexation gaps. A sitemap closes those gaps with five minutes of setup.

There’s no site size below which having a sitemap is a waste of time.

Section D: Troubleshooting

Q31: Google Search Console is showing sitemap errors. How do I fix them?

Start by reading the specific error message. Search Console tells you both the error type and the affected URLs.

“URL submitted in sitemap but not found (404)” The page was deleted or the URL changed. Remove it from your sitemap, regenerate, and resubmit. If the page moved, set up a 301 redirect and add the new URL to your sitemap.

“Submitted URL marked ‘noindex'” You have a noindex meta tag on the page, which directly conflicts with its inclusion in your sitemap. Decide: do you want this page indexed? If yes, remove the noindex tag. If no, remove it from your sitemap.

“URL blocked by robots.txt” Same conflict, different mechanism. Either remove the URL from your sitemap or remove the robots.txt block — depending on whether you want the page crawled.

“Duplicate URL” The same URL appears more than once in your sitemap. Deduplicate and regenerate.

After fixing errors, regenerate your sitemap, upload the clean version, and resubmit in Search Console.

Q32: I submitted my sitemap but Google still isn’t crawling it. What’s wrong?

Work through this checklist:

1. Verify the file is accessible. Open a browser and visit yoursite.com/sitemap.xml directly. If it doesn’t load, the file either wasn’t uploaded to the right location or your server has a configuration issue.

2. Check for XML errors. Run your sitemap through a validator. A single malformed tag can cause Google to reject the entire file silently.

3. Confirm you actually submitted it. Uploading the file to your server is not the same as submitting it to Search Console. Go to Search Console → Sitemaps → submit the URL.

4. Check robots.txt. Make sure your robots.txt isn’t accidentally blocking Googlebot or blocking access to the sitemap file itself.

5. Give it time. Google typically processes submitted sitemaps within 24–48 hours. If it’s been less than two days, wait before troubleshooting further.

Q33: My sitemap is showing a low indexation rate in Search Console. Why aren’t my pages getting indexed?

A low coverage rate doesn’t necessarily mean your sitemap is broken. There are several reasons Google crawls a page but chooses not to index it:

Thin content: Pages with minimal unique content frequently get crawled but not indexed. This isn’t a sitemap problem — it’s a content quality problem.
Duplicate content: If Google identifies a page as substantially similar to another on your site (or elsewhere), it may index only one version.
noindex tag present: Manually check the affected pages in Search Console using the URL Inspection tool.
Soft 404: Page returns a 200 OK status code but displays a “not found” or error message. Google treats these as low-quality.
Crawled but not indexed: Google sometimes crawls pages and decides they don’t meet the quality threshold for inclusion in its index.

Use Search Console’s URL Inspection tool on specific affected pages to see exactly what Google sees and why it made its indexation decision.

Q34: My sitemap file is over 50MB. How do I fix this?

Split it into multiple files and use a sitemap index.

Create separate sitemap files for different content types or date ranges, each under 50MB and 50,000 URLs. Then create a sitemap_index.xml file that references all of them:

xml

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://yoursite.com/sitemap-1.xml</loc>
    <lastmod>2026-04-01</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://yoursite.com/sitemap-2.xml</loc>
    <lastmod>2026-04-01</lastmod>
  </sitemap>
</sitemapindex>

Upload all files to your root directory. Submit only the index file URL to Google Search Console.

Professional tools like Screaming Frog handle this splitting automatically. If you’re managing sitemaps manually for a very large site, consider switching to an automated solution.

Q35: Can I have separate sitemaps for mobile and desktop?

No — and you don’t need to.

Google uses mobile-first indexing, which means it primarily evaluates your mobile site when determining how to crawl and rank your pages. But it treats mobile and desktop as the same website, not separate entities.

A single sitemap covers both. If you have a responsive design (which you should), one sitemap handles everything. If you have a separate m.yoursite.com subdomain for mobile, that subdomain would need its own sitemap — but this architecture is increasingly rare.

Q36: How do I keep certain pages out of search results without removing them from my site?

Use the noindex meta tag — don’t rely on excluding pages from your sitemap alone.

Add this to the <head> section of any page you want excluded from search results:

html

<meta name="robots" content="noindex">

Simply leaving a page out of your sitemap doesn’t guarantee Google won’t index it. If the page is linked to from anywhere on the web, Google can still find and index it through normal link-crawling. The noindex tag is the reliable mechanism.

Once you add noindex to a page, also remove it from your sitemap to keep your sitemap clean and accurate.

Q37: Should I include UTM parameters and tracking URLs in my sitemap?

Never. Your sitemap should contain only clean, canonical URLs.

UTM parameters (?utm_source=newsletter), referral tags (?ref=twitter), session IDs, and other tracking additions create duplicate URL variants. Including them in your sitemap tells Google these are separate pages worth indexing — which causes duplicate content issues and dilutes your indexation signals.

Standard practice: strip all parameters and include only the clean base URL.

✅ https://yoursite.com/blog/post-title
❌ https://yoursite.com/blog/post-title?utm_source=email
❌ https://yoursite.com/blog/post-title?ref=newsletter

Q38: How do I handle international sites with multiple languages in my sitemap?

Use hreflang annotations within your sitemap to tell Google about language and region variants of each page.

xml

<url>
  <loc>https://yoursite.com/en/article</loc>
  <xhtml:link rel="alternate" hreflang="en" href="https://yoursite.com/en/article"/>
  <xhtml:link rel="alternate" hreflang="es" href="https://yoursite.com/es/article"/>
  <xhtml:link rel="alternate" hreflang="fr" href="https://yoursite.com/fr/article"/>
  <xhtml:link rel="alternate" hreflang="x-default" href="https://yoursite.com/en/article"/>
</url>

This tells Google: this page exists in English, Spanish, and French, and here’s where each version lives. Google then shows the appropriate language version to users based on their location and language settings.

The x-default attribute points to the fallback version shown when no other language variant matches a user’s settings.

For multilingual WordPress sites, plugins like WPML and Polylang handle hreflang sitemap generation automatically.

Q39: How often should I regenerate my sitemap?

For CMS sites, this question doesn’t apply — your sitemap updates automatically.

For manually managed sitemaps:

Whenever you add new pages or delete existing ones — update immediately
Whenever you restructure your site’s URL architecture — regenerate completely
Minimum: once a month if you’re actively publishing content
For static sites that rarely change: once per quarter is sufficient

The habit that matters most: never delete a page or change a URL without updating your sitemap the same day. Stale sitemap data is one of the most common sources of Search Console errors.

Q40: What does Google’s official guidance actually say about sitemaps?

Google’s documentation states: “Google can usually discover most of your pages without a sitemap. However, using a Sitemap helps Google discover and crawl your site’s pages more efficiently and comprehensively.”

Beyond that general guidance, Google specifically recommends sitemaps for:

Large sites with many pages
New sites that haven’t accumulated many inbound links yet
Sites with rich media content (images, video) that should appear in specialized search results
Sites with deep architecture where some pages are poorly linked internally

In practice, Google’s recommendation is simple: there’s no downside to having one, and there are meaningful upsides. Every site should have a sitemap.

Part 6: Sitemap Best Practices — What Professional SEOs Actually Do

The Setup That Works

Professionals don’t just generate a sitemap once and forget it. They build a system that keeps the sitemap accurate over time and uses it as an ongoing diagnostic tool.

Step 1: Generate cleanly from the start Use your CMS plugin or a professional tool. Don’t manually write sitemaps for sites with more than 20 pages. The risk of syntax errors and missed pages isn’t worth it.

Step 2: Audit before submitting Before submitting to Google, run your sitemap through a validator. Fix any errors. Verify that every URL in the file loads correctly and returns a 200 status code.

Step 3: Submit through Search Console and robots.txt Submit via Search Console for immediate processing and monitoring. Add the Sitemap: directive to robots.txt for automatic discovery by all crawlers.

Step 4: Monitor coverage weekly for the first month After initial submission, check Search Console’s Sitemaps report weekly. Watch for coverage errors, unexpectedly low indexation rates, and warning messages. Most issues surface in the first two to four weeks.

Step 5: Quarterly sitemap audits Every quarter, review your sitemap for:

Dead URLs (pages that return 404)
Pages that have been moved without sitemap updates
Noindex conflicts
Pages that should be excluded but aren’t
New content sections that should be added

Step 6: Resubmit after major site changes If you redesign your site, restructure your URL architecture, or migrate to a new domain — regenerate your sitemap completely and resubmit to Search Console. Don’t assume the old sitemap transfers.

Common Professional-Level Optimizations

Separate sitemaps by content priority On large sites, having a dedicated sitemap for your most important content (core service pages, top products) and a separate sitemap for secondary content (blog posts, archive pages) lets you see at a glance whether Google is indexing your priority content at the expected rate.

Set accurate lastmod dates When you update a piece of content, update its lastmod date. Google uses this to decide whether a page is worth recrawling. Pages with stale lastmod dates get crawled less frequently.

Monitor coverage rate over time, not just at launch A coverage rate that’s slowly declining — where the number of indexed pages is dropping month over month — is a signal worth investigating. It could indicate a technical issue, a Google quality update affecting your content, or a noindex configuration that changed.

Connect Search Console data to your editorial calendar When you know your indexation speed (how long from publication to indexed), you can time content publishing to hit competitive trends before competitors. Sites with fast indexation can publish content two to three days before a trend peaks and rank first.

Part 7: Your Complete Sitemap Action Plan

If you’ve read this far and haven’t yet set up your sitemap, here’s exactly what to do.

Today (15 minutes): Check whether you already have a sitemap by visiting yoursite.com/sitemap.xml. If it loads, you have one. If not, generate one using your CMS plugin or an online tool.

This week: Submit your sitemap URL to Google Search Console. Add the Sitemap: directive to your robots.txt file. Submit to Bing Webmaster Tools if Bing traffic matters to your business.

After 7 days: Check Search Console for the initial coverage report. Review the number of submitted vs. indexed URLs. Look for any errors and fix them.

After 30 days: Review your full coverage data. If your indexation rate is below 70%, investigate the specific pages not getting indexed using the URL Inspection tool. Common causes: thin content, noindex tags, duplicate pages, or pages blocked by robots.txt.

Ongoing: For CMS sites, your work is done — the system maintains itself. For manually managed sitemaps, schedule a monthly regeneration and resubmission. Build the habit of updating your sitemap immediately whenever you delete or move pages.

The Takeaway

A sitemap is the clearest, most direct signal you can send Google about what exists on your website and what matters.

It doesn’t replace good content. It doesn’t substitute for strong internal linking or high-quality backlinks. But it eliminates the most basic failure mode in SEO: Google simply not knowing your pages exist.

Every page that isn’t indexed is invisible to search. A properly implemented sitemap is what stands between your content and that invisibility.

The implementation takes fifteen minutes. The benefit runs for as long as your website exists.

Generate your sitemap. Submit it to Google Search Console. Keep it current.

That’s the whole job. </parameter> <parameter name=”path”>/mnt/user-data/outputs/xml-sitemap-complete-guide.md</parameter>

XML Sitemap Generator The Complete Guide to Getting Every Page Indexed (2026)