← Back to the full checklist

GA4, Search Console & Bing: The Setup Nobody Explains Clearly

DISCOVERY · Part of the Idea to Traffic checklist

A site can be fully live, fast, and well-built — and still be functionally invisible to Google and Bing for weeks, simply because a few specific setup steps never happened. None of these are hard individually. They're just scattered across different products with confusingly similar names.

Google Analytics: the two IDs that get confused constantly

When you install GA4, you get a measurement ID — it looks like G-XXXXXXXXXX. This is what goes in your site's tracking snippet.

Separately, every GA4 property also has a numeric property ID — just a plain number, like 123456789. This is a completely different identifier, and it's the one you need for anything involving the Analytics reporting API rather than just the tracking snippet itself. Mixing these two up is one of the most common points of confusion in the entire setup process.

To find your numeric property ID: in Google Analytics, go to Admin (the gear icon) → under the Property column → Property details. It's shown directly there, separate from the measurement ID.

Google Search Console: verification, and what it actually unlocks

Search Console is not analytics — it's how you tell Google "this domain exists, here's what's on it," and it's how you see actual search performance data (what you rank for, impressions, clicks) that Analytics doesn't show you.

The cleanest verification method is a domain property using a DNS TXT record — this covers every subdomain and protocol (http, https, www or not) under one verification, instead of verifying each URL variant separately. Add the TXT record your DNS provider gives you, wait for it to propagate (usually minutes, not hours), then verify.

Once verified, submit your sitemap.xml through Search Console directly — having the file exist on your server is not the same as submitting it. This step is easy to genuinely forget because nothing visibly breaks if you skip it; your site just gets discovered slower.

The indexing reality check

Even with everything set up correctly, don't expect instant results. A newly submitted page commonly sits in a "discovered, not yet indexed" state for days before Google actually crawls it — this is normal, not a sign something's broken. There's no legitimate way to force this faster for regular content; Google's automated indexing-request tools are officially restricted to job listings and livestream events specifically, and using them for anything else violates their terms.

Bing: the step almost everyone skips

Bing still represents real search volume, and setup is genuinely fast if you've already done Google Search Console: Bing Webmaster Tools has a feature that lets you import already-verified sites directly from Google Search Console, skipping DNS verification entirely a second time. Sign into Bing Webmaster Tools, look for the import option, and authorize it with the same Google account that owns your verified Search Console properties.