Know which pages matter before the move.
Export a baseline from your analytics and Search Console. Identify landing pages that bring relevant visitors or conversions, not just the pages with the most impressions. Keep the date range and any seasonal context with the export.
Build a review list combining those pages with your sitemap and important externally linked resources. Include older articles and downloads that are easy to overlook when reviewing the navigation.
Review each important page as a whole.
For each page in your review set, compare the source and replacement. The example checks below are useful even when the domain and path are staying the same.
| Check | What a useful comparison establishes |
|---|---|
| Content and purpose | The page still answers the same need and retains important text, media, headings, and links. |
| Address and response | The intended page opens at its expected address rather than returning an error or unrelated content. |
| Title and description | The intended metadata is present in the delivered page, not only stored in an editor. |
| Canonical and indexability | The live page identifies the intended public URL and has no accidental preview noindex setting. |
| Internal links and discovery | Navigation, article links, archives, and the sitemap lead to the intended public pages. |
| Structured information | Relevant structured data is reviewed for accuracy and duplication where the site uses it. |
Keep the scope of change understandable.
A CMS change, a new domain, a rewrite of the content, and a full redesign introduce different variables. Plan the sequence so you can diagnose a problem if results change.
For an OffPress preview, keep a separate list of intentional changes. If an article loses a section or a title changes unexpectedly, that should appear as a review issue rather than being hidden inside a broad redesign approval.
Check the production domain, not only the preview.
Review canonical URLs, sitemap entries, HTTPS, and indexability on the published domain. A preview that looks correct is not evidence that the domain configuration is complete.
When URLs must change, map each useful old destination to an appropriate new one and test the redirect. The companion URL guide includes a worked mapping example and common mistakes to avoid.
Measure after launch and investigate specifics.
Check important URLs and business conversions soon after the switch, then compare page-level search performance over time. A drop in form submissions may come from a broken form even when search traffic is stable.
Separate crawl or indexing problems from demand changes and ranking movement. Google notes that search rankings can fluctuate during a significant site move; treat the monitoring period as part of the migration rather than declaring success from a single day.
- Inspect unexpected missing pages or redirect destinations.
- Confirm that monitoring still measures the live domain.
- Review changes by landing page and relevant query group.
- Keep a dated record of fixes so you can interpret subsequent changes.