QueryRev Terms
Change Ledger
The Change Ledger is QueryRev’s record of every material change made to a website through the product. Each entry keeps the page, the decision behind the change, who proposed and approved it, the state before and after, the expected impact, how it was applied, its verification status, the measured outcome and any rollback.
- QueryRev’s own term
By QueryRev ResearchPublished Updated5 min read
Why it matters.
Most SEO work leaves no trace beyond a ticket. Three months later nobody can say what changed on a page, who agreed to it, or whether the lift in the report came from that change or from the season. Without a before state there is nothing to roll back to, and without a date there is nothing to measure from.
Google’s guide to traffic drops lists algorithmic updates, technical issues, seasonality and changing interests among the main causes to tell apart[1]. A dated record of your own changes takes one cause off that list, or puts it at the top.
A ledger turns changes into evidence. It is an audit trail for a client or a legal team, the starting point of every verification, and over time the record of which kinds of change worked on this site.
The idea is old in data work. The W3C’s PROV documents describe provenance: the record of the entities, activities and people involved in producing a piece of data, so its quality and reliability can be judged[2]. A change ledger is provenance for a website. QueryRev’s study of AI crawler access keeps the same kind of record for the web: it reads one fixed panel of 9,973 domains again every month and logs every domain that started or stopped blocking a crawler by name[3].
Agencies and in-house teams need the same record for different reasons. An agency shows a client exactly what it did and what each change produced; an in-house team shows finance which work paid for itself. Both need the before state, the date and a result measured the same way every time.
How it is measured.
A ledger is judged by its completeness: the share of changes with a recorded before and after state, an approver, a publish time and a verification result. An entry is closed when its outcome has been measured against a baseline, not when the change is published.
Completeness is checked on every change, not on a sample: one change missing from the ledger is one result nobody can explain.
Read the ledger by kind of change as well as by page. Over a year, the share of title rewrites, merges or redirects that produced a measured lift is the evidence for which work to repeat on this site.
Measured by
- Entries with before and after
- Entries verified
A worked example.
Sample data: an invented site, to show the method.
An approved Update decision rewrites a product page’s title. The entry holds the old title, the new one, the approver, the path it was applied through and a 14-day verification window. One step restores the old title.
Fourteen days later the entry gains its result: the title’s click-through against the baseline, with the window and the comparison stated. Then the entry closes.
What to do, step by step.
Record every material change before it ships: the page, what changes, why, and who approved it.
Keep the before state exactly as it was: the old title, the old text, the old redirect, not a description of them.
Record how and when the change was applied, to the minute where you can, so measurement starts from the right day.
Set the verification window and the baseline before the result is known.
Close the entry with the measured outcome, including no change or a fall.
Keep a one-step rollback for every entry, and record its use as an entry of its own.
Mistakes to avoid.
Logging only the successes. A ledger of the changes that worked teaches nothing about the ones that did not. Every change gets an entry, and every entry gets a result.
Describing the before state instead of keeping it. “Shortened the title” cannot be rolled back. The old title can.
Measuring from the wrong day. A change published on a Friday and measured from the Monday mixes three days of the old page into the new. The publish time is part of the record.
Testing in a way search engines read as deception. When a change is tested with variants, Google asks that tests avoid cloaking, use temporary redirects and run only as long as needed[4].
Closing an entry at publish. A published change is an execution, not an outcome. The entry closes when its result has been measured against the baseline.
How QueryRev treats it.
“Change Ledger” is QueryRev’s own name. The rule behind it does not bend: nothing changes a customer’s website outside its policy, and every material change is written to the ledger with its before and after state. That holds equally when a person applies the change by hand.
Questions people ask.
What counts as a material change?
Anything that can change how a page is found, read or ranked: its title, headings, main text, structured data, canonical, redirects, robots rules, internal links and status. A typo fixed in a footer is not one; a change to the words a page ranks for is.
Does the ledger hold changes made by hand?
Yes. A change a person applies outside the product is entered with the same before and after state, so the record holds for every material change, not only the ones applied through QueryRev.
How long should a change ledger be kept?
For as long as the site is worked on. The value of the record grows with its length, since old entries are the baseline for new ones and the history of which kinds of change worked on that site.
Sources and citation.
Primary sources only: the search engines, the AI vendors, standards bodies and QueryRev’s own research. Each is cited in the text by its number.
Debugging drops in Google Search trafficGoogle Search Central ·
PROV-Overview: An Overview of the PROV Family of DocumentsW3C ·
State of AI crawler access, October 2026QueryRev Research ·
Minimize A/B testing impact in Google SearchGoogle Search Central ·
Cite this definition
A suggested citation. Its link goes to the definition, whose anchor does not change.
QueryRev Research. “Change Ledger.” QueryRev AI glossary, 18 October 2026. https://queryrev.com/glossary/change-ledger#definition
Related terms