A redesign should not begin with the homepage mockup. Start by inventorying indexed URLs, organic traffic, backlinks, conversions, analytics, technical constraints and content that already performs. Preserve useful URLs where possible, map every changed URL to an intentional redirect, test technical SEO before launch and monitor Search Console immediately afterwards.
Know what already creates traffic, authority and leads.
Every meaningful old URL needs a deliberate destination.
Crawl, indexing, rankings and conversions are checked after launch.
Create a baseline
Export indexed URLs, traffic, queries, backlinks and conversions.
What this changes in practice
In practice, this step should connect to Baseline and URL strategy. Export organic pages, queries, leads and backlinks before changing the site. Decide which URLs stay, merge, move or disappear. This turns a preference into a testable project decision.
Bring Content into the same review. Keep intent and valuable information even when rewriting. For an SME, this reduces late rework, makes supplier scope easier to compare and connects the project to a commercial or operational outcome.
Preserve valuable intent
Old-looking pages may still carry rankings and links. Rewrite carefully instead of deleting accumulated value.
What this changes in practice
In practice, this step should connect to URL strategy and Content. Decide which URLs stay, merge, move or disappear. Keep intent and valuable information even when rewriting. This turns a preference into a testable project decision.
Bring Technical SEO into the same review. Review status codes, canonical, hreflang, sitemap and robots rules. For an SME, this reduces late rework, makes supplier scope easier to compare and connects the project to a commercial or operational outcome.
| Dimension | Question to ask | Good signal |
|---|---|---|
| Baseline | Export organic pages, queries, leads and backlinks before changing the site. | There is a measurable pre-redesign reference point. |
| URL strategy | Decide which URLs stay, merge, move or disappear. | Redirects are designed before launch. |
| Content | Keep intent and valuable information even when rewriting. | High-performing pages retain their purpose. |
| Technical SEO | Review status codes, canonical, hreflang, sitemap and robots rules. | A staging crawl finds issues before production. |
| Analytics | Preserve events, consent, UTM attribution and conversion tracking. | The new site measures the same business outcomes. |
| Launch control | Monitor logs, Search Console and important landing pages. | Critical issues have an owner and rollback path. |
Plan redirects and technical details
Every important URL needs the most relevant destination. Update internal links, sitemap, canonicals, hreflang and structured data.
What this changes in practice
In practice, this step should connect to Content and Technical SEO. Keep intent and valuable information even when rewriting. Review status codes, canonical, hreflang, sitemap and robots rules. This turns a preference into a testable project decision.
Bring Analytics into the same review. Preserve events, consent, UTM attribution and conversion tracking. For an SME, this reduces late rework, makes supplier scope easier to compare and connects the project to a commercial or operational outcome.
Improve conversion
Make offer, proof and CTA understandable immediately. Pass page context into the CRM form.
What this changes in practice
In practice, this step should connect to Technical SEO and Analytics. Review status codes, canonical, hreflang, sitemap and robots rules. Preserve events, consent, UTM attribution and conversion tracking. This turns a preference into a testable project decision.
Bring Launch control into the same review. Monitor logs, Search Console and important landing pages. For an SME, this reduces late rework, makes supplier scope easier to compare and connects the project to a commercial or operational outcome.
Monitor after launch
Track crawl errors, excluded pages, speed, positions and conversions for several weeks.
What this changes in practice
In practice, this step should connect to Analytics and Launch control. Preserve events, consent, UTM attribution and conversion tracking. Monitor logs, Search Console and important landing pages. This turns a preference into a testable project decision.
Bring Baseline into the same review. Export organic pages, queries, leads and backlinks before changing the site. For an SME, this reduces late rework, makes supplier scope easier to compare and connects the project to a commercial or operational outcome.
Pedagogik: redesign around a stronger digital experience.
The work focuses on modernising presentation and usability while treating existing visibility and content as assets to preserve.
View the project ↗Questions to settle before you start
Make the main unknowns visible before committing budget. An unanswered question is not a problem when it is explicit; it becomes a risk when it is hidden inside a supplier assumption and discovered during development.
Answer these questions with the people who will use, sell or operate the solution. Discovery then becomes an internal decision tool, not just a document sent to a supplier.
- How is baseline handled today, and what should measurably improve after the change?
- How is url strategy handled today, and what should measurably improve after the change?
- How is content handled today, and what should measurably improve after the change?
- How is technical seo handled today, and what should measurably improve after the change?
- How is analytics handled today, and what should measurably improve after the change?
- How is launch control handled today, and what should measurably improve after the change?
Common failure patterns and warning signs
The failure patterns below all push important decisions towards the end of the project, where change is more expensive. A strong process makes these risks visible early.
Use the warning signs as review criteria. If several appear at once, reduce scope, add discovery or validate a prototype before investing further.
- Leaving baseline until the solution has already been built
- Leaving url strategy until the solution has already been built
- Leaving content until the solution has already been built
- Leaving technical seo until the solution has already been built
- Leaving analytics until the solution has already been built
- Leaving launch control until the solution has already been built
Recommended action plan
A good decision should be measurable after launch. Establish a baseline, an owner and a review cadence, then compare the same indicators after launch.
A useful roadmap separates launch from evolution. Prioritise later work from usage data, leads, support tickets and operational gains instead of an old pre-project wish list.
- 1. Discovery — Goals, users and the current process.
- 2. Scope — Must-haves, assumptions and risks.
- 3. Prototype — Critical journey and key decisions.
- 4. Build — Content, data, technology and integrations.
- 5. Launch — Testing, analytics and ownership.
- 6. Improve — Usage, feedback and KPIs drive the roadmap.
Build the business case before comparing proposals
A project involving Website redesign without losing SEO: migration and conversion plan is easier to govern when it is framed as an investment rather than a feature list. Start with one measurable outcome: more qualified enquiries, less manual re-entry, a shorter sales cycle, greater user self-service or lower operational risk. Use that outcome to judge every scope decision that follows.
The first layer of the business case connects Baseline with URL strategy. Export organic pages, queries, leads and backlinks before changing the site. Decide which URLs stay, merge, move or disappear. Quantify the current state where possible: enquiries per month, minutes per task, drop-off, licence cost, error volume or average cycle time. A reasonable baseline is more useful than a vague objective such as ‘modernisation’.
The second layer includes costs that appear after launch. Analytics and Launch control therefore belong in the same decision as design and development. Preserve events, consent, UTM attribution and conversion tracking. Monitor logs, Search Console and important landing pages. A cheaper initial proposal can become more expensive if it leaves heavy manual work, unexpected licences or an architecture that is difficult to evolve.
Finally, assign value to risk reduction. Content and Technical SEO often affect total cost more than expected. Keep intent and valuable information even when rewriting. Review status codes, canonical, hreflang, sitemap and robots rules. The right question is not only ‘how much does it cost?’, but ‘what level of investment is proportionate to the outcome, the risk and the expected useful life?’.
Three scope scenarios to make the decision concrete
These scenarios are not price packages. They separate the essential need from medium-term ambition. A good proposal makes the layers visible so functions can be postponed without breaking the logic of the product.
Compare proposals without comparing apples and oranges
Two proposals with the same headline deliverable can cover very different realities. Ask suppliers to respond to the same scope, assumptions and definition of ‘done’. Price then becomes a consequence of visible choices instead of a number that is impossible to interpret.
Make responsibilities explicit as well: who provides content, who approves, who configures access, who migrates data, who tests, who hosts and who responds after launch? Grey areas are often the first source of budget and timeline overruns.
| Criterion | What to review | Evidence to expect |
|---|---|---|
| Baseline | Export organic pages, queries, leads and backlinks before changing the site. | There is a measurable pre-redesign reference point. |
| URL strategy | Decide which URLs stay, merge, move or disappear. | Redirects are designed before launch. |
| Content | Keep intent and valuable information even when rewriting. | High-performing pages retain their purpose. |
| Technical SEO | Review status codes, canonical, hreflang, sitemap and robots rules. | A staging crawl finds issues before production. |
| Analytics | Preserve events, consent, UTM attribution and conversion tracking. | The new site measures the same business outcomes. |
| Launch control | Monitor logs, Search Console and important landing pages. | Critical issues have an owner and rollback path. |
Measure value after launch
Measurement starts before launch. Choose two to four KPIs that come directly from the business case, record the current baseline and assign someone to review them after 30, 60 and 90 days. For Baseline and URL strategy, favour indicators that show changed behaviour or business outcomes rather than traffic alone.
Add quality indicators around Content and Technical SEO. A product can convert more while creating more errors or support demand; an automation can save time without improving the experience. Use several dimensions of value rather than a single vanity metric.
Finally, connect Analytics and Launch control to operating cost: licences, administration time, tickets, maintenance and required enhancements. After a few months you will have enough evidence to decide whether to invest further, simplify or expand the solution.
- Conversion or adoption
- Time saved
- Quality / error rate
- Cycle time
- Operating cost
- User satisfaction
How ready are you?
Are you ready to move forward?
Frequently asked questions
Should URLs remain identical?+
Keep clear, strong URLs where possible.
Can a CMS migration preserve SEO?+
Yes, with controlled content and technical migration.
How long should monitoring continue?+
At least several weeks, especially during the first days.
How large should the first release be?+
Large enough to support one valuable journey end to end, small enough to test and improve quickly.
What needs to happen after launch?+
Monitoring, support, ownership and a roadmap are part of the solution, not just the delivery project.