How to Write an SEO Project Brief That Actually Protects You
An SEO brief isn't a box-ticking formality — it's the one document that protects a client from vague 'we'll get you to the top' promises. Here's which sections are non-negotiable and which metrics make a brief verifiable rather than declarative.
Why you need a brief when you already have a contract
A contract fixes legal obligations — timelines, payment, liability. A brief fixes the technical content of the work — exactly what gets done, by what method, and how results are measured. Without a brief, a 'did you or didn't you' dispute turns into an argument with no documentary footing on either side.
A common client mistake is accepting a phrase like 'get the site to the top for key queries' with no specifics. That's not a brief, it's a marketing slogan — it's unclear which queries, what 'top' means, over what timeframe, and what counts as success.
Section 1: current state and goals
Record starting positions for key queries as of the signing date — a screenshot or export from Google Search Console dated precisely. Without that baseline, evaluating progress six months later becomes impossible to do objectively: the agency can always claim it was worse, the client that it was better.
The goal must be measurable and time-bound: not 'improve rankings' but 'bring 15 priority queries from cluster [X] into the Google top 10 within 6 months' or 'increase organic traffic to commercial pages by 40% in 4 months per GA4.' A goal with no number and no deadline can't be verified.
Section 2: the priority query list
The brief must contain a concrete list of target queries with current positions and search volume — not an abstract topic like 'dentistry' but a list like 'dental implants tashkent,' 'dental clinic prices samarkand.' The list should be agreed jointly: the client knows the business, the agency knows search demand.
For a bilingual market, split the list explicitly into separate language clusters — these are different semantic cores with different competition levels, not one list translated twice.
Section 3: scope of work by workstream
Technical work: a concrete task list — fixing duplicate titles, setting canonical URLs, optimizing Core Web Vitals to specific thresholds, resolving errors in GSC's Page Indexing report. 'Technical optimization of the site' with no itemized list is a future dispute waiting to happen.
Content work: number of new articles per month, length and structure requirements, who writes and who approves publication. Link building: quantity and quality of external links per month, donor site standards, prohibited tactics (buying links from low-quality marketplaces, link farms).
Separately, spell out the client's responsibility zone: hosting and CMS access by an agreed date, copy approval within N business days, providing photos and materials. Client-side delays are a frequent cause of missed deadlines, and without this in writing, blame defaults to the agency.
Section 4: reporting and acceptance criteria
Reporting cadence (monthly), format (per-query positions, GA4 traffic, completed work list with before/after screenshots), and delivery channel. A report saying 'we worked on the site' with no numbers is not acceptable — write that explicitly into the brief as grounds for rejecting acceptance.
Stage acceptance criteria should be specific and checkable: e.g., 'all 15 listed queries reached top 30 by end of month 3' or 'all critical indexing errors from the GSC report resolved.' If a criterion isn't met, the brief should spell out the procedure — rework at the agency's expense, a revised timeline, or termination.