Content strategy · Enterprise migration
What should move to the new site?
I led a content inventory covering hundreds of URLs for a multi-location hospitality organization preparing for a CMS migration.
Deliverables
Content audit · Inventory
Every URL, with a decision
Scroll sideways to see all columns
| Page | Decision | Rationale | Proposed destination |
|---|---|---|---|
Locations directory /locations/ | Keep | Core page with a clear job and no overlapping page. | Existing URL |
Duplicate news archive /archive/news/ | Retire | Empty archive that duplicates the main newsroom. | /newsroom/ |
Shared promotion /offers/seasonal-7/ | Consolidate | Combine local copies once participating locations confirm their terms. | /offers/seasonal/ |
Dining venue /dining/restaurant/ | Improve | The venue was excluded from search indexing. Move it and make it indexable. | /locations/resort-a/dining/restaurant/ |
Executive readout · Slide excerpt
What the analytics changed
- Most of the plan holds
- Pages proposed for merging, archiving, or removal accounted for under 1% of page views in the analysis.
- Some pages need confirmation
- Several candidates still drew meaningful traffic. The plan flagged them for a review of search clicks and inbound links.
- A recommendation changed
- A frequently used how-to page had originally been proposed for consolidation. The updated plan kept its existing address.
- Still needed
- Search Console evidence and access to the analytics account that tracks booking.
Content audit · Information architecture
One property model, applied to every property
Before
- Some locations had full site sections while others had one long page.
- A separate site held venue, event, and newsroom content for one location.
- Recurring offers accumulated separate URLs.
Proposed
- Give locations a shared structure, with rooms, dining, and venues where relevant.
- Bring the separate property into the main site and map its pages individually.
- Give each recurring offer a permanent URL.
Content audit · Redirect strategy
Every removal has somewhere to go
Scroll sideways to see all columns
| Old address | Proposed destination | Rule | When |
|---|---|---|---|
/archive/news/ | /newsroom/ | 301 to the surviving news index. | Cleanup |
/offers/seasonal-7/ | /offers/seasonal/ | 301 to the consolidated offer once terms are confirmed. | At launch |
old-site.example/dining/restaurant/ | /locations/resort-a/dining/restaurant/ | 301 directly to the replacement venue page. | At launch |
Use the closest relevant destination. Update internal links and point old redirects directly to the final URL.
Excerpts adapted from the content audit and executive readout. Identifying details have been removed or replaced.
Case study
The decision
The migration forced a decision about every page. Which ones should stay, change, merge, or come down? The team also needed to make it easier for guests to explore options across locations and keep people who arrived from a local campaign oriented to that location.
My role
I owned the inventory from start to finish. I used AI throughout the work and was responsible for the final recommendations, which drew on a review of the live sites, traffic data, and stakeholder input.
What the analytics changed
Most pages I proposed merging, archiving, or retiring accounted for a small share of visits. A frequently used help page was an exception. I recommended keeping its existing URL and flagged other pages for a review of search traffic and inbound links before retirement.
What the team could act on
I delivered a page-by-page inventory and a proposed redirect plan. The team could use them to identify fixes for the live site, schedule structural changes for launch, and see which decisions still needed input from marketing, SEO, compliance, or IT.