No sitemap, and Google finds your pages by luck.
A sitemap is the list of pages you want Google to know about. It is only a hint, not a command, yet many AI-built sites ship without one or never point to it in robots.txt.
When a tool builds your site, it builds the pages. It rarely builds the list that tells a search engine which pages exist. That list is sitemap.xml.
It guarantees nothing about indexing, and a small site may not even need it. But checking costs one command, and fixing it costs one prompt.
What Google says about sitemaps
According to Google's documentation, a small site of roughly 500 pages or fewer, well linked from its menu or other pages, may not need one. If your site is new with few external links, or large, the same page says most sites benefit from having one.
One caveat worth keeping in mind: submitting a sitemap is only a hint. Google does not promise to download it or crawl every URL in it.
What a good one looks like
The guide to building a sitemap asks for this:
- XML, RSS or Atom, or a
.txtfile with one URL per line, encoded as UTF-8. Google says it has no preference. - At most 50 MB uncompressed or 50,000 URLs per file. Past that, split it and add an index.
- Fully qualified, absolute URLs. A path like
/pricingwill not work. - Only the canonical URLs you want to see in results.
- Google ignores
priorityandchangefreq, so you can drop them. lastmodcounts only if it is accurate and verifiable: a real content change, not a new copyright year.
<?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-11-20</lastmod>
</url>
<url>
<loc>https://yoursite.com/pricing</loc>
</url>
</urlset>A minimal one looks like this:
Point to it from robots.txt
Having the file is not enough if nobody knows where it is. One way to tell crawlers is a line in your robots.txt; it can go anywhere in the file and be repeated for several sitemaps:
Sitemap: https://yoursite.com/sitemap.xmlThe other way is the Sitemaps report in Search Console. Doing both does no harm. And if that file already blocks bots, also check which AI bots you let through.
Check it in a minute
See whether the file exists and whether robots.txt mentions it. Swap in your own domain:
curl -sI https://yoursite.com/sitemap.xml | head -1
curl -s https://yoursite.com/robots.txt | grep -i sitemap
curl -s https://yoursite.com/sitemap.xml | grep -c '<loc>'The first line should say 200. A 404 means it is missing. A 200 that returns your homepage instead of XML means the tool answers every path with the same page, which is not a sitemap either. The third command counts the URLs listed: compare it with the pages you really have.
Ask your AI tool for it
Generate a /sitemap.xml for yoursite.com with every public page:
absolute https URLs, canonical ones only, and lastmod only if you
can compute the real change date (otherwise leave it out). No
priority or changefreq. It must update itself when I add a page.
Add the line Sitemap: https://yoursite.com/sitemap.xml to
robots.txt and change nothing else. Return the list of URLs you
included.Slop Score Pro checks this: it flags a site with no sitemap, or one that exists but robots.txt never mentions, and leaves the prompt for each case. You can start by measuring your site from the field on the homepage. And if your sitemap lists pages with the same title, this post explains why that costs you too.
Sources
- Learn about sitemaps, Google Search Central, November 20, 2026
- Build and submit a sitemap, Google Search Central, November 20, 2026
Frequently asked questions
Do I need a sitemap for a five-page site?
Per Google, a small, well-linked site may not need one. Having one does no harm and helps once the site grows.
Does sitemap priority matter to Google?
No: its documentation says Google ignores priority and changefreq.