Pre-redesign audit
Analytics, search console and technical performance review to establish what's currently working and what isn't.
Website Redesign
We redesign existing websites by auditing what's actually working first — rankings, traffic sources, conversion paths — so the rebuild improves the site without throwing away what it already earned.
The most common redesign failure isn't visual — it's technical. URLs change, redirects get missed, page titles are rewritten without checking what was ranking, and three months later organic traffic is down 40% with no one sure why.
We start with a full audit of current analytics, search console data, top-performing pages and technical debt before any new design work begins. That audit becomes the checklist the redesign is measured against — every ranking page gets a mapped equivalent, and every performance issue is fixed rather than repainted.
What's included
Analytics, search console and technical performance review to establish what's currently working and what isn't.
A full old-to-new URL map with 301 redirects implemented before launch, not patched afterward.
Reassessing navigation and page structure rather than assuming the current sitemap should carry over unchanged.
Updated design system applied across templates, replacing outdated layouts and inconsistent components.
Rebuilding the underlying code where the old site's performance, accessibility or CMS limitations were the real problem.
Tracking rankings, traffic and Core Web Vitals against the pre-redesign benchmark for the weeks after go-live.
Process
Recording current traffic, rankings, conversion rates and technical performance before any changes are made.
Deciding what's being redesigned — visual only, full rebuild, or platform migration — and mapping the new structure against the old.
Executing the redesign with the audit findings as a constraint, not an afterthought.
Testing every mapped redirect and checking for broken links before launch.
Monitoring rankings and traffic against the benchmark, correcting quickly if something regresses.
Outcomes
Redirect mapping and pre-launch QA prevent the sudden ranking drop that untracked redesigns cause.
Performance and accessibility debt addressed in the rebuild, not hidden under new visuals.
A documented benchmark means you can see exactly what improved and by how much.
Structure and content updated to reflect current offerings, not what the business looked like when the old site launched.
Why D2S
Industries
FAQ
Not if it's planned properly. Most ranking loss during redesigns comes from missed redirects or rewritten content on pages that were already performing — our audit-first process is built to catch both before launch.
The pre-redesign audit tells us which pages, URLs and content are actually earning traffic or conversions, and those get preserved or carefully migrated rather than redesigned away by default.
Yes, redesigns can be visual-only within your existing CMS, or include a platform change if the current one is limiting you — we'll scope this based on the audit.
It depends on site size and whether it includes a platform migration; a mid-size business site typically takes 6-10 weeks including the audit phase.
Yes, we benchmark rankings, traffic, conversion rate and Core Web Vitals before launch and report against them after.
Keep exploring
Let's audit what's working before we touch anything.