How to keep a published page accurate after it goes live

18 September 2026 · Chris Dolan

The short version

A published page stays accurate when later evidence is added in the words it was written in rather than rewritten, when a page you have edited on your site, by changing our words or adding your own, is left alone, and when you can make every change wait for your approval. Since 18 September the engine updates live pages that way.

A page the engine publishes on your site is often put together from the pieces written for its subject: a guide, a table of figures, a slide deck. Until this week that assembly happened once, so a piece finished after its page existed, usually the deck, never reached the page. Now a late piece is added and the page on your site is updated in place, using the words those pieces already had, with no new AI writing.

Several things stop that update, and three matter most to you. Before anything changes, the live page is read and compared with what we published, and if our sentences have been reworded or removed on your site, or you have added text of your own, the page is left alone. If the page has been rewritten as a single text, a fresh assembly would undo the rewrite, so it is not attempted. And if you have switched on review before publishing, the update waits on the project page with Publish in place and Discard, and you are told about it once.

When a page is updated, its record stays honest. The date it was first published is kept, and a separate date for the last change is added, which no page carried before. The machine-readable note of where the page came from, which a pushed rewrite used to strip, is put back every time.

For a page that says the wrong thing about one of your products, there is Re-align. You give a one-line description of the product, and a link to its page or video if you have one. The page is rewritten to agree with your words and your own pages, keeping its structure, and the result is checked against what you said. Nothing replaces the live page until you approve it.

Two things are not done yet. Rewriting a page does not rewrite the pieces it was built from, so they keep their original wording. And an edit you make by hand in one of those pieces does not yet reach the page; making it count is among the next pieces of work.

AI assistants reviewing the product in September said it lacked governance over machine-written content, and that it relied on its own provenance fields rather than the standard schema.org ones. Neither was true.

The technical detail

Every week an AI assistant with web search reviews the product and lists what it lacks, and we check each claim against the code. Two September claims touch what happens to a page once it is published.

"Use the existing schema:citation relationship rather than relying only on custom provenance fields" (review of 17 September)

What is true. Pages published to a customer's own site already carry a schema.org Article block. It has dateCreated, datePublished and dateModified only for events we recorded; a date never observed is left out, and dateModified is never defaulted to the publication date. The publisher and author are the organisation, and a person is named only when the customer names a real one. Sources appear as citation entries, each a CreativeWork with its address and, where known, its name and publisher, and the same addresses appear again as isBasedOn. ClaimReview is never emitted, because it is reserved for eligible fact-checkers. WordPress, Ghost and webhook destinations carry the block. Wix stores posts as structured content with no place for it, so a Wix page carries its sources as visible links instead.

What changed this week. Until 18 September a rewrite pushed to a live page replaced it with a version that had no block. Every push now puts it back: a shape rebuild, an approved Re-align and an approved update all carry the recorded dates, with the update time as dateModified. An update event existed in the code and nothing recorded it, so dateModified had never been written; it is written now.

How to check. Open the source of a page the engine has published to a WordPress, Ghost or webhook destination and search for isBasedOn. The public roadmap entry "Published work carries provenance a machine can read" describes the block.

What the review got right. This is a record, not a signature. Nothing is cryptographically signed, and there is no C2PA manifest on media.

"Missing explicit governance around model-generated content" (review of 14 September)

The checks a draft must pass before it is published are set out in How to stop AI-written pages inventing facts about your business. Approval works like this.

• Review before publishing (Settings) holds every page the engine writes for the customer's site until they approve it; an Evidence Engine page waits under Needs you until they press Close it now. It has covered the Evidence Engine's own pages since 15 September, and the nightly plan's posts before that. Documents, tables and decks created in the customer's Google Drive are not held, because they are not posts on the site.
• Updates wait too. Since 18 September an automatic update on such an account becomes its own card on the project page, "A page update waits for you", with the updated page to read, Publish in place and Discard. One update waits per page: a later piece replaces the waiting one, because the newer assembly already contains it. The customer is notified once, and the dashboard note counts it.
• Re-align always stops at review.

How to check. The Review before publishing setting states what is and is not held, and the roadmap entry "Nothing replaces a live page until you approve it" describes the rule.

How an update is built, and what refuses it

When a piece finishes for a subject that already has a live page, the page is assembled again from every piece for that subject, with no model call. It never includes another page as a piece, never lists the page as a source of itself, and leaves out a piece that was stored as a complete web page rather than pasting it in. The update is refused, and the refusal logged with its reason, when:

• the page was rewritten and is one text now;
• the page is an article with its evidence set out beneath it, because rebuilding that section on its own is not built yet;
• the page is about a product of the customer's that nothing of theirs explains;
• the live page cannot be read, so it cannot be checked;
• any sentence of six words or more that we published is no longer on the live page, word for word. Words are compared on letters and digits only, so a theme's quotation marks and dashes do not read as edits, and headings are not compared;
• the live page carries a sentence of six words or more that we did not publish. On a connected WordPress site the post is read as the site stores it, so an addition anywhere in it counts.

Any other site can only be read as a web page, where menus, related posts and comments surround the article, so there only the text between the first and the last of our sentences is compared. A paragraph added after the end of our article on such a site is not seen, so anyone who adds to our pages that way should switch on review before publishing.

The page is replaced in place where it lives on a connected WordPress site or behind a receiver that supports updates. Anywhere else, nothing is sent.

Re-align

Re-align rewrites a published page so that what it says about a product agrees with the owner's one-line description and their own pages and videos. The old page supplies structure only, and without the owner's description there is no rewrite. The result is checked against the owner's words, and the Re-align card shows what was found: statements the old page made that were marked to go and still appear, whether the description is reflected at all, and any statement about the product that nothing of the owner's supports. A rewrite left too short by the sentence cuts described in the companion article is refused with a message saying what would fix it.

Not done yet

A rewrite changes the page, not the pieces it was built from, so after a Re-align those pieces keep their old wording. An edit made by hand in one of those pieces does not reach the page. And a rewrite can cite only the page's existing links and sources already recorded for the business, not new outside sources.