First, settle which version is true and list every place the fact appears
A customer quotes a blog post's price that the plans page contradicts, or a support agent finds help pages describing steps the product no longer has. Hold off fixing whichever page looks wrong until two things are settled.
Which version is true now. Ask whoever owns the fact: the person who sets prices, the product team for steps and features, whoever approved an eligibility rule. Record the answer and its date. Never assume the newest page is right: it may have been written from an old brief or an AI draft, while the older page may be the one already corrected. Sometimes neither is current.
Every place the fact appears, not only the two pages someone noticed. Search the site for the fact, its old values and the wording around it, then work through the places a site search does not reach.
| Where the fact can sit | How to find it | What to record |
|---|---|---|
| Pages on the site | Site search; the content inventoryA record of every published content page with its owner, review date, audit decision and changes, kept so the next review knows what exists and what happened. | Owner, version shown, last change |
| Derivatives | The derivatives recorded against each source | Channel, and whether it can be edited |
| Newsletters and automated emails | Send archives and live automations | Which are still sending |
| Partner and syndicated copies | Agreements and partner contacts | Who can change the copy |
| Downloadable files | Files linked from pages or sent by sales and support | The version each was exported from |
| Translated editions | The record linking source pages to editions | The source version each reflects |
The dates often tell the story: a fact changed on a known day, some pages followed that week, and copies kept the earlier value. The content inventory and audit template gives the page columns, including overlap and change record fields, and the guide to repurposing content records each derivative against its source.
A reader holding two answers cannot tell which one the business stands behind. Google's helpful content guidance asks whether content is accurate and a site trustworthy, and the E-E-A-T guide reports that the rater guidelines treat trust as the most important quality and that a page with experience, expertise and authority can still be untrustworthy if it is inaccurate.
Then walk one contradiction back with the five whys. The brochure showed the old price: why? It was exported before the change. Why was it not updated? Nobody changing the price knew it carried one. Why not? Nothing records where the price appears. Stop at the first answer naming a missing record, check or rule rather than a person; the table below sorts it. Two jobs sit elsewhere: a wrong version in a live ad or landing page is contained first with the live ad and page error response SOP, and what to tell readers who acted on it is answered by the guide to updating and correcting published content, linked under the correction cause below.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Two pages answer one question differently | The inventory's overlap field | A newer page answered a question the library already answered, and nobody compared the two | Consolidate into the stronger page and redirect the other |
| The main page is current; articles or files are not | When the fact changed against each page's last change | A fact changed, such as a price, a plan, a rule or a specification, and only the pages someone remembered were updated | List every place the fact is used, update all of them, keep the list |
| Older pages use a name the plan no longer has | A search for the old name | A renamed product, plan or feature that older pages still call by its old name | Mark the name retired; correct pages where it misleads |
| The page is corrected; a copy still has the error | The copies recorded against the page | A correction made on the page but not in its copies: derivatives, newsletters, partner copies and downloadable files | Carry the correction to every copy, or withdraw it |
| An ended offer page shows old terms | Whether pages with end dates say they ended | Expired offer, event or campaign pages still live with old terms | Mark as ended, redirect to the equivalent or remove |
| The source is right; an edition in another language is not | The source version each edition reflects | A translated edition left behind when the source page changed | Bring the edition in step; log changes against every edition |
| The wrong version is in pages drafted with AI help | The draft's sources and its fact check | AI-assisted drafts restating outdated or invented facts that review did not catch | Trace every fact to a current source and review again |
Fix, verify and prevent each cause
A newer page answering a question the library already answered
A writer researches a question afresh without knowing an older page gave a different answer. The content governance guide handles this in the audit, where a read for accuracy and duplication ends in a decision per page, and treats consolidation as the usual cure when a library holds "two answers to one question".
Fix: agree the right answer with the fact's owner, choose the page with the stronger history and fit, merge the useful material into it and redirect the other address to the survivor. Where the pages also compete for searches, the guide to keyword cannibalization covers the search side, and cannibalizationTwo or more pages on one site competing for the same query and intent, splitting signals. showing up first as a slow loss of visitors belongs to the diagnosis of old content losing traffic.
Verify: a site search for the question returns one page, and the old address redirects.
Prevent: search the inventory for an existing answer before every brief; the content brief tutorial already names the single question each piece answers, so the check is one search.
A fact that changed in one place
A price, rule or specification changes, and the pages repeating it follow only if someone knows they exist. The tutorial on building a claims library solves this for marketing claims: each entry holds the approved wording, a recheck date and a "used in" field listing the assets that carry it, so a claim that stops holding can be retired and found wherever it runs.
Fix: turn the search from the first section into the fact's "used in" list, update everything on it and keep it. A claim in that tutorial's sense belongs in the claims libraryA record of every marketing claim in its exact approved wording, with the evidence behind it, the conditions and markets it is approved for and the approver.; price and reference-price claims, which that tutorial leaves to promotion review, and facts such as terms or eligibility rules need the same owner and list in a record beside it.
Verify: a search for the old value finds nothing, and every entry on the list shows the owner's current version.
Prevent: make working through the list part of the change, so a price is not changed until every page, file and copy on its list has been.
An old name that older pages still use
A renamed plan keeps its old name in older articles, and readers assume two plans. The tutorial on writing an editorial style guide has the guide list each old name, flagged as no longer in use, next to the name that replaced it, which gives a reviewer something to search old pages for. It also sets two speeds: pages breaking a changed rule are corrected at their next review, unless the old wording misleads readers, when they are fixed at once as a correction. A name that sends readers looking for a vanished plan misleads.
Fix: add the old name to the style guideThe house rules a writer checks while drafting, so spelling, names, numbers, formatting, links and sources are handled the same way by everyone. as retired, search for it and correct every page where it misleads. For a whole new business or product line name, the guide to rolling out a rebrand inventories every surface carrying the old one.
Verify: the retired name appears only where it is mentioned on purpose.
Prevent: the product team tells the style guide's owner the day a name changes, and each retired name joins the searches run at review.
A correction that stopped at the page
A page corrected openly can leave the error alive in its copies: the newsletter that quoted it, derivatives cut from it, a partner's syndicated version, a file exported before the fix. The guide to updating and correcting published content treats fixing the copies as part of an open correction, with correcting the error where people saw it.
Fix: work through every copy recorded against the page and correct it; where a copy cannot change, such as a sent email, follow that guide on reaching the people who met it, and replace any file still offered for download.
Verify: every copy shows the corrected version or is withdrawn, and the change record names each.
Prevent: add a "copies corrected" line to every correction's change record, and treat a correction without it as open.
An ended offer, event or campaign page still live
An offer or event page outlives its end date, and old links bring readers to its terms beside the current offer. The guide to expired pages sets out the honest options: keep the page with a clear ended notice and a next step, keep it for people following old links while noindexing it, point it with a permanent redirect at its replacement, or take it down, decided before pages expire rather than when someone notices.
Fix: apply the guide's default for each ended page; for a time-limited offer that is a redirect to the offer's stable page, or removal.
Verify: no ended page presents old terms as current.
Prevent: record each page's end date and expiry decision in the inventory when it is published.
A translated edition left behind
Localised editionsOne market's version of a site, email or campaign, adapted from a source edition and kept in step with it as prices, claims and pages change. change only when somebody starts the job, so every source edit not sent on widens the gap. The guide to keeping localised content in step links each source page to its editions, logs every source change against the editions it touches, and ranks each change by risk, so a new price, a withdrawn claim, revised legal text or an altered safety instruction reaches every edition at the same moment.
Fix: bring the edition up to the source's current version, urgent lines first, and record which version it now reflects.
Verify: a reader of the edition meets the same fact as a reader of the source.
Prevent: log every source change with its editions, and treat a changed price, offer, claim, legal or safety line as a change to every edition, not a task for the next translation round.
An AI-assisted draft that restated an old or invented fact
A model asked for a fact it was not given writes a plausible one, and a grounded tool can retrieve the older of two documents in the team's library. The diagnosis of AI content containing invented facts separates those causes, distinguishes a stale fact from an invented one and archives superseded documents outside the library.
Fix: trace every fact on the affected pages to the owner's current version, correct what does not trace and put the pages back through human reviewThe step where a named person checks AI-assisted work for accuracy, sources, originality, privacy and disclosure before it is published or sent..
Verify: each fact traces to a current source, checked by someone other than the person who prompted the draft.
Prevent: put current facts in the brief rather than letting the draft find them, and keep the review gate in the guide to AI-assisted content with human review, where the person checking every factual claim is not the one who prompted the draft. Wider faults in such pages belong to the diagnosis of AI content that does not perform.
Prevention: one owner and one record for every fact that changes
Every cause above is one failure in a different place: a changeable fact repeated across pages with nobody responsible for all its copies. Prevention gives each such fact an owner and a list. Start with the facts readers act on: prices, plan names, eligibility rules, specifications, offer terms and product steps. The record holds the current version, its owner, when it last changed and everything that uses it. Claims live in the claims library, names in the style guide, and the inventory ties both to pages. Then attach a check to each moment that can split a fact.
| When | Check | What it catches |
|---|---|---|
| A fact changes | Everything on the fact's list | Updates reaching only remembered pages |
| A brief is written | The inventory, for an existing answer | Newer pages contradicting older ones |
| A name changes | Retired names and a search for the old one | Old names on older pages |
| A correction is made | The copies recorded against the page | Corrections stopping at the page |
| A page with an end date goes live | Its expiry decision | Ended offers left live |
| A source page changes | The editions it touches | Translations left behind |
| An AI-assisted draft is reviewed | Every fact against the owner's version | Old or invented facts restated |
| The periodic audit | Pages that contradict another page | Splits the other checks missed |
The governance guide counts pages that contradict another page among the measures an audit reads; comparing that count with your own previous audits shows whether the other checks work.
Readers are the cheapest detector, and the tutorial on publishing your editorial standards gives them a route to report an error to a named owner. If a contradiction returns after a fix, the gap is in the process, and the diagnosis for marketing mistakes that keep happening follows a repeat back to the missing step. The content troubleshooting section lists neighbouring symptoms.
A heat pump installer finds three prices for one service plan (illustrative)
Yomblisk Heating finds three prices for one service plan
Yomblisk Heating, an invented heat pump installer, sells an annual service plan. In May a customer books quoting £129 from a blog post; the plans page shows £149, the help centre £139 and a downloadable brochure £129. The pricing lead confirms £149, set in January. The price had changed twice in 14 months, from £129 to £139 to £149, and each time only the plans page and whichever pages someone remembered were updated: the help centre caught the first change only, and the brochure was exported before either. A newer post on what the plan includes contradicts an older one, the translated plans page shows £139, and the plan's previous name survives on 9 articles. The installer honours £129 for the customer, then records each price, plan name and term once, with the pricing lead as owner and the 23 places that use them. It merges the older post into the newer one, which fits the question better, and redirects the older address to it. It replaces the brochure, updates the translated page, marks the old name retired and corrects all 9 articles. When the price next changes, every entry on the price's list shows the new figure before it takes effect.
Common mistakes
- Assuming the newest page is right. Ask the fact's owner.
- Fixing only the two pages someone noticed. Files, copies and editions carry the fact too.
- Deleting the page that lost. Merge it and redirect it to the survivor.
- Correcting the page and not its copies. Newsletters and brochures keep the old version alive.
- Leaving ended offers live without a notice. An old offer page reads as a current one.
- Ending the review at a person. "Someone forgot" is not a cause; the missing record or check is.
