A sitemap is a machine-readable file that lists the important, preferred URLs on a website so search engines can discover them more easily. An XML sitemap can include accurate last-modified dates and alternate-language relationships, but submitting a sitemap is only a crawling and discovery hint—not a guarantee that Google or Bing will crawl, index, or rank every listed page.

For most websites, the first step is not writing XML by hand. Check whether your content-management system already generates a sitemap, confirm that the file contains only public canonical pages, and submit the sitemap or sitemap index through Google Search Console and Bing Webmaster Tools.

Guide Helped? Tip Us

Key takeaways

  • An XML sitemap is a list of important absolute URLs that helps search engines discover pages, but it does not guarantee crawling, indexing, or ranking.
  • Google says a sitemap may not be necessary for a small site of approximately 500 or fewer search-worthy pages when important pages are comprehensively linked internally.
  • A sitemap file can contain up to 50,000 URLs or 50 MB uncompressed; larger sites need multiple files linked through a sitemap index.
  • Include canonical, public, indexable URLs and exclude redirects, errors, duplicate variants, noindex pages, and staging or utility URLs.
  • WordPress, Wix, and Shopify commonly generate sitemaps automatically, so most beginners do not need to create XML manually.
  • Google Search Console and Bing Webmaster Tools provide free ways to submit a sitemap and monitor processing problems.

What is a sitemap?

A sitemap is a file that identifies important URLs on a website for search-engine crawlers. The most common type is an XML sitemap, a machine-readable document that can also provide optional information such as when a page was meaningfully modified or which alternate-language versions correspond to one another.

A sitemap is primarily a discovery and crawling aid. Internal links remain essential: internal links are the roads crawlers travel, while a sitemap is an index that points out important destinations. Google’s sitemap overview explains that sitemaps are particularly useful for large or complex websites, new sites with few external links, sites with isolated pages, and sites containing substantial video, image, or news content.

A sitemap is not a visual map of a website’s menus or page hierarchy. A sitemap is also not a ranking file, a replacement for internal linking, or a command that forces a search engine to include pages in its index.

What is the difference between XML and HTML sitemaps?

An XML sitemap is mainly for search engines. An HTML sitemap is a human-readable webpage containing links to sections or pages on a site. An HTML sitemap can help visitors and may strengthen internal linking, but an HTML sitemap is not automatically a substitute for an XML sitemap.

Type Primary audience Typical use
XML sitemap Search-engine crawlers List preferred URLs and optional metadata
Sitemap index Search-engine crawlers Point to multiple sitemap files on a large site
Plain-text sitemap Search-engine crawlers List one absolute URL per line
RSS or Atom feed Search-engine crawlers Help expose recently updated content where appropriate
HTML sitemap People and crawlers Provide a linked, user-facing directory of pages

Google supports XML, plain-text, RSS, and Atom formats depending on a site’s needs. Google’s sitemap creation documentation also covers specialized sitemap information for images, videos, news content, and alternate-language versions.

How does a sitemap help search engines?

A sitemap helps search engines discover new or updated URLs that may be difficult to find through ordinary crawling. The benefit is greatest when a site has deep archives, JavaScript-generated navigation, isolated pages, many product URLs, or content that changes frequently.

The search process has several distinct stages:

  1. Discovery: A crawler learns that a URL exists from a sitemap, internal link, external link, feed, or another source.
  2. Crawling: The crawler requests the URL and examines the response.
  3. Processing: The search engine evaluates the content, canonical signals, rendering, structured data, and other technical information.
  4. Indexing: The search engine decides whether the page belongs in its searchable index.
  5. Ranking: The search engine determines where the indexed page may appear for a query.

A sitemap primarily supports discovery and supplies structured hints. A sitemap does not guarantee any of the later stages. Google’s crawling and indexing FAQ states that a sitemap does not guarantee indexing or increase ranking.

A sitemap can also help a site owner monitor technical health. Google Search Console can report whether Google accessed a submitted sitemap and whether Google encountered processing errors. Sitemap data is especially useful when compared with internal links, canonical tags, HTTP status codes, robots.txt rules, and indexing reports.

Does your website need a sitemap?

Your website may not need a sitemap if the site is small, important pages are comprehensively linked internally, and the site has few or no important image, video, or news pages. Google’s guidance uses approximately 500 pages or fewer, counting only pages that should appear in search, as a practical small-site example.

