Digital Visibility
Protecting search visibility through a replatform, redesign, domain change or restructure. The work happens before launch; after it, options narrow to recovery.
Stated as we hear it, before any mention of what we would do about it.
Qualitative, because we do not publish numbers we cannot evidence.
Approach
Runs alongside the build; typically engaged from design freeze through the first quarter after launch.
Captured before the new site exists. Building this afterwards is materially harder and usually incomplete.
Before design freezeEach URL to a destination: kept, redirected once, or retired with a clean 410. Chains, loops and blanket homepage redirects cause most migration damage.
During buildParity of content and rendering on staging, against the inventory. This is where a template that trims 700 words gets caught.
Pre-launchIndex coverage, redirect resolution and priority rankings: daily for two weeks, weekly for a quarter, because effects lag the change.
Post-launchScope
Stated plainly, so there is no ambiguity about what you are buying.
How it works
A process before and after automation
Before: five steps, four of them manual. After: the same outcome with one human decision point and a defined exception path for when the system is unsure.
The boundary
Naming the boundary early removes the most common source of disappointment in an engagement.
Before the information architecture is signed off. Involved at that point, most migration risk is designed out; involved at launch, the work is limited to redirects and the damage from template and rendering decisions is already fixed.
It depends on the cause. A missing redirect map corrected within days usually recovers in weeks. Lost content depth or a rendering change takes a quarter or more, because the pages have to re-earn their position.
Protecting search visibility through a replatform, redesign, domain change or restructure. The work happens before launch; after it, options narrow to recovery.
Teams mid-way through a redesign or replatform; Businesses consolidating multiple sites or changing domain; and Organisations that lost visibility in a previous migration
Pre-migration inventory of every indexable URL with its traffic, links and rankings; URL mapping to destinations, reviewed page by page for the pages that matter; Content parity checks so ranking pages are not trimmed to fit a template; Rendering parity checks, because a move to client-side rendering loses visibility no redirect can restore; Launch-day verification and staged rollout where the site allows it; and Post-launch monitoring across the recovery window, not just the first week
A replatform is scheduled and nobody owns what happens to search visibility; A previous migration lost traffic that never fully returned; and Two sites are merging and no one has decided what happens to the retiring one
Every valuable URL either kept, redirected in one hop, or retired deliberately; Content and rendering parity verified before launch rather than diagnosed after; and A monitored launch with a rollback path and a known recovery window
Runs alongside the build; typically engaged from design freeze through the first quarter after launch.
Connected
Describe where the work currently is and what it has to achieve commercially. We will tell you what we would scope, what we would leave alone, and whether this is the right service to be buying first.
