Website redesign. Keep what earns its place.
A redesign starts with what the current site already does well. Inventory useful content, established URLs and enquiry paths before changing templates or navigation. We agree the build, any URL migration and release responsibilities as a separate website project.
Thoughtfully scoped. Separately quoted.
A good place for your next chapter.
Inventory before the visual redesign.
Identify useful URLs, content, existing search evidence and enquiry paths before changing navigation or templates. Record what should remain stable and who owns the release.
Use the migration QA checklist to plan pre-launch and released-page checks. A limited content issue may need an existing-page refresh rather than a full redesign.
A new design with a release plan.
Keep, improve or justify a move.
A page with a useful independent job can often stay at the same URL. Improve incomplete content in place. An actual overlap needs content and equity review before a combination is proposed.
A smaller existing-page refresh may solve the problem without rebuilding.
Agree the map and receiving behavior.
Map any approved old-to-new move directly to a relevant destination. Update links and intended canonicals together, preserve useful content and document what happens if verification fails.
Check a proposed CSV with the redirect map planner; it does not deploy host rules.
Launch checks and rollback ownership.
Verify important pages, real response behavior and the receiving form system at the actual host. A failed key enquiry route or unintended crawl restriction is a release blocker. Keep the prior known state and rollback decision owner available.
Use the migration QA checklist before and after the approved release.
Separate from monthly SEO.
The $99 monthly subscription excludes full rebuilds, major migrations and custom engineering. A website enquiry is a scope conversation, not acceptance of an unlimited development service or a fixed-price package.
Before you scope the project.
Will the redesign preserve every ranking?
No ranking retention can be guaranteed. We plan URL, content and launch checks to manage avoidable regressions, using actual performance evidence when available.
Do all existing URLs need to change?
No. Existing useful paths are preserved where possible. A changed or removed URL requires an explicit decision and appropriate destination plan, not an automatic redirect to the homepage.
Who decides whether the site is ready?
The agreed owner accepts the page/content inventory, functional checks and launch dependencies. Release authority and rollback responsibilities are named before launch.
Find your way forward.
Let’s make something useful.
Tell us about the site you have in mind.