What Makes a Business Website SEO-Ready? A Client Brief

An SEO-ready business website brief tells the designer what the site must help customers do, what topics it must explain and which technical standards must be proven at handover. “Include SEO” is too vague. Use this client brief to turn SEO readiness into visible deliverables and acceptance tests.

Reviewed: 18 August 2026

Start with business outcomes, not page count

State the primary outcome: qualified enquiries, bookings, calls, purchases, applications or store visits. Add the secondary actions that show progress, such as viewing pricing, reading a case study or downloading a guide.

Define the customers, geographic market, core services and questions they ask before buying. Give the agency real sales calls, proposals, support questions and objections. These are more useful than a list of keywords detached from the buying process.

Copy this project summary

We need a fast, accessible and maintainable business website that clearly explains our services and turns relevant visitors into qualified enquiries. The site must be crawlable, use a logical information architecture, preserve valuable existing URLs, include measurement and give our team ownership of all accounts and content.

Define audiences and journeys

For each important audience, describe the problem, required evidence and likely next step. A technical buyer may need implementation detail and security information; an owner-manager may need plain-language scope, pricing signals and reassurance that disruption will be controlled.

Ask the designer to show the route from landing page to decision. Navigation, internal links, calls to action and forms should support that route without forcing every visitor through the home page.

Specify the information architecture

Request a proposed sitemap before visual design is finalised. It should cover:

• a clear home page and primary service hubs;
• distinct pages for materially different services or audiences;
• about, contact, privacy and other trust information;
• case studies, proof and useful educational content;
• logical parent-child relationships and breadcrumbs where useful.

Ask which search intent and customer question each page serves. Challenge pages that differ only by a few words, and pages that combine several unrelated services because the page count was fixed too early.

Content responsibilities

Agree who interviews subject-matter experts, writes copy, supplies evidence and approves claims. Define the number of revision rounds and whether content migration, image selection and redirects are included.

Each important page should have one descriptive H1, useful section headings, a direct opening, clear next steps and specific evidence. Require unique page titles and meta descriptions, but do not measure success by keyword repetition.

Technical SEO deliverables

Put the following in the scope:

• clean, descriptive and stable URLs;
• unique titles, descriptions and canonical tags;
• correct 200, redirect, not-found and server-error responses;
• intentional robots.txt and index/noindex controls;
• an XML sitemap containing canonical indexable pages;
• redirect mapping from valuable old URLs;
• descriptive alt text and correctly sized images;
• valid Organization, breadcrumb, article, product or other applicable structured data;
• HTTPS with no mixed content;
• Google Search Console and Bing Webmaster Tools ownership.

Google’s SEO Starter Guide explains the underlying principles: help search engines understand content while making the site useful and well organised for people.

Performance requirements

Do not request a vague “fast website”. Ask how performance will be tested on representative page types and mobile devices. Use Google’s Core Web Vitals recommendations as goals for real-user experience: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint below 200 milliseconds and Cumulative Layout Shift below 0.1 at the 75th percentile.

These are not a complete user-experience score, but they create measurable acceptance criteria. The agency should explain image optimisation, font loading, caching, third-party scripts and what ongoing hosting or content changes may affect performance. See Google’s Core Web Vitals guidance.

Accessibility and responsive behaviour

Request semantic HTML, keyboard access, visible focus, labelled forms, sufficient contrast, meaningful error messages and layouts that work at small and large sizes. Define an accessibility target appropriate to the organisation, ideally WCAG 2.2 AA, and ask how it will be tested.

Accessibility and SEO are not interchangeable, but both benefit from clear structure, meaningful controls and content available without fragile interactions.

Analytics and conversion measurement

List the decisions the business wants data to support. Ask for consent-aware analytics, Search Console verification and events for genuine outcomes: submitted enquiry, booked consultation, phone link, purchase or qualified lead.

Require a short measurement document showing event names, triggers and where reports can be found. Confirm that the business—not only the agency—has administrative ownership.

Content management and training

The team should be able to edit normal page copy, add an article, replace an image and change basic metadata without breaking the layout. Ask for reusable components, sensible permissions, editorial guidance and a recorded or written handover.

Clarify who updates the content management system, plugins, framework and server after launch. A site is not SEO-ready for long if unsupported software or careless edits degrade security and performance.

Handover evidence to request

1. Final sitemap and URL redirect map
2. Crawl report covering statuses, canonicals, titles and index controls
3. Structured-data validation results
4. Performance results for representative templates
5. Mobile, keyboard and form QA record
6. Analytics event and consent test
7. Search Console and sitemap verification
8. Backup, monitoring, update and rollback responsibilities
9. Account ownership and credential handover

For the implementation-level review behind those deliverables, use our 25-point SEO-ready website checklist.

Red flags in website proposals

• Guaranteed rankings or traffic without research
• No plan for existing URLs and redirects
• SEO treated as a plugin installed at the end
• No named owner for copy, images or approvals
• No measurable performance or accessibility acceptance tests
• The agency retains sole ownership of the domain or analytics
• Maintenance and security end at launch without warning

Commission an SEO-ready build

ACA Tech Solutions combines strategy, design, build, SEO foundation, QA, launch and care in one website track. Current published packages begin at £500, with scope varying by page count, hosting and ongoing care. Review the business website service and current pricing.

Frequently asked questions

Who should write the website brief?

The business owner should define outcomes, audiences and evidence with input from sales, operations and subject experts. The designer or SEO specialist can translate that into architecture and technical requirements.

Is keyword research part of web design?

It should inform structure and content before design is fixed. Confirm the depth of research, deliverables and whether competitor and Search Console data are included.

What should happen after launch?

Monitor indexing, errors, real-user performance and conversions; publish useful content; maintain software and backups; and improve pages using evidence rather than redesigning by instinct.