How to Brief an Agency for a New Website Without Losing the SEO
The brief that protects your rankings, your budget and your launch date — what to put in writing before the discovery call, and what to leave out.
- Published
- Updated
- Reading time
- 8 min
The website brief is the most under-used artefact in a website build. The team that writes a clear brief saves 2–3 weeks of discovery churn, lands on a scope the agency can price, and gets a website that ships on the date the marketing calendar depends on. The team that does not write a brief pays for the missing artefact in scope creep, in re-designs, and in the rankings the redesign silently erased.
This post is what a good brief looks like, and what to leave out.
What the brief is for
A brief is not a screen-by-screen description. A brief is a constraint: who the audience is, what the site has to do, what the site cannot lose, what the launch date is, and what the budget band is. The agency will design the screen, write the copy where needed, and propose the architecture. The brief gives them the boundaries so the proposal lands on the first try.
The brief is also the artefact that protects the SEO. Every URL on the current site that ranks, every page that earns backlinks, every section of the navigation the customer has learned — those are not in the agency's brief unless you put them there. A website redesign is a migration, and a migration without a URL map is how rankings disappear.
The sections of a good brief
1. Audience and the action. Two paragraphs. Who the visitor is, what they are trying to do, what success looks like (a form submitted, a phone call placed, a demo booked). The agency cannot design for everyone, and the brief is where the focus lands.
2. The pages that exist today, and the page that should exist tomorrow. A sitemap, not a wireframe. The current sitemap, the new sitemap, and the deltas. The agency will translate the deltas into a redirect map and a content parity check.
3. The constraints. Brand system, accessibility baseline, performance budget, integrations (CRM, marketing tools, the analytics stack), the security review if any. The constraints are non-negotiable. The agency can propose, but the constraint is the floor.
4. The launch date and the budget band. Not a fixed number, a band. The agency will scope against the band, with the assumptions named. The date and the band together let the agency decide what is in scope and what is not.
5. The change process. How scope changes are handled, who approves them, and what the cost is. The brief is the only time this is uncontroversial. After the build starts, the change process is the difference between a website that ships and a website that does not.
What to leave out
Leave out the screen design. The agency will propose three directions in the first sprint, with the trade-offs named. The screen design is the agency's work, not yours.
Leave out the page-by-page copy. The agency will write the copy against the brief and the brand voice, with a copy review at the end. Writing the copy in the brief is a trap — the agency will treat it as final, and the copy review becomes a re-write.
Leave out the technology choice. The agency will propose the stack against the brief, the budget and the performance budget. The technology choice is the agency's call, with the rationale in the proposal.
A brief that names the constraint, the audience, the sitemap, the launch date and the budget band is enough to scope a website. Anything else is the agency's work.
The SEO decisions the brief has to make
A redesign without a URL map loses rankings. The brief has to name the URLs that have to survive the migration, the pages that have to be content-parity checked, and the schema that has to carry over. The agency will do the redirect map, but the brief is where the SEO decisions are made.
A redesign without a Core Web Vitals budget loses the post-launch rankings. The brief has to name the LCP, INP and CLS targets, with the rationale. The agency will build to the target, but the target is the brief's call.
A redesign without an analytics audit loses the post-launch attribution. The brief has to name the events, the conversions, the funnels and the dashboard the marketing team will run. The agency will wire the analytics, but the events are the brief's call.
The handoff
After the brief, the discovery call is a 30-minute call to align, not a 2-hour negotiation. The brief is the artefact. The discovery is the clarification. The proposal is the agency's response to both. The handoff is clean, the scope is fixed, and the build is on the calendar.
If you do not have time to write the brief, that is the right answer. Tell the agency the brief is "no brief", and the agency will write one for you — at the cost of 2–3 weeks of discovery and a proposal that is wider than the budget. The brief is cheaper than the alternative.
If you want a second opinion on the brief, our website development team can run the review. If the brief is "we need a CMS that the marketing team can run", our CMS development engagement is the right one.
Key takeaways
- A written brief saves 2–3 weeks of discovery churn on a typical website build.
- The brief should name the constraint, not the screen — the agency will design the screen.
- URL mapping and content parity are SEO decisions, not afterthoughts.
- A fixed scope with a written change process is the only way a website build ships on time.
Ready to put this into practice?
Let’s build the solution that gets you there.