Copilot and Bing Traffic: Putting Search Insights Next to AI Crawls and Citations

When traffic moves, the first question is always whether it is a search problem or an AI problem. Those two have different owners, different fixes and different timelines, and teams often argue about it with screenshots from different tools.

The cleanest way to settle that is to put classic search data and AI data on the same page, per URL. That is what Search Insights is for. It overlays Google Search Console and Bing Webmaster traffic, including Microsoft Copilot, on AI crawls and citations.

Why Bing belongs in an AI visibility plan

Bing is easy to ignore in a Google-centric program. Microsoft Copilot is one of the AI surfaces worth tracking, and Bing Webmaster data is where you see how your pages perform in that ecosystem. If you manage visibility by looking only at Google Search Console, a whole engine's behavior is missing from your picture.

Copilot is one of the live-search platforms Promptwatch monitors through the real UI, next to ChatGPT Search, Google AI Overviews, Google AI Mode, Gemini, Perplexity, Alexa and Meta AI. Search Insights adds the Bing Webmaster side, so you can compare what is being cited in Copilot answers with what Bing reports about your pages.

The problem the overlay solves

Consider a page whose clicks drop. There are several competing explanations:

1. A ranking loss in classic search.
2. A change in the search result layout that pushes your result lower.
3. An AI answer now satisfying the query without a click.
4. A crawl or indexing problem.
5. Seasonal demand.

Each points to a different action, and each leaves different traces. A ranking loss shows in Search Console positions. An AI answer taking clicks may show stable impressions with falling clicks and rising AI citations. A crawl problem shows in the bot logs and errors. Without the data side by side, you guess, and the guess is usually whichever explanation the loudest person in the room already believed.

What to look at per URL

Pick your 20 most important pages and review each across five columns.

• Search clicks and impressions from Google Search Console.
• Search clicks and impressions from Bing Webmaster.
• AI crawler fetches, from Agent Analytics logs.
• AI citations, from citation analytics and the Page Tracker.
• AI-referred visits, from visitor analytics.

Promptwatch's 360 Insights view joins crawler logs, citation clicks and AI-referred visits per page, and Search Insights adds the search columns. The pattern in each row tells the story.

Reading the patterns

Impressions stable, clicks down, AI citations up. Your page is probably being used in answers without producing clicks, or users are getting what they need earlier. Consider whether the page offers something worth clicking for, such as a tool, a dataset or a decision aid.

Impressions down in Search Console, AI citations stable. A classic ranking problem. Treat it as SEO.

Bing clicks down, Google stable. Check Bing-specific issues, including indexing and Copilot citations. A drop here may not show anywhere in your Google reporting.

AI crawls absent, search steady. The bots are not reaching the page. Check robots.txt and CDN rules. Search can look healthy while AI discovery is blocked.

Everything flat, conversions down. Not a visibility problem at all. Look at the page itself and the funnel.

Connecting the data sources

Connecting Search Console to Promptwatch is a standard integration, and Bing Webmaster Tools is supported too. Prompt Explorer can also draw prompt suggestions from Search Console data, which is a helpful way to turn queries you already rank for into prompts to track.

For crawler logs, you will need a log source: Cloudflare, AWS CloudFront, Fastly, Vercel, Netlify, Akamai, Google Cloud CDN, a custom HTTP source or the WordPress plugin.

Plan gating

Check this part before you scope a project. Crawler logs start on Professional, so on Essential the "AI crawls" column will be empty. 360 Insights and site audit are on every paid brand plan. For agencies, every plan includes crawler logs, though the 360 Insights dashboard is not part of agency plans, so confirm your needs against the plan matrix.

A weekly 20-minute review

1. Open your top pages in the combined view.
2. Mark pages where search and AI signals disagree.
3. For each, write down the most likely explanation and the check that would confirm it.
4. Run the check. Do not skip this step.
5. Log the cause and the fix, with a date.

The disagreement pages are the interesting ones. Pages where search and AI agree usually need nothing but maintenance.

Limits to remember

Search Console and Bing report on their own terms, with their own sampling and delays. Do not expect exact reconciliation between them and an AI visibility tool. The aim is direction and diagnosis. Also, AI citation data comes from a tracked prompt panel, which is a sample of the questions real users ask, not a census.

The recommendation

If your reporting lives in several tools, you will keep having the "is it search or AI" argument without resolving it. Put the data on one page, per URL. Promptwatch does that with Search Insights, 360 Insights and the crawler logs, and it covers Copilot and Bing in the same view as Google. Connect Search Console and Bing Webmaster Tools first, since they are free sources, and see what the first month shows. Start at promptwatch.com.