SEO

Bing URL Coverage

Q: How often are the figures updated?

Cache TTL is 24 hours per URL. The nightly cron bing_url_index_sync at 04:00 pulls in up to 40 URLs per project. The ”Refresh Bing status” click runs ad hoc. After every successful IndexNow submission, the cache entry for that URL is invalidated.

Also known as: Bing indexation coverage, URL coverage report, Bing GetUrlInfo, Bing coverage

Bing URL Coverage answers the question: how many of my URLs does Bing know, and in what status? The Bing Webmaster Tools interface shows this information only for a single URL at a time in the ”URL Inspection” tab. Rankmio automates the view: for every URL from the most recent sitemap crawl (up to 500 at once), a GetUrlInfo API call is made to Bing, the result is cached for 24 hours and sorted into four buckets. The outcome is a table from which content owners can tell in seconds which new pages still have no Bing signal — precisely the candidates that should be submitted via IndexNow.

The four coverage states

Indexed — Bing has crawled the page and holds it in the index (signals: DocumentSize > 0 and LastCrawledDate set). No action required.
Known, not indexed — Bing is aware of the URL through the sitemap or a backlink (AnchorCount > 0 or LastCrawledDate) but has not yet added it to the index. Action: strengthen internal linking, refresh content signals or submit it again via IndexNow.
Unknown to Bing — No signal at all (neither crawled nor linked). Action: submit the URL via IndexNow — the fastest way to enter Bing's field of view in the first place.
Query pending — Rankmio has not yet run a status check with Bing for this URL. It says nothing about Bing, it is merely an internal cache state.

Why coverage is stronger than the bare indexation figure

Bing's health report shows the number of indexed pages as an aggregate (”In index: 34”). What is missing: which 34, and which of the remainder are known-but-not-indexed (and could make it in with content optimisation) versus entirely unknown (and need a push). That is exactly the distinction the coverage view provides. For content teams the difference is decisive: a ”known, not indexed” URL is a content problem, an ”unknown to Bing” URL is a distribution problem.

Limits and caching strategy

Bing's GetUrlInfo is a single-URL endpoint — one call per request. With 500 URLs that means 500 requests. Rankmio throttles this to 40 URLs per manual refresh with a 120 ms delay between calls and caches the result for 24 h.
The nightly cron bing_url_index_sync (04:00) fills the cache automatically with the oldest and as yet unchecked URLs. After roughly 15 nights a 500-URL sitemap is fully covered.
Only URLs returning HTTP 200 in the last sitemap crawl enter the coverage analysis — non-crawlable or 4xx URLs are filtered out beforehand.

Example from practice

Example: A content team publishes 12 new insights articles in one week. In the Bing coverage view on Friday, 8 of them appear as ”unknown to Bing”, 3 as ”known, not indexed” (Bing has them from the sitemap but has not indexed them yet) and 1 already as ”indexed”. The team marks the 8 unknown ones via bulk select and sends them to IndexNow with a single click. By the following Tuesday, 10 of the 12 URLs show as ”indexed” and the remaining 2 as ”known, not indexed” — a documented acceleration of at least 4-5 days compared with passive waiting.

Frequently asked questions

Why is my ”Bing query pending” figure so high?

This is not a Bing problem but a Rankmio cache state: ”pending” means ”we have not asked Bing about it yet”. A click on ”Refresh Bing status” checks the next 40 URLs live. In addition, a nightly cron fills the cache step by step.

Can I refresh all URLs at once?

No — 40 URLs per click, with a 120 ms delay between calls (roughly 5 seconds of runtime). This is gentler on Bing's API. With a 500-URL sitemap that amounts to around 13 clicks until everything is covered; simpler still: let the nightly cron do it, as it checks 40 URLs per project each night.

What is the difference to Bing's own ”URL Inspection” report?

Bing's report is a single-URL tool: you enter a URL and see its status. Rankmio coverage aggregates this across the entire sitemap in a table with filters, bulk actions and historical comparisons. For content teams the aggregated view is considerably more efficient.

How often are the figures updated?

Cache TTL is 24 hours per URL. The nightly cron bing_url_index_sync at 04:00 pulls in up to 40 URLs per project. The ”Refresh Bing status” click runs ad hoc. After every successful IndexNow submission, the cache entry for that URL is invalidated.

Used in Rankmio for

Open Bing coverage report

Go to the feature →

Last updated: 2026-07-11 · Browse all glossary entries