The Internal Model We Use to Decide What Gets Kept
This is the actual decision framework behind every audit, laid out here so it isn't a mystery to the teams we work with.
Consolidation Shouldn't Feel Like a Black Box
A lot of migration work gets treated as a technical formality, something handed to a developer with a spreadsheet of old URLs and new ones. We think the decisions behind that spreadsheet matter more than the spreadsheet itself.
The framework below is the same one we walk clients through during an engagement. It's not proprietary in the sense of being secret. It's proprietary in the sense that we've refined it across enough fragmented content ecosystems to know where it tends to break down if steps get skipped.
Five Phases, Each With a Specific Question to Answer
Phase One Discovery
Question: What actually exists, and where?
We crawl every domain, pull whatever historical data access allows, and produce a raw inventory before forming any opinion about what should happen to it. Skipping this step is the most common reason consolidation projects run into surprises later.
Phase Two Equity Mapping
Question: What is each page actually worth in search?
Traffic alone is a weak signal. We weigh backlink profile, ranking depth across a spread of keywords, and engagement pattern together to score each URL's real standing, not just its recent numbers.
Phase Three Decision Assignment
Question: Merge, redirect, or retire?
Every URL gets assigned one of three outcomes, with a documented reason. Pages with unique value but weak individual traffic are frequently merged into a stronger equivalent rather than deleted outright.
Phase Four Structural Rebuild
Question: What should the new architecture actually look like?
Taxonomy, navigation, and internal linking get rebuilt around the consolidated content, not retrofitted onto whatever structure happened to survive the merge.
Phase Five Monitoring & Adjustment
Question: Is it behaving the way the plan predicted?
Crawl behavior, index coverage, and ranking trend get tracked closely for a period after launch, with adjustments made if something isn't resolving the way the equity mapping suggested it would.
Questions We Hear Early in an Engagement
How long does a full consolidation usually take?
It depends heavily on the number of URLs involved and how much overlap exists between properties. Discovery alone can take longer on large catalogs, while the redirect and technical phases tend to move faster once decisions are finalized.
Do you need admin access to both websites?
Access to analytics, search console, and the content management system speeds up discovery considerably. Where access is limited, we rely more heavily on crawl data and third-party backlink tools instead.
What happens if a redirect doesn't behave as expected after launch?
This is exactly what the monitoring phase is built to catch. We review crawl and index reports on a set schedule after go-live and adjust mappings if something isn't resolving cleanly.
Can this framework apply to more than two merged domains?
Yes. The equity mapping and decision assignment phases scale to multiple properties, though discovery takes proportionally longer as more domains and CMS platforms are involved.