Indexed on Bing but Not Google: Why and How to Fix It

By Ugur Saritepe · July 25, 2026

Search your domain on Bing and it is there. Search it on Google and nothing comes back. Most of the time nothing is broken: Bing indexes fast and permissively, Google indexes slowly and selectively. But a real block produces the same symptom, and the URL Inspection tool in Search Console separates the two in about two minutes.

First, stop trusting site: and ask URL Inspection

A site:yourdomain.com search is a rough probe on both engines. It routinely misses pages that are indexed and it never tells you why a page is absent. The ground truth for Google is the URL Inspection tool in Google Search Console: paste the exact URL and read the status line.

The result sends you to exactly one branch of this guide:

• You have no Search Console property at all: that is already your answer. Go to cause 1, Google may have never heard of your site.
• “URL is not on Google” with a named reason such as Duplicate, Google chose different canonical, Blocked by robots.txt, or noindex: a real fold or block. Go to causes 2 and 3.
• “Discovered - currently not indexed” or “Crawled - currently not indexed”: nothing is blocking you. Google knows the page and has not picked it yet. Go to cause 4.

The four causes, ordered by how often they are the answer

1. Google has never heard of your site

Bing learns about new URLs by push: the IndexNow protocol lets a site announce changed URLs the moment they deploy, and much of the web sends those pings without the owner knowing, because Cloudflare and several WordPress SEO plugins submit them automatically. Google does not consume IndexNow at all as of July 2026, so it discovers your site only by pull: crawling links, or reading a sitemap you submitted. A site can sit in Bing's index with zero effort from you while Google waits for a link path that never comes.

30-second check: do you have a verified Search Console property, and does its Sitemaps page show your sitemap with a Success status? Good: both exist. Bad: no property, or no sitemap submitted. Fix: verify a domain property, submit yourdomain.com/sitemap.xml, and use Request Indexing on the homepage plus your few most important pages. Our guide on what an XML sitemap is and why Google cannot read yours covers the sitemap traps.

2. Google indexed a different version of your domain

Google folds duplicate URLs into one chosen canonical, the single URL it treats as the real one. If your site answers on both www and non-www, or on both http and https, Google may have indexed the other host. Search the version you always type and it looks like you are not on Google at all, while Bing happily shows the variant you searched.

Say you registered example.com but every marketing link points at www.example.com, and neither redirects to the other. Google picks one, usually the linked one, and site:example.com comes back empty even though your content is indexed and ranking under www.

30-second check: URL Inspection reads Duplicate, Google chose different canonical, or a site: search on the other three host variants returns your pages. Fix: pick one version, 301-redirect the rest, and make every canonical tag agree. Our www vs non-www guide walks through testing all four variants in 30 seconds.

3. Something blocks Googlebot specifically

Crawler access is per engine, not global. A robots.txt file can carry a User-agent: Googlebot group that a Bingbotgroup does not share, and firewall or bot-protection rules, often tightened after a scraper wave, can challenge Google's crawler while letting Bing's through. We do the inverse deliberately on our own games site: its robots.txt disallows the thin /game/ detail pages for Bingbot only, while Googlebot stays fully allowed. Per-engine rules are normal, so confirm yours are intentional.

30-second check: open yourdomain.com/robots.txt and read every User-agentgroup for rules that hit Googlebot. Then run URL Inspection's Live Test, which fetches the page as Googlebot from Google's own infrastructure. Good: the live test loads the page. Bad: the live test fails while your browser works, which means a block sits between Google and your server. Fix: remove the Googlebot rule or allowlist verified search crawlers in your firewall. If third-party SEO tools also error on your site, read our guide to 403 errors that only crawlers see.

4. Google knows the page and has not picked it yet

This is the structural gap behind most “Bing has me, Google does not” cases. Bing's bar for inclusion is low. Google crawls conservatively and indexes selectively, and its own documentation is explicit that indexing is never guaranteed, even for a perfectly crawlable page. On a new domain the wait is typically weeks, and thin or near-duplicate pages can wait forever.

30-second check: URL Inspection shows Discovered - currently not indexed, Google has not visited yet, or Crawled - currently not indexed, Google visited and declined. The two need different fixes, and our Discovered - currently not indexed guide splits them in detail. Fix: link the page from already-indexed pages, keep the sitemap fresh, publish genuinely distinct pages on a steady cadence, use Request Indexing once, and give a new site weeks rather than days.

