Most redesign briefs are three pages of brand adjectives and a Pinterest board of sites the leadership team likes the look of. That's not a brief, it's a mood board, and it's exactly why so many B2B redesigns launch looking better and performing worse. A proper brief covers what the site needs to achieve, not just how it should look while achieving nothing measurable.
The gap usually isn't a lack of care from whoever writes the brief. It's that nobody on the team has been through a redesign that went badly enough to know exactly what needs specifying in advance. This is written for the team writing that brief for the first time, or the team who's been through a rough one and wants to avoid repeating it.
Start with what's actually broken, not what looks dated
This reframing alone changes the conversation with a design agency significantly, since it gives them a measurable target to design toward rather than a purely subjective brief they can only judge by whether the client likes how it looks in a final review.
A redesign triggered purely by "our site looks old" tends to produce a purely cosmetic outcome. A redesign that starts by documenting specific problems, low conversion rates on key pages, confusing navigation that buries important content, slow load times, poor mobile experience, produces a brief with a clear definition of success beyond a fresh coat of paint.
SEO requirements, stated explicitly and early
This is the section most briefs skip entirely, and it's the one most likely to cause real damage if it's missing. At minimum, a proper brief should specify:
- A commitment to preserve or improve on current organic rankings, with a defined process for redirect mapping
- URL structure decisions made deliberately, not as a side effect of whatever the new CMS defaults to
- A content migration plan for every existing indexed page, not just the ones featured in the new design
- Technical requirements: Core Web Vitals targets, structured data implementation, and confirmed AI crawler access
- A defined process for maintaining SEO input throughout the build, not just a review after development is finished
Conversion paths, mapped explicitly for every key audience
A brief should name the specific actions the site needs to drive, a demo request, a contact form, a resource download, and map how each type of visitor actually reaches that action. Redesigns frequently make sites more visually impressive while accidentally burying the contact form three clicks deeper than it used to be, because nobody wrote down explicitly that it needed to stay prominent.
Content responsibilities, decided before the build starts
Who is writing new copy, who is migrating and updating existing copy, and what happens to content that doesn't have an obvious home in the new structure. This sounds basic, but it's one of the most common sources of delay and scope creep, because it usually only gets addressed once development is already underway and someone realises nobody actually owns the content workstream.
What to do with content that used to rank well
Every page that currently drives meaningful organic traffic needs an explicit decision: keep it as is, improve it, or merge it into a new page with a proper redirect. "We'll figure that out during the build" is how rankings quietly disappear, because that decision ends up made by whoever's under the most time pressure in the final week before launch.
Technical and platform requirements
Beyond the visual design, a brief should specify hosting and performance requirements, integration needs with existing CRM or marketing tools, accessibility standards, and a realistic content management workflow for whoever maintains the site after launch. A beautiful site that the marketing team can't easily update themselves becomes a maintenance bottleneck within months.
What a properly written brief prevents
Consider a B2B services firm redesigning their site around a new brand identity. Without an explicit brief, the project focuses entirely on the new look, and three months post-launch the marketing team discovers organic traffic has dropped by a quarter, the contact form is now four scrolls deep on mobile, and nobody redirected sixty blog posts that used to bring in steady search traffic. With a proper brief, each of these would have been an explicit line item reviewed before development even started: a redirect mapping requirement, a stated conversion path requirement for the contact form, and a content migration plan covering every existing indexed page. The difference isn't more work overall, it's the same work happening before launch instead of as a panicked recovery effort after.
Post-launch accountability
This is the section almost no brief includes, and it matters more than most of the ones that do. Who is responsible for fixing issues discovered after launch. What does the warranty period actually cover. Who monitors rankings and traffic in the weeks following launch, and what's the process if something goes wrong. Without this, a redesign agency can disappear the moment the invoice is paid, leaving the business to discover and fix problems alone.
Common objections, answered
Our design agency says they handle SEO as part of the build, isn't that enough?
Ask exactly what that means before assuming it covers what you need. Many design agencies handle basic on-page elements, title tags, meta descriptions, but don't proactively map every existing indexed URL for redirects or assess content parity against current rankings. Get specific commitments in writing rather than accepting a general reassurance that SEO is covered.
We're on a tight timeline, can we skip some of this to launch faster?
Some sections can be lighter depending on site size, but redirect mapping and content parity checks specifically shouldn't be cut to save time, since they're the two things most directly responsible for post-launch traffic loss. If timeline pressure is genuinely tight, it's better to delay launch slightly than to skip these and spend months afterward recovering lost rankings.
How detailed does the brief actually need to be for a smaller website?
Proportionate to the site, not identical regardless of size. A twenty-page small business site needs a much lighter version of this brief than an enterprise site with thousands of pages, but even a lighter version should still explicitly cover SEO requirements, conversion paths and content ownership rather than skipping them because the site is small.
Bringing it together
A genuinely useful brief reads less like a design mood board and more like a project specification: current problems, defined success metrics, explicit SEO requirements, mapped conversion paths, clear content ownership, and post-launch accountability. A B2B website redesign built around outcomes rather than just appearance starts with exactly this kind of brief, before a single design concept is even discussed.
Planning a website redesign and want it to actually perform, not just look better?
Book a call