Website situation Practical sitemap priority Reason
Small brochure site with strong navigation Lower Search engines may already discover every important page through internal links.
New site with few external links High A sitemap gives crawlers a structured list while the site builds its link profile.
Large ecommerce catalog High Many product, collection, and category URLs can be difficult to discover consistently.
News, video, or image publisher High Specialized sitemap information can help expose relevant content.
Multilingual or international site High Language and regional URL relationships require careful, consistent signals.
Site with severe server, quality, or canonical problems Secondary A sitemap cannot repair inaccessible pages, duplicate content, poor content, or incorrect canonicalization.

A sitemap is usually harmless and convenient when a CMS creates one automatically. The distinction is between need and benefit: a small, well-linked site may function without a sitemap, while a sitemap can still make discovery and diagnostics easier.

What should a sitemap include?

A sitemap should include the canonical, public, indexable URLs that the site owner wants search engines to consider for search results. Sitemap contents should agree with canonical tags, internal links, redirects, and indexing directives.

Include these URLs

  • Canonical URLs preferred for search results.
  • Public pages that return a successful, accessible response.
  • Important product, category, service, article, and landing pages.
  • Meaningfully updated pages with accurate modification dates.
  • Preferred language or regional versions where the site supports them.
  • Important media or specialized content when the relevant sitemap format is appropriate.

Exclude these URLs

  • URLs that redirect to another destination.
  • Pages returning 4xx or 5xx errors.
  • Duplicate URL variants and non-canonical duplicates.
  • Pages marked noindex.
  • Login pages, carts, internal search results, filters, and thin utility pages unless there is a specific reason to expose them.
  • Password-protected, firewall-blocked, staging, test, preview, or development URLs.
  • Temporary or parameter-heavy duplicates.

If a page is intentionally marked noindex, the page will usually not belong in the sitemap. Some CMS platforms and SEO plugins automatically exclude noindex content; Yoast documents this behavior in its WordPress XML sitemap guidance.

What does an XML sitemap look like?

A valid XML sitemap uses a container element, one URL entry, and an absolute URL in each required location. This short example contains one page and an optional last-modified date:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.example.com/guide/</loc>
    <lastmod>2026-08-10</lastmod>
  </url>
</urlset>
Element Purpose Requirement or caution
<urlset> Document container Wraps the URL entries.
<url> One URL record Contains information about one location.
<loc> The URL Required; use a fully qualified absolute URL such as https://example.com/about/.
<lastmod> Last meaningful modification date Optional; use only when the value is accurate and consistently verifiable.
<changefreq> Suggested change frequency Do not treat this as a Google crawl-control or ranking signal.
<priority> Suggested relative priority Google ignores this field as a meaningful ranking control.

Google’s official sitemap format guidance says that URLs must be fully qualified and absolute. Google may use lastmod when the value is accurate and consistently verifiable, but Google ignores priority and changefreq. The official sitemap protocol provides the broader XML specification.

How large can a sitemap be?

A single sitemap file can contain up to 50,000 URLs or be up to 50 MB uncompressed. If a site exceeds either limit, split the URLs across multiple sitemap files and create a sitemap index.

A sitemap index points crawlers to the individual files; the index does not replace those files:

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

Sitemap files should use UTF-8 encoding. A large ecommerce site might separate product, collection, blog, and page URLs, while a publisher might separate content by type or date.

Where can you find your sitemap?

The conventional filename is not mandatory. Start with the domain root and check the common paths below:

  • https://example.com/sitemap.xml
  • https://example.com/sitemap_index.xml
  • https://example.com/wp-sitemap.xml for WordPress core

Also check the following locations:

  1. Open /robots.txt and look for a line such as Sitemap: https://example.com/sitemap.xml.
  2. Review the CMS settings or SEO-plugin settings.
  3. Check Google Search Console’s Sitemaps report for previously submitted files.
  4. Check Bing Webmaster Tools if the site has already been added there.

Google recommends placing a sitemap at the site root where possible. A sitemap can use another valid path, but directory scope can matter when the sitemap is discovered through normal crawling rather than submitted directly. The robots.txt specification allows one or more sitemap locations to be declared with the Sitemap field.

How do you create a sitemap?