The verdict: run these in order

Stop at the first one that matches:

1. No Search Console property or no submitted sitemap: cause 1. Set both up today, that alone often ends the mystery.
2. URL Inspection names a reason: a canonical fold is cause 2, a robots rule or failed live test is cause 3. Fix the named thing.
3. Status is Discovered or Crawled - currently not indexed: cause 4. Nothing is broken. Build internal links, keep publishing, and wait.

What Bing-only visibility is worth while you wait

Set expectations with a real same-site comparison. Over the same month, June 23 to July 22, 2026, our games site game-scout.app logged 51,016 impressions and 921 clicks on Google against 7,359 impressions and 190 clicks on Bing. Once Google lets you in, it pays roughly seven times more. That is why this symptom feels urgent.

But Bing-only indexing is not a waiting room with nothing in it. Microsoft Copilot retrieves its web answers from Bing's index, and ChatGPT has used Bing as a retrieval source. The deploy script on our own site states its purpose in its header comment: Bing indexation is the prerequisite for Copilot and ChatGPT retrieval. A page indexed on Bing but not Google can already be found and cited by AI assistants today.

How to confirm Google finally indexed you

Re-run URL Inspection on the same URL. Good:the status flips to “URL is on Google.” After fixing a block (causes 2 and 3), expect the flip within days to a couple of weeks of the next crawl. For a new site riding out cause 4, weeks is normal, and movement through the states is progress: unknown to Discovered means Google found it, Discovered to Crawled means Google visited. A site:yourdomain.com/the-exact-path search works as a rough second probe. If pages index but never earn clicks, that is a separate diagnosis, covered across our symptom guides.

From experience: we run indexing as two separate tracks

Every deploy of game-scout.app ends with a script that submits the changed URLs to Bing's IndexNow endpoints. On June 21, 2026, for example, it announced a batch of 12 changed URLs and both endpoints answered with HTTP 200 within seconds. The Google side has no equivalent pipe: the same URLs go through Request Indexing in Search Console by hand, and our project log for those weeks repeatedly reads “Bing submitted, Google manual, still pending.”

The result is exactly the symptom this guide is about: our new pages routinely appear in Bing days before Google shows them. We have never treated that as a bug, because it is the protocol difference doing what it does. Two details from that routine are worth copying. We push only changed URLs, since Bing's own guidance on IndexNow is that less is more. And we keep the two tracks honest per engine, which is how we know a per-engine robots rule (cause 3) is easy to create and easy to forget.

That per-engine blind spot is also what the robots and index-signals checks in our free Triage Report are built to catch from the URL alone, before you spend weeks blaming Google for a rule your own config is enforcing.

FAQ

Why does Bing index sites faster than Google?

Bing accepts push notifications: the IndexNow protocol lets a site announce new URLs the second they go live, and many hosts and plugins send those pings automatically. Google only pulls, discovering URLs through crawling, sitemaps, and links, and it applies a stricter selection bar before letting a page in. Push plus a lower bar is faster than pull plus a filter.

Does Google support IndexNow?

No. Google ran an IndexNow test in 2021 and, as of July 2026, has not adopted it. To tell Google about new URLs you use a submitted XML sitemap and the Request Indexing button in Search Console's URL Inspection tool. Google's separate Indexing API only covers job postings and livestream pages.

Is being indexed on Bing but not Google a penalty?

Almost never. A real Google penalty is a manual action, and Search Console lists it under Security and Manual Actions, so you can check in seconds. If that panel is empty, your symptom is discovery, a duplicate-version fold, a crawler block, or ordinary selection lag, all of which this guide covers.

Is Bing indexing worth anything on its own?

Yes. Microsoft Copilot answers questions by retrieving from Bing's index, and ChatGPT has used Bing as a retrieval source for web answers. A page indexed on Bing but not Google can already be found and cited by AI assistants, which is real visibility while you wait for Google to catch up.

In your AI assistant

Ask your AI about your own site

TrafficTriage plugs into Claude, Cursor, and ChatGPT. Your assistant runs the 8 checks, reads your Search Console data, and can even check your site every morning. Free account, no API key, nothing to install.

Sign up freeSee how it works