Skip to the indexed answers
Digital Marketing Index

usdigitalmarketingindex.com SEO

Which SEO requirements belong in the brief for a planned website redesign?

Four groups of requirements belong in the brief, each written as something that can be checked: which URLs are kept and where every changed URL redirects, what must stay crawlable and indexable, which content and page-level elements carry over, and who tests all of this before launch. They belong in the brief, not in a later audit, because each one constrains design and build decisions that are expensive to reverse. Google’s guidance on hiring SEO help names the moment: when “considering a site redesign (the earlier, the better)” (Google’s guidance on hiring an SEO).

URL preservation and redirects

The first requirement is the default: existing URLs stay the same unless there is a stated reason to change them. A redesign that keeps its URLs avoids the largest class of risk.

Where URLs do change, Google’s guidance for site moves lists the preparation in plain terms, including “Prepare the new site and test it thoroughly” and preparing a URL mapping from the current URLs to their new ones (Google’s guidance on site moves with URL changes). In the brief that becomes four acceptance criteria.

  • A complete inventory of current URLs exists before design starts, drawn from the sitemap, a crawl, analytics, and Search Console.
  • Every URL that changes has a single mapped destination that serves the same purpose.
  • Redirects are permanent, server-side, and go to the final URL in one step.
  • Internal links, canonical tags, and the sitemap use the new URLs directly.

Crawl and index constraints

The second group protects what search engines can reach.

Requirement Acceptance check
Content and links are present in the rendered HTML URL Inspection on each template shows the main content and navigation links
Navigation uses real links with href attributes A crawl discovers every page that the current site exposes
No noindex or blocking robots.txt rule reaches production Checked on launch day for every template
Each page has one canonical URL, pointing to itself unless consolidation is intended Crawl report of canonical targets
Mobile pages contain the same content as desktop Side-by-side comparison of each template
Status codes are correct: 200 for live pages, 404 or 410 for removed ones Crawl of old and new URL lists

Development and staging environments need their own line in the brief: how they are kept out of search, and who removes that protection, and only that protection, at launch.

Content and metadata handoff

A redesign is a design project, and content gets lost in it unless the brief says otherwise.

  • Page content carries over unless a named owner approves its removal. This includes body copy hidden behind new tabs or accordions.
  • Title elements and main headings are migrated as they are, then improved deliberately, not regenerated by a template.
  • Image alt text, structured data, and hreflang annotations, where present, are inventoried and carried across.
  • Internal links inside body content are preserved and updated to new URLs.
  • Pages that receive search traffic or external links are flagged, so no one deletes them as clutter.

Add one requirement that designers do not expect: a list of the pages that currently bring organic visits, attached to the brief, so that changes to those templates get extra scrutiny.

Prelaunch testing ownership

Requirements without owners are not met. Assign each check to a person and a point in the schedule.

Requirement group Owner When
URL inventory and mapping SEO lead Before design sign-off
Redirect implementation Developer Before staging review
Redirect testing against the full map SEO lead On staging, and again at launch
Crawl of staging for links, canonicals, status codes SEO lead Before launch approval
Rendered-content check on each template Developer and SEO lead Each template at completion
Content and metadata comparison, old against new Content owner Before launch approval
Removal of staging blocks, verification of robots.txt and noindex Developer, confirmed by SEO lead Launch day
Benchmark of current performance in Search Console and analytics SEO lead Before launch

Two schedule items deserve their own lines. Google’s site move guidance suggests timing a move “to coincide with lower traffic, if possible”, so the launch date should be chosen with the traffic calendar in view. And launch approval should require a written sign-off that the checks above passed, with the evidence attached.

The brief ends at launch. What to watch in the weeks afterward, and how to tell a normal settling period from a problem, is the subject of the guide to the SEO indicators to review in the first month after a CMS migration.

The measure of a good brief: every SEO requirement in it names a check, an owner, and a date. A requirement that names none of the three is a wish.

Link trail

Reader comments on this answer

Add your comment to this answer

Your email address will not be published. Required fields are marked *