Tracking AI visibility for a small site with Google Search Console and Bing Webmaster Tools
I’m Angel Baez, an Applied AI Engineer and co-founder of Prepa IN and Recupera. This is the measurement stack I actually use on small sites when the goal is search traffic plus AI visibility: being cited inside answers, not only ranking classic results.
You do not need an enterprise SEO suite on day one. Two free consoles cover most of the signal: Google Search Console (GSC) and Bing Webmaster Tools. Below is a practical setup, what to look at each week, and how we read the numbers at Prepa IN.
What you are measuring
For a small site, “AI visibility” is not a single vendor score. It is a bundle:
- Discovery in search (impressions, queries, pages) that still feeds AI Overviews and classic results.
- Indexation and crawl health so new posts can be found at all.
- Query and page trends so you know whether growth is real or just seasonality.
- Mentions and citations in assistants, which you sample manually or with brand-monitoring workflows until better first-party AI analytics mature.
GSC is the ground truth for Google. Bing Webmaster Tools is the second search engine you should not ignore. Together they tell you whether crawlers can find your content and whether discovery is compounding.
Step 1: Google Search Console as the source of truth
- Verify the property as a Domain property when you can (DNS), so
www, apex, and subdomains share one view. - Submit your sitemap (
/sitemap-index.xmlor/sitemap-0.xml) and confirm it stays “Success”. - Open Performance → Search results. Default the date range to Last 28 days, then compare to the previous period and to Last 3 months.
- Track four columns, in this order of importance for early AI/SEO work: Impressions → Clicks → CTR → Position.
- Slice by Queries, Pages, Countries, and Devices. Export CSV monthly so you can keep a baseline outside Google’s UI.
At Prepa IN, the headline win we talk about publicly is roughly 20x growth in Google Search Console impressions from a near-zero baseline. That figure is about impressions, not clicks. Impressions moved first as the agent-run blog and technical SEO compounded; clicks and conversions followed on their own lag.
When you review GSC each week, ask:
- Which new URLs gained impressions?
- Which queries look like questions an assistant would answer?
- Did impressions rise while CTR fell (common when AI Overviews or rich results answer on the SERP)?
Step 2: Bing Webmaster Tools as the second console
- Import the site from GSC if Bing offers that flow, or verify with DNS/file/meta.
- Submit the same sitemap you use in GSC.
- Check URL Inspection / Index, crawl stats, and the search performance report for Bing queries.
- Use Bing’s SEO reports for broken links and crawl anomalies as a cheap second opinion.
Even if Bing is a minority of sessions, a healthy Bing index is a useful canary: if Bing cannot fetch a page, something is often wrong for other crawlers too. Bing data also covers Microsoft search surfaces that GSC will never show.
A weekly 15-minute review ritual
| Minutes | Tool | Action |
|---|---|---|
| 0–8 | GSC | Compare 28-day impressions vs previous period; note top new queries and pages |
| 8–12 | Bing Webmaster Tools | Skim index errors and sitemap status |
| 12–15 | Notes | Write one sentence: what changed, what you will publish or fix next |
Keep a running doc (or agent memory) with the date, impression total, and one observation. The ritual matters more than any single dashboard.
How this ties to AI visibility work
Measurement without a content system stalls. The systems side (agent fleets, FAQ-shaped posts, llms.txt, structured data) is covered on the AI agents for growth: SEO, AI visibility and RevOps pillar. This post is the instrumentation layer: how you know the system is working.
A durable loop looks like:
- Publish answer-shaped content with clear claims and internal links.
- Make sure GSC and Bing can crawl and index it.
- Watch impressions before you overfit to clicks.
- Pick the next topic from query and page gaps in the consoles.
- Re-measure.
Common mistakes on small sites
- Optimizing only for clicks in week one. Impressions are the leading indicator; clicks lag, especially when answers appear on the results page.
- Skipping Bing because “nobody uses it.” The console is free and catches crawl issues early.
- Reading one console in isolation. If GSC impressions rise but Bing cannot index the same URLs, fix crawl or sitemap issues before you change the content strategy.
- Inventing AI-citation percentages. Unless you have a measured sample, say what you measured (GSC impressions, indexed pages, Bing crawl health) and leave the rest as qualitative checks.
What to do next
- Verify GSC (domain property) and Bing Webmaster Tools today.
- Submit sitemaps in both.
- Snapshot current GSC impressions (28-day and 3-month).
- Run the 15-minute weekly ritual for four weeks before changing the whole strategy.
If you want the production pattern behind Prepa IN’s content engine, start with the AI SEO pillar and the Claude managed-agent fleet write-up. Measurement is how those systems stay honest.
Frequently asked questions
What is AI visibility in practice?
AI visibility is how often your brand, product, or pages are cited or recommended inside answers from assistants such as ChatGPT, Perplexity, Google AI Overviews, and similar tools. You measure it with a mix of search console impressions, referral patterns, and brand mention checks. It is related to classic SEO, but the unit of success is being referenced inside an answer, not only ranking a blue link.
Why track Google Search Console impressions instead of only clicks?
Impressions show how often your pages appear in search results, including surfaces that feed AI Overviews and related discovery. Clicks lag when users get the answer on the results page. At Prepa IN we treat the roughly 20x growth in GSC impressions as the primary early signal that content and technical SEO are compounding, even when click growth is slower.
Do Bing Webmaster Tools matter if almost all traffic is Google?
Yes, for a small site. Bing Webmaster Tools is free, covers Bing and related Microsoft search surfaces, and is a second independent crawl and index report. It also helps you catch sitemap, indexation, and query issues that Google Search Console alone can miss.
What should I export from Search Console each month?
Export the Performance report as CSV for the last 28 days and the last 3 months, plus a Pages and Queries breakdown. Keep those files outside Google's UI so you can compare baselines after the console's date picker resets or the UI changes.
How often should a small site review these dashboards?
Weekly is enough for most small sites: GSC Performance (28 days and 3 months) plus Bing index and crawl summaries. Monthly is fine for a deeper look at top queries and pages that gained or lost impressions. Daily checking usually creates noise without better decisions.