Scope note. This article is general educational and measurement guidance, not legal, tax, financial, security, or platform-specific advice. Current law, first-party platform rules, the facts of the real case, and qualified professional advice control any consequential decision. Scope note. This article is general educational and measurement guidance, not legal, tax, financial, security, or platform-specific advice. Current law, first-party platform rules, the facts of the real case, and qualified professional advice control any consequential decision. Somebody has proposed a review campaign, and the business case attached to it is that AI assistants will start naming you. Before you approve the budget, you need three separate answers: what review content plausibly contributes to an AI answer, what obligations attach to soliciting reviews at all, and where the line sits between a program you can defend and one that creates legal exposure. The obligations come first, because they constrain the tactics rather than the other way round.
Start with the obligations, not the tactics
This section is general information, not legal advice. Review solicitation sits inside advertising and consumer-protection law in most jurisdictions, and specific rules vary by country, sector, and platform. Have qualified counsel review any program before it launches, and re-review it when it changes.
Three obligations recur across regimes and are worth understanding before you design anything:
-
Material connections must be disclosed. If a reviewer received something of value — a payment, a free product, a discount, an entry into a prize draw, employment — that connection is generally treated as material and expected to be disclosed clearly and conspicuously in the review itself.
-
The advertiser is generally responsible for what its agents do. Using an agency, a reseller, or a review-generation vendor does not move the obligation off you. If a vendor's practice would be non-compliant when you did it directly, it is unlikely to become compliant because a contractor did it.
-
Platform terms bind you separately from the law. Every major review platform publishes rules on solicitation, incentives, and filtering. Those rules are contractual and are enforced on the platform's own timeline, regardless of whether anything unlawful occurred. Write these three into the brief before anyone drafts an email template. A program designed around them is usually still a good program. A program designed first and audited later usually has to be rebuilt.
Where review content actually shows up in AI answers
Assistants assemble answers from a mix of parameters learned during training and, in retrieval-enabled modes, documents fetched at answer time. Review content can enter through either path, and the two behave differently.
| Route | What it means | What you can observe |
|---|---|---|
| Retrieved review pages | The assistant fetches a review platform or roundup page while answering | Sometimes visible as a citation or link in the answer |
| Retrieved editorial coverage | A publication that summarizes ratings gets fetched instead of the platform | Visible as a citation to the publication, not the platform |
| Learned associations | Descriptions of your product that were common in training data | Not directly observable; inferred from answer wording |
| Structured rating data | Ratings expressed in markup on your own or a third party's pages | Not reliably attributable from the answer alone |
The honest position is that we can observe the first two by reading citations, and we cannot separate the last two from everything else that shaped the model. Anyone telling you they have isolated the contribution of a specific review platform to a specific assistant's output is describing an experiment they would need to publish to be believed.
What we can verify and what we can't
Verifiable by you, today: whether an assistant cites review platforms when answering your category's buying prompts, which platforms it cites, how often, and whether your profile on those platforms is present, complete, and accurate. That is a citation-source question, and it is answerable with a prompt set and a log of citations. The method for building one is covered in earning cited sources.
Not verifiable by you, today: that adding fifty reviews caused a change in how often you are recommended. Assistant outputs vary run to run, models change without notice, and your competitors are moving at the same time. A single before-and-after comparison cannot separate your campaign from any of that.
If a vendor's pitch includes a specific uplift figure tied to review volume, ask for the prompt set, the model versions, the run dates, the sample size, and the variance. Without all five, the figure is a marketing artifact, not a measurement.
This article makes no study claim. A study on the question would need published prompt sets, run dates, and a reproducible method. Until then, treat review platforms as a plausible input to citation-heavy answers and an implausible source of guaranteed placement. Nothing anyone does guarantees placement.
Legitimate review-generation practice
The defensible version is unglamorous and mostly consists of removing friction rather than adding pressure.
- Ask every customer, not a filtered subset. The request goes to the whole eligible population on the same trigger and the same schedule.
- Ask neutrally. The wording does not suggest a rating, does not describe what a "good" review contains, and does not imply consequences either way.
- Do not condition anything on the content. No discount, credit, entry, or continued service that depends on what the review says or how many stars it carries.
- Route complaints properly, but route them to everyone. A support-first path is fine when every customer sees it and every customer still reaches the review request afterwards.
- Keep receipts. Retain the request template, the send list logic, the timing rule, and the date each version took effect. If a platform or regulator asks how a run of reviews was generated, that record is the answer.
- Fix the profile before you fix the volume. An accurate category, a current description, correct locations, and resolved duplicate listings do more for how you get described than another twenty ratings.
Third-party coverage follows the same logic. Being included in a roundup because a journalist tested your product is durable. Being included because you paid for the slot is an advertisement, needs to be labelled as one, and tends to be discounted accordingly by the publications that assistants cite most.
The line: incentives, gating, and selective solicitation
Review gating is the practice of screening customers before the review request so that only those likely to leave a positive rating are asked, or so that unhappy customers are diverted into a private feedback channel and never reach the public one. It is a compliance risk for two reasons. It is generally prohibited or restricted by major platforms' own terms. And because it systematically suppresses negative reviews, it can render the resulting aggregate rating misleading to consumers, which is the concern consumer-protection regimes address. It is worth naming plainly because it is frequently sold as a legitimate "reputation management" feature rather than as what it is.
Three more practices sit on the wrong side of the line and should be refused at the brief stage:
- Incentives conditioned on sentiment or star rating.
- Undisclosed incentives of any kind, including free product, where the reviewer's connection to you is not visible to a reader.
- Reviews written by employees, contractors, family, or agencies without a clear disclosure of the relationship.
Buying reviews, seeding threads under invented identities, and running networks of accounts belong to a different category entirely. The detection picture and the consequences are covered in review fraud and astroturfing, and the short version is that the downside is asymmetric and durable.
If you find that a program you inherited crossed the line, the sequence is: stop it, preserve the records, get counsel involved before you communicate externally, and follow each platform's documented remediation route. Deleting the evidence is the version of this that goes badly.
How to measure whether any of it moved your visibility
Assume nothing moved until you have re-measured, and design the measurement before the campaign so the baseline exists.
- Baseline first. Run your buyer-realistic prompt set across the models you care about, with enough repetitions to see the run-to-run spread, and record citations as well as mentions.
- Record which sources get cited. If no assistant in your category ever cites a review platform, a review campaign is a customer-trust investment rather than an AI-visibility one. That is a legitimate reason to do it, just not the reason in the business case.
- Change one thing. If the review program launches alongside a site rebuild and a PR push, you will not be able to attribute anything to any of them.
- Wait for indexing and retrieval reality. New review content has to be crawlable, retrievable, and actually retrieved before it can appear in a cited answer. That lag is real and unpredictable.
- Re-run the identical prompt set. Same prompts, same models, same sample size, and note any model version changes between runs, because a version change is a confound you cannot remove after the fact.
- Report the spread, not the point. If your mention rate moved from a noisy range into an overlapping noisy range, the honest reading is "no detectable change yet."
The failure mode here is not measuring badly. It is not measuring at all, then declaring victory because someone saw a good answer once. One answer is one sample.
In Plain English
Real reviews from real customers, asked for neutrally and at scale, are a legitimate part of how your category gets described publicly — and public description is what assistants synthesize. What nobody can currently show you is a clean causal line from review volume to a specific assistant recommending you. So run the program for the reasons that hold up on their own, keep it compliant by design, and measure the AI-visibility effect honestly instead of assuming it.
This helps marketing and reputation leads who are being asked to approve a review budget, and anyone who has been sold "reputation management" that turns out to include gating. Use it before the program is designed, not after. The next step is to check whether review platforms are cited at all in your category's answers, and to read the risk and brand safety material before you sign anything with a vendor who promises volume. The full set of legitimate levers lives on what actually changes recommendations.
Use the briefing template to record dated changes in AI answers and the rules around them.
Primary-source verification
Checked July 28, 2026. The operational and factual guidance above was reviewed against the primary references below. Provider features, prices, policies, interfaces, jurisdictions, and account-specific results can change; recheck the controlling first-party document and your own account or measured data before acting.
- Google Search: AI features and your website - How Google describes eligibility, preview controls, and appearance in its AI search features.
- Google: common crawlers and special-case user agents - Current Googlebot and Google-Extended identities and controls.
- OpenAI: overview of OpenAI crawlers - Current GPTBot, OAI-SearchBot, and ChatGPT-User descriptions and publisher controls.
- Anthropic: web-crawler controls - Current ClaudeBot, Claude-SearchBot, and Claude-User descriptions and controls.
- Perplexity: crawler and user-agent documentation - Current PerplexityBot and Perplexity-User descriptions and controls.
- FTC: Endorsement Guides Q&A - Current U.S. regulator guidance on endorsements, disclosures, and reviews.
- FTC: Consumer Reviews and Testimonials Rule Q&A - Current U.S. rule guidance on deceptive review practices.