No Signup Unlimited Usage Real Data 100% Free Privacy First Fast Results Export Reports Mobile Friendly

Sitemap Finder & Validator for News Publishers

Find out whether Google can locate your news sitemap, how many stories from the last two days it lists, and which entries are missing required tags.

Fetching live data…

Why News Publishers need this

A scoop goes live at 9:02, a wire rewrite lands at 9:40, and by ten the rewrite holds the Top Stories slot because Google leans toward more recent articles. Add AI Overviews trimming clicks even on page-one results, and a news desk cannot afford a second quiet leak: a sitemap that Google cannot read or that lists nothing fresh. Most news SEO advice, from google news seo best practices to every news sitemap validator search, comes back to the same question: can a crawler find the file, and does it hold the stories you published today? Enter your domain and the Sitemap Finder & Validator checks robots.txt and the usual paths, including /news-sitemap.xml and /sitemap-news.xml, then reports each sitemap's type, its URL count and, when news entries exist, how many fall inside the last two days. It reads the live file the way a crawler would. It will not say whether a story is indexed, whether it appears in Google News, or where it ranks. What it gives a news publisher is a fast, factual answer on discoverability, before anyone spends a morning blaming the algorithm.

News Publishers specific guidance

What to run first

Start with the bare domain, for example news.example.com, not an article URL. Within ten minutes you can read three things: the Sitemaps card, the In robots.txt card, and the table of sitemap types. If the News Sitemap section is missing, open your robots.txt at the root and look for a Sitemap: line pointing at the news file. A file at an unusual address is only found if robots.txt lists it or an index links it with news in its address. Then open the file in a browser and confirm that a headline from this morning is in it. A found file does not prove Google has processed it; that status lives in Search Console.

Reading the News Sitemap section

For each sitemap you get News URLs, Last 2 days, Older, Newest date and Missing tags. The note there cites Google's guideline of articles from the last two days and at most 1,000 news:news entries per sitemap. A desk publishing about 150 stories a day should see Last 2 days near 300 and a Newest date from this morning. A big Older figure means the file carries stale stories, and a Newest date from last week means the generator has stopped. Missing tags counts entries short of a publication name, language, publication date or title. Keep in mind that this is a presence and count check: it does not read tag values and does not test whether each story URL answers 200.

What to fix, and in which order

Fix discovery first: a missing news file or a missing Sitemap: line in robots.txt, because nothing else matters if crawlers cannot find it. Second, a stalled Newest date; restart whatever job writes the file, usually a CMS plugin or a scheduled task. Third, Missing tags, which you correct in the template that prints each entry. Last, stop old stories piling up under Older. After that, make visible bylines and dates match your Article markup, since Google's news policies ask for visible dates and author credits. A clean sitemap does not replace that transparency, and it does not decide Top Stories placement. Also remember that Total loc skips child sitemaps without news in their address, so a low total on an index is not proof of a shortage.

Example scenarios

1. The generator that quietly stopped

Situation
Illustrative example: a regional daily moved its CMS to a new host on a Friday, and the cron task that rewrites the news sitemap was never recreated. Nobody noticed over the weekend because the file still loads.
Input
news.example.com
Reading the result
The table would typically show /news-sitemap.xml as a URL Set with 480 news URLs, but Last 2 days at 0, Older at 480 and a Newest date from Friday. The file is found and referenced in robots.txt, yet it offers crawlers nothing current. Recreate the scheduled job, then run the domain again and expect Last 2 days to climb.

2. The index that hides the news file

Situation
Illustrative example: a magazine site runs its sitemap through an index file listing eight children named by year and section. The news feed sits at /feeds/latest-stories.xml and is not referenced anywhere.
Input
magazine.example.com
Reading the result
You would typically see Sitemaps at 1 or 2, a modest Total loc, and no News Sitemap section at all. That absence means nothing it opened had news:news entries; it does not mean the feed is broken. Add a Sitemap: line for the feed in robots.txt or rename it with news in the address, then re-run to see the section appear.

3. Entries that lost their language tag

Situation
Illustrative example: after a template change, an agency-built news sitemap stopped printing the language for each entry. Publishing volume is high, so the file sits right at the entry cap.
Input
gazette.example.com/news-sitemap.xml
Reading the result
The section might read News URLs 1,000, Last 2 days 640, Older 360, Newest date today and Missing tags 212. Fresh, but the Older share suggests old stories are crowding the cap, and 212 entries are short of a required field. Fix the template, then trim the file so it holds only the last two days.

Common mistakes

  • Treating a found file as a processed one. The tool shows what a crawler can fetch, not what Google accepted. Processing errors are reported in Search Console.
  • Testing an article URL instead of the domain. Sitemap discovery starts from the site root and robots.txt, so run the bare domain or subdomain that serves your news.
  • Reading an empty News Sitemap section as a broken feed. The section only appears when an opened sitemap has news:news entries, so it may simply mean the file sits at an address the tool could not reach.
  • Letting the file grow past two days. Keeping weeks of stories in the news file piles up Older entries and pushes you toward the 1,000-entry cap that the guideline sets.
  • Expecting the sitemap to win Top Stories. A healthy file only helps Google discover URLs; recency, eligibility and visible dates and bylines still decide who is shown.

Frequently asked questions

How do I validate a news sitemap?

Enter your domain and look for the News Sitemap section, which appears only when a sitemap it opened contains news:news entries. Compare News URLs with what you published, Last 2 days with your daily output, Newest date with this morning, and Missing tags for entries short of publication name, language, date or title. It checks that tags are present, not that their values are correct, so confirm processing errors in Search Console afterwards.

Why does the News Sitemap section not show for my site?

It appears only when a sitemap the tool opened has news:news entries. If your file is at an address other than /news-sitemap.xml, /sitemap-news.xml or /sitemap_news.xml, add a Sitemap: line to robots.txt, or make sure an index links it with news in the address. Child sitemaps without news in the name are not opened, and only three children of an index are followed. Fix the declaration, then run the domain again.

Will a valid news sitemap get my stories into Top Stories?

No. The sitemap helps Google find fresh URLs, nothing more. Top Stories placement depends on eligibility under Google News policies, such as visible dates and author credits, and on ranking, where recency often beats the original scoop. The tool does not check indexing, Google News appearance or Top Stories, and it submits nothing. Use it to rule out discovery as the cause, then look at transparency and page quality.

How many URLs should a news sitemap contain?

Google's guideline, which the tool's note cites, is articles from the last two days and at most 1,000 news:news entries per sitemap. Compare Last 2 days with your output: a desk running about 120 stories a day would expect roughly 240. A far larger number suggests the file never drops old stories, and a far smaller one suggests the generator is missing a section. The count alone cannot tell you which stories are good.

Can a sitemap check explain my AI Overviews traffic loss?

No. AI Overviews lower click-through even on pages that still rank, and a sitemap has no bearing on that. The tool reports discovery and counts, not rankings or referrals. What it can do is remove one variable: if the news file is healthy and fresh, a traffic drop is not a discovery problem, and you can turn to headlines, snippets and how AI answers cite your brand.

Reference: Eligibility for news surfaces rests on transparency rules such as visible publication dates and author credits, which are set out in the Google News policies in Publisher Center Help.

Last updated: Türkçe sürüm