What is a Sitemap? Why Your Website Needs One (2026 Guide)

What is a sitemap, exactly?

A sitemap is a structured file that tells search engines which URLs on your site you want them to know about. Think of it as a table of contents for your website, written in a format that crawlers can read in seconds. Instead of relying purely on internal links to discover pages, Google can pull your sitemap, see every URL you care about, and decide which ones to crawl and index.

The term "sitemap" usually refers to an XML file because that is the format Google, Bing, and other search engines officially support. There are also HTML sitemaps, which are user-facing pages, and specialized sitemaps for video, images, and news content. We will cover all of them, but the XML sitemap is the one almost every site needs.

The protocol behind XML sitemaps is open and standardized. It is called the Sitemaps protocol, and it has been jointly supported by Google, Bing, and Yahoo since 2006. That means a single sitemap file works across every major search engine without modification.

Why sitemaps matter for SEO

Google's documentation is clear on this point: a sitemap will not directly boost your rankings, but it will help your pages get discovered and indexed faster. And without indexing, ranking is impossible. So while a sitemap is not a ranking factor, it is a prerequisite for everything else SEO does.

Sitemaps are especially important if

• Your site is brand new. New domains have no backlinks pointing in, so Googlebot has no natural way to find your pages. A submitted sitemap is often the first signal Google receives that your site exists.

• Your site is large. Once you have hundreds or thousands of URLs, internal linking alone struggles to expose every page. Crawl budget becomes a real constraint, and a sitemap helps prioritize what gets fetched.

• Your pages are not well linked internally. Orphan pages (pages with no internal links pointing to them) are invisible to crawlers. A sitemap is sometimes the only way Google learns about them.

• You have rich media. Image and video sitemaps help Google understand and surface multimedia content in image search and video results.

• Your site updates frequently. News sites, blogs, and ecommerce stores benefit from fresh sitemaps that signal when content was last modified.

XML sitemap vs HTML sitemap

The two formats serve different audiences. An XML sitemap exists for search engines. An HTML sitemap exists for humans. Most sites need an XML sitemap, and many sites also publish an HTML sitemap as a backup navigation page.

Anatomy of an XML sitemap

An XML sitemap follows a specific structure defined by the Sitemaps protocol. Each URL entry can include <loc> (required, the full canonical URL), <lastmod> (date last meaningfully updated, Google uses this to decide whether to re-crawl), <changefreq> (largely ignored by Google in 2026), and <priority> (also largely ignored by Google).

Sitemap limits to remember

• Maximum 50,000 URLs per sitemap file.

• Maximum 50 MB uncompressed per sitemap file.

• You can gzip the file to save bandwidth, but the uncompressed limit still applies.

• If your site exceeds either limit, split into multiple sitemaps and use a sitemap index file.

Sitemap index files for huge sites

When a site has more than 50,000 URLs, you cannot put them all in one file. Create multiple sitemap files and one sitemap index file that points to all of them. The index file is what you submit to Google Search Console. Google then fetches each child sitemap automatically. Large CMS platforms like WordPress with Yoast, Shopify, and Webflow use this pattern by default.

What to include and what to exclude

Your sitemap should be a curated list of the canonical, indexable pages you actually want ranked.

Include

• Canonical URLs only (the version you want indexed)

• Pages that return a 200 OK status

• Important blog posts, product pages, category pages, and landing pages

• Static informational pages (About, Contact, Pricing)

Exclude

• Noindex pages. Including a page in your sitemap while it has a noindex meta tag sends conflicting signals to Google.

• Redirected URLs (301/302). Only include the final destination URL.

• 404 or 410 pages. Broken URLs in your sitemap waste crawl budget.

• Non-canonical duplicates. Only the canonical version belongs in the sitemap.

• URLs blocked by robots.txt. Google cannot crawl them anyway.

• Login pages, admin pages, cart pages, internal search results. These add no SEO value.

How to find your existing sitemap

Before creating a new sitemap, check whether you already have one. Most modern site builders and CMS platforms generate one automatically. Try these locations in order:

• yourdomain.com/sitemap.xml

• yourdomain.com/sitemap_index.xml

• yourdomain.com/sitemap1.xml

Also check yourdomain.com/robots.txt, most sites declare their sitemap URL at the bottom. If your site is verified in Google Search Console, check the Sitemaps section in the left sidebar.

How to submit your sitemap to Google Search Console

Submitting your sitemap to Google takes about 60 seconds and is one of the most impactful one-time SEO tasks for a new site.

1. Sign in at search.google.com/search-console and verify your site (DNS TXT record is the most reliable method). You cannot submit a sitemap until your property is verified.

2. From the left sidebar, click Indexing > Sitemaps.

3. Type the relative path to your sitemap into the input field (e.g. sitemap.xml). Do not include the domain, GSC adds it automatically.

4. Click Submit and wait for the status to update. You want to see Success with a Discovered URLs count matching what you expect. If you see "Couldn't fetch" or "Has errors," click the row to see specifics.

How to submit your sitemap to Bing Webmaster Tools

Bing powers about 8% of global search and feeds results to DuckDuckGo and Yahoo. The fastest method is Import from Google Search Console, which automatically imports your verified properties and sitemaps in one click. If importing manually, add your domain, complete verification, and go to Sitemaps under Configuration.

Common sitemap mistakes to avoid

1. Including broken or redirected URLs

Every URL in your sitemap should return a 200 status. Audit your sitemap periodically with a crawler.

2. Including noindex pages

Listing a URL in your sitemap tells Google "please index this," while a noindex tag tells Google "do not index this." Google will respect the noindex but treat the conflict as a quality issue.

3. Not regenerating after publishing

If you publish a new page but your sitemap still reflects yesterday's state, that page will be discovered later than necessary.

4. Including non-canonical URLs

If both example.com and www.example.com resolve, only the canonical version should appear in the sitemap.

5. Forgetting to submit it

Having a sitemap is not enough. Submitting it explicitly via Search Console gets you reporting on indexing status, which is invaluable for diagnosing problems.

6. Putting fake lastmod dates on every URL

Setting every URL's lastmod to today on every regeneration trains Google to ignore your lastmod values entirely. Only update lastmod when the page content has meaningfully changed.

If You Have a Framer Site

Framer handles sitemap generation automatically. Every time you publish, Framer regenerates an XML sitemap at yourdomain.com/sitemap.xml that includes all published pages and CMS items. See our complete Framer sitemap guide for Framer-specific details. Framer also automatically references your sitemap in your robots.txt file.

That said, you still need to verify your domain in Google Search Console, submit yourdomain.com/sitemap.xml manually in the Sitemaps section, and repeat in Bing Webmaster Tools. For a full walkthrough, see our guide on how to submit your Framer site to Google.

RankFrame lives inside the Framer editor and gives you indexing tools Framer alone does not provide: an indexing dashboard showing exactly which pages are indexed, one-click submission to Google's Indexing API, automated site audits that catch sitemap-related issues like noindex conflicts and broken canonicals, and schema markup tools that complement what your sitemap is already telling Google.