9,200 Articles in the Sitemap, Google Only Indexes the Homepage
An audit of a news site with 9,200 articles in its sitemap and almost nothing indexed: crawl demand, internal linking, and the fixes that actually matter.
TL;DR
An audit of a news site with 9,200 articles in its sitemap found only about 44 that ever earned a Google impression, dropping to zero for the most recent publish months. Every technical check came back clean, so the problem is crawl demand: publishing volume far outpacing authority signals, plus an archive cut off from internal links. The fixes are editorial: lower the volume, build contextual links into old content, trim the news sitemap, and earn external validation.
Open Search Console and the first number staring back: 9,200 articles in the sitemap. Daily impressions for the whole site? 20 to 130. Of every click ever recorded, 92 percent landed on the homepage, and nearly all of it came from people typing the site's name straight into Google.
That is not a projection or a simulation. It comes from an audit of an Indonesian news site publishing 40 to 60 articles per day. Sixteen months of Search Console data, thousands of URLs, and only about 44 articles ever earned a single impression from Google. The rest live exclusively in the sitemap.
Every technical door is open
The first step stays standard: make sure nothing blocks Google. robots.txt tested with the Googlebot user agent blocks only the admin area and two theme AJAX endpoints. Self-referencing canonicals on every sampled page. Meta robots index, follow. No X-Robots-Tag in the headers. Google processed the sitemaps with zero errors.
So every door is open, and Google simply chooses not to walk in. At this point my suspicion moved from something-is-broken to Google-is-just-not-interested.
Crawl budget is about intent, not just capacity
Google's own documentation calls the per-hostname allocation of crawling resources the crawl budget [1]. It has two components. The crawl capacity limit, a technical ceiling computed from your server's load. And crawl demand, how much Google actually wants to explore a site's content.
Demand is the part people forget. Google puts it plainly: when demand is low, your site gets crawled less even if capacity sits idle [1]. The factors you can influence include how popular your URLs are across the web, document staleness, and the size of the URL inventory Google knows about for your site.
The interesting part: Google scopes its crawl budget guide to two site profiles. Sites with 10,000+ pages updated daily, and sites where a large share of URLs sits in the Discovered, currently not indexed state [3]. The site I audited matched both at once.
The monthly numbers keep getting lonelier
Here is the distribution of published articles per month against the ones that ever earned an impression in Search Console:
| Publish month | Articles | Ever got an impression | Share |
|---|---|---|---|
| February 2026 | 1,000 | 11 | 1.1% |
| March 2026 | 1,446 | 14 | 1.0% |
| April 2026 | 1,354 | 12 | 0.9% |
| May 2026 | 1,117 | 3 | 0.3% |
| June 2026 | 1,286 | 4 | 0.3% |
| July 2026 | 1,597 | 0 | 0.0% |
| August 2026 | 1,135 | 0 | 0.0% |
The trend is clear. The younger the publish month, the smaller the share of articles that ever surfaced. For everything published from July onward the number is zero percent. On a healthy news site it should be the exact opposite: fresh articles are the ones that deserve impressions most.
URL Inspection paints the same picture from another angle. Indexed articles were last crawled around April through May. Articles from August and September show URL is unknown to Google, meaning the URL was never even discovered. February articles hang in the discovered or crawled, currently not indexed states. Google documents this state officially: the page was found but not crawled yet, usually because the crawl was rescheduled to protect the site's load [4].
The archive becomes an orphan
The site's homepage HTML carries roughly 62 unique article links, all pointing at content published within the last 48 hours. At a pace of 40 to 60 new URLs per day, any article older than two days loses its only discovery path from the pages Googlebot actually visits.
What remains is paginated channel archives. Crawlable, yes, but a single channel runs a dozen to dozens of pages deep, and on a domain with thin external signals Google stops long before reaching the deep pages. The related-articles widget is configured for nine items but renders three in the HTML, and those three are fresh content too. The homepage popular block holds articles aged one to three days.
So there is no contextual link anywhere pointing into the old archive. The site effectively publishes new content while cutting the path to its own back catalog every single day.
What I recommend
Given the sequence above, the fixes come in layers, and most of them are editorial rather than technical.
Lower the volume, raise the bar. Five to ten original articles a day beat fifty rewrites. Google itself names content quality and uniqueness as factors in allocating crawl budget [1]. High volume at uniform quality on a young domain also reads like a farm pattern, which pushes demand down even further.
Contextual links into the archive. Related posts per category that are actually relevant, latest-per-channel blocks that touch content older than a week, tag pages that connect articles across time. Ideally every URL has a discovery path that is not the sitemap.
Trim the news sitemap. The official advice: include only articles from the last two days, then drop them [7]. Keep the full post sitemap as is, but do not turn it into a storefront for an unindexed backlog.
External paths. There is IndexNow, a free push protocol that notifies search engines like Bing and Yandex the moment a URL changes [6]. Google has said it is evaluating the protocol but is not a participant, so treat it as a complement. For Google News itself, Publisher Centre remains the official door [8]. Outside validation, from citations to press-council verification, feeds the same signal: how much this site deserves priority.
A note on the Request indexing button. I built a small automation that submits new URLs through the Search Console UI daily, complete with a SQLite log and a site-query index check. In practice it processes only about a dozen URLs per day. Treat it as a diagnostic instrument for measuring time-to-index, not a crawl budget solution. Submitting thousands of never-crawled URLs only tells Google how big the backlog is.
I have slowly grown convinced of one thing: a news site that publishes too eagerly can train Google to ignore it. Crawl demand is built on evidence, not on the number of URLs in a sitemap. And the cheapest evidence you can provide is a link graph that genuinely connects new content to old, plus a volume low enough to keep quality guarded.
Sources
[1] Optimize your crawl budget, Google Search Central.
[3] Optimize your crawl budget (large sites guide), Google Search Central.
[4] Page Indexing report, Google Search Console Help.
[6] IndexNow Documentation, indexnow.org.
[7] Create a News Sitemap, Google Search Central.
[8] Publisher Centre overview, Google News Publisher Help.