Keep your sitemap and RSS feed in agreement

Start with a single URL inventory

For every public page, record its preferred URL, page type, indexability, original publication date, and genuine modification date when known. Mark which pages belong in the feed. An About page can belong in the sitemap without becoming an RSS update; a newly published guide can belong in both.

This inventory prevents a common drift: navigation points to a clean directory address, the sitemap lists a file ending in .html, and the feed uses a third variation. Select one public address and reuse it consistently across these outputs.

Respect the purpose of each file

Google's sitemap documentation explains that RSS and Atom feeds can serve as sitemaps, but generally expose recent URLs. A dedicated sitemap is useful when you need broader coverage of an archive. Submission is a discovery signal and does not guarantee indexing.

Use a site's content model to decide which records are indexable. Exclude temporary previews and duplicate alternatives. Retain substantive category pages only when they help readers explore useful content. Avoid creating empty archives solely to increase the number of sitemap entries.

Check an example publication

• Home: include its canonical URL in the sitemap.
• Reference guide: include it in the sitemap; add a feed entry when publication or a substantial update merits one.
• Blog post: include its canonical URL in both outputs.
• Draft preview: keep it outside public publication outputs.
• Removed duplicate: stop listing the obsolete address and repair internal links to the surviving page.

Keep dates meaningful

A new deployment does not necessarily mean every page changed. Preserve the dates attached to actual editorial events. If you cannot establish a reliable modification date, avoid manufacturing one. Compare the article's displayed date, structured data, and feed date to catch accidental contradictions.

As a release check, parse both XML files and compare their URLs against files available on the host. Then follow a sample URL from each content type. This catches missing directory index files, accidental staging domains, and feed links to pages that were never deployed. A small consistency check makes both subscribers and search crawlers more likely to reach the content you intended to publish.