Question 1

How long should an SEO brief be?

Accepted Answer

Long enough to cover the five areas above — typically 2–5 pages for an initial engagement brief. A brief for a specific deliverable (a technical audit, a content strategy) can be shorter if the scope is well-defined. A brief for a long-term retainer engagement needs more business context. The test isn't length but completeness: could an agency reading this brief understand your business, your current situation, what you want to achieve, what they're responsible for, and how you'll measure success? If yes, it's long enough. Briefs fail by being too thin (too little context for the agency to work well) more often than by being too long.

Question 2

Should I share my analytics data in the brief?

Accepted Answer

Yes — at least a summary of current performance metrics, even before you've formally engaged an agency. An agency responding to a brief without any data about the current state is guessing about the baseline. For initial pitches where you don't yet want to share full access: share a Search Console export (90-day performance data by query and page), current organic traffic trend (a screenshot or data export from GA4), and any traffic events you know about (drops, spikes, algorithm impacts). This is enough for an agency to assess what they're working with and propose meaningfully. Once you've selected an agency, provide full access to Search Console and GA4 as a precondition of the engagement starting — any agency that won't audit the current data before proposing strategy is working blind.

Question 3

What if I don't know what scope or deliverables to ask for?

Accepted Answer

A discovery brief is a valid format: rather than specifying deliverables, you brief the agency on your business context, goals, and current situation and ask them to recommend scope and approach. This works well when you don't have enough SEO expertise in-house to specify what the engagement should cover. The risk is that without scope constraints, agencies tend to propose the maximum engagement (and maximum fee). Counter this by specifying a budget range upfront and asking for a prioritised proposal: "Given a budget of X, what would you focus on first and why?" A response that explains their reasoning and prioritises clearly tells you more about the agency's quality than a comprehensive proposal covering everything they could possibly do.

Question 4

What are the most common mistakes in SEO briefs?

Accepted Answer

The most damaging: (1) No business context — "increase organic traffic" without explaining what the business does, who it serves, or what organic traffic is supposed to produce. This produces generic SEO strategy. (2) No current state data — an agency can't set realistic expectations or prioritise correctly without knowing your baseline. (3) Undefined success — without agreement on what success looks like and how it's measured, the engagement ends without anyone being able to say whether it worked. (4) Omitting constraints — not flagging that your developer is unavailable for 3 months, that legal must approve all content, or that you recently had a manual action — means these constraints appear mid-engagement and disrupt delivery. (5) Overly prescriptive scope — telling an agency exactly what to do (rather than what to achieve) without the contextual knowledge to know whether those activities are the right ones. Good agencies will flag a bad brief; the problem is that agencies trying to win a pitch may not.

Question 5

Should the same brief be sent to every agency I'm evaluating, or tailored per agency?

Accepted Answer

Send the same core brief to every agency under consideration — this is what makes the resulting proposals genuinely comparable. Tailoring the brief differently per agency (even with good intentions, like emphasising different things based on each agency's stated specialism) makes it much harder to judge proposals against each other on a like-for-like basis, since you're no longer comparing responses to the same set of facts and goals.

Question 6

Does the brief need to be updated once an agency is engaged, or is it a one-time document?

Accepted Answer

Treat it as a living reference, not a one-time document — revisit and update it whenever a goal, constraint, or major business fact changes (a new product launch, a shift in target customer, a change in approval process). An agency working from a brief that's a year out of date on your business context is in nearly the same position as one that received a thin brief at the start; keeping it current is a small, cheap habit that prevents the same context-gap problem from quietly re-emerging mid-engagement.