TECHNICAL / SERVICE SCOPE
SEO migration.
Make URL changes reviewable before launch. Map old pages to intended destinations and keep a release checklist and recovery decision ready.
Explore the scope ↓- Best starting point
- A domain, CMS, store platform or URL structure is changing and existing search entry points need to be preserved.
- Working artifact
- Old URL, New URL and the fields shown below.
- How to evaluate
- Check the output, implementation owner and acceptance evidence.
What the scope produces
- An old-to-new URL map with an explicit disposition for retired pages
- Checks for redirects, canonical URLs and internal links
- A pre-launch inventory of important landing pages
- A post-launch monitoring and recovery checklist
What the work needs
Old and new URL inventories, a working preview, platform access and the planned release window.
A sample working artifact
Illustrative structure, not a client result. A completed record should make the work and its verification clear.
- Old URL
- A specific value recorded for the engagement.
- New URL
- A specific value recorded for the engagement.
- Disposition
- A specific value recorded for the engagement.
- Expected status
- A specific value recorded for the engagement.
- Redirect check
- A specific value recorded for the engagement.
- Page check
- A specific value recorded for the engagement.
How the work moves forward
Map the destinations
Match pages by their purpose. Do not send every removed URL to the homepage.
Check the preview
Verify the new templates, navigation and page signals before traffic is routed to them.
Monitor the move
Inspect important old and new URLs after launch. Record defects and the decision needed to correct them.
Scope boundaries
A migration may involve temporary search fluctuations. Keeping redirects correct does not guarantee an unchanged position.