How editions drift apart
Drift starts with a difference in speed. The source team edits the source whenever something changes: a price, a feature, a claim, a better sentence. The localised editions change only when a job is commissioned, reviewed and published, which takes longer and needs someone to start it. Each source edit that is not sent on widens the gap, and after a few months nobody can say with confidence what each edition says.
The guide to updating and correcting content sorts changes into four kinds for one language: a slip, a substantive update, a correction and a withdrawal. Every one of those has a localised shadow. A correction made in the source but not in the editions is a correction made for one market only. A withdrawal in the source that leaves the editions standing keeps the withdrawn content live where the source team no longer looks.
Drift has three consequences. The edition tells its market something that is no longer true, which is the most serious. The edition's search signals fall out of step with the other editions, which the troubleshooting page on the wrong country version ranking traces to locale signals that disagree. And the cost of catching up grows, because a large batch of accumulated changes is harder to brief and review than a steady flow.
Knowing which editions a change touches
The foundation is a record that links every source page or asset to its localised editions: the source URL or asset, each edition's URL or asset, the date each edition was last brought in step and the version of the source it reflects. The hreflang guide recommends a locale map in the content system for generating hreflangAnnotation for language/region versions. at scale, and the same map serves this purpose: for each content item, where it exists in each locale.
Then log every source change against that record. The change log the updating guide asks for, with what changed, why, who and when, gains one field: which editions carry this page. A change to a page that exists in three editions creates three pending updates. A change to a page that exists only in the source creates none, which is also worth knowing.
Some changes do not touch pages directly. A change in the editorial style guide, a renamed product or a retired claim affects many pages at once. Those are logged as changes to the reference files, the Editorial Style GuideThe house rules a writer checks while drafting, so spelling, names, numbers, formatting, links and sources are handled the same way by everyone., the termbaseA record of the approved translation of each product, feature and brand term per language, with terms not to translate, definitions and rejected alternatives. or the claims library, and the record shows every edition that uses them.
Triage: what changes everywhere at once
Not every change is urgent, and treating every edit as urgent overwhelms the reviewers. Triage each change by what a stale edition would tell its market.
| Kind of change | Example | What a stale edition would do | How it travels |
|---|---|---|---|
| Price or offer | A price rise, a discount ending, a changed delivery charge | Tell the market a price or offer that no longer applies | Every edition at once, with the market owner's sign-off |
| Claim | A claim withdrawn, qualified or newly approved | Carry a claim the business no longer stands behind | Every edition at once, through the claims library and compliance |
| Legal text | Terms, privacy or cookie wording changed | Show legal text that is out of date | Every edition at once, through local legal review |
| Safety | A warning, an instruction or a usage limit changed | Leave customers with an old safety instruction | Every edition at once, treated as the highest priority |
| Product fact | A specification, size or feature changed | Describe a product that no longer exists in that form | Next scheduled batch, or at once if customers would act on it |
| Copy refresh | Better wording, new examples, a restructured section | Read a little older than the source | Batched on a regular cycle |
| Slip | A typo or a formatting fix in the source | Nothing different for the reader | Only if the edition has the same slip |
This guide gives no rule of consumer law. Price, claim, legal and safety changes are urgent because a stale edition would tell a market something no longer true, and the claims library and legal review own the substance of each. The localisation workflow's job is to make sure the approved change reaches every edition, together. The academy checkpoint on localised editions, rollouts and PR across countries tests which changes go everywhere at once, how editions drift and how pages are retired across them.
Updating in step: one change, every edition
An urgent change goes out as one job to every edition that carries it, with the same brief, the approved source wording and the deadline. Each edition's in-country reviewer signs off its language, as the translation and transcreation guide sets out, and the change is published in every edition before it is closed. The record then shows every edition in step with the new source version.
The approved change also goes into the reference files, so it travels to the next job. A new or changed term goes into the termbase; the new approved sentences go into the translation memoryA record, kept by the business, of each source sentence or segment and the translation a reviewer approved for it, so repeated wording comes back the same way., replacing the old ones. The tutorial on building a termbase and translation memory explains why: a memory that still holds the old price line or the withdrawn claim will offer it back to the next translator.
Batched changes follow the same route on a regular cycle that the market owner and the reviewers agree. Batching saves review effort, because a reviewer reading several related changes on one page works faster than one reading them across separate jobs. A RACI matrix names who is accountable for each edition being in step, who triages, who briefs and who reviews.
Content that exists only in one market
Not every page has a source. Some pages are created locally because the market needs them: a page about a local payment option, a local partner or a local regulation, as the localising websites and campaigns guide describes. Some source pages were deliberately left out of an edition, which the tutorial on deciding which content to localise first records.
Both belong in the record. Local-only pages have an owner in the market, a review date in the content governance cycle and no source to follow, so drift checks look at them against the market's facts rather than against the source. Pages excluded from an edition are noted so that a source change to them creates no pending update, and so that the next scoping review can see what the edition still lacks.
Retiring and replacing pages across editions
A page retired in the source is usually retired in every edition, at the same time. The tutorial on withdrawing an asset from every channel covers finding every use of an asset and removing it; for localised pages, the extra rule is the alternates set.
The hreflang guide, drawing on Google Search Central's documentation on telling Google about localized versions of a page, states that annotations must be reciprocal, that each edition must be its own canonical (Canonical TagTells search engines the preferred URL.), and that a group should not point at a page that does not exist or redirects. So when a page is retired in one edition, it has to leave every other edition's alternates in the same release. When a retired page is redirected with a 301 RedirectA permanent server redirect telling browsers and search engines a URL has moved for good. to a replacement, the hreflang set is updated to the replacement's final URLs, not left pointing at the redirected address; the hreflang guide makes the same point for migrations, where the set is regenerated rather than redirected.
Each edition stays in one language, navigation and content alike, as the international SEO section states Google Search Central's guidance. A source page replaced by a new one does not leave an edition with a source-language page in its place while the translation is waiting. Either the edition keeps its existing page until the replacement is localised, or the page is retired in that edition and added back when the localised replacement is ready.
Drift checks and who owns them
Even with a change log, editions drift. Run drift checks on a regular cycle and after any large source change:
- Compare each edition's record with the source version. Any edition behind the current source for a page is listed with how long it has been behind.
- Read the high-risk lines. Prices, claims, legal text and safety lines in each edition are compared with the current approved versions, through a back-translationA translation of the target-language version back into the source language, made to check what risky lines say; it shows meaning, not how the text reads. where the checker does not read the language.
- Check the alternates. Every live page appears in the alternates of every edition it should, and none points at a retired or redirected page.
- Look at local-only pages. Each has an owner and a current review date.
The drift check has one named owner, usually the localisation owner, with each market's reviewer checking their edition's high-risk lines. Results go into the record, and anything found behind on a price, claim, legal or safety line is treated as an urgent change from that moment. If launches slip at the localisation step every time, the diagnosis page on localisation delaying every launch checks whether untriaged changes are the queue the reviewers are stuck behind, beside the other constraints a launch can wait on. To review drift alongside calendars, rollouts, prices and reporting across every live market, the multi-market marketing audit scorecard scores whether source changes reach every edition as a gate and ranks the fixes.
A camping stove maker catches a stale safety line (illustrative)
Toskwen Stoves catches a stale warning in Market B
Toskwen Stoves, an invented maker of camping stoves, has editions for Market A and Market B. In one week it changes a fuel-canister warning on 6 product pages and raises the prices of 2 stoves in the source edition.
Its change log links each source page to its editions, so the 8 changes create 16 pending updates. The warning and price changes are triaged as urgent. Market A's reviewer signs off within the week and the edition is published. The weekly drift check then shows Market B still carrying the old warning on 4 of the 6 pages: the job had gone to Market B's supplier without the urgent flag and been queued behind a copy refresh.
The localisation owner sends the warning and price changes to Market B as a separate job the same day, with the reviewer's sign-off, and adds the new warning to the translation memory in both languages, replacing the old line. The copy refresh of 22 product descriptions is batched for the end of the month.
The same month a discontinued stove is retired. Its page is removed from the source and from both editions in one release, and its alternates are taken out of the hreflang annotations of all three editions together, with each edition's page redirected to its own edition's replacement model.
Common mistakes
- No link between source and editions. Without the record, nobody knows which editions a change touches.
- Treating every change as urgent. The reviewers drown and urgent changes queue behind refreshes. Triage by what a stale edition would tell its market.
- Updating prices and claims one market at a time. Price, claim, legal and safety changes go to every edition together.
- Fixing the asset but not the memory. The old line comes back on the next job. Update the termbase and translation memory.
- Retiring a page in one edition only. The other editions still list it as an alternate. Retire it everywhere in one release, with the alternates removed together.
- Filling a gap with the source-language page. Each edition stays in one language. Keep the old localised page or retire it until the replacement is ready.
- Drift checks with no owner. Name the owner and the cycle, and treat anything behind on a high-risk line as urgent.
The marketing localisation hub shows where upkeep sits in the language and asset workflows.
