I already published my rate card for one-time AI-visibility audits, audit price, fix sprint price, the four questions I ask before quoting either one. The question I get after that post isn't "what's the audit cost," it's "okay, but what does the retainer actually include." Fair question. A monthly number without a deliverable list is just a number.
So this is the retainer breakdown specifically: what's in scope every month, what triggers a tier change, how long I ask clients to commit, and what happens if I miss a deadline. No "it depends." If the structure below doesn't fit your site, you'll know before we get on a call.
Why a retainer is a different product than an audit
An audit is a snapshot. I crawl the site once, score it against the same structural stack I wrote about in how to dominate SEO in the age of super intelligence, hand over a fix list, and I'm done. A retainer exists because that snapshot goes stale the moment the site ships a new page.
Schema breaks when a dev changes a template. FAQ sections go generic when someone else writes the next ten pages without the checklist in front of them. Internal links rot as old posts get buried under new ones. None of that shows up in a one-time audit, it shows up three months later as a citation that quietly stopped happening. The retainer is the thing that catches it before it compounds.
I wrote about that compounding pattern in detail in what happens when you ignore GEO for six months: nothing breaks on day one, the gap just gets wider every cycle nobody checks it. A retainer is the counter to that specific failure mode, not a general "do more SEO" line item. If a site's structure is already solid and nothing new ships, a retainer has almost nothing to do, and I'll say that plainly on the call instead of inventing busywork to justify it.
A retainer is maintenance and expansion of a structure that already works, not a rescue mission for a site that was never audited. If a prospect wants a retainer without ever running the audit first, I quote the audit first anyway. I've tried skipping that step twice, both times I spent the first month just doing the audit for free, buried inside what was supposed to be maintenance work.
What's actually in scope, month to month
Every retainer, regardless of tier, includes the same five recurring line items. The tier changes how many pages and how much writing time each one gets, not whether it's included.
- Schema re-validation. I re-run Rich Results Test and a manual check against every page template at least once a month, flagging anything a dev change broke since the last pass.
- FAQ and answer-first audits on new content. Any page published that month gets checked against the same answer-first and FAQPage criteria from the original audit, before it's a month old, not after.
- Internal link maintenance. New posts get linked into the right topic cluster, and I check for orphans the way I described in the pre-launch SEO/AIO/GEO/AEO/SXO/LLMO checklist, monthly, not just at launch.
- A written monthly report. What changed, what I fixed, what I flagged but didn't touch because it needs a decision from the client, and the AI-referral numbers from GA4 and Search Console that month.
- One scoped revision round per deliverable. If I rewrite a FAQ section or restructure a page, the client gets one round of "change this" before it's considered done for that cycle.
How the three tiers actually differ
Tier is driven by two things: how many pages are in active rotation (published or edited that month), and how often new content ships. A site publishing weekly needs a different cadence than one that touches four pages a quarter, even if both sites are roughly the same total size.
| Maintenance | Growth | Scale | |
|---|---|---|---|
| Monthly rate | $1,500 | $2,400 | $3,500 |
| Pages in active rotation | Up to 20 | 21โ60 | 61+ |
| New content checked per month | Up to 2 pages | Up to 8 pages | Unlimited, same-week turnaround |
| Schema re-validation | Monthly | Monthly + after any template change | Monthly + after any template change |
| Reporting cadence | Monthly written report | Monthly report + mid-month check-in | Monthly report + biweekly call |
| Response SLA on a flagged schema break | 5 business days | 3 business days | 1 business day |
Most clients start at Maintenance even if they publish more than twice a month, then move up once the backlog of unreviewed pages actually becomes a problem. I don't upsell on the first call. I've had sites sit at Maintenance for eight months and never need more.
The jump from Maintenance to Growth usually isn't a page-count trigger, it's a cadence trigger. A site adding four pages a month fits inside Maintenance's cap on paper, but if those four pages ship in one rushed week, the schema check queues up and the next month's batch arrives before I've cleared the last one. That's the real signal I watch for, a growing backlog of unreviewed pages, not the raw page count against the tier ceiling.
Scale exists mostly for sites running the same structural stack across more than one property, an affiliate network or a multi-brand setup where schema drift on one site tends to show up on the others within weeks. The biweekly call at that tier isn't a status update, it's where I flag pattern breaks across properties before they become five separate fix lists instead of one shared fix.
Contract length and what changes it
I ask for a 3-month minimum on every retainer, paid monthly, not upfront. Three months is roughly one full cycle of seeing whether schema fixes and FAQ rewrites are actually moving AI referral numbers in Search Console and GA4, one month isn't enough signal, and I don't want to lock anyone into a year before either of us knows if it's working.
After the first 3 months, it's month-to-month with 30 days' notice to cancel either direction. Two things change the rate mid-contract: the client's page count crosses into the next tier's range for two consecutive months, or the client asks for something structurally new, a Schema.org Product pass for a site that just added ecommerce, for example, which gets quoted as an addition to the existing tier rather than folded in for free.
New page copywriting from scratch, dev work like page speed or server config, and paid GEO monitoring tool subscriptions are not included at any tier. I check the output of those tools and act on it, I don't pay for the software underneath. The first retainer I ever ran didn't draw this line clearly, and I ended up writing full pages at an hourly rate that worked out below my audit rate. Now it's a separate quote, every time.
Key takeaways
- A retainer covers five fixed line items every month: schema re-validation, new-content checks, internal link maintenance, a written report, and one revision round per deliverable.
- Three tiers, $1,500 to $3,500 a month, driven by page count in active rotation and publishing frequency, not brand size.
- I require the one-time audit before any retainer starts, maintenance only works on a structure that's already been scored once.
- Minimum commitment is 3 months, then month-to-month with 30 days' notice, long enough to see real signal, short enough that nobody's stuck.
- Copywriting from scratch, dev work, and GEO monitoring tool subscriptions are never bundled in, they're quoted separately every time.
What I'll do next
I'm tracking how many Maintenance-tier clients actually cross into Growth within the first two quarters versus how many stay put. If most stay at Maintenance, I'll probably narrow that tier's page ceiling instead of leaving room nobody uses. I'm also adding a short section to the monthly report template that shows tier utilization directly, pages checked against pages allowed, so the upgrade conversation is based on the client's own numbers instead of me suggesting it.
FAQ
Do I need the one-time audit before starting a retainer? +
What happens if my site doesn't publish anything in a given month?
Can I pause a retainer instead of canceling it?
How is the retainer different from just rebooking the one-time audit every quarter?
Do you ever discount the retainer for a longer upfront commitment?
Want this built for your team?
I design AI agents and growth automation that run without babysitting. If that sounds useful, let's talk.
Get in touch โ