Articles ·

Verifying your domain in Bing Webmaster Tools and Google Search Console — the 15-minute setup

The one-line version: Google Search Console and Bing Webmaster Tools together cover the search-engine backends of every mainstream AI search product. GSC drives Google’s AI Overviews and AI Mode (Google’s own docs confirm the Domain property covers every subdomain and protocol variant). Bing Webmaster Tools drives ChatGPT Search retrieval, since ChatGPT retrieves exclusively from Bing’s index. Both use the same DNS TXT method against your DNS provider — total setup time for both, once DNS is live: ~15 minutes.

Why both, in that order

Neither engine is optional. Skipping Google means you won’t see which of your pages appear in AI Overviews or what queries trigger them. Skipping Bing means you’re blind to the entire ChatGPT Search citation surface — the second-largest AI-search citation pool after Google.

Do Google first, then Bing. Once Google is verified, Bing lets you import via OAuth in ~2 minutes and skip Bing’s own verification step entirely. Doing it the other way around means duplicating the DNS work.

Prerequisites

  • A working DNS zone for your domain (this guide uses Cloudflare, but the DNS TXT process is universal — Namecheap, Route 53, Google Domains, GoDaddy, and every other DNS provider follow the same pattern)
  • Edit access to that DNS zone
  • A Google account (for GSC) and a Microsoft account (for Bing)
  • A live sitemap.xml at your site root

If your DNS still resolves to a preview/staging host (Cloudflare Workers .workers.dev, Vercel preview, Netlify subdomain, etc.), verify on the real production domain — not the preview. Preview subdomains lose their verification the moment you migrate off them.

Part 1 — Google Search Console

Source: Google’s official verification docs.

Step 1: Add a Domain property

