Search Insights: Overlaying Google Search Console and Bing Data on AI Crawls and Citations
Why classic search data and AI visibility data belong in one view, and how to use a combined overlay to find pages that underdeliver.
Most teams run two separate worlds. One has Google Search Console and Bing Webmaster Tools, with queries, clicks, and impressions. The other has an AI visibility tool, with prompts, mentions, and citations. They answer similar questions about the same pages, and they rarely meet in the same report.
That separation hides the most interesting pattern: pages that perform in one world and fail in the other. A page that ranks well in Google but is never cited by an AI engine has a different problem from a page cited often but invisible in classic search. You only see the difference when the data sits side by side.
What a combined view shows
Promptwatch's Search Insights overlays Google Search Console and Bing Webmaster traffic on AI crawls and citations. Bing coverage includes Microsoft Copilot traffic. It sits inside the 360 Insights area, which joins crawler logs, citation clicks, and AI-referred visits per page. Topic Insights adds a view of where pages underdeliver for their topic.
The idea is simple. For each page, you can see how classic search treats it, whether AI bots fetch it, whether engines cite it, and whether visits arrive from AI engines.
Four patterns to look for
Strong in classic search, absent in AI. Ranking is fine, but the page is not cited. Check whether the AI bots fetch it at all. If not, look at robots.txt, bot protection, and rendering. If they do fetch it and still do not cite it, compare it with the pages that are cited for the same question.
Strong in AI, weak in classic search. The engines like the page, but classic search does not rank it. This is often a signal that titles, snippets, or internal links need work for classic queries. You have proof the content is good, so you do not need to rewrite it.
Crawled heavily, rarely cited. Bots fetch the page but no citation follows. The content may be too general, too long before the answer, or outclassed by competing sources.
Strong in both. Protect these pages. Add them to your refresh calendar and watch their citation decay.
Using Search Console to seed prompts
Search Console is also a source of prompts. The queries people actually typed are the best raw material for the questions they ask AI engines. Promptwatch's Prompt Explorer suggests prompts from Search Console, ranking keywords, People Also Ask, or any page. Start with queries that have impressions but a poor click rate, since those often reflect questions an AI answer is already satisfying without a click.
A weekly walk-through
- Open Search Insights for the last 28 days.
- Sort pages by classic clicks and mark the top twenty.
- For each, check AI crawl activity and citations.
- Flag the pages in the first pattern above: strong classic, no AI.
- Pick two and look at the crawler logs.
Step five usually finds the cause fast. A blocked path, a challenge page served to bots, or a rendering issue shows up as failed requests, and Agent Analytics provides failure explanations for those errors.
Why Bing is worth the trouble
Bing data is often skipped because its traffic is smaller than Google's. It deserves a look for a specific reason: Microsoft Copilot draws on the Bing ecosystem, so Bing Webmaster data gives a window into a source that Copilot-related visibility depends on. Promptwatch tracks Microsoft Copilot among its real-UI monitored platforms, so you can compare what Bing sees with what Copilot answers.
Common mistakes
- Comparing click counts with citation counts as though they were the same unit. They are not. Use rank order, not absolute values.
- Judging a page on a week of data. Use at least four weeks for classic search and watch the citation life cycle for AI.
- Ignoring country. Classic and AI visibility can both differ by market, and Promptwatch tracks by country on every paid plan.
Connecting the setup
Search Console and Bing Webmaster Tools both connect as data sources in Promptwatch. Crawler logs come in through Cloudflare, AWS CloudFront, Fastly, Vercel, Netlify, Akamai, Google Cloud CDN, a custom HTTP endpoint, or the WordPress plugin. Crawler logs start on the Professional plan, so Essential brands see less of the join.
What to do with the output
The output is a list of pages with a diagnosis each: access, content, linking, or competition. Feed it to the Action Board. The Discovery agent investigates your data weekly and proposes up to five evidence-backed actions, so the diagnosis ends up as tasks rather than as a slide.
The recommendation
Stop reading classic and AI data in separate meetings. Promptwatch puts Search Console and Bing Webmaster data on the same page-level view as AI crawls, citations, and AI-referred visits, which is the quickest way to learn why a page works in one world and not the other. Begin by listing your top twenty classic search pages and checking each one for AI citations. The gaps will set your next month of work.