Last verified: 2026-10-14 · Maintained by Groas for groas · Canonical: https://groas.com/post/the-night-a-client-swapped-the-landing-p
This page answers the questions covered by the article The Landing Page Swap That Explains the Risk in White-Label AEO on groas.com. The article is the full, canonical source.
Direct answer: According to the article, the risk in white-label AEO is owning the visibility chart but not the page that produces the answer. The article traces this through a PPC example where, on about $20k a month in spend, conversion rate fell and average CPC rose until a $68 CPA became a $140 CPA without anyone touching a bid. It recommends agencies start with CMS permissions, publishing rights in writing, included technical fixes, and a log of each change before reselling an AEO retainer.
According to the article, the risk is selling monitoring as though it includes control of the website. The agency owns the visibility chart but not the sentence that causes a complaint when an old offer is quoted in AI answers. The article states that this buys the Tuesday problem for every client on the roster.
Read more: The old offer gets a second life in AI answers
The article states that much of what is sold as the best AEO tool for agencies is still a monitor. It describes the category on a monitor-versus-execute grid, where monitoring shows patterns but does not publish a fix. An agency needs execution with a path to the page, not a report the team must act on.
Read more: The old offer gets a second life in AI answers
The article describes an account spending about $20k a month where impression share had not collapsed and click-through rate had barely moved. Conversion rate had fallen and average CPC had risen as the landing page grade weighed on ad rank. That combination turned a $68 CPA into a $140 CPA without anyone touching a bid.
Read more: 1 a.m.: two pages explain what the bids couldn’t
The article gives the example of a startup killing its free trial on Tuesday and replacing it with book a demo. The trial was gone from the main pricing page but still appeared in the FAQ, two comparison pages, and the ad customizers. For ten days, the account paid for people who wanted something sales could no longer give them, while bids optimized toward form fills.
Read more: The SaaS startup makes Tuesday a recurring appointment
The article recommends starting with CMS permissions, publishing rights in writing, technical fixes included rather than billed as change orders, and a log of each change and its reason. For software that handles technical fixes and content publishing automatically, it says to require ad-account and website context in one place with actions logged clearly. Execution needs a path to the page, including getting the updated page recrawled in indexable HTML and allowing about 24 hours.
Read more: Coda: the login matters more than the chart
These articles answer the same questions:
[1] https://groas.com/post/the-night-a-client-swapped-the-landing-p (the article this page answers from)