Short answer
Sitemaps help identify the public URLs competitors make available to search engines. Content Radar can use them to discover content movement such as new blog posts, resource pages, product pages, and guides. A successful sitemap check filters likely content URLs, normalizes them, and writes unseen results directly to Articles. It does not send them through Candidate URL review.
Definition
An XML sitemap is a file a website publishes to help search engines find its pages. Sitemaps often include blog posts, resource pages, product pages, category pages, and guides, sometimes organized through a sitemap index that links to multiple sitemap files.
Useful for
SEO and agency teams that want a broader public URL source than a feed alone provides. use sitemaps monitoring to keep competitor publishing visible without checking every source by hand.
Coverage limit
Sitemap indexes are limited to 10 safe same-site child sitemaps, and each fetch keeps at most 200 sitemap items before likely-content filtering. A sitemap is not a complete record of every site change.
What this is
An XML sitemap is a file a website publishes to help search engines find its pages. Sitemaps often include blog posts, resource pages, product pages, category pages, and guides, sometimes organized through a sitemap index that links to multiple sitemap files.
Because a sitemap reflects URLs the site exposes for discovery, Content Radar can check it manually or through configured ingestion and compare likely content URLs against known Articles.
Why it matters
Not every competitor page is promoted through a blog feed. Resource pages and guides may appear in a sitemap without a separate announcement.
Sitemap monitoring gives teams a broader but bounded picture of what a competitor has published, which is useful for content gap review, SEO research, and spotting new sections of a site as they appear.
Signals to watch
These are the sitemaps signals most worth a team's attention.
How Content Radar helps
A practical workflow for turning sitemaps into reviewed, actionable signal.
Add the source
Add a public sitemap or sitemap index URL for a competitor. The XML parser distinguishes a URL set from a sitemap index.
Monitor for updates
Run the source check manually, or let configured ingestion process it within the documented index and item limits.
Detect new content
Likely content URLs are normalized and deduplicated against the workspace Article library.
Review the Articles
New likely-content URLs are written directly to Articles. Review their derived titles and status, and archive items that are not useful.
Turn signal into action
Use reviewed sitemap Articles as source material in the planning or analysis workflow your team already follows.
Use cases by team
Review likely content URLs not exposed through a feed, then assess them in your existing SEO workflow.
Review likely campaign or landing-page URLs when they pass the sitemap content filter.
Find new resource and guide pages a competitor has published, even when they are not linked from the homepage.
Get an occasional, structured view of what new pages a competitor has published.
Run sitemap checks across client competitor sets to find new pages worth reviewing.
Discovering likely public content URLs a competitor has exposed through an XML sitemap, including pages that are not announced through a blog feed.
No. Content Radar filters likely content URLs before direct Article insertion, and the team can archive results that are not useful. Sitemap entries do not use Candidate URL review.
No. Content Radar reads the published sitemap file. It does not crawl the wider site or follow links beyond what you choose to review.
Sitemap indexes are supported. Content Radar can work with sitemap index files that point to multiple individual sitemaps.
RSS feeds typically cover articles and announcements. Sitemaps tend to cover a broader range of page types, including resource pages, product pages, and guides.
Related source types
Related industries