For the broader search framework, see search visibility and Answer Engine Optimization.
Overview
Start with the system,not another disconnected tactic.
A B2B technology company was preparing to move its website onto a new platform. The migration involved more than changing the content management system. It also created an opportunity to reconsider how the company, its products, its solutions and its expertise were represented across the website.
The existing site had accumulated overlapping pages, inconsistent terminology and several competing navigation paths. Search engines could crawl the website, but the relationships between the company, its product category, its capabilities, its audiences and its use cases were not always explicit.
The migration therefore needed to preserve existing search equity while rebuilding the website around a clearer information architecture—one that could support traditional search discovery and improve entity recognition across AI-powered search systems.
01
Business context
02
Search intent
03
Visibility system
04
Execution plan
The challenge
The migration risk was not only losing rankings. It was transferring structural ambiguity into the new platform.
Website migrations introduce technical risk even when the visible design changes very little. URLs can disappear, internal links can weaken, redirects can be mapped incorrectly and previously established relevance signals can become fragmented.
In this scenario, the structural problem went deeper. Years of content growth had produced multiple labels for similar capabilities, disconnected resource sections and pages that competed for the same intent. Moving that structure unchanged would carry its ambiguity into the new platform.
The migration needed to treat information architecture as part of the company’s search identity. Every important page required a defined purpose, an entity relationship and a clear place within the customer journey.
Search journey
Discover
What solutions exist for this problem?
Category, problem and educational content used inconsistent language, making topical relationships harder to interpret.
Evaluate
Can this platform support our requirements?
Product capabilities, industries and use cases were distributed across overlapping pages without a consistent hierarchy.
Validate
Is this company a credible choice?
Evidence, company information and expertise signals were not systematically connected to the claims they supported.
What matters most
The existing website described the business, but it did not consistently model how its entities were connected.
The taxonomy reflected publishing history
Sections had been added as new campaigns, products and content programs emerged, rather than according to one durable information model.
Priority action
Define a controlled taxonomy for company, product, capability, industry, use case, problem and resource entities.
Several URLs competed for the same intent
Pages with similar themes used different labels but addressed substantially overlapping customer questions.
Priority action
Assign one primary intent and one canonical destination to every strategically important topic.
Entity relationships were mostly implied
Visitors could infer how capabilities connected to products and use cases, but those relationships were not consistently expressed in navigation, copy or internal links.
Priority action
Create explicit connections between products, capabilities, audiences, problems, industries and supporting evidence.
Terminology changed between sections
The same capability appeared under multiple names, weakening consistency across product, solution and educational pages.
Priority action
Create a preferred entity vocabulary and apply it across headings, body copy, metadata, navigation and structured data.
Internal links followed page templates
Links were often determined by where content was published instead of the contextual relationship between topics.
Priority action
Rebuild internal linking around intent progression, semantic relevance and entity relationships.
Migration decisions were URL-led
The early migration plan focused on matching old URLs to new URLs without first deciding which pages should remain, merge or change purpose.
Priority action
Complete content consolidation and intent mapping before producing the final redirect plan.
Evidence was separated from claims
Case studies, product evidence and expertise content existed, but important commercial pages did not consistently connect to them.
Priority action
Link claims to relevant proof and place supporting evidence close to the decisions it helps users make.
The strategy
Use the migration to create an entity-led information architecture.
The strategy was to design the new website as an entity-led information system rather than a collection of pages. The company, platform, products, capabilities, industries, use cases and resources would each have a defined role and a consistent relationship to the others.
The new architecture would separate page purpose from page format. A product page, for example, would own product intent; capability pages would explain what the platform could do; use-case pages would connect capabilities to specific outcomes; and educational resources would support the questions surrounding those commercial topics.
Technical migration controls would then preserve the strongest existing signals. Every legacy URL would be classified, mapped to an appropriate destination and tested alongside canonicals, internal links, metadata, structured data and indexation directives before launch.
Before
Connected system
Execution roadmap
Put the work in the right order.
Model the entities
Inventory existing URLs and content
Identify core business and topic entities
Define preferred names and relationships
Map search intent to canonical destinations
Rebuild the architecture
Create the new taxonomy and hierarchy
Consolidate overlapping page purposes
Design contextual internal link paths
Align navigation with customer research
Migrate and validate
Implement and test redirect mappings
Validate canonicals and indexation signals
Check structured data and entity consistency
Monitor search coverage after launch
What improvement looks like
Measure whether the system is becoming stronger.
Lower migration risk
Every valuable legacy URL has a documented destination, purpose and validation requirement before launch.
Clearer entity recognition
Consistent terminology and explicit relationships make the company, platform and capabilities easier for search systems to interpret.
Stronger intent ownership
Important topics have one primary destination instead of being divided across competing pages.
More useful internal linking
Links help users and crawlers move between problems, capabilities, use cases, evidence and commercial destinations.
Better AI-search readiness
Clear definitions, relationships and evidence give answer engines more structured material to interpret and reference.
A scalable content model
New products, industries and resources can be added without recreating the structural ambiguity of the previous website.
Key takeaway
A successful platform migration should preserve more than URLs and rankings. It should leave the website with a clearer model of the business—one that helps customers, Google and AI-powered search systems understand what the company is, what it offers and why its information is relevant.
Continue exploring
Related insights
Insight
How to Do a DIY AEO Audit (And What a Tool Catches That You Won’t)
Learn how to run a practical AEO audit yourself, what to inspect across your website and AI search presence, and where manual analysis starts to miss important patterns.
Read the insight →Case study
Knowledge Base Optimization: Ungating Core Documentation to Achieve 85% Google AIO Inclusion
An illustrative strategy showing how a B2B software company could make core documentation publicly accessible, improve machine readability and reach Google AI Overview inclusion across 17 of 20 tracked query groups.
See the case study →Insight
Entity SEO & the Knowledge Graph: How AI Actually Understands Your Brand
Learn how entity clarity, structured data, consistent business information, relationships and third-party corroboration help search and AI systems understand what your brand actually is.
Read the insight →