A website redesign changes how visitors understand your business, but it can also change the addresses and content that search engines already know. Before hiring an agency, separate what needs a better presentation from what genuinely needs to be removed, moved, or rewritten.
A useful redesign brief includes content ownership, important existing URLs, working forms, and launch responsibilities alongside visual direction. This is a project-planning guide, not a promise that a redesign will increase rankings or conversions.
Related service: Website design and development services- 01Inventory the current site
- 02Agree page purposes
- 03Design with real content
- 04Build and test
- 05Launch and monitor
SECTION 01
Record what the current website already does
List current URLs and their purposes. Note important search landing pages, service explanations, downloadable material, forms, and external links your business relies on. Where you have access, use Search Console and analytics to understand which pages visitors actually find and use.
Mark each page to keep, improve, merge, or retire, with a reason. A page receiving few visits might still answer an important buyer question. Conversely, two near-identical pages may confuse users even if both contain attractive keywords.
Keep this inventory available during development. It becomes the source for navigation, migration decisions, and post-launch checking rather than an audit document nobody opens again.
SECTION 02
Illustrative example: a service business reorganizing its site
Imagine an agency redesigning a business site with a general services page and several detailed service URLs. The new design can introduce clearer navigation and smaller headings while keeping those established service addresses and useful explanations.
If two overlapping pages are consolidated, the team should select the appropriate destination, preserve the information visitors still need, update internal links, and implement a direct redirect from the retired URL. Redirecting every removed page to the homepage does not give users an equivalent answer.
This is an illustrative migration decision, not a claim about a client outcome. The acceptance evidence is a tested mapping and a page that still answers the original intent, not a screenshot of the new homepage.
SECTION 03
Design with complete content and clear responsibilities
Agree who writes, reviews, and uploads each page. Use realistic headings, paragraphs, and images in design reviews so the layout is tested against actual information. A short placeholder can hide awkward wrapping and leave no room for the explanation a buyer needs.
Keep one main purpose per page and use headings that help readers choose where to look. Put the answer to the page's main question near the beginning. Include relevant evidence and links rather than repeating service keywords in every section.
For forms, specify required fields, validation, the delivery destination, confirmation behavior, and who handles the inquiry. W3C's forms guidance provides useful checks for labels, instructions, and errors. A form that looks complete but never reaches your team is not a finished lead journey.
SECTION 04
Scope migration checks as real development work
Google's site-move guidance describes URL mapping, redirects, canonical references, and sitemap updates when addresses change. For your project, make a test list from the actual old and new URLs rather than applying a generic redirect rule without review.
Check whether the preview environment is blocked from indexing and whether the production release removes any temporary restriction. Inspect representative rendered pages for their titles, descriptions, canonical URLs, main heading, and visible content. Keep useful internal links pointing directly to the final destination.
SECTION 05
Compare redesign quotes using the same delivery boundary
Ask whether the proposal includes content migration, editable components, accessibility checks, performance review, analytics continuity, and post-launch fixes. A design-only engagement and a complete rebuild with migration cannot be compared by page count alone.
A lower-budget redesign can retain the existing platform and URLs while improving templates and content hierarchy. If you also change the platform, domain, content, and integrations, the project needs more coordination. Sequence changes where practical so failures are easier to diagnose.
After launch, check real inquiries, broken links, indexing signals, and important landing pages. Rankings can fluctuate and recrawling takes time. Keep monitoring evidence separate from guarantees about when traffic will recover or grow.
SECTION 06
Frequently asked questions
Will a website redesign affect SEO?
It can if URLs, content, links, rendering, or indexing settings change. Preserve useful pages, test migration details, and monitor Search Console after launch. A redesign alone does not guarantee improved rankings.
Do we need new URLs for a redesign?
Not usually just for a visual change. Keep meaningful existing URLs when they still fit. If a URL must change, plan a relevant redirect and update internal references.
What should a website redesign agency hand over?
The agreed deliverables should cover the website, editing access, content, account ownership, migration mapping, test results, deployment instructions, and any support arrangement. Confirm which items are included before work starts.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Site moves with URL changesGoogle Search Central
- Accessible forms tutorialWorld Wide Web Consortium
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy