Which AEO Agency Can Show Citation Lift?

Give finalists matched page cohorts and the same observation rules. Compare each agency’s change in Google citation rate against an untouched holdout and inspect the page evidence behind the apparent lift.

Preserve eligibility failures in the pilot

Google requires a page to be indexed and eligible for a search snippet before it can appear as a supporting link in AI Overviews or AI Mode. Ask each agency to document index and snippet eligibility before assigning pages to the pilot. If the engagement is meant to improve already eligible pages, form cohorts from that set and report exclusions before collecting results. If fixing eligibility is part of the brief, keep those pages in their original cohorts and record the fixes. Use unique query and page pairs, collect observations on one surface with a fixed locale, and retain the observed answer and cited destination. Record an absent AI feature separately from a displayed answer with no citation. Dropping either from just the follow-up can make a flat result look like a gain.

AI Features and Your Website | Google Search Central  |  Documentation  |  Google for Developers

Check what the winning proposal actually adds

Ask each finalist to produce an inspectable change memo for one page in its assigned cohort. Give them the same type of work, such as improving a compatibility guide buyers consult before ordering. A candidate could add a tested model-by-model compatibility table with the test conditions and an explicit result for each model. Have a reviewer reproduce one result from the underlying records and check that the published text supports the claim. Google’s guidance flags the risk of producing pages at scale without adding value. A plan to publish dozens of near-identical pages offers a different deliverable from a plan to test and document compatibility. When comparing bids, count accepted evidence-backed changes alongside adjusted citation lift. If multiple queries point to one edited page, treat those observations as related when judging how repeatable the result is.

Google Search's Guidance on Generative AI Content on Your Website | Google Search Central  |  Documentation  |  Google for Developers

Separate discovery from delivery

Ask the agency to pick five buyer questions it believes you should answer. For each, request the intended audience, the page that should answer it, the source evidence missing today, and the person responsible for publishing the correction. A proposal focused on publishing volume leaves those decisions with your team.

For Google AI features, ask how its proposed work relates to ordinary search eligibility, access and content quality. Google documents the technical requirements and search policies that apply. Ask for the exact defect the agency observed on your site before approving a special markup or infrastructure project.

AI Features and Your Website | Google Search Central  |  Documentation  |  Google for Developers

Build a reproducible baseline

Freeze the questions, engines, locale, signed-in state, dates and definition of a citation. Save the returned answer and destination URL for each observation. Separate a brand mention without a link from a citation to a page you control. Record when an AI feature did not appear. Otherwise a change in feature availability can look like improved visibility.

For example, suppose 20 questions produce 15 answer panels, six of which link to your domain. Report both six out of 20 checks and six out of 15 displayed panels. Those denominators answer different business questions. A small pilot describes observed behavior and cannot establish a ranking guarantee.

AI Features and Your Website | Google Search Central  |  Documentation  |  Google for Developers

Inspect a sample deliverable

Give each finalist the same page, a real customer question and the same source material. Ask for a revised answer, its sources, and a list of factual changes. Have your product expert review the draft without knowing which agency supplied it. Score factual correctness, whether the answer resolves the question, and how much work remains to publish.

Google’s guidance on generative content emphasizes accuracy, quality and relevance. Use that as a review criterion. Generic copy that could describe five competing products is a poor deliverable even when it includes the right keywords.

Google Search's Guidance on Generative AI Content on Your Website | Google Search Central  |  Documentation  |  Google for Developers

Contract for decisions you can audit

Request a written sample report before awarding the retainer. It should connect each observation to a page-level change, identify who signed off, and preserve the before-and-after evidence. Ask what happens when citation frequency rises but visits or qualified inquiries fall. A responsible answer should investigate the mismatch before assigning credit.

Set a review date, content ownership terms and a handover format. Keep the prompt panel and measurement history under your control. For a fixed budget, compare proposals on how many validated questions they can resolve and what evidence you will own afterward.

AI Features and Your Website | Google Search Central  |  Documentation  |  Google for Developers

Sources