News sitemap has more than 1,000 URLs
news_sitemap_too_manyShort answer
One of your News sitemaps contains more than 1,000 <news:news> URLs. Google reads at most 1,000 news URLs per News sitemap file, so the extra entries are not used. In most cases the file also contains old articles: keep only the last two days, and if you really publish more than 1,000 articles in two days, split them into several files listed in a sitemap index.
Why it matters
When the limit is exceeded, which articles are skipped is not under your control — it can be the newest ones. A file this large also usually signals that the two-day window is not applied (see News sitemap lists articles older than 2 days).
How Glimana detects it
Glimana counts the news entries in every sitemap that returns 200. The rule fires when a single file has more than 1,000. The evidence names the sitemap and its count.
How to fix it
- Find the affected pages in Glimana. Open Issues › News sitemap has more than 1,000 URLs. This is a site-level check, so the single row carries the full evidence: the URLs, values or days involved. The task under Tasks shows the same list and the expected gain.
-
Apply the fix on your platform.
First apply the two-day window; that alone brings most sites well under 1,000. If you still publish more than 1,000 articles in two days, generate several News sitemap files (for example one per section or per day) with at most 1,000 entries each, list them in a sitemap index, and submit the index in Search Console.
SEO plugins limit their news sitemap to the last two days. A file over 1,000 usually means a cached or static copy, or a plugin configured to include all posts of a type: check the news sitemap settings and exclude the file from page caching.
Configure the news sitemap app to include only recent articles; very few stores publish at this volume, so a count over 1,000 almost always means the app lists all articles.
Add
LIMIT 1000together with the 48-hour filter. If you need more, paginate intonews-sitemap-1.xml,news-sitemap-2.xml… and serve asitemapindexthat lists them. -
Publish and clear caches. Save and publish, then make sure the crawler will see the new version: WordPress — clear the page cache in your cache plugin and purge the CDN; Shopify — theme and content changes go live on save, but purge any CDN in front of the store; custom code — deploy and purge the edge cache. Check in a private window or with
curl -s https://your-domain/page | grep -i '<title\|canonical\|robots'that the live HTML has changed; Glimana reads what the server sends, not what your browser has cached. - Verify in Glimana. Open the task under Tasks and click Mark as done. The affected pages are queued for a verification crawl within a few hours, and the task closes when every News sitemap has at most 1,000 news URLs. If the check still fails, the task returns to New with a note; when it passes, the task is listed under Resolved technical issues on Impact reports. To check sooner, use Re-crawl affected pages on the issue.
How the fix is verified
The next crawl recounts the news entries; the task closes when no file has more than 1,000.