For most beginners, the best way to create a sitemap is to let the CMS generate and update it automatically. Manual XML creation is suitable for a small static site or a controlled test, but manual maintenance becomes error-prone as URLs change.

How do you create a sitemap in WordPress?

WordPress commonly provides a core sitemap at https://example.com/wp-sitemap.xml. A WordPress SEO plugin may instead provide an index at https://example.com/sitemap_index.xml. Identify the authoritative sitemap before submitting one; do not automatically submit both the WordPress core sitemap and a plugin-generated sitemap.

For Yoast SEO, use this current settings path:

  1. Open the WordPress Dashboard.
  2. Select Yoast SEO.
  3. Select Settings.
  4. Open Site features.
  5. Under Technical SEO, turn XML sitemaps on.

Yoast automatically updates its sitemap and excludes content types configured as noindex. Buying a plugin solely for sitemap generation is usually unnecessary because WordPress core can generate one, but a plugin may be useful when its broader SEO controls justify it.

How does Wix generate a sitemap?

Wix automatically maintains a sitemap index at https://example.com/sitemap.xml. Wix says the index can contain separate files for pages, products, blog posts, events, multilingual content, and other site features, and the files update when site content changes. Wix also documents automatic submission through its SEO Setup Checklist. See Wix’s sitemap documentation for platform-specific behavior.

How does Shopify generate a sitemap?

Shopify automatically generates https://example.com/sitemap.xml at the store’s domain root. The generated structure can link to separate product, collection, blog, and webpage sitemaps, and Shopify says the files update as store content changes. Shopify’s official sitemap instructions explain how to locate the file.

How do you create a sitemap for a static or custom website?

Use the site’s build process, database, CMS, or a reputable automated generator to produce a UTF-8 sitemap containing only canonical, public, indexable URLs. Developers should validate the generated XML, check the HTTP response, and make sure the file remains available after deployments. For a very small static site, a hand-maintained file can work, but every URL change creates another opportunity for stale or invalid entries.

How do you submit a sitemap to Google?

Submit a sitemap in Google Search Console using Search Console → Sitemaps → Add a new sitemap → Submit.

  1. Open Google Search Console.
  2. Select the correct verified property.
  3. Open Sitemaps.
  4. Enter the sitemap path or full sitemap URL.
  5. Select Submit.
  6. Review the status and processing errors.
  7. Check again later rather than repeatedly submitting the same unchanged file.

The property must match the site and URL scope you intend to manage. Differences in protocol, subdomain, or path can create confusion even when the sitemap opens successfully in a browser.

You can also make the sitemap discoverable through robots.txt:

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

Google describes sitemap submission as a hint. Submission does not guarantee that Google will download the file, crawl every listed URL, index the URLs, or rank the pages.

How do you submit a sitemap to Bing?

Submit a sitemap through Bing Webmaster Tools after adding and verifying the site. Bing’s sitemap documentation describes a Sitemaps area for submitted, imported, and organically discovered sitemap files.

  1. Add and verify the site in Bing Webmaster Tools.
  2. Open the Sitemaps section.
  3. Submit the sitemap URL or sitemap index.
  4. Review processing status and reported errors.
  5. Keep the sitemap available and declare it in robots.txt where appropriate.

Bing supports sitemap discovery through robots.txt under the broader robots specification. Bing submission is useful for sites seeking visibility in Bing and Microsoft search experiences, but Bing Webmaster Tools does not replace Google Search Console when Google is the primary traffic source.

What is the difference between a sitemap and robots.txt?

A sitemap tells crawlers about URLs the site considers important, while robots.txt provides crawling instructions. The two files work together but have opposite practical roles: a sitemap recommends destinations, and robots.txt can restrict crawler access to paths.

Feature Sitemap robots.txt
Main purpose Identify preferred URLs and content relationships Give crawlers crawling instructions
Typical question “What pages should you know about?” “Which areas may or may not be crawled?”
Can guarantee indexing? No No
Can block crawling? No Yes, subject to crawler compliance
Typical location /sitemap.xml or another declared URL /robots.txt at the site root

A sitemap does not override a crawl block. Google documents that a sitemap may be inaccessible or partly inaccessible when blocked by robots.txt. A robots.txt disallow is also not the correct general method for preventing indexing: a blocked URL may still appear in search without a normal snippet. Use appropriate indexing controls for pages that should not appear in search, and do not put intentionally blocked or non-indexable URLs in the sitemap.

