We respect your privacy.

We use strictly necessary cookies to keep you signed in and to protect against CSRF. With your permission we also use a small amount of first-party analytics to improve the product. We do not sell your data and we do not use third-party advertising trackers. See our cookie policy and privacy policy .

← All posts

Google now writes your citation card blurb

Crawlmind Engineering··5 min read

A citation card blurb is the short description Google shows under a source link in an AI Overview, and Google is now testing blurbs that it writes itself instead of lifting them from your page.

That changes what a citation card is. Until now, the text in the card was a snippet: a passage pulled from the page, or the page's meta description. If you owned the page, you owned the words, even if Google chose which words. In the test, the words belong to a summarizer.

#What is being tested

Search Engine Roundtable reported in October 2026 that Google appears to be testing or rolling out AI-generated summaries inside the citation cards that sit beside AI Overviews. The test was spotted by SEO consultant Brodie Clark, who noted that the card text does not appear in that exact form on the cited page. It is a summary built from whatever Google considers most relevant to the query. Barry Schwartz saw the behavior on some of his test queries and not on others, and the report includes no statement from Google. Treat it as a test, not a launch.

It is also one of several experiments on the same component. Days later the same outlet reported that Google may be testing removing the citation card from desktop AI Overviews for some users, possibly a bug, and Google has previously tested placing the cards at the bottom of the answer instead of the side. The card's position, presence, and text are all moving at once.

#Why this is a different kind of rewrite

Google has rewritten snippets for years. Its own documentation says snippets are created automatically from page content, that the meta description is used only when Google thinks it describes the page better, and that the same page can show different snippets for different searches. An Ahrefs study of 20,000 keywords found Google replaced the hand-written meta description 62.78% of the time. That data is from 2020 and covers desktop results only, but the direction has never been in doubt.

The difference is the source of the replacement. A rewritten classic snippet is still a substring of your page. You can search your HTML for it, find the paragraph, and fix that paragraph. A generated blurb is a paraphrase. There is no paragraph to find. If the summary overstates a claim, drops a qualifier, or describes the page as covering something it covers only in passing, the error lives in Google's output, not in your source.

This matters more inside an AI Overview than on a classic results page. The card sits next to an answer that has already been written. The reader is deciding whether to click based on two pieces of machine-written text: the answer and the blurb. Your title is the only text in that unit you wrote.

#What you can still control

Google's AI features documentation lists the same controls for AI Overviews and AI Mode as for regular snippets: nosnippet, data-nosnippet, max-snippet, and noindex. It also says a page must be indexed and eligible to show with a snippet to appear as a supporting link. Those controls limit what Google may take from the page. None of them lets you supply the card text.

That leaves the inputs a summarizer reads. A summary of the passage most relevant to a query is only as accurate as that passage. Practical steps:

  • Make the relevant passage self-contained. If a section answers a common question, open it with a sentence that states the answer and its main condition. A summarizer that compresses a well-scoped paragraph has less room to drop the condition.
  • Keep qualifiers next to the claim. "Supports SSO on the Enterprise plan" survives summarization. "Supports SSO" in one paragraph and "Enterprise only" three paragraphs later may not.
  • Write titles that carry the page's scope. The title is the only text in the card you still author. A title that names the subject and the audience limits how far a blurb can drift.
  • Check data-nosnippet placement. If you used it to hide boilerplate, confirm it is not also hiding the passage that best answers the query. Google's documentation does not spell out how the attribute interacts with generated summaries, so test before relying on it.
  • Keep meta descriptions accurate anyway. They were already a suggestion rather than a guarantee, and they still feed the classic results page.

#How to monitor it

A snippet rewrite could be audited with string matching: compare the shown text to the page and flag what changed. A generated blurb needs a different check. The question is no longer "which part of my page did Google show" but "does Google's description of my page match what the page says."

That is the same check you already need for AI answers themselves. For each query where your page is cited, capture the card text along with the answer, then compare the claims in the blurb against the claims on the page. Look for three failure types: a claim the page does not make, a missing condition (plan, region, version, date), and a scope error where a side mention is presented as the page's main topic. Record the capture date. Because Google is testing, the same query may show a generated blurb one day and a classic snippet the next, and you want to know which version a reader saw.

When you find a mismatch, the fix still happens on your page. Rewrite the passage the blurb was most likely summarizing so that a compressed version of it stays correct, then recheck the query after Google recrawls. Google's documentation notes that recrawling can take several days to several months, so log the change and do not expect the card to update the same week.

#The practical read

Nothing here is confirmed as a permanent change, and the card itself may move or disappear in the next round of tests. The direction is still clear. Google already writes the answer. It is now testing writing the description of the sources too. The text a reader uses to decide whether to visit you is moving further from text you wrote, and the only lever left is making the source passage hard to summarize wrongly.

Related field notes

Share or discuss

Field notes in your inbox

New posts, no spam. Roughly monthly. Unsubscribe with one click.