A building facade layered with cyan architectural panels and a cobalt frame.
All articles
Website migrations and rebuilds7 minute read

Briefing your web agency: the SEO requirements to agree before a rebuild

Give your agency a clear brief, assign responsibilities and agree the evidence you need before approving a new website.

Written by

“SEO included” is not a sufficiently precise scope for a website rebuild. It might mean editable page titles, or it might include a full migration plan, content review and post-launch verification. You need to know which before the work starts.

A good brief describes what must continue to work, what is changing, who will make the decisions and how the result will be checked. It gives your agency something concrete to price and gives you a fair basis for accepting the work.

Begin with business journeys worth protecting

Describe how people currently discover the business and what they need to accomplish. Include your important service pages, successful product categories, useful resources and routes to enquiry. Explain which markets and languages matter. Avoid reducing the brief to a list of your favourite keywords.

Share evidence where available: search landing pages, conversions, valuable backlinks, existing research and the current site structure. Include pages used by sales, customer support or campaigns even if they attract little organic traffic. A rebuild can damage a useful journey without producing an obvious search-report alert.

Write down the intended changes separately. A new design, a domain move, a platform replacement, a URL restructure and a major content rewrite create different dependencies. If all are happening together, the brief should say so. “Like the current site, but better” leaves too much room for incompatible assumptions.

Agree responsibilities before deliverables

A redirect spreadsheet is of little use if nobody is responsible for implementing it. An implemented rule is not finished until someone has checked its behaviour. Separate the person who decides, the person who builds and the person who verifies.

Use named individuals or roles that will be assigned before kickoff. One person may hold several roles in a small project, but the responsibilities still exist. Your commercial sponsor should decide who accepts residual risks; that decision should not fall accidentally to the last developer available on launch day.

Example responsibility matrix to adapt with your agency
WorkstreamDecision ownerImplementation ownerVerification
Old-to-new URL mappingClient content lead with SEO adviserAgency developerSEO reviewer tests routes and relevance
Content retained, rewritten or removedClient subject ownerEditor / CMS teamContent lead checks approved inventory
Templates and indexing controlsSEO adviser specifies expected behaviourAgency developerReviewer tests representative templates
Analytics and enquiriesClient measurement ownerAnalytics implementerTest events, consent states and real forms
Launch decisionNamed client sponsorRelease leadEvidence reviewed; accepted exceptions logged
Post-launch faultsAgreed incident ownerRelevant technical teamOriginal acceptance test rerun

Turn broad promises into acceptance criteria

An acceptance criterion says what you should be able to observe. It does not promise a ranking. Ask your agency to respond to each requirement with its proposed implementation, evidence, dependencies and exclusions.

For example, “preserve SEO” becomes a set of testable requirements: approve a URL inventory, define each page's disposition, implement the agreed mapping, check final destinations and ensure the public navigation reaches important pages. Decide how exceptions will be handled before testing finds them.

Make access part of the scope. Your reviewer needs a working staging environment early enough to influence the build, then permission to verify the public deployment. The staging site's protection and the live site's intended indexing behaviour must be distinct, with a specific release check to prevent staging directives being carried across.

Use the detailed CMS migration SEO requirements when specifying platform behaviour.

A fictional example: rebuilding a specialist B2B website

Consider a fictional engineering business replacing its CMS. It has 140 service and resource pages, technical PDFs used by sales and three regional contact routes. Its agency proposal includes 12 page templates and content entry, but does not mention PDF URLs, redirect testing or regional form routing.

The buyer adds a discovery step before design sign-off. The team identifies useful documents, agrees which pages will merge and tests a regional contact journey. The brief records who maps document URLs, who approves the destination content and who confirms that each form reaches the right team.

This does not guarantee that search performance will remain unchanged. It removes identifiable scope gaps while they are still relatively cheap to address. The practical value is shared understanding: the agency can estimate the work and the buyer can see what they are paying for.

Set review points that can influence the build

A single audit the day before launch leaves little room to correct structural decisions. Agree reviews at points when useful choices are still possible: information architecture, representative templates, content readiness and release preparation.

For each review, define the inputs and an achievable response window. A template review cannot assess pages that do not yet exist; a content review cannot verify copy that is still a placeholder. Mark incomplete evidence as pending, not passed.

Agree how change requests affect budget and timing. If the business adds a market or rewrites the URL structure late in the project, the original estimate may no longer cover the work. A clear change process protects both parties from an informal promise becoming an unpriced obligation.

  • Structure review: proposed navigation, URL rules and page inventory.
  • Template review: working examples, metadata controls and rendered content.
  • Content review: approved copy, redirects and document destinations.
  • Release review: test evidence, unresolved issues and incident ownership.
  • Live review: public responses, important journeys and measurement checks.

The website release verification guide explains the checks to repeat on the public deployment.

Ask what happens after launch

Specify a correction window and the types of issue it covers. Distinguish defects against the agreed scope from new optimisation work. State how to report an issue, who responds and who can authorise an urgent change. Out-of-hours launch coverage should be agreed rather than assumed.

Decide which baseline will be used and who will review it. Comparing the new site's first incomplete day with an old monthly average tells you little. Preserve enough pre-launch evidence to understand later changes, and separate technical verification from performance interpretation.

Make handover tangible: access ownership, configuration notes, approved mapping, test results and unresolved decisions. If all the knowledge remains in a contractor's private messages, your team has not received a maintainable outcome.

Questions to send with your next agency brief

Use these questions to expose uncertainty without turning the relationship into a confrontation. Good answers may be short, but they should make responsibilities visible. If something is outside scope, ask who will cover it and whether your launch plan depends on it.

  • Which existing URLs and documents are included in the migration inventory?
  • Who decides whether each page is retained, merged, replaced or removed?
  • Who implements redirects, and what evidence demonstrates they work?
  • When can an independent reviewer inspect representative templates?
  • How are tracking, consent and enquiry routing tested?
  • Which unresolved issues would prevent launch, and who accepts other risks?
  • What support is included after launch, for how long and during which hours?
  • What files, access and documentation will the business receive?

Get a second opinion while choices are still open

Independent support is particularly useful when your business lacks a technical search lead or several suppliers share delivery. You can commission a scope review, a requirements workshop or defined review gates without buying a permanent management retainer.

Bring the proposed sitemap, agency scope, platform choice and target launch date. The aim is to find omissions, settle ownership and make acceptance measurable. Your agency still builds the site; you gain a clearer basis for making decisions.

Key takeaways

  • Describe the business journeys and changes before listing technical tasks.
  • Assign decision, implementation and verification responsibilities.
  • Specify observable acceptance criteria rather than ranking guarantees.
  • Agree review gates, post-launch ownership and a usable handover.

Sources and further reading

Continue planning your website change

The right control plan depends on what is changing. Explore the full website change and SEO guide collection, or go straight to another relevant scenario:

About

Rob is an independent SEO and AI-search consultant with experience spanning LinkedIn, technical SEO and search leadership at MoreNiche. He helps teams turn difficult questions into clear decisions, practical plans and measurable next steps.

Need to apply this to your business? Work with Rob to establish your AI-search baseline, plan a migration, investigate technical issues or give your content team a clear direction. Remote projects, fractional support and strategic advice are available, with scope agreed around your goals.

Want an independent review of your rebuild brief?

Turn an agency proposal into clear requirements, responsibilities and launch checks before avoidable gaps become expensive changes.

Explore migration planning Discuss your project with Rob