Does a sitemap improve rankings?

No, a sitemap does not directly improve rankings. A sitemap can help a search engine discover and interpret the URLs a site owner cares about, but a sitemap does not create authority, relevance, content quality, or technical accessibility.

A sitemap cannot:

  • Guarantee that a page will be crawled or indexed.
  • Make low-quality or duplicative content rank.
  • Override a canonical URL selected elsewhere.
  • Repair a server error, rendering failure, access restriction, or weak internal-link structure.
  • Force a search engine to rank a page higher.

If pages are not appearing in search, treat the sitemap as one diagnostic input rather than the entire solution. Inspect HTTP status codes, canonical tags, noindex directives, robots.txt, internal links, rendered content, duplication, and overall page quality.

What are the most important sitemap best practices?

  1. Use canonical URLs: List the URL preferred for search results, including the intended HTTPS and hostname version.
  2. Use absolute URLs: Write https://www.example.com/about/, not /about/.
  3. Keep URLs accessible: A listed URL should be public and return a successful response rather than a redirect, error, or authentication request.
  4. Exclude noindex pages: Keep sitemap contents consistent with indexing directives.
  5. Maintain accurate lastmod values: Update the date for meaningful content changes, not merely for a recrawl or automated field change.
  6. Use a sitemap index at scale: Split files when a sitemap exceeds 50,000 URLs or 50 MB uncompressed.
  7. Automate updates: Use the CMS, database, build process, or a trusted generator rather than editing a large file by hand.
  8. Keep the file available: Avoid firewall rules, authentication, DNS failures, server timeouts, and accidental deployment removals.
  9. Make discovery redundant: Submit the file in webmaster tools and declare its location in robots.txt where appropriate, while continuing to build useful internal links.
  10. Do not rely on obsolete controls: Google ignores priority and changefreq as meaningful ranking controls.

How do you troubleshoot sitemap errors?

Start with the exact error reported by the webmaster platform, then test the sitemap URL and the URLs listed inside it. A sitemap problem often exposes a wider technical SEO inconsistency.

Why does Search Console say “Sitemap could not be read”?

“Sitemap could not be read” usually means Google could not retrieve or parse the file. Check the following causes in order:

  • The submitted URL is wrong or the file returns a 404.
  • The server times out or has a temporary DNS or hosting problem.
  • A firewall, access-control rule, authentication layer, or robots.txt rule blocks the file.
  • The server returns an HTML error page instead of XML.
  • The XML is malformed, incorrectly encoded, or uses invalid URL entries.
  • The file is caught in a redirect chain or returns an unexpected redirect.
  • The sitemap was submitted to the wrong Search Console property.

Open the exact submitted URL in a browser, inspect the response status, and verify that the response is the intended XML document rather than a branded error page. Google’s Search Console sitemap troubleshooting guidance specifically identifies robots.txt blocking as a reason Google may be unable to access a sitemap or all of its listed content.

Why does a sitemap contain URLs that are not indexed?

A sitemap can contain a valid URL that Google has not indexed because the page is new, has not been crawled, is weak or duplicative, is canonicalized elsewhere, is blocked or protected, returns an error or redirect, lacks useful internal context, or was simply not selected for indexing.

The sitemap reports the URLs the publisher wants considered; the sitemap does not force those URLs into Google’s index. Compare the sitemap with the page’s HTTP status, canonical tag, noindex state, robots.txt access, internal links, rendered content, and indexing report.

How do you fix redirected or noncanonical URLs in a sitemap?

Replace each redirecting URL with its final canonical destination, then remove duplicate variants unless a specific valid reason requires them. For example, if https://example.com/old-page redirects to https://example.com/new-page/, list the final preferred URL rather than the old URL.

What should you do about inaccurate lastmod dates?

Set lastmod only when the page received a meaningful content change and keep the date accurate across the site. Do not change lastmod simply because a crawler visited the page or an automated field changed. Google may use an accurate and consistently verifiable value, but unreliable dates reduce the usefulness of the signal.

Can a sitemap fix a JavaScript or international SEO problem?

A sitemap can reveal URLs that are difficult to discover through JavaScript navigation, but a sitemap cannot make a JavaScript application automatically crawlable or indexable. Pages still need accessible responses, usable content, and normal indexing eligibility.

