# SEO site migration: what to check before and after

> Prepare URL equivalents, rehearsals and follow-up through a worked migration map, without promising unchanged rankings.


**A site migration involving URL changes moves content to new addresses and requires a meaningful relationship between old pages and their replacements.** It may accompany a domain or structural change. Changing CMS while keeping addresses involves other checks; this article’s map focuses on URL moves.

Google documents [preparation, execution and monitoring](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) for these moves. Search visibility can fluctuate while the change is processed. A sound map reduces avoidable errors; it does not guarantee unchanged rankings or traffic.

## Four pages that should not share one rule

This case is fictional. A studio reorganizes its class pages, keeps its contact page and retires an activity it no longer offers. Before configuring redirects, it decides:

| Old URL | Situation | Expected result |
| --- | --- | --- |
| `/beginner-class/` | Same class moves to `/workshops/beginner-pottery/` | 301 to its equivalent, then 200 with the complete class page |
| `/advanced-class/` | Moves to `/workshops/advanced-pottery/` | 301 to its equivalent, then 200 showing the correct level |
| `/contact/` | Unchanged | 200 at the existing address |
| `/old-event/` | Retired without a relevant replacement | 404 without a homepage redirect |

The [migration-map CSV](/resources/site-migration-map-en.csv) retains all four decisions, expected content and a follow-up check for each row. They are teaching scenarios; listed statuses are targets, rather than results from an executed deployment.

## Before opening the new site

Inventory existing pages and identify those receiving traffic, links or bookings so their destinations receive particular attention. Map equivalents by content. Matching slugs can help suggest pairs, but cannot establish that a beginner and advanced class are substitutes.

Rehearse initial and final responses. In this scenario, a broad rule sends both classes to the beginner page. The destination returns 200 and the homepage looks good, but the migration is not ready: someone looking for advanced tuition receives a different offer. Fix that row before opening the new routes.

Update internal links, canonical declarations and the sitemap to use current destinations. Ensure temporary testing restrictions do not reach production accidentally. Establish who decides when to launch and which defects require stopping or reversing the change. Agree on that operational decision before discovering a production failure.

## After launch, test the old addresses

Opening only the new class pages misses half the move. Request every old address and check the initial status, final destination and content visitors receive. Include `/contact/`: that row detects rules affecting pages intended to remain unchanged.

When changing domains or subdomains, assess whether Search Console’s Change of Address tool applies. Google does not require it for path changes within one domain or HTTP-to-HTTPS moves. Do not automatically add it to every migration.

Google recommends keeping redirects as long as possible, generally for at least a year; retaining them longer may help visitors following old links. Updating your own links reduces dependence on those hops. The [301 and 302 explanation](/en/guides/301-redirect/) helps assess the chosen response.

## Separate migration defects from search changes

Record launch time and monitor relevant properties or paths in Search Console alongside server responses and destinations. An accidental 404 on the advanced class is a reproducible defect. A click decline also requires examining impressions, queries, periods and other changes. Follow-up should distinguish those cases, rather than labeling every website that loads a successful migration.

## Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.

[Start free](https://app.heymark.ai) · [See how it works](https://heymark.ai/en/#product)

## Developer and agent resources

- [HeyMark MCP documentation](https://heymark.ai/en/mcp/)
- [llms.txt](https://heymark.ai/llms.txt)
- [Full site content for language models](https://heymark.ai/llms-full.txt)
- MCP protocol endpoint: `POST https://mcp.heymark.ai`
- OAuth protected-resource metadata: [/.well-known/oauth-protected-resource](https://mcp.heymark.ai/.well-known/oauth-protected-resource)
- MCP server card: [/server-card](https://mcp.heymark.ai/server-card)
