Search Console + Bing Importer: Cross-Reference Your Co...

Google Search Console tells you which pages are indexed, which are "Discovered but not currently indexed," and which have errors. Bing Webmaster Tools has its own coverage report with its own categories. Both are useful. Neither talks to the other.

The practical problem: you have pages that Google indexes but Bing doesn't. You have pages in your sitemap that neither engine has picked up. You have pages that were indexed last month but quietly dropped out this month. None of these show up as alerts anywhere unless you manually export both CSVs and compare them yourself.

That's exactly what the Search Console + Bing Importer does.

The two silos problem

GSC's Coverage report categorizes every URL it knows about into buckets: Valid, Valid with warnings, Error, and Excluded. Under Excluded, you get sub-reasons like "Discovered - currently not indexed," "Crawled - currently not indexed," "Duplicate without user-selected canonical," and about twenty others.

Bing Webmaster Tools has its own URL inspection and crawl reporting, but the categories don't map 1:1 to GSC's. Bing might report a URL as "Discovered" while GSC calls the same URL "Crawled - currently not indexed." Same URL, same problem, different terminology, different dashboards.

When you're managing a site with hundreds or thousands of pages, switching between two dashboards and eyeballing the overlap is not a real workflow.

What "Discovered - not indexed" actually means

This is the most common coverage issue I see across client sites, and it's the one that causes the most confusion.

"Discovered - currently not indexed" means Google found the URL (usually via sitemap or internal link) but hasn't bothered to crawl it yet. It's in the queue. The queue might be long. Google is making a judgment call about whether your page is worth crawling based on the site's overall crawl budget, the page's perceived value, and how many other URLs are competing for attention.

This is not a penalty. It's a prioritization decision. But if half your site lives in this bucket for months, you have a structural problem: either the pages aren't being linked to internally, the sitemap is submitting URLs that Google considers low-value, or the site's crawl budget is exhausted by higher-priority pages.

The fix depends on the cause. The first step is knowing how many pages are in this state and whether the number is growing or shrinking month over month.

How the tool works

The Search Console + Bing Importer runs in two modes:

Mode 1: Live Site Audit. Enter a URL and the tool fetches the sitemap, checks robots.txt, looks for GSC and Bing verification tags, and reports the sitemap-declared URL count against what's discoverable. This gives you a quick baseline without needing any CSV export.

Mode 2: CSV Import + Cross-Reference. This is where it gets useful. You export your GSC Coverage report as CSV (Pages report, then export). You export your Bing Webmaster Tools URL report. You paste the sitemap URL. The tool:

Parses both CSVs and normalizes the URL formats
Fetches the sitemap and extracts all declared URLs
Builds a three-way comparison: sitemap vs. GSC vs. Bing
Flags URLs in sitemap but not indexed by either engine
Flags URLs indexed by one engine but not the other
Flags "Discovered - not indexed" and "Crawled - not indexed" URLs separately
Detects month-over-month regression if you paste two snapshots

Everything runs in your browser. The CSV data never leaves your machine.

Month-over-month tracking matters

A single snapshot of your coverage data is useful but limited. The real value is in comparing two snapshots taken a month apart.

If your "Valid" count went from 450 to 420, thirty pages dropped out of the index. Which thirty? Are they important? Did Google recrawl and decide they were thin content, or did a technical change (robots.txt edit, noindex tag, canonical shift) accidentally de-index them?

If your "Discovered - not indexed" count went from 80 to 150, your crawl budget problem is getting worse, not better. That's the kind of signal that doesn't trigger any alert in GSC but means your newer content isn't reaching the index.

The tool handles this by accepting two CSV snapshots and computing the delta. Pages that were Valid last month and aren't this month get flagged explicitly.

The sitemap as ground truth

Your sitemap is the canonical list of "pages I want search engines to index." When the tool finds a URL in your sitemap that neither GSC nor Bing Webmaster Tools has indexed, that's a direct gap. You asked them to index it. They didn't.

When the tool finds a URL indexed by both engines that isn't in your sitemap, that's a different signal: either your sitemap is incomplete, or you're indexing pages you didn't intend to (pagination, filter URLs, staging pages).

Both directions matter. Both are invisible if you're only looking at one dashboard at a time.

When this saves real work

The sites that benefit most from this tool are mid-size properties: 200 to 5,000 pages. Small enough that you haven't invested in enterprise SEO tooling, large enough that manual CSV inspection isn't practical.

If you're building web properties from scratch and want to understand what infrastructure like this means for your launch timeline, I covered the full indexing and deployment stack in The $97 Launch.

Run the importer

The Search Console + Bing Importer is free, runs in your browser, and needs no OAuth connection. Export your CSVs, paste them in, and see where the gaps are.

Fact-check notes and sources

GSC Coverage report categories and definitions: Google Search Console Help - Index Coverage
Bing Webmaster Tools URL submission and reporting: Bing Webmaster Help
"Discovered - currently not indexed" explanation: Google Search Central - Crawl Budget
Sitemap protocol specification: sitemaps.org

Search Console + Bing Importer: Cross-Reference Your Coverage Data Before It Costs You Traffic