Decide which changes pause during migration
A content freeze is a coordination rule, not a technical lock or a claim that the business stops operating. Product stock, orders and essential corrections may need separate handling. The useful boundary is the exact content or system being transferred and the point at which later changes must be reconciled.
Illustrative cutover log:
| Change | Source | Action before release |
|---|---|---|
| Corrected opening hours | Approved editor update | Copy to the candidate and verify |
| New collection paragraph | Deferred draft | Schedule after acceptance |
Illustrative editor message: “Page-copy changes pause after the agreed snapshot. Send urgent corrections to the named release owner with the page URL and replacement text; that owner records and reconciles each exception.” The message needs real names and dates before use.
Record emergency edits for reconciliation
A freeze does not create a backup, synchronize data or authorize publication. Unlogged exceptions can make the candidate stale even when the original snapshot was correct. Google’s migration guidance supports careful preparation; this change-control template is an original operating example, not a Google requirement.
Next, define the frozen scope, exception owner and final reconciliation check. Compare both versions after the last approved correction, then record who may lift the freeze once release acceptance is complete.
Website field guide · Website content migration services · Staging site
Reference: Google Search Central: preparing a site move. Checked November 4, 2026.