--- title: XML Sitemap — definition and what belongs in it | Siite description: "XML sitemaps explained: what they do and do not guarantee, which pages belong in one, and how to submit and monitor them in Search Console." url: "https://siite.co/dictionary/xml-sitemap" type: static generatedAt: "2026-10-22T08:21:10.862Z" --- Web & Technical # XML Sitemap A machine-readable list of the pages you want indexed, submitted to search engines so nothing important depends on being discovered by chance. Also goes by Sitemap.xml [![Siite](/images/layout/logo.svg)Written by Siite](/about/)Updated September 8, 2026 ## Entry contents [All Terms A to Z←Browse the full dictionary](/dictionary/) An XML sitemap is a file listing the pages you want indexed, usually with the date each was last changed. Search engines read it as a hint about what exists and what moved. It is a table of contents, not an argument: it helps pages get found, and decides nothing about whether they deserve to rank. > **Briefly explained** > > - A machine-readable list of your indexable pages. > - It assists discovery. It does not guarantee indexing. > - It matters most right after a launch or migration. > - Its best use is diagnostic, through the coverage report. ## When does it actually matter? Less often than its reputation suggests, and sharply in two situations. - **After a launch or migration**, when internal links have not settled and new addresses need finding quickly. - **On a larger site**, where service and location combinations multiply faster than anyone links to them. On a twenty-page site with decent [internal links](/dictionary/internal-links/), discovery was never the problem. ## What belongs in it? Only pages you would be happy to see in search results. - Canonical versions, not duplicates - Indexable pages, never ones carrying a no-index directive - Real content, not thank-you pages or tag archives A sitemap that lists pages you told Google to ignore sends two contradictory instructions, and Google resolves the contradiction however it likes. ## What is it most useful for? Reading, rather than submitting. In Search Console, the gap between pages submitted and pages indexed is one of the clearest diagnostics available. A large gap usually means duplicates, soft 404s, or thin pages Google chose not to keep — all of which are worth knowing before the traffic chart tells you. ## How do you keep it honest? - Generate it automatically on publish, never by hand - Keep the last-modified dates truthful. Faking freshness helps nothing - Reference it from robots.txt - Submit it once, then read the coverage report monthly ## What do the terms mean? - **Sitemap index:** A sitemap that points to other sitemaps, for larger sites. - **lastmod:** The date a page genuinely changed. - **Coverage report:** Search Console’s account of what is indexed and what was excluded. - **Soft 404:** A page that returns a success code while showing nothing of substance. - **robots.txt:** The file that tells crawlers where they may go, and where the sitemap is. Owner questions ## What owners ask us about XML Sitemap ### Does a sitemap guarantee indexing? +No. It helps discovery. Google still decides whether a page is worth indexing, and thin or duplicate pages get skipped regardless. ### What should be excluded? +Thank-you pages, no-indexed pages, tag archives and anything you would not want in results. A sitemap listing pages you told Google to ignore sends conflicting signals. ### Where should it live? +At a predictable address, referenced from robots.txt and submitted in Search Console so coverage errors are visible to somebody. ### Should it be updated by hand? +No. It should regenerate on publish. A hand-maintained sitemap is out of date within a month and wrong within three. ### What does the submitted-versus-indexed gap tell me? +More than almost any other report. A large gap usually means duplicate pages, thin content or pages Google decided were not worth keeping.Put this to work ## Guides that use this Step-by-step playbooks from the team, written for owners doing the work themselves. No sign-up and no email required. [### Why your Austin HVAC site ranks #4 (and the H1 isn't the fix) Most Austin HVAC sites stuck at #4 in the map pack get diagnosed wrong. It isn't your H1, meta tags, or blog. Here's what actually moves the needle. Read the guide→](/articles/austin-hvac-rank-4-h1-not-the-fix/)4.9191 reviewsWhere this turns into work ## A table of contents search engines trust Generated automatically, listing only the pages you want indexed, submitted and then actually read — because the coverage report is where problems surface first. [See the service→](/services/web-design/)[Ask us about it](/contact/) ![Elvir Sejfulai, Head of Development at Siite](/images/team/panel/elvir-sejfulai.webp) *Our head of development* ## Related entries - [### Technical SEO The part of SEO concerned with crawling, indexing and delivery — whether search engines can reach your pages, understand them, and render them quickly.](/dictionary/technical-seo/) - [### Internal Links Links from one page of your site to another — how search engines discover pages, how importance is distributed, and how visitors move from reading to booking.](/dictionary/internal-links/) - [### JSON-LD The script format Google recommends for structured data — a block of JSON in the page's code that describes the business, service or article in machine-readable terms.](/dictionary/json-ld/) [All terms A to Z Browse every term A to Z Open the dictionary→](/dictionary/)