A support retainer is the normal way this work is bought and the least clearly defined thing most businesses pay for monthly. The contract usually names a fee and a list of activity categories, and almost never names a quantity, a turnaround or a person. That is what makes it so easy for a retainer to become an invoice with a report attached, and it is entirely avoidable by settling four things before the first month.
Name the hours, or name the outputs, but name something
A retainer that says content, technical work and reporting has committed to nothing measurable. Either it buys a number of hours a month from named people, or it buys specific deliverables, so many pages, so many fixes implemented, a defined reporting cycle. Both are legitimate. Neither being stated is how a business discovers in month seven that it has bought a monthly conversation.
Decide who implements, because that is the real cost
A great deal of support work stalls not because the recommendation is wrong but because nobody has the access or the time to make the change. Settle whether the agency has the ability to edit your site directly, whether they wait on your developer, and what happens when that developer is busy for a quarter. A retainer whose output is recommendations into a queue nobody works is an expensive way to produce documents.
Ask what happens in a slow month
Some months there is genuinely less to do. A good supplier will say so and propose something useful; a poor one will produce activity to justify the invoice. The way to find out early is to ask, at the proposal stage, what they do in a month where the technical work is done and no new content is due. The answer is one of the most informative you will get.
Reporting should say what changed and what it did
A dashboard of positions and sessions is data, not an account of the work. What you want monthly is a short written record: what was changed, why, what is queued, what was learned, what would have been done with more of your time. It takes the supplier half an hour and it is the only thing that lets you tell diligence from drift, which at a monthly fee is the whole question.
Agree the exit before you need it
Everything produced, the pages, the analytics property, the search console access, the documentation, should be in your accounts and remain yours. Notice periods should be short enough that the relationship is renewed by choice each quarter rather than by inertia. A supplier confident in the work is comfortable with both; one that is not will explain why neither is customary.
Questions people ask about seo support services
What should an SEO retainer include?
Either a stated quantity of time from named people or specific monthly deliverables, plus who implements changes, a defined reporting format and an exit that leaves everything in your accounts. A list of activity categories with a price is not a scope.
How long before a retainer should show results?
Six to twelve months for outcomes in most competitive markets, three months for evidence of competence. Judge the second on schedule and give the first the time it needs rather than cancelling early or waiting passively.
Is a retainer better than a project?
It depends on whether there is continuing work. If the site is broken, buy a project to fix it. If the problem is that nothing is maintained and nothing new is published, a retainer is the right shape, provided it says what it buys.
What is the most common problem with support arrangements?
Recommendations that nobody implements. The work stalls in a queue, both sides get frustrated, and the fee continues. Settle who can change the site before the first invoice.