In This Article
- Direct answer
- The brief is where search is won or lost
- Templates and URLs, written as requirements
- Content ownership before the design is pretty
- Speed, indexation, and what to measure
- What a financial-services brief changed
- The one-page appendix to attach
- Briefs that create a redesign you cannot find
- Frequently Asked Questions
Direct answer
A search-ready web development brief names the templates, the content owner, the URLs that must exist, and the speed and index rules before anyone picks a colour. Development that starts from a homepage mock-up alone usually launches a site search engines can see and customers cannot use, or the reverse.
Cite as: Dsignr Digital, “A Web Development Brief That Search Can Actually Use”, dsignrdigital.co.za, updated November 2026, Rosebank, Johannesburg.
The brief is where search is won or lost
Last updated: November 2026. Teams ask for SEO after the templates are built. By then the URL scheme, the heading structure, and the component library are already decisions. Changing them is a variation. Putting them in the brief is scope.
This is for a marketing lead and an IT lead writing a development brief together. It is not a keyword list and it is not a substitute for the web development service page, which is where the commercial offer lives. If you are still deciding whether to rebuild, start with when a mid-sized company should rebuild. If you are ready to ask suppliers to price the work, use how to write a website RFP and attach the items on this page as an appendix.
Google’s page experience guidance asks whether the page is usable, not whether a report is green. Your brief should say what “usable” means for your users: a form that submits on a mid-range phone, a page that can be reached without a script maze, and content that is in the HTML rather than only in an image.
Do not paste a competitor’s sitemap and call it requirements. Say what a visitor must be able to do, and which pages your own staff must be able to edit without a developer. If the only success measure in the brief is “modern”, add the jobs the site must keep doing on the Monday after launch: the form that sales already uses, the careers URL on job ads, and the service pages a salesperson sends in a proposal. Those jobs are the requirements. The visual direction is how they should feel, not a replacement for them.
Templates and URLs, written as requirements
Name the templates. A corporate site usually needs a home page, a service or product template, a location or sector template, an article template, a contact template, and a legal template. Each one should state:
- The single H1, edited in the CMS, not baked into a picture
- Where the meta title and description are written, and that they are not copied blindly from the H1 on every URL
- The index rule: which templates are indexable, and which are utility pages (thank-you, search results, gated duplicates) that must be noindex
- The canonical URL when the same offer can be reached two ways
- A stable path. Do not launch on /new-home-v3 and plan to “fix URLs later”
List the URLs that already earn impressions or links. Those paths should survive, or the brief must include a one-hop redirect map. A redesign that 404s last year’s service URLs is a development defect, not an SEO phase two.
Components need rules too. An accordion that hides the only copy of a pricing explanation is still content, and it should be in HTML. A banner that is the only place the offer is written, as pixels, is invisible to anyone who cannot see the image and weak for search. Say in the brief: offers, proof, and contact details are text.
Agree the redirect map as a spreadsheet in the appendix: old path, new path, status 301. Suppliers can price that. They cannot price “keep SEO the same”.
Include the pages that are easy to forget because they are not in the design file: careers, investor PDFs, dealer login, and campaign URLs still running in ads. Each one is either kept, redirected, or explicitly retired. “We will see at launch” is how a paid-search ad keeps spending against a 404 while the new homepage is celebrated in the board pack. Ask whoever runs ads for the destination URLs before the map is called finished. IT can export the current routes. Marketing can mark which ones a customer still uses. The spreadsheet is the brief.
Say how editors will preview a page. A brief that specifies templates but not a staging password, a review role, and a way to compare old and new URLs will stall in week six. Build the preview into the timeline next to design approval. Content owners cannot approve a page they cannot open, and they should not approve it on production.
Content ownership before the design is pretty
Development does not invent your expertise. If the brief says “SEO copy included” and nobody inside the company will review it, you will publish smooth paragraphs that legal cannot defend and sales do not recognise.
Name a content owner per template. That person approves claims, prices, and the sentences that might be quoted. A second person, not the supplier working alone, should fact-check anything drafted with AI. Google’s guidance on generative AI says that review is critical, and that it includes titles, descriptions, and alt text. Put the review in the timeline. A two-day “content drop” at the end is how errors ship.
For each indexable template, the brief should require a real example, not lorem ipsum, before front-end build finishes. One true service page will show that the template cannot hold a table, a credential, or a South African phone number. Better to learn that in staging.
Also say who may publish. Marketing should be able to edit approved components. They should not need a developer for a paragraph, and they should not be able to inject an unreviewed script. That split is a CMS permission, and it belongs in the brief next to the roles, not in a post-launch argument.
Speed, indexation, and what to measure
Ask for a performance budget in words a project manager can test. For a marketing site that usually means: the primary template renders useful text without waiting on a tag manager, images are sized for the slot they sit in, and third-party scripts are listed with an owner. Every new chat widget, heatmap, and advertising tag needs a name next to it. Untagged scripts are how launches miss the budget.
Indexation requirements are shorter:
- An XML sitemap of indexable URLs only, generated by the CMS
- A robots.txt that blocks the admin and utility paths and does not block CSS or the public site
- A canonical host. One of www or the apex, one of http or https, with redirects in a single hop
- Noindex on search results, thank-you pages, and parameter duplicates
- A staging site that is not indexable, so the unfinished build does not compete with the live one
Measure on the templates you listed, on a phone-sized viewport, against the staging password being off for the test URLs. A perfect score on a blank framework page is not the site you are buying.
Do not write “Core Web Vitals: all green” as the only line. Say which template and which connection you care about. A heavy dealer-locator may never match a brochure page, and pretending otherwise produces a change request on the week of launch.
What a financial-services brief changed
A regional financial-services brand arrived with a homepage design and a request to “keep our SEO”. The live site had twelve service URLs that already appeared in search, a thank-you page that was indexed, and a blog of thin city pages. The design file had none of those URLs.
The brief we could price added three lines the design had skipped. First, the twelve URLs mapped to the new service template or to a redirect. Second, city pages would be removed and redirected to the real office pages, not rewritten. Third, the thank-you page would be noindex, and the application form would be HTML with labels legal had already approved.
That appendix was two pages. It prevented a launch that would have looked new and lost the only URLs the business had earned. The visual design barely changed. The development scope did, because redirects, permissions, and a form review are work.
Use the same test on your draft brief. If a developer can build the pictures without knowing which URLs survive, the brief is not ready to send.
The one-page appendix to attach
Attach this to the RFP or the internal brief. Suppliers should answer it in the proposal, not after kickoff.
- List of templates and which are indexable.
- Redirect map for every current URL you care about, including PDFs that still get visits.
- Content owner and fact-checker named, with dates for example content.
- CMS roles: who edits, who publishes, who can add a script.
- Canonical host, sitemap, robots rules, and a noindex staging site.
- Third-party scripts with an owner, and a performance check on the real templates.
- Analytics and search console access in the company’s own accounts before launch.
- Care after go-live: who patches, and for how many hours a month. Link the SLA if you have one.
If a proposal answers “SEO is included” and does not address this list, ask again. Included often means a plugin and a blog post. You are buying a site your team can run.
Bring the appendix to a working session rather than sending it into a void. Book a 30-minute call with the person who will own content and the person who will own DNS. We would rather price a brief that names the URLs than discover them at launch.
Briefs that create a redesign you cannot find
- Starting from the homepage only. The templates that repeat are the site.
- Letting the new CMS invent URLs and promising redirects in a later phase that has no budget.
- Putting all proof inside sliders and images so the text a visitor needs is not in the page.
- Indexing every tag, author, and parameter because the default was left on.
- Shipping AI copy no one read because the timeline said content was “done” when the file was generated.
A brief that prevents those five outcomes is doing the job. You do not need a separate SEO document that contradicts it. One appendix, owned by marketing and IT, is enough to hold the supplier to a site that can be crawled and maintained.
Frequently Asked Questions
Should SEO be a separate phase after development?
Indexation, URLs, headings, and redirects are development scope. Ongoing content and promotion can be a later engagement. Leaving URLs and templates to “phase two” means phase two is a rebuild.
What if we do not know which old URLs matter?
Export Search Console and the current sitemap before you write the brief. Keep URLs that have impressions, links, or a real user task. Redirect or retire the rest on purpose.
Do we need a keyword list in the brief?
A short list of the services and locations you actually offer is enough to name pages. A hundred-row keyword sheet does not replace templates, owners, and redirects.
How does this fit an RFP?
Use the RFP for commercial terms, timeline, and evaluation. Attach this appendix so every supplier prices the same index and content rules.
Who should sign the brief?
The marketing owner of the words and the IT owner of the CMS and DNS. Legal should see any form or claim template before build, not on the morning of launch.