Most disappointing SEO engagements are not caused by incompetence. They are caused by two parties agreeing to work together without ever agreeing on what the work is. The client expects enquiries. The agency delivers deliverables. Both are behaving reasonably, and the relationship still ends badly around month six.
This guide covers the part that comes after choosing a supplier: how to define the scope, what a realistic project plan looks like, which deliverables are worth paying for, and how to structure the relationship so that progress is visible before results arrive.
Define the Objective Before the Scope
"More traffic" is not an objective. It is a proxy that can move substantially without changing anything about the business. A workable objective names the commercial outcome and the constraint around it: more enquiries for a specific service, from specific districts, at a fit level you can actually serve.
The constraint matters as much as the goal. An agency told only to increase enquiries will optimise for volume. An agency told you can handle twelve additional projects a quarter and want them in central Oslo will build something quite different, and better.
The Question to Settle First
What would make this engagement obviously worth renewing in twelve months? Write the answer down before the kickoff meeting. If you cannot, the scope will be written by whoever can — and it will be written to be deliverable rather than valuable.
Setting Expectations Early
Three expectations are worth being explicit about at the start, because all three are common sources of friction later.
- Time to result — foundational and local work shows movement in weeks; competitive organic terms take quarters. Agree the shape of the curve, not just the destination.
- Who does what — most engagements require something from the client: developer access, content review, review requests to customers. Unassigned work stalls projects more often than difficult work does.
- What counts as evidence — decide in advance which metrics will be used to judge progress. Choosing them retrospectively guarantees an argument.
Typical Deliverables in an Oslo Engagement
Deliverables vary, but a competent local engagement usually includes the following. The right-hand column is the one worth scrutinising: a deliverable with no stated purpose is a line item, not a plan.
| Deliverable | Typical timing | What it should change |
|---|---|---|
| Technical audit | Month 1 | A prioritised fix list, not a 90-page PDF |
| Business Profile optimisation | Month 1 | Category accuracy, completeness, map pack impressions |
| Citation and NAP cleanup | Month 1–2 | One consistent identity across Norwegian directories |
| Keyword and competitor map | Month 1–2 | An explicit list of what you will and will not target |
| Service and district pages | Month 2–4 | Coverage of high-intent, low-competition local terms |
| Review programme | Ongoing | Steady review velocity, not a one-off push |
| Reporting | Monthly | Decisions — if a report changes nothing, it is theatre |
A Realistic Project Plan
Month 1 — Diagnose
Audit, profile review, competitor analysis, baseline measurement. No content production yet. Resist pressure to show output in the first four weeks; diagnosis is the output.
Month 2–3 — Repair and Anchor
Technical fixes, citation cleanup, profile work, first district and service pages. This is where the earliest measurable movement usually appears.
Month 4–6 — Build
Systematic content coverage, internal linking, review programme running, first authority work. Organic entrances should be trending.
Month 7–12 — Compound
Competitive terms, authority building, iteration on what the data shows. Returns accelerate here if the foundation was done properly.
Governance: The Monthly Rhythm
The most useful structure is unglamorous — a monthly meeting with a fixed agenda: what moved, what was shipped, what is blocked, what happens next, and what we learned that changes the plan. The last item is the one that distinguishes an engagement that is thinking from one that is executing a template.
Blocked items deserve particular attention. In practice, a large share of stalled Oslo engagements are stalled on the client side — developer time that never materialised, content awaiting approval, review requests never sent. Making blockers visible monthly resolves most of them.
The Long-Term Horizon
SEO compounds, which is its main advantage and the source of most impatience with it. Work done in month two continues producing in month twenty, but it does very little in month three. This shape is genuinely unintuitive and it is why engagements are so often cancelled shortly before they would have paid off.
A practical hedge: agree a minimum term matched to the realistic timeline — typically six months — with an explicit checkpoint at the halfway mark that tests leading indicators rather than final results.
Getting Started
Three things prepared before kickoff will save several weeks: administrative access to your own accounts (Search Console, Analytics, Business Profile — verify you actually control these, as they are frequently held by a previous supplier), a named internal owner with authority to approve content, and an honest statement of capacity so that targets match what the business can absorb.
How long should the first contract be?
Long enough to match the timeline — usually six months — with a defined mid-point review. Shorter terms encourage agencies to prioritise visible activity over foundational work.
Who owns the content produced?
Settle this in writing before starting. The default should be that you own everything created for you, including pages, data and account access.
What if nothing has happened after three months?
Check the leading indicators rather than rankings. If indexation, profile metrics and technical health have not improved either, that is a genuine problem worth escalating.
Can we pause and resume?
Technically yes, but momentum is real — content programmes and review velocity both decay. A reduced ongoing scope usually outperforms a full stop followed by a restart.
Should reporting be monthly or quarterly?
Monthly for operational visibility, quarterly for strategic review. Monthly reports should be short; the long-form thinking belongs in the quarterly.
A good agency relationship in Oslo looks less like outsourcing and more like adding a specialist function to the business. The engagements that work are the ones where both sides know exactly what they owe each other each month — and can say so without checking the contract.