Information checked: 21 July 2026.
An XML sitemap lists the canonical URLs a website wants search engines to know about. It supports discovery and monitoring, but it does not replace internal links, make a blocked page indexable or guarantee that an included URL will appear in search results.
In brief: Generate the sitemap automatically from publishable canonical records, exclude non-indexable and error URLs, use accurate modification dates and submit the final location through Search Console and robots.txt.
What belongs in the sitemap
| URL state | Include? | Reason |
|---|---|---|
| Published canonical page returning 200 | Yes | It is an indexable preferred URL |
| Draft, preview or staging page | No | It should not be offered for indexing |
| Redirecting URL | No | Include the final destination instead |
| 404, 410 or server-error URL | No | It is not a current canonical page |
noindex page | No | The signals would conflict |
| Duplicate filtered or parameter URL | No | Use the canonical version |
Generate it from the same source as publication
For a 300-article blog, the engine should create the sitemap automatically from the content records marked for publication. A manual file will become stale when an article is renamed, unpublished or redirected. The generator should output absolute HTTPS URLs using the preferred hostname and escape XML correctly.
Use lastmod honestly
The modification date should change when the page's significant visible content changes, not whenever a template is rebuilt or the sitemap is regenerated. Inflating every date to today removes the field's value. Keep the editorial updated date separate from the original publication date and pass the meaningful value into the sitemap.
Respect size and location rules
Google supports the sitemap protocol and limits one sitemap to 50 MB uncompressed or 50,000 URLs. This project is far below that threshold, but separating content types through a sitemap index may still make monitoring easier. Hosting the sitemap at the site root is the simplest arrangement for a single-domain editorial site.
Submit and monitor
Add the sitemap URL to robots.txt and submit it in the verified Search Console property. A successful submission means the file could be processed; it does not mean every URL is indexed. Compare submitted URLs with indexed pages and use URL Inspection for specific problems.
The most common weak point
A CMS sitemap often includes author archives, tags, internal search pages, attachment pages or old URLs that the editorial plan never intended to index. Review the actual XML after import rather than assuming the plugin or engine has chosen correctly.
Before you publish
- The sitemap loads over HTTPS and returns a successful XML response.
- Every listed URL is canonical, indexable and returns 200.
- Drafts, redirects, errors and
noindexpages are absent. lastmodreflects meaningful content changes.- The same sitemap URL appears in robots.txt and Search Console.
- The published URL count matches the content inventory.
Start with this
After the test import, generate the sitemap from the engine, compare every URL against the final URL map and crawl the list before submitting it to Google.
Sources and date checked
Sitemap limits and submission guidance were checked against the following primary sources. Date checked: 21 July 2026.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.