Sitemap review prompt for developers
Give a sitemap review prompt the URL list, response observations and canonical policy. Ask it to flag duplicates and unsupported assumptions, then use the browser-local generator to create the file only after the list is reviewed.
Updated 7 October 2026. Use the prompt with evidence you have actually checked.
Copyable prompt
Review this candidate sitemap URL list against the stated canonical policy. Return: duplicate or fragment URLs, non-HTTPS or wrong-host URLs, redirects or errors observed, private or temporary paths, noindex conflicts, missing URL classes, and questions that need a live fetch. Do not claim that a URL is indexed or canonical unless the supplied evidence shows it. End with a publish and recheck checklist.How to use it
Give the prompt the policy
A URL list without a canonical policy cannot tell the assistant which regional host, protocol or language path is preferred. State the public hostname, allowed path patterns and any excluded sections.
Include response evidence
Add status, final URL, robots and canonical observations where you have them. Mark untested URLs as untested. A prompt should not infer a redirect from a URL spelling alone.
Generate after review
Use the local Sitemap Generator after the list is clean. It validates one hostname and produces XML, but it does not decide whether the page should be public or canonical.
Recheck in production
Fetch the published file, search for a known URL and an excluded path, then submit it to search tools if appropriate. Keep the file and review record together with the deployment.
Questions
Can a prompt find every broken URL?
Only if you supply current response evidence or connect it to a tool that can fetch the URLs. A text-only prompt cannot crawl.
Should developers include noindex pages?
Usually no when the noindex is intentional. Resolve any conflict between the sitemap and the page policy before publishing.