What we mean by a Surface Diet
The Surface Diet is a planning framework: identify the AI products your buyers use, inspect the sources those products cite for relevant questions, and decide which missing evidence is worth producing. It is not a fixed list of websites that every company must publish on.
For a small business, that distinction saves work. You do not need a video channel, a community programme and a long list of directory profiles just because a broad report contains their names. You need to understand where a buyer is getting an incomplete or unhelpful answer about the problem your company solves.
A useful source can be your own service page, an independent comparison, a demonstration, a professional profile or a relevant discussion. The choice should follow the question and the evidence gap. Counting how often a large domain appears across unrelated prompts is not enough to make that choice for your business.
This article reviews published observations and proposes a way to apply them cautiously. It does not claim that TCC has rerun the cited datasets or established permanent preferences for ChatGPT, Perplexity, Claude, Copilot, Gemini, AI Mode or AI Overviews. Where we do not have comparable observations, we do not fill the gap with a ranking.
Methodology and scope of this review
The correction started by separating three kinds of material: direct product observations, externally published research and our own recommendations. The earlier article's search-tool outputs could not establish what a person saw in the named AI interfaces. We removed those outputs as evidence of product behaviour rather than relabelling them as equivalent tests.
The retained evidence comes from linked primary publications by Tinuiti and Ahrefs, plus Google's documentation about its search features. We selected them to illustrate measurement boundaries, not to create a complete census of AI citations. Their datasets are not merged, their counts are not added together, and their percentages are not averaged into a market-wide estimate.
Our interpretation is narrower than a universal channel prescription. A reported source pattern can suggest a question to investigate in your category. It does not establish a causal advantage from publishing on that source, a guaranteed recommendation, or a return on the cost of producing an asset.
The workflow later in this article is a proposed TCC measurement protocol. The example buyer questions are illustrative, not records of searches we ran. That separation matters: a sensible plan for collecting evidence should not be presented as evidence that the plan has already succeeded.
Name the product before comparing the result
An AI surface is the product experience in which an answer appears. Record the product and mode actually used, not just the model family or company name. A model name alone does not describe the interface, available retrieval tools or collection conditions.
For Google, keep AI Overviews, AI Mode and the Gemini app in separate reporting rows. For a chat product, record whether search was enabled or invoked when that information is available. If a measurement platform uses an API or automated collection method, label that method rather than assuming it duplicates the consumer interface.
A tool returning web results and a synthesized answer is evidence of that tool's response. It is not evidence that the same response appeared in another product. If your provider cannot access a requested surface, the honest entry is not measured. An inaccessible product should not quietly receive the results of a different one.
This does not make tool-based monitoring useless. It makes the label part of the measurement. A repeatable API-based series can help track changes under its own conditions. A manual interface check can answer a different question about the buyer experience. Keep both if useful, but do not mix them in an unexplained trend.
What the linked research actually supports
Tinuiti: product differences within a defined commercial sample
Tinuiti's Q1 2026 report covers nine commercial categories and seven AI features using fixed mid- and lower-funnel prompts. Its cross-platform aggregate weights platforms equally, not by market share. In January 2026, Reddit supplied 24% of Perplexity citations in that sample. The Google products also differed:
Share of all citations in the sample
Share of all citations in the sample
Share of all citations in the sample
What the chart shows: Social platforms accounted for 3% of Gemini citations, 9% of AI Mode citations and 13% of AI Overview citations in Tinuiti's sample. These are separate products, not a single Google rate.
Our planning inference is to keep product-level reporting separate. It is not that a particular business should copy the report's average source mix. You still need to inspect relevant answers and decide whether the cited material exposes a gap you can credibly address.
Ahrefs: the denominator changes the meaning
Ahrefs' March 2026 analysis covered 863K keyword results pages and 4M AI Overview URLs. YouTube represented 18.2% of cited URLs outside Google's top 100 results for the same keyword; that subset represented 5.6% of all cited URLs. Neither number is a universal YouTube citation share.
The report also distinguishes the first ten result blocks from the first ten organic blue links, and notes a parsing-method change from its earlier analysis. Those details matter when interpreting a headline or comparing periods.
For your own reporting, preserve the full measurement definition beside a number. A sentence saying which subset was counted is more useful than a larger-looking percentage stripped of its denominator. Do not turn a subset finding into a general recommendation to shift your publishing budget.
Google: a shared search foundation
Google's guidance for AI features describes AI Overviews and AI Mode using related searches, or query fan-out, to gather supporting information. It also says there are no additional technical requirements beyond normal Search eligibility. That documentation does not promise that an eligible page will be selected.
Our recommendation is to fix access problems and missing information before multiplying channels. A clear, usable source is a sensible starting point. Whether an answer cites it still needs to be observed, and whether that citation helps the business needs its own assessment.
Why citation leaderboards can mislead a buyer
A domain can accumulate many links because it publishes across many subjects. Your business may operate in one narrow category and one geography. A broad leaderboard can identify a place to investigate, but it does not show that a page about your service has the same opportunity as the pages driving that domain's overall count.
The counted object also matters. A report can count link appearances, unique URLs, unique domains or answers containing a domain. Repeated links to the same page can affect these measures differently. Without the definition, a comparison between two percentages can conceal a comparison between two different questions.
Some reports select commercial prompts; others include general information requests. Some include only answers that produced citations. Others keep every completed answer in the denominator. Neither choice is automatically wrong, but changing the population can change what a reader is entitled to conclude.
A company should therefore avoid treating a league table as a production brief. Before commissioning an asset, inspect actual source pages attached to relevant answers. Work out what job each source is doing: establishing a fact, comparing options, explaining a process or providing independent testimony. That job is the useful clue.
Separate the outcomes you want to improve
Start with answer accuracy. Is the company described correctly, including its services, audience and relevant boundaries? An answer that sends the wrong kind of buyer to your site is not necessarily useful visibility. Log the inaccurate claim and the source supporting it where one is visible.
Then separate mentions, citations and recommendations. A mention is the company name appearing in the answer. A citation is a visible source link. A recommendation is an answer presenting the company as an option for the buyer's stated need. Decide how your reporting will classify each event before looking at the results.
Commercial outcomes sit further along the journey. Referral visits can show that someone followed a link. Qualified enquiries require an agreed qualification rule. Revenue requires a reliable connection to a transaction or customer record. Do not label any of these as measured when you only have a screenshot of an answer.
This separation makes the work easier to diagnose. Accurate answers with few visits suggest a different problem from inaccurate answers that attract unsuitable leads. You can improve a service page, clarify an offer or change a distribution plan based on the actual constraint, without pretending every problem is a shortage of citations.
Build a question set around a real buyer
For an initial audit, choose a clearly defined audience and a commercial decision. Start from questions already asked in sales conversations, enquiry forms or customer support. If those records are unavailable, write a provisional set and label it as a hypothesis to validate with the business.
Here are illustrative questions for an accounting firm serving small businesses. These are prompt examples, not measured search results:
- How do I choose an accountant for a small business?
- What should a monthly accounting package include?
- How do I switch accountants without disrupting payroll?
- What should I compare before hiring an accountant in my city?
The wording covers selection, scope, switching and local fit. Adapt it to the actual service rather than copying the same prompts into every account. An e-commerce fulfilment company or a local maintenance business will have different buying objections and different evidence needs.
Keep questions that name the company separate from questions that do not. A branded question tests representation when the buyer already knows the name. An unbranded question tests whether the company enters the answer without being supplied. Both can matter, but combining them hides where discovery is actually happening.
Freeze a core question set for comparison over time. Keep a second list for new questions discovered during research. When the core set needs a substantive change, version it and explain the break in the series. Do not delete difficult prompts simply because the company remains absent from them.
Capture a record another person can inspect
A useful answer record connects the question to the output and its sources. Retain the prompt, product, mode, date, language and relevant location settings. Keep the response text and visible citation URLs. Where permitted, retain a screenshot or response export so a later reviewer can check the interpretation.
Record settings that are known, and mark unknowns honestly. Do not invent a model version because a product uses that model family elsewhere. If search was unavailable or a run failed, preserve that status. A completed answer without a citation is a valid observation; a failed request is a collection failure.
For each cited URL, record enough page context to understand why it matters. A domain name alone cannot distinguish a detailed service comparison from an unrelated news item. Note the page type, the buyer question it answers and whether it discusses your company, a competitor or only the broader topic.
Respect access controls and personal information while collecting evidence. Use authorized accounts and approved collection methods. Remove private customer details from shared reports. Inspectable evidence does not require exposing confidential conversations or attempting to bypass a product's access restrictions.
Before reporting an aggregate, review a sample of the underlying records manually. Check that company names were not confused, source links were extracted correctly and negative references were not counted as positive recommendations. Automated collection can save effort; the interpretation still needs an explicit quality check.
Use metrics that preserve the question
A practical starting measure is answer coverage: the number of eligible answers that contain a defined event divided by the number of eligible answers inspected. The event could be a company mention, a citation to its site or a positive recommendation. Report each separately and include the underlying counts.
Citation share is a different measure: links assigned to a domain or company divided by all counted links in the sample. State how repeat links are handled. If your counting unit is unique URLs rather than link appearances, say so. Do not compare the two rates without reconciling that choice.
These measures can disagree without either calculation being wrong. A company may appear in many answers while receiving few links per answer. Another source may collect several links in one detailed response but be absent from the rest. The first measure describes breadth; the second describes the distribution of counted links.
For a small sample, show observations rather than hiding them behind a precise-looking score. List the questions where the company appeared, where it was missing and where the answer was inaccurate. Keep the raw counts beside the rate so the reader can judge how much one changed answer affects the conclusion.
If you need a single management summary, make it a decision summary. Identify the most important gap, the work assigned to it and the evidence that will be checked next. A composite score is optional. A clear explanation of what the team should do is not.
Turn source inspection into publishing decisions
Fix the source you control first
Inspect the pages that should answer the buyer's practical questions. Are service boundaries clear? Is the process explained? Are fees or pricing factors addressed where appropriate? Can a buyer understand who the offer is for and when it is not a fit? Missing information is a concrete production brief.
Technical basics belong in the same plan. Confirm that the intended public pages can be accessed and that important information exists as readable page content. Keep company details consistent. These checks support a usable website even when no AI product chooses to cite the page.
Create the format the question needs
Choose the format after identifying the missing explanation. A switching question can justify a step-by-step guide. A complex demonstration can justify a video with a useful written explanation. A choice between approaches can justify a comparison that states the trade-offs rather than declaring your company the winner in every row.
Do not turn every insight into several near-identical assets. One accurate, maintainable answer can be more useful to a small team than a publishing quota that nobody can keep current. Repurpose material when the new format serves a distinct audience need, and preserve the factual qualifications across versions.
Earn outside evidence where it belongs
If relevant answers repeatedly cite independent comparisons or community discussions, inspect the standards and purpose of those sources. A legitimate opportunity can include supplying verifiable information to an editor, answering a question with disclosed affiliation or requesting an honest customer review under the platform's rules.
It does not justify fake accounts, manufactured praise, planted threads or attempts to present promotional copy as independent reference material. Those tactics make the evidence less trustworthy. A source strategy should improve the information a buyer can inspect, including information that does not come from your own marketing team.
Keep an owner and a recheck date
Every chosen action should have a named owner, a clear output and a reason for existing. Record what changed and when. Recheck the relevant questions after publication without implying that publication guarantees discovery or that a later answer change proves causation.
Some work will produce no observable citation change in the review window. Keep that result. Decide whether to improve the asset, investigate access, extend observation or stop the tactic. A useful programme learns from non-results instead of quietly replacing the measurement with one that looks better.
Run a review that produces the next decision
For an initial working rhythm, use a regular review date and additional checks after meaningful changes. This is an operating recommendation, not a measured universal expiry period for citation data. Choose a cadence the team can sustain and tighten it when a specific launch or suspected problem needs closer observation.
At each review, keep the core collection conditions as stable as practical. Note any product, prompt or extraction changes. Compare the retained answers as well as the summary. A movement in a metric deserves an explanation of what changed in the actual buyer experience, not just a new colour in a dashboard.
Separate the work shipped from the outcomes observed. A page can be complete while discovery remains unobserved. A company can gain visibility without a measurable commercial effect. Reporting those states separately protects the team from both premature celebration and the mistaken conclusion that useful foundational work had no value.
End with a short decision log. State which gap matters next, what will be done, what evidence supports that choice and what remains unknown. The founder should be able to understand the next move without reconstructing the analyst's entire research session.
Limitations and where to start
This review does not establish a best platform for every business, a universal Reddit or YouTube share, a fixed overlap between engines, or a standard shelf life for citation data. Published samples remain bounded by their collection conditions. A report being recent does not make its audience identical to yours.
The proposed workflow is also a starting point, not a statistically validated benchmark design. Repeated observations improve inspectability but do not automatically eliminate selection effects or establish causation. Larger commercial decisions may require a more formal study and specialist measurement support.
The Surface Diet is useful when it turns an observed gap into a sensible publishing decision. Start with your buyers, choose the products worth inspecting, retain the evidence and do the work the evidence supports. For help interpreting a provider's research, use our GEO research checklist.
If you want that process applied to your company, request an audit. The useful output is a set of relevant buyer questions, the gaps we can show you and a prioritized plan for what to fix or publish. A universal leaderboard cannot make that plan for you.