How do evidenced changes reach a WordPress page without breaking it?
Software that writes to a live website on its own needs no creativity, it needs a way back. Every change is bound to a revision, and every one can be undone.
What the area does
Import the inventory, then a diff with evidence
The page inventory is read through the Companion. What is to be improved arises as a diff — with the finding it answers and the source it relies on. No proposal without a reason.
Approval by risk, publishing as a high-risk step
Low-risk changes run within the agreed scope. New content first arises as an evidenced WordPress draft. The step to “published” is always a high-risk change and needs a personal approval.
Bound to a revision — a changed remote state stops the process
Draft, publication, public re-crawl and rollback are all bound to the same WordPress revision. If somebody changed something in the WordPress backend in the meantime, the process aborts instead of overwriting other people's work.
Re-crawl and effect measurement
After applying, the page is deliberately read again and the effect observed per page and topic — with source, sample and measurement window on the number.
How you can tell
- ✓Every approval is logged with the user account, the timestamp and the reviewed version.
- ✓If a single word changes after approval, the approval lapses. What is published is always exactly the reviewed version.
- ✓Rollback leads back to the evidenced previous state, not to a reconstruction.
- ✓Statements without cover in the fact store block approval instead of going live unnoticed.
Where it stops
- ×The safe write path currently supports WordPress with the Companion. Other CMSs are not presented as available.
- ×Without confirmed ownership of the domain the platform writes nothing.
- ×Quick check, audit and analysis also work without WordPress — the automatic write path does not.
- ×A published page is no promise of placements. Whether a machine cites it is measured, not promised.
Frequent questions
Can the software publish something I have not seen?
No. New content arises as a draft in your WordPress; the step to “published” counts as a high-risk change and needs a personal approval. Decision, text state and rollback stay logged, and the approval applies to exactly the reviewed version — if a word changes afterwards, it lapses.
What happens if my editor works on the same page at the same time?
The process stops. Every step is bound to a WordPress revision; if the state in the CMS deviates from it, the platform aborts instead of overwriting. That is the reason for the revision binding: an automatic write path without it will eventually overwrite someone else's work, and nobody notices.
Do I need WordPress?
For the automatic write path yes, with the Companion. Checking, auditing, measuring, topic planning and analysis do not need it — they work on any publicly reachable website. We do not promise other CMS publishers as long as they are not accepted.