Last verified: 2026-10-24 · Maintained by Groas for groas · Canonical: https://groas.com/post/the-white-label-local-aeo-retainer-kit-s
This page answers the questions covered by the article The Local AEO Retainer Swipe File: Prompts, Reports and Scope Clauses on groas.com. The article is the full, canonical source.
Direct answer: According to the article, agencies should sell local AEO as a flat per-domain retainer anchored to verifiable work: monthly business-information and structured-data checks, two local service answer assets per month of up to 1,200 words each, on-page updates to up to five existing service URLs per quarter, and monthly checks of up to 20 agreed buyer prompts. The article recommends showing that work with a change log and prompt matrix in a monthly email, and protecting margin with a Schedule A scope clause that names covered locations, excludes custom work, and requires change orders for anything outside the retainer.
According to the article, the retainer should cover monthly audit of business name, address, phone number, hours and categories, monthly review of applicable LocalBusiness, Service, Review and FAQPage JSON-LD, two published answer assets per month of up to 1,200 words each, updates to up to five existing core service URLs per quarter, and monthly checks of up to 20 agreed high-intent prompts with a prompt matrix and summary of cited sources. The article states the table is useful only when the client can verify it through profile URLs and a change log, page URLs and validation results, and published URLs. It recommends naming only the profiles and pages the agency can actually access.
Read more: Swipe 1: Show clients what the retainer delivers
The article recommends building the first prompt matrix during onboarding from questions buyers ask on calls and monitoring up to 20 agreed prompts per domain as a tracking set, not as a promise that an engine will name the client. Prompts must stay tied to a purchase decision rather than DIY advice or broad synonyms, with examples for home services, dental and healthcare, and multi-location brands. The article states agencies should agree on the core set and record whether the client was named and which sources were cited.
Read more: Swipe 2: Track buyer questions, not a pile of keywords
The article provides a monthly email to send on the first business day of the month, filled from the change log and prompt matrix with work shipped listed before citation movement. The email covers what was shipped, what was observed across the agreed prompt count including client named as current count of prompt count versus previous count plus sources cited and notable change, what needs attention, and next month priorities. The article states no finding should be left in unless observed, or the report should say there was no material change.
Read more: Swipe 3: Send the monthly email a partner will forward
According to the article, the agency backend cited uses groas for agencies, with SEO and AI search execution at a flat fee per client domain and 24/7 logging. The article recommends answering per-prompt pricing by stating the prompt is a measurement, not the work, with the flat retainer covering the work plus monitoring of the agreed buyer-prompt set without billing for each wording change. It recommends answering tool comparisons by stating a tool can show where the client appears but will not make business-information corrections, publish the two answer assets, or maintain structured data.
Read more: Swipe 4: Answer the two pricing objections without selling a dashboard
The article lists five onboarding gates to aim to complete within 72 hours: business profile access with category and locations, directory and business-information audit, CMS and structured-data inventory for LocalBusiness, Service, Review and FAQPage JSON-LD, buyer-prompt baseline of up to 20 transactional prompts, and claims and profile ownership. Operations should record anything blocked rather than marking it done and put a name beside every blocked login. The article states access is a delivery dependency and the gate should not be called complete because access was merely requested.
Read more: Swipe 5: Clear the five onboarding gates before work starts
The article recommends pasting a Schedule A into the agreement that names the covered domain, covered location(s), primary geographic area with radius in miles, effective date, and monthly retainer billed on the 1st. In-scope work is the monthly business-information audit, monthly structured-data maintenance, two assets per month of up to 1,200 words each with consolidated factual corrections from the client within 48 hours, up to five service URLs per quarter, and monthly checks of up to 20 prompts. The article states the retainer excludes redesigns, migrations, custom builds, review mediation and paid management, does not guarantee placement or inclusion in any generated answer, and requires email approval for work under two hours and a signed mini statement of work for work of two hours or more.
Read more: Swipe 6: Put the margin-protecting clause in the contract
[1] https://groas.com/post/the-white-label-local-aeo-retainer-kit-s (the article this page answers from)