International sites should keep canonical URLs and language or regional relationships consistent. Google supports localized versions through sitemap extensions, while platforms such as Wix and Shopify may generate multilingual sitemap structures automatically. Shopify documents multilingual sitemap behavior in its international SEO guidance.

Which sitemap tools should you use?

Most site owners can complete basic sitemap work with built-in CMS features and free webmaster tools. Paid SEO software becomes useful when the site is large, frequently changing, technically complex, or professionally audited.

Tool or service Best use When to choose it When not to buy it
Google Search Console Submit sitemaps and inspect Google processing and indexing diagnostics Every site owner It is not a complete custom sitemap generator or full technical crawler.
Bing Webmaster Tools Submit sitemaps and inspect Bing crawling and indexing diagnostics Sites seeking Bing and Microsoft search visibility It does not replace Google Search Console for Google-focused sites.
WordPress core sitemap Built-in sitemap generation, commonly at /wp-sitemap.xml Small and medium WordPress sites Advanced exclusions or specialized sitemap logic may require more tooling.
Yoast SEO Automatic WordPress sitemap maintenance plus broader on-page SEO controls WordPress users who need its wider feature set Buying Yoast solely for an XML sitemap is usually unnecessary.
Wix or Shopify built-in sitemap Automatic platform-managed sitemap generation Owners of those hosted platforms Server-level customization is limited by the platform.
Screaming Frog SEO Spider Site crawling, redirect and indexability checks, and sitemap auditing or generation Technical SEOs, agencies, and larger sites It is overkill for a tiny automatically managed site.
Semrush Site Audit Broader technical SEO auditing alongside sitemap-related checks Marketers or agencies wanting keyword, competitor, backlink, and audit features together It is unnecessary for simply locating or submitting one sitemap.

Semrush’s official pricing page displayed Pro at $117.33 per month when billed annually, with a shown regular monthly price of $139, and Guru at $208.33 per month when billed annually, with a shown regular monthly price of $249, during research retrieval on August 18, 2026. Check Semrush’s current pricing page before purchasing because software prices can change.

What is the simplest sitemap workflow?

  1. Find the existing file: Check /sitemap.xml, /sitemap_index.xml, /wp-sitemap.xml, robots.txt, and CMS settings.
  2. Inspect the contents: Confirm that URLs are absolute, canonical, public, indexable, and successful.
  3. Fix inconsistencies: Remove redirects, errors, noindex pages, duplicate variants, and temporary or utility URLs.
  4. Submit the authoritative file: Submit the sitemap or sitemap index in Google Search Console and Bing Webmaster Tools.
  5. Monitor and maintain: Review processing errors, keep the file available, and let the CMS or build system update it automatically.
  6. Investigate indexing separately: If pages remain unindexed, inspect content quality, internal links, canonicalization, rendering, access, server responses, and indexing reports.

Frequently Asked Questions

Does submitting a sitemap make Google index pages faster?

Submitting a sitemap can help Google discover pages, but it does not guarantee faster crawling or indexing. Google treats sitemap submission as a hint and may decide not to crawl or index individual listed URLs.

Can I have multiple sitemaps?

Yes. A site can use multiple sitemap files, and a sitemap index can list those files. Use multiple files when the site exceeds 50,000 URLs or 50 MB uncompressed, or when separating content types makes maintenance clearer.

How often should a sitemap be updated?

A sitemap should be updated whenever its eligible URLs change, preferably automatically through the CMS, database, or build process. The lastmod value should change only for meaningful, accurately recorded content updates.

Can a sitemap include noindex pages?

A sitemap generally should not include pages marked noindex. A noindex page in the sitemap creates conflicting signals, so remove intentionally excluded pages and confirm that the CMS or SEO plugin is not generating them.

Is sitemap_index.xml better than sitemap.xml?

Neither filename is inherently better. sitemap.xml commonly identifies one sitemap or a sitemap index, while sitemap_index.xml is a conventional name for an index containing multiple files; the correct choice depends on the CMS and site structure.

The Bottom Line

For most sites, sitemap work is simple: use the CMS-generated sitemap, keep only important canonical and indexable URLs, and submit the authoritative sitemap or sitemap index to Google Search Console and Bing Webmaster Tools. Treat the sitemap as a discovery aid and diagnostic signal—not as a shortcut around internal linking, accessible pages, sound canonicalization, or useful content.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi