URL inventory
For SEO migrations, we start by reviewing url inventory. We identify what already works and which decisions your team needs to make.
Protect important search signals during a site move.
A new website can change the URLs customers and search engines already know. Planning redirects, content and post-launch checks helps preserve the useful connections during the move.
0207 183 9270A new website can change the URLs customers and search engines already know. Planning redirects, content and post-launch checks helps preserve the useful connections during the move.
Useful search work joins technical health with content that answers real questions. We establish what can be measured and keep priorities focused on the pages and enquiries that matter to the business.

For SEO migrations, we start by reviewing url inventory. We identify what already works and which decisions your team needs to make.
We agree how redirect mapping will fit the people and tools involved. Dependencies are reviewed before the implementation is scheduled.
We check launch checks in a realistic working journey. The result records any limitations and the person responsible for follow-up.
Agree how the item or order is recorded and updated through the operation. The rules should explain what is available, what has changed and which person handles the next step.
Prepare the working detail for review, with time to ask questions and resolve assumptions.
Give the change a repeatable route to production. We agree the checks, timing and responsibility for updates, with a practical handover for the person maintaining the result.
Make the state of the work visible and give important failures an owner. We agree which events need attention, how they are reported and what information the responder should receive.
The url inventory stage provides the agreed starting information for redirect mapping. The owner checks this step before the work moves on.
The redirect mapping stage provides the agreed starting information for launch checks. The owner checks this step before the work moves on.
The launch checks stage provides the agreed starting information for post-launch monitoring. The owner checks this step before the work moves on.
The post-launch monitoring stage forms part of the final handover. The owner checks this step before the work moves on.
Discuss the real task, existing systems and constraints. Record what success looks like before choosing a solution.
Review the structure and agree the scope, responsibilities and acceptance examples. Set a realistic sequence for delivery.
Build the agreed work in reviewable stages. Check the important details with your team and explain decisions as they are made.
Test the finished journeys, agree the launch and explain ownership. Discuss ongoing support separately from the initial build.
Useful search work joins technical health with content that answers real questions. We establish what can be measured and keep priorities focused on the pages and enquiries that matter to the business.
Platform choices follow the requirements. We review existing accounts, data formats and supplier agreements before proposing replacements or additional subscriptions.
Access should match the task. Your business keeps ownership of its accounts and records.
Map each important old address to its intended replacement before launch. Test redirects, canonical URLs and internal links, then monitor the new site for missing pages and indexing changes after the move.
Your project uses examples agreed with your team. This scenario explains the checks to consider; it is not a completed client case study.
We review access requirements and keep permissions aligned with the responsibilities of each role.
Important journeys are checked with realistic data and a range of expected and unexpected inputs.
The people using and maintaining the result are involved before handover, with time for questions and training.
Choose the level of work that fits your goal. We confirm the price after reviewing the requirements and list recurring and third-party costs separately.
You do not need a finished specification. A real example, a clear goal and someone who knows the current process are enough to begin.
Sample perspectives for this service. Verified client testimonials will replace these with permission.
“We wanted url inventory explained clearly, so everyone knew what the project needed to achieve.”
Business owner · sample perspective
“Having redirect mapping agreed before delivery made it easier for our team to review the work and ask the right questions.”
Project lead · sample perspective
We start with url inventory, then agree what redirect mapping needs to cover. A real example from your business helps us define the work accurately.
Your proposal sets out url inventory, redirect mapping, launch checks, post-launch monitoring. The handover records the agreed setup, the checks completed and the responsibilities that remain with your team.
We review the tools and access available before promising a connection. Where an integration is limited, we explain the options and any manual steps that remain.
We quote for the agreed deliverables, complexity and support needs. Hosting, subscriptions, advertising spend and third-party charges are identified separately.
No. Rankings depend on competition, search engines and many factors outside one supplier’s control. We agree useful measures and report progress without promising a particular position.
We explain the handover and maintenance needs. Ongoing support is a separate agreed scope with clear responsibilities and a review schedule.
Tell us what you want to improve, what you use today and any deadline you need us to consider.