Count AI Citations, Visits and Emails as Three Numbers

On Monday, October 19, the agent that writes my weekly site scorecard reported something new. Microsoft's AI answers, Copilot included, had cited this site.

The same report had two other lines. Visitors who arrived from an AI assistant. People who emailed me about work.

In my own weekly scorecards, AI citations showed up before any visits or emails did. Being seen, being visited, and being emailed are three different counts. Only conversations are why I run the sites.

The reports arrived this year

Until recently a small firm had no direct way to see whether AI answers used its pages. Now both big search engines report it.

Google's Search Console has a Generative AI performance report, open to every site since the end of August. It counts how often your pages appeared in AI Overviews and AI Mode, by page, country and device. It doesn't report clicks.

Bing's AI Performance report counts citations across Copilot and Bing's AI summaries, and shows the queries the AI used to find you. On October 13 Bing added a beta view that groups those queries into topics and lists questions where other sites get cited and yours doesn't. Smaller sites may not even see that view. Bing's own advice on it: "Treat the numbers as directional signals for planning, not as a precise ledger."

That's good advice for all of it.

Three numbers that move separately

The new reports make it easy to put one big count at the top of a dashboard. I keep three, and I keep them apart.

| Number | What it tells you | Where it comes from | | --- | --- | --- | | Seen | An AI answer showed or cited your page | Search Console's AI report, Bing AI Performance | | Visited | Someone clicked through from an AI assistant | Your site analytics, by referrer | | Asked | A real person contacted you about work | Your inbox |

A citation means an AI answer used your page. It doesn't mean anyone came to your site or asked you for work.

For a young site I expect that order: Seen moves first, Visited later, Asked last. The danger is a scorecard that puts Seen on top. Whoever reads it, person or agent, will start working to raise that count.

One week's swing proves little

I also run a few spot checks each week. I type questions a buyer might ask into an AI search tool, and note whether my pages come up.

One week, pages I care about came up for questions about AI enablement and how to manage AI agents across a company. Midweek I reworked the second page to aim at a bigger query.

The next Monday those pages no longer showed. Meanwhile a different question, about helping a startup become AI-native, showed up for the first time.

Did my rework cause the drop? I can't tell. Bing says the same about its own data: changes in citation trends "cannot be attributed to a specific cause or event." The answers depend on the question wording, the model, and what everyone else published that week.

The rule my reporting agent follows

The agent pulls the counts every Monday and proposes changes. These are the rules it works under:

• Report all three counts every week. If a source can't be read, it says "unavailable," never zero. We had weeks without Search Console access, and they're marked that way.
• Score the week on Asked. Seen and Visited are leading signals. They explain the week, and Asked grades it.
• Propose at most two page changes, each naming the count it should move, so next Monday can check it.
• Wait a second week before reacting to a swing. A page that loses its spot gets watched for one more week before anyone touches it, including to undo the last change. That's where my reworked page sits now.
• Before reworking a page that's winning one question, name the question you might lose. I didn't, and now I have a page I can't diagnose.

The point of writing the rules down is that an agent will do what the scorecard rewards. If the top line is citations, a weekly agent that edits pages will learn to chase citations. If the top line is conversations, citations stay what they are: a sign that the pages are being read. It's the same evidence-level habit I use in a personal agent's weekly review, and it's one part of the larger content loop behind this site.

Try it this week

Write down last week's three counts for your site:

1. Seen. Open Search Console's Generative AI performance report and Bing's AI Performance report. Note impressions and citations. If one won't load or shows nothing yet, write "unavailable."
2. Visited. In your analytics, count visits referred by AI assistants.
3. Asked. Count the emails or calls from people who found you that way, and ask them how.

Then pick the page with the most AI impressions and check one thing: does it say, in plain text, who you help and how to reach you? If an AI answer is going to quote you, that's the part worth quoting.

For the wider picture of how people and agents share work, start with Key AI interfaces or the field guide, From AI Sprawl to an Operating System.

Frequently asked questions

What is an AI citation in Search Console or Bing Webmaster Tools?

A citation, or an AI impression, means an AI answer showed or used your page. Google's Generative AI performance report counts impressions in AI Overviews and AI Mode. Bing's AI Performance report counts citations across Copilot and Bing's AI summaries.

Do AI citations mean people visited the site or asked for work?

No. A citation means an AI answer used your page. Visits come from your analytics, by referrer. Conversations come from the inbox. Keep the three counts apart, and score the week on conversations.

Does Google's Generative AI performance report include clicks?

No. It reports impressions by page, country, and device. Clicks from AI Overviews and AI Mode sit inside the ordinary Search Console performance report, mixed with the rest of web search, so you cannot read them as a separate AI-click line.

When should a weekly reporting agent change a page after an AI-visibility swing?

Wait a second week. Report Seen, Visited, and Asked every week, mark a source unavailable rather than zero if it cannot be read, and propose at most two page changes, each naming the count it should move. One week's swing does not tell you what caused it.