SEO project pricing covers work with a defined scope, a defined outcome and an end date. You are buying a specific piece of work rather than a continuing relationship, which makes it the easier model to budget for and the harder one to scope.
The alternative, retainer pricing, buys ongoing capacity. Which suits you depends less on budget than on whether your problem has an end.
When project pricing fits
- The problem is bounded and identifiable, such as a migration, a restructure or an audit.
- You have implementation capacity and need direction rather than hands.
- Budget is approved per initiative rather than as a standing cost.
- You want to evaluate a provider before committing to something ongoing.
- The work has a natural completion point after which the situation is different.
It fits badly where the requirement is continuous. Competing in an active market is not a project, and buying it as one usually means paying for the same discovery repeatedly.
Work that prices well as a project
- Audits. Bounded by site size and depth. See SEO audit pricing.
- Migrations. Bounded by the launch date, though monitoring extends past it. See migration SEO cost.
- Keyword and architecture mapping. Produces a document that remains useful.
- Technical remediation. A defined issue list, worked through and verified.
- Strategy development. Produces a plan your team then executes.
What drives the number
- Site size, since crawl analysis and mapping scale with URL count.
- Depth of diagnosis, which is the difference between a tool report and interpreted findings.
- Whether implementation is included, the largest single variable between quotes.
- Data availability. Missing analytics history or server logs adds reconstruction work.
- Stakeholder load. More approvals means more time in meetings and revisions.
Scoping it so it does not drift
Project pricing fails in one predictable way: the scope was never precise enough, so either the work expands or the outcome disappoints.
- Define the deliverable as an artefact, not an activity. “A prioritised issue list with implementation notes” beats “a technical review”.
- State explicitly whether implementation is included, and if so, whose developers.
- Agree how many revision rounds are included.
- Name what is out of scope, particularly content production and development time.
- Agree what happens if diagnosis reveals a larger problem than expected.
Frequently asked questions
Is project or retainer better value?
Neither in the abstract. Projects suit bounded problems and give budget certainty. Retainers suit continuous competitive work. Buying continuous work as repeated projects usually costs more, because each one re-does discovery.
Can we start with a project and move to a retainer?
That is a common and sensible sequence. An initial audit or strategy project establishes the priorities and lets both sides assess the working relationship before committing to something ongoing.
Why do project quotes vary so much?
Usually because they describe different scopes. One may be a tool-generated report; another may include interpretation, prioritisation and implementation support. Compare deliverables rather than headline figures.
What if the project uncovers more problems?
Agree in advance how that is handled. A reasonable arrangement is that the project completes as scoped and additional findings are documented for a separate decision, rather than being absorbed or silently expanding.
Consulting CTA
If you have a bounded SEO problem and need it scoped and priced properly, book an SEO consultation to define the deliverable and what it should reasonably cost.