Website decision guide
Compare the work behind relaunch and redesign.
Suppliers use these labels differently. Mark what changes, what stays, and how each result will be accepted before you compare price.
Direct answer
- The words relaunch, redesign, revamp, and refresh do not define a reliable scope. One supplier may call new templates a redesign. Another may include a CMS and URL migration.
- Choose by change boundary: audiences, content, navigation and URLs, templates, CMS work, integrations, analytics, infrastructure, accessibility, and transfer.
- Keep five outcomes open: measure first, repair the current site, improve selected pages, redesign templates and journeys, or rebuild the platform and structure.
- Protect search pages with current query, landing-page, and URL evidence. A URL-changing migration needs mapping, redirects, canonical checks, internal-link updates, and monitoring.
- Compare quotes line by line. The dedicated Germany website cost guide explains the cost inputs without turning them into a universal price.
Possible decisions
Your evidence can support five different decisions.
Measure before approving work
Use this when the team has opinions but no page, query, form, editor, or performance evidence. Record what must be measured and set a decision date.
Repair or take over the current site
Use this when access, updates, backups, forms, security, or supplier transfer is the immediate problem. The visible design can remain in place.
Improve selected pages or journeys
Use this when evidence points to a bounded set of landing pages, forms, navigation paths, or performance faults. State which pages and measures enter scope.
Redesign templates and journeys
Use this when page patterns, visual hierarchy, navigation, or user journeys need coordinated change. Confirm whether the CMS, content model, and URLs also move.
Relaunch or rebuild
Use this when the platform, information architecture, content model, URLs, or operating model must change together. Write migration and transfer controls into scope.
Change boundary
Make every supplier mark the same ten rows.
| Area | Current state | Proposed change | Evidence | Acceptance test |
|---|---|---|---|---|
| Positioning and audiences | Who the site addresses today | Audiences, offers, messages, languages | Approved commercial priorities and buyer research | A reviewer can find the relevant offer and next step |
| Content inventory | Pages and assets kept, merged, removed | Writing, editing, entry, translation | URL export, owners, search and usage data | Every current item has a recorded destination or removal decision |
| Navigation, structure, URLs | Menus, hierarchy, current addresses | New hierarchy, page moves, URL rules | Crawl, top landing pages, internal search or user evidence | Old-to-new URL map and navigation tasks pass |
| Templates and design system | Reusable page and interface patterns | Changed templates, components, states | Page sample and usability findings | Approved templates work with real content and required states |
| CMS and editorial work | How editors create, review, and publish | Content model, permissions, preview, training | Observed editor tasks and publishing constraints | Editors complete agreed tasks without supplier help |
| Forms and integrations | Forms, CRM, email, search, feeds, APIs | Connections replaced, retained, or removed | Integration inventory and failure history | Test records reach the correct system and failures are visible |
| Analytics and consent | Events, dashboards, tags, consent settings | Measurement plan and migration | Current event list and reporting needs | Agreed events and consent states pass in production |
| Hosting, performance, security | Host, CDN, updates, backups, recovery | Infrastructure and operating controls | Field data, logs, update and restore records | Performance budget, security checks, and restore test pass |
| Accessibility | Known barriers across key pages and functions | Target criteria, fixes, and evaluation scope | Representative sample reviewed by a qualified evaluator | Defined sample and complete processes meet the agreed checks |
| Accounts, support, transfer | Domains, hosting, repositories, licenses, access | Ownership, documentation, response and exit work | Account and dependency inventory | Client access, documentation, export, and handover test pass |
Evidence before scope
Collect evidence that can change the recommendation.
✓
**Search demand:** export landing pages and queries from Search Console, including clicks and impressions. Google explains the [Performance report and its limits](https://support.google.com/webmasters/answer/7576553).
✓
**Commercial paths:** list the forms, calls, downloads, applications, and other actions the business uses. Test delivery before treating the event count as reliable.
✓
**URL inventory:** crawl the current site and join each address to search, link, content-owner, and destination data.
✓
**Editor task test:** ask an editor to update a service, add an asset, preview it, obtain approval, and publish. Record where work stops.
✓
**Connections and accounts:** list CRM, email, analytics, consent, search, feeds, domains, hosting, repositories, and license owners.
✓
**Index and performance state:** save the current crawl/index reports and field performance data where enough real-user data exists.
✓
**Accessibility sample:** include key page types, important functions, and complete processes. W3C [WCAG-EM](https://www.w3.org/WAI/test-evaluate/conformance/wcag-em/) explains representative sampling and its limits.
✓
**Recovery and transfer:** verify backups can be restored and that the company can access the systems and exports needed to change supplier.
Comparable quotes
Normalize the work before comparing the total.
| Quote line | Supplier A | Supplier B | Internal work | Excluded or recurring |
|---|---|---|---|---|
| Evidence review and written recommendation | Included scope and output | Included scope and output | Data access and reviewers | Additional research |
| Content inventory, writing, entry, translation | Pages, rounds, languages | Pages, rounds, languages | Subject experts and approvals | New pages or extra rounds |
| Structure, templates, and design states | Specified outputs | Specified outputs | Decision makers and review time | Extra templates or states |
| CMS, integrations, analytics, consent | Systems and tests | Systems and tests | Credentials and business rules | Licenses and third parties |
| Migration and launch | URL map, redirects, checks, support | URL map, redirects, checks, support | Acceptance and release decision | Work after the stated support period |
| Hosting, maintenance, licenses, transfer | Initial and recurring work | Initial and recurring work | Account ownership | Renewals, usage, exit assistance |
Search migration
Let the URL decision set the search controls.
When URLs change, Google recommends an old-to-new URL map, permanent redirects, updated internal links and canonical references, a new sitemap, testing, and monitoring. Google also advises changing major variables one at a time where practical. Its site-move guidance describes possible ranking fluctuations and does not promise a recovery date.
A hosting move with the same visible URLs is a different case. Test crawl access, keep Search Console verification, monitor old and new server traffic, and remove temporary crawl blocks at launch. Google documents this separately in its hosting-change guidance.
Save a launch baseline: indexed URLs, top landing pages and queries, clicks, impressions, form tests, analytics events, crawl errors, and redirects. Assign a person and review dates for each check.
Acceptance and review
Approve a change budget with tests and a review trigger.
Write the allowed change boundary beside the budget. A supplier must raise a decision when evidence requires another template, URL group, integration, content batch, or platform change. Record the effect on price, client work, launch conditions, and recurring cost before the boundary moves.
Attach acceptance tests to the work: editor tasks, form delivery, consent states, analytics events, redirect samples, accessibility sample, performance budget, restore test, account access, and transfer export. State who accepts each result and which evidence they receive.
Record the current decision, evidence gaps, approved boundary, protected pages and functions, owner, and review date. Reopen the decision when an integration changes, editors cannot complete agreed tasks, priority pages lose visibility, the change budget is consumed, or the commercial offer changes.
Conversion next step
Get a second look at: Website relaunch vs redesign
Tell us where visitors drop off. We reply with the change most likely to lift conversion.
Buyer questions
Questions to settle before a website proposal is approved.
What is the difference between a website relaunch and redesign?
There is no dependable market-wide boundary. Ask what changes across content, URLs, templates, CMS work, integrations, infrastructure, and operation. That written boundary is more useful than the package name.
Can we redesign the website without changing the CMS?
Yes, if the current CMS can support the required templates, content fields, preview, permissions, and publishing work. Test those editor tasks with realistic content before approving the design.
Does a website relaunch always change URLs?
No. The label does not determine the URL plan. If any URLs change, require a complete mapping, relevant permanent redirects, updated internal links and canonical references, testing, and monitoring.
Will a website relaunch reduce our Google traffic?
Traffic can fluctuate during a significant move. No supplier can guarantee rankings or a recovery date. Protect current landing pages and queries, follow Google migration controls, and agree who monitors which signals after launch.
How should we compare relaunch and redesign prices?
Compare the same outputs, quantities, internal work, exclusions, recurring fees, migration controls, and acceptance tests. Use the worksheet above, then review the cost inputs in the Germany relaunch cost guide.
When should we postpone the decision?
Postpone the build when missing evidence could change its boundary. Define the page, query, form, editor, performance, accessibility, or integration evidence to collect and set a date for the next decision.
A practical next step
Turn the evidence into one proposal boundary.
Send the current site, the proposals you received, and the business change behind the project. We will identify the evidence gaps and write which rows belong in the first scope. If operation and access are the immediate problem, start with WordPress repair and takeover.
If a rebuild is justified, review the website relaunch service, the step-by-step redesign process, and relevant website work. The scope remains tied to the evidence and acceptance tests you approve.
Editable scope template
Put the decision into a brief suppliers can price.
Free resource
Download the B2B website relaunch scope template
Commercial objective, audiences, change boundary, responsibilities, launch acceptance checks, and the first review plan.
Loading form…
Written by
Vineet Talwar
Co-founder, Tech & Operations at Some Tech Work. WordCamp speaker across Europe and Asia, and host of the WP Shoutout podcast.
Start here
Ready to talk.Book a short diagnostic.
Tell us what needs fixing
We read every brief and reply within one business day.
Prefer to talk first?or request a tech stack audit →or email us directly →
Not sure where to start? Send the stuck decision, workflow, or page. We will say whether you need a diagnostic call, a tech stack audit, or a different first step.