XML Sitemaps for Small Business Websites: What to Include

If you run a small business website, or look after one, you have probably been told you "need a sitemap". Most website platforms and SEO plugins already make one, but nobody checks what is in it. Wrong URLs, a file that quietly broke after a redesign, or a sitemap nobody ever submitted are all common.

This guide explains what a sitemap does, which pages belong in it, and how to check, submit and troubleshoot it. By the end you will be able to review your own with confidence.

In short: An XML sitemap is a list of the pages you want search engines to find. It helps discovery but does not make Google index or rank anything. Keep it to clean, public, indexable URLs, submit it once in Google Search Console, and re-check it after big site changes.

What a sitemap does (and doesn't do)

Search engines work in three steps, and it helps to keep them apart:

Search engines work in three steps: discovery, crawling, indexing. A sitemap only helps with discovery. Being listed does not mean a page is indexed.

Discovery: Google learns a URL exists, from a link or a sitemap.
Crawling: Google fetches the page.
Indexing: Google decides whether to store the page and show it in results.

A sitemap only helps with the first step. Being listed does not mean a page will be crawled or indexed, and being missing does not mean it will be ignored. What a clean sitemap gives you is a reliable list of the pages you consider important.

A sitemap is a file, usually at /sitemap.xml or /sitemap_index.xml. Each entry holds a page address and, optionally, a last-modified date:

<url>
  <loc>https://yourbusiness.com/services/roof-repair</loc>
  <lastmod>2026-09-14</lastmod>
</url>

Your platform wraps these entries in the required outer structure for you. You should never need to write one by hand.

When it matters most

Your site is new and few other sites link to it.
You publish often, such as a blog or a product catalogue.
Some pages sit many clicks away from the home page.

If your site has fifteen pages, all in the main menu, and rarely changes, internal links do most of the work. A sitemap is still harmless.

What to include

Your sitemap should list the canonical, indexable, public pages you want people to find in search. Typically that means:

Checklist: every page in your sitemap should return 200 OK, not be blocked by robots.txt, carry no noindex directive, and have a canonical URL matching the sitemap entry.

The home page and your main service or product pages
Location pages, if each one is genuinely useful on its own
"About", "Contact" and other key information pages
Blog or news articles
Category or hub pages that are useful in their own right

Every listed URL should be the exact version you want shown: https, your chosen domain (with or without www, pick one) and no tracking parameters.

Each listed page should also:

Return a 200 OK status, not a redirect or an error
Not be blocked by robots.txt (see robots.txt mistakes that block Google)
Not carry a noindex directive, in a meta tag or an X-Robots-Tag header
Have a canonical URL that matches the sitemap entry

Tip: A page that looks fine in your browser may still redirect or be marked noindex. Paste the URL into the URL Inspection tool in Google Search Console to see the status, canonical and indexability that Google sees.

What to leave out

Just as important is what should not be there.

Six kinds of URL to leave out of a sitemap: redirects, error pages, noindex pages, non-canonical duplicates, admin and staging URLs, and tracking-parameter URLs. Leaving out does not make a page private.

Leave out	Why
Redirected URLs	List only the final destination
404 and error pages	Auto-generated files sometimes keep deleted pages
`noindex` pages	Thank-you pages, internal search, login, cart, checkout
Duplicates that canonicalise elsewhere	Only the canonical version belongs
Admin, staging and test URLs	Not for public search
URLs with `?utm_` or session IDs	Duplicates of the clean page
Filter combinations on shops	Unless you deliberately want one to rank
Thin tag or date archives	Nothing a visitor would search for

Mixed signals cause confusion. A page that is in the sitemap but marked noindex tells Google two opposite things.

Watch out: Leaving a URL out of a sitemap, or blocking it in robots.txt, does not make it private. Neither is access control. Protect staging sites, admin areas and confidential files with a login. Also note that Google must be able to crawl a page to see its noindex tag, so do not block the same page in robots.txt.

One sitemap or several?

For most small sites, one file is fine. Some platforms split the list into several files joined by a sitemap index:

sitemap_index.xml
├── sitemap-pages.xml
├── sitemap-posts.xml
└── sitemap-products.xml

Each sitemap file is limited to 50,000 URLs and 50 MB uncompressed, according to Google's sitemap documentation. Few small sites come near that.

Splitting by content type also makes reporting easier, because you can see whether blog posts are indexed differently from product pages.

Keep `lastmod` honest

The lastmod date should show when a page's content last changed in a meaningful way. Google's documentation says it uses the value when it is consistently and verifiably accurate. If every URL shows today's date on every visit, search engines have little reason to trust it.

Check a few entries. If dates change whenever you edit a sidebar widget or tweak the theme, ask your developer or plugin support how the dates are produced.

Google's documentation also says it ignores the priority and changefreq fields. If your plugin offers them, you can leave them alone.

Find, publish and submit your sitemap

Four steps: find your sitemap at /sitemap.xml or /sitemap_index.xml, add a Sitemap: line in robots.txt, submit it in Search Console, then read the Sitemaps report, which is not the same as indexing.

Find it

Try these in order:

https://yourbusiness.com/sitemap.xml
https://yourbusiness.com/sitemap_index.xml
https://yourbusiness.com/robots.txt, looking for a line starting Sitemap:
The "XML sitemap" section of your SEO plugin or platform settings

Reference it in robots.txt

Adding this line lets any crawler find the file:

Sitemap: https://yourbusiness.com/sitemap_index.xml

Use the full address, starting with https://.

Submit it in Google Search Console

Sign in to Google Search Console and add your site as a property. Verification is usually by DNS record or HTML file, and Search Console walks you through it.
Open the Sitemaps report in Search Console.
Enter the sitemap path, for example sitemap_index.xml, and submit.

If you use a sitemap index, submit just the index. Google reads the files listed in it. Google's Sitemaps report help covers this in more detail.

The Sitemaps report shows whether the file was processed and how many URLs it found. That is not the same as indexing. To see why specific pages are not indexed, use the Page indexing report and URL Inspection.

Bing has a similar sitemap feature in Bing Webmaster Tools.

If you see "Couldn't fetch"

Google's help page lists a few causes. Work through them in this order:

Symptom	Likely cause	Fix
HTML page instead of XML	Wrong address or error page	Open the URL and confirm it shows XML
Fetch fails	Wrong URL (404)	Check the address you submitted against the one in your browser
Fetch fails	Blocked in `robots.txt`	Remove the block
Fetch fails	Server problem, or the file not being reachable by Googlebot	Check with your host, and look at CDN and security plugin settings

A temporary server problem can clear on its own, so if everything else looks right, try again later.

What you don't need to do

Ping Google. Google deprecated its sitemap ping endpoint in 2023. Submit in Search Console and reference the sitemap in robots.txt.
Resubmit an unchanged sitemap again and again.
Publish copies on other domains or paths.

When to revisit

Review your sitemap after:

A migration or redesign
A domain or HTTPS change
Bulk URL changes, such as new slugs or categories
Switching SEO plugins or platforms
Any error reported in Search Console

A sitemap also cannot fix pages that nothing links to, or content that search engines struggle to see. Important pages still need crawlable internal links. If your site relies heavily on JavaScript, read why your React site might be invisible to Google.

To see how one of your pages looks to search engines, you can run the free single-page SEO scan at seo.lordevo.com. If you want help prioritising what any audit finds, see how to read an SEO audit.

Key takeaways

Treat the sitemap as a list of pages you want found, not as a ranking tool.
Include only canonical, public, indexable URLs that return 200 OK.
Remove redirects, errors, noindex pages, admin or staging URLs and tracking-parameter duplicates.
Reference the sitemap in robots.txt and submit it once in Search Console.
Make sure lastmod changes only when the page content really changes.
Re-check after migrations, redesigns and plugin changes.

FAQ

Do I need a sitemap to be in Google?

No. Google can find pages through links. A sitemap makes discovery more reliable, especially for new sites and pages that are hard to reach.

Why does Search Console say pages are "Discovered - currently not indexed"?

It means Google knows the URL exists but has not crawled it yet. That is common for new pages and does not by itself say anything about the page's quality. Check the page in URL Inspection, and make sure it is linked from other pages on your site so Google has a clear path to it.

Should I include every blog post and tag page?

Include posts you want found. Tag and date archives that only repeat the same snippets rarely help, so many sites leave them out.

How often should I update the sitemap?

You should not have to. Your platform or plugin should update it automatically when you publish or change pages. Your job is to check now and then that it still works.