Setting The Proper Expectation For SEO Clients
[]The first expectation to set in an SEO engagement is that nobody can give a universal timetable for a ranking change. The work may involve crawling, indexing, page quality, links, competitors, technical changes, and the offer itself. Those conditions are different for every site and can change while the work is underway.
That uncertainty is not a reason to avoid planning. It is a reason to plan around work and evidence rather than promise an outcome by a particular date.
Separate the work from the outcome
A provider can usually describe work they will do: inspect important URLs, document technical issues, improve a page, publish useful material, repair internal links, or configure measurement. The site owner can confirm whether that work was implemented.
A provider cannot control how a search engine evaluates the site, what competitors publish, which result a person chooses, whether the offer fits, or whether the business can handle demand. Rankings and revenue are therefore outcomes to observe, not deliverables to guarantee.
Make dependencies explicit
At the start, record the conditions that could affect the result:
- who can change templates, content, redirects, links, analytics, and hosting;
- which approvals or legal, privacy, and accessibility reviews are required;
- whether important pages are accessible to crawlers and usable by people;
- what other marketing, product, pricing, or technical changes are happening;
- which markets, devices, queries, and pages are included in the review;
- what capacity exists to respond when an issue is found.
If implementation depends on a third party, say so in the plan. A recommendation waiting in a report is not the same as a change made on the site.
A useful scope document therefore records each task’s owner, dependency, evidence of completion, and next review date. That makes a missed implementation visible without treating it as a failed ranking promise.
Use milestones that can be checked
Replace ‘rank in the top ten within six months’ with milestones such as:
- the important page set and baseline are documented;
- the highest-risk access or indexing issues have an owner and a decision;
- agreed page, link, or template changes are implemented and checked;
- the content and conversion path are reviewed against the intended audience;
- the evidence is assessed before the next piece of work is chosen.
These milestones do not imply that a ranking will follow. They make progress visible even when the external result is still uncertain.
Report with enough context to interpret change
A useful report names the page, query set, market, device, date, and method. It distinguishes impressions, visits, enquiries, purchases, and other outcomes instead of combining them into a single success score.
Record changes outside SEO as well. A product launch, outage, price change, seasonality, competitor action, search feature, or analytics change can affect the numbers. Without that context, a report can attribute too much to the last task completed.
Do not present an average position or a traffic increase as proof of revenue. Ask whether the measured change matches the business question and whether another explanation is plausible.
Handle attribution honestly
Some work has a direct check: a redirect returns the intended status, a blocked page becomes accessible, or a title is changed in the template. Other work has a more indirect relationship with search visibility or business results.
Use language that matches the evidence. ‘We implemented this change’ is different from ‘this change caused the increase’. Where attribution is uncertain, say what was observed and what remains unknown.
When the situation is urgent
A real incident may need prompt attention: an accidental site-wide block, a broken migration, a removed product catalogue, a security issue, or a search action that has a documented cause. The urgency should come from the observable incident and its potential impact.
A generic warning, an obsolete score, or a claim that recovery is impossible is not a diagnosis. Ask for the affected pages, evidence, proposed action, owner, and way to verify the repair.
The expectation worth keeping
SEO is a process of making pages findable and useful, then learning from how people and search systems respond. It can be planned, implemented, and reported without pretending that rankings or revenue are guaranteed.
The honest agreement is simple: define the work, name the dependencies, measure the right things, report what happened, and keep uncertainty visible.
