A monthly SEO invoice should map to monthly SEO work. If it does not, ask why.

A logistics company we spoke with had been paying a monthly SEO retainer for the better part of a year. The invoice read "SEO Management, R6,500." One line. No breakdown of what had actually happened that month, no list of pages touched, no note on what had shipped versus what had simply been "monitored." When the owner finally asked for specifics, the agency struggled to name more than a handful of concrete actions across the entire period.

That is the single biggest problem with how SEO retainers get sold in South Africa: the deliverable is often described as an outcome ("we will improve your rankings") rather than a defined body of monthly work. Outcomes in SEO are legitimately uncertain, algorithm behaviour, competitor activity and seasonality all interfere with any promise. Work, on the other hand, is entirely knowable in advance and should be written down before money changes hands.

This guide sets out what a monthly SEO retainer should actually include, month over month, so you can compare a proposal against a real standard instead of trusting a single vague line item and a graph that only ever points up.

A technical SEO audit at the start of an engagement is standard and useful. What should continue every month afterward is smaller but just as important: checking that nothing has broken. Sites change constantly (a developer ships a new template, a plugin updates, a redirect gets misconfigured during a routine content edit) and any of these can quietly undo months of ranking progress overnight.

A retainer worth paying for treats this as routine maintenance: crawl reports reviewed for new errors, Core Web Vitals checked against real user data, and indexation confirmed for anything recently published or restructured. None of this produces an exciting monthly headline. All of it protects the investment you have already made.

If technical work is only ever mentioned in the first month’s proposal and never referenced again, ask directly what technical monitoring happens now. A retainer that only ever adds new content on top of an unmaintained technical base is building on a foundation nobody is actually checking.

Content is where most retainer budget visibly goes, and it is also where the biggest gap between "busy" and "useful" tends to open up. A retainer earning its fee can show you, in one document, which pages exist or are planned, which specific search intent each one targets, and why that intent matters to your business rather than a competitor’s.

Without that roadmap, content work drifts toward whatever is easiest to write that month, generic listicles, seasonal filler, topics with no commercial connection to what you actually sell. Volume without intent produces published pages that neither rank meaningfully nor convert anyone who happens to find them.

Ask to see the roadmap for the next quarter, not just the article going live this week. If nobody can produce one, the content stream is being generated reactively rather than run as a programme, and a programme is what a retainer fee is supposed to be buying.

1. Define target content and pages worth linking toDigital PR and outreach work far better when there is something genuinely link-worthy to point at, not just a generic service page.
2. Run a realistic, disciplined outreach cadenceA steady, honest process beats a promised quantity, link acquisition is not something any agency fully controls month to month.
3. Vet quality over volumeRelevant, real publications and directories beat a pile of low-quality links that create more risk than authority.
4. Report placements transparentlyYou should be able to see exactly where links were placed, not just a monthly count with no detail.
5. Avoid guarantees phrased as commitmentsAny promise of a fixed number of backlinks per month deserves direct scrutiny, no one fully controls another publisher’s decision to link.

If an agency guarantees a specific number of backlinks every month, they are either buying low-quality links or making a promise they cannot actually control.

Thandiwe Nkosi, SEO & Content Strategy Lead

Search Console and GA4 data matter, but they answer "what happened on the site," not "did this retainer make the business money." A retainer that stops its reporting at rankings and sessions is reporting on activity, not outcome, and it is very easy to make activity look impressive while outcomes stay flat.

A stronger reporting standard connects organic sessions to actual enquiries: forms, calls and WhatsApp clicks that started on an organic landing page, and (where your sales process allows it) which of those enquiries your team actually qualified. That closing step is uncomfortable for an underperforming retainer to include, which is exactly why it matters that you ask for it explicitly.

If your current reporting cannot answer "how many qualified enquiries came from organic search this month," that is not a minor gap. It is the entire point of the exercise missing from the conversation you are having with your agency every month.

Retainers drift for two very different reasons, and only one of them is the agency’s fault. Sometimes an agency simply keeps billing the same fee for shrinking effort once a client stops asking questions. Just as often, though, a client’s own team cannot keep up with implementation (approvals stall, developer access goes quiet, content sign-off takes three weeks instead of three days) and the retainer’s output slows down with it, through no fault of the strategy.

A fair retainer conversation names both possibilities honestly. If your team is the bottleneck, the fix might be a lighter, cheaper scope rather than the same fee for undelivered work. If the agency is the bottleneck, the fix is a documented deliverable list you can hold them to, month by month.

Either way, "we are paying the same amount and getting less" deserves a direct conversation before month six, not a quiet cancellation in month twelve after the relationship has already soured.

A useful habit either side can adopt: review the deliverable list against the invoice every quarter, out loud, on a call. Written scopes drift quietly when nobody revisits them; a short, scheduled check keeps both the agency and the client honest about what the fee is actually buying that quarter.

• What specific work is planned this month, can you name it, not just describe the theme?
• What does the roadmap look like for the next quarter, not just the next article?
• How are backlinks or digital PR actually earned, and what happens if a target month underdelivers?
• What does the report connect to, sessions, or actual qualified enquiries?
• What happens to my content, structure and rankings if I cancel this retainer?
• What is explicitly not included, so nothing gets billed twice as a "surprise addition" later?

Not every business is ready for an open-ended monthly retainer, and we say so plainly when a scoped project is the more honest fit, a technical fix sprint, a content cluster build, or a local SEO foundation pass, priced and delivered against a fixed list rather than an ongoing fee. Retainers earn their place once the foundation is solid and there is a genuine, ongoing content and authority programme to run.

When we do run a retainer, the scope is written down before the first invoice: what ships monthly, how link-earning is actually pursued, and which numbers we will show you beyond a rankings screenshot. If a month underdelivers against that scope, we say so in the report rather than dressing it up with a chart that only ever points up.

If you already have a retainer, ask for last month’s specific deliverable list this week, not a summary, the actual list. A vague answer to a direct question is the clearest signal available.

If you are evaluating new proposals, request the monthly rhythm and the quarterly content roadmap before comparing price. Two retainers at the same fee can represent wildly different amounts of real work.

Pair this guide with our SEO cost and SEO ROI articles before you negotiate, and bring your current invoice to a conversation with Nexus if you want a second, plain-language read on whether it matches what is actually happening on your site.