Two property types exist in Google Search Console: Domain and URL-prefix. Choose Domain — it covers http, https, and every subdomain (www., blog., shop., etc.) in one entry. URL-prefix requires a separate property for each protocol/subdomain combination.

  1. Open search.google.com/search-console
  2. Property selector (top-left) → Add property
  3. Choose Domain (left column), not URL-prefix
  4. Enter your domain name (no https://, no trailing slash) — e.g. example.com
  5. Google shows a DNS TXT record to add. It looks like:
    google-site-verification=aBc123XyZ456...
    

Copy the entire string, including the google-site-verification= prefix.

Step 2: Add the TXT record in your DNS provider

For Cloudflare:

  1. dash.cloudflare.com → select your domain
  2. DNS → Records → Add record
  3. Type: TXT
  4. Name: @ (Cloudflare shows the apex domain when you save)
  5. Content: paste the entire google-site-verification=... string
  6. TTL: Auto
  7. Proxy status: DNS-only (TXT records aren’t proxied)
  8. Save

For other DNS providers, the fields are the same — Host/Name = @ or blank, Type = TXT, Value/Content = the token.

Step 3: Verify

  1. Back in Search Console, click Verify
  2. If it fails, wait 5-15 minutes for DNS propagation (up to 48 hours on legacy registrars, per Google’s guidance) and retry
  3. Once verified, leave the TXT record in place forever — Google periodically re-checks. Removing it invalidates ownership.

Step 4: Submit the sitemap

  1. Search Console → left sidebar → Sitemaps
  2. Enter sitemap.xml in the field (Google prepends the domain automatically)
  3. Submit
  4. Status changes from “Couldn’t fetch” to “Success” within a few hours
  • URL Inspection tool (top search bar) — paste any page URL to see indexation status, canonical, and crawl issues
  • Settings → Users and permissions — add secondary emails as owners so ownership doesn’t die with a single account
  • Settings → Ownership verification — add a second method (Google Analytics, HTML file, meta tag) as a backup layer

Part 2 — Bing Webmaster Tools

Source: Bing Webmaster Tools setup guide, which mirrors Bing’s own documentation.

Fastest path: import from Google Search Console (~2 minutes)

Only works after GSC verification is complete.

  1. bing.com/webmasters → sign in with a Microsoft account
  2. On the home screen, choose Import your sites from Google Search Console
  3. Grant OAuth permission using the Google account that just verified your property
  4. Bing pulls the verified property list — select your domain
  5. Click Import. Bing:
    • Auto-verifies ownership via the Google linkage
    • Imports the sitemap submission you already made
    • Kicks off its own crawl

That’s the whole flow. Skip the manual verification section below unless import fails.

Fallback: manual DNS TXT verification

If the Google import isn’t available or you prefer independent Bing verification:

  1. Bing Webmaster Tools → Add a site
  2. Enter the canonical URL (with protocol): https://example.com
  3. Choose DNS TXT record as the verification method
  4. Copy the token — it looks like:
    msvalidate.01=ABC123DEF456GHI789JKL012MNO345PQ
    
  5. In your DNS provider (same process as the Google TXT record):
    • Type: TXT
    • Name: @
    • Content: paste the full msvalidate.01=... string
    • Save
  6. Wait 5-15 minutes for propagation
  7. Back in Bing Webmaster Tools, click Verify

Submit the sitemap to Bing

Skip if you used the Google import path — the sitemap comes across automatically.

  1. Bing Webmaster Tools → left sidebar → Sitemaps
  2. Enter the full URL: https://example.com/sitemap.xml
  3. Submit
  4. Bing typically processes sitemaps within 24-48 hours

Register your IndexNow key

If you’ve already wired IndexNow into your build pipeline, Bing should auto-register the key on first successful submission. To confirm:

  1. Bing Webmaster Tools → Settings (gear icon) → API AccessIndexNow
  2. The key should be listed as active
  3. If it isn’t, you can add it manually here

The reports that matter

Once verified, these give the fastest read on how Bing (and by extension ChatGPT Search) sees the site:

  • Search Performance — clicks, impressions, top queries; Bing’s version of GSC Performance
  • URL Inspection — the fastest way to answer “why isn’t ChatGPT citing this page?”; if URL Inspection shows the URL as unindexed, you have a Stage 1 failure per the ChatGPT three-stage pipeline
  • Backlinks — Bing’s inbound link graph, materially different from Google’s; useful for the training-data authority-building work
  • Site Explorer — every crawled page on your domain

What to expect after verification

Google Search Console:

  • First crawl within 24 hours; full sitemap ingestion within 2-7 days
  • Performance data (clicks, impressions, queries) starts populating within 3-7 days for a new domain
  • AI Overviews eligibility signals appear in Performance data within ~2 weeks
  • Coverage reports (indexed / not indexed) populate within 3-7 days

Bing Webmaster Tools:

  • First crawl within 24-48 hours (per Bing’s stated processing time)
  • ChatGPT Search retrieval eligibility follows Bing indexation directly — every URL that shows “Indexed” in Bing URL Inspection is a candidate for OAI-SearchBot to cite
  • Full sitemap processing within 48 hours

The measurement loop

After both verifications land, this is what your monthly check-in looks like:

  1. Google Search Console → Performance — click-through rate on queries where your pages rank. Low CTR on high-impression queries usually means the AI Overview is answering instead of driving clicks.
  2. Google URL Inspection — spot-check any page that mysteriously fell out of AI Overviews. If Google shows “Discovered - currently not indexed,” the fix is external referring domains, not more content.
  3. Bing URL Inspection — spot-check the same pages. Bing lags Google materially; a page indexed on Google may still be missing from Bing weeks later.
  4. Bing Search Performance — this is the closest available proxy for ChatGPT Search citation share. Rising Bing impressions on your priority queries correlates with rising ChatGPT citation eligibility.
  5. Cross-reference with Perplexity monitoring — see the Perplexity model tiers article for the parallel measurement axis. Perplexity’s Sonar retrieval doesn’t flow through either console — you need to test it directly.

Common problems and fixes

“TXT record not found” after 30 minutes

  • Check the record propagated: dig @8.8.8.8 example.com TXT should list both the Google and Bing tokens
  • Ensure the record is on the apex (@), not a subdomain
  • Confirm Proxy status is DNS-only in Cloudflare

“Verification succeeded then failed”

  • Google and Bing periodically re-verify. If the TXT record was removed after initial verification, ownership is lost. Never delete the record.
  • If the domain expires or nameservers change, verification is lost. Renew and re-verify.

Google shows “Domain property” but no Performance data

  • Domain properties take 3-7 days for Performance data to populate on brand-new domains
  • Confirm the sitemap status is “Success” — “Couldn’t fetch” means the sitemap URL isn’t reachable; test with curl -sI https://example.com/sitemap.xml

Bing shows “0 pages indexed” 48 hours after submission

  • Normal for new domains with zero external referring links
  • Post the site URL somewhere Bing already crawls (Reddit, HackerNews, a LinkedIn article) — Bing weighs external signals heavily for indexation velocity on new domains
  • IndexNow submissions accelerate crawling but don’t override the need for external references

The strategic point

Both consoles are free, both take under 10 minutes each, and neither is optional if you care about AI-search visibility. The gap between “verified in both” and “verified in neither” is the difference between a measurable GEO program and a blind one. Do it once, do it early, and every subsequent metric you care about becomes observable.

The ChatGPT Bing indexation article covers the deeper Stage 1 work that becomes possible once Bing Webmaster Tools is verified. The measuring GEO article covers the four-metric framework that both consoles feed into.

Related reading: What actually gets ChatGPT to cite you — the three-stage pipeline that starts with Bing indexation. ChatGPT Stage 1 in depth — the deeper Bing / OpenAI crawlers / IndexNow work. Measuring GEO in 2026 — the four-metric framework the consoles feed.