Every edit to the pages that matter, with a word-level diff and the traffic that followed.
Version history for the pages you choose to watch — every edit captured, graded by what it can cost you, and annotated on your traffic charts.
A title gets rewritten in a sprint nobody logged. A plugin update strips the schema. A canonical disappears in a template change. A client edits their own copy and mentions it three weeks later. Rankings drift, and the investigation starts with the Wayback Machine, a stale staging copy and someone's memory — none of which tell you what the page said the day before traffic turned.
Weeks late
content changes surface long after the traffic has already moved
No record
CMS history is per-author, per-field, and gone when the plugin is
No link
nothing connects an edit to what happened to the page afterwards
Content Changes turns raw Search Console data into clear signals and next steps.
Pick the pages worth watching
Choose from your top pages in Search Console, or paste a list. Money pages, landing pages, the twenty URLs that carry the site — not everything, just what matters.
Rankerli snapshots each one
Every check captures the page's title, meta description, canonical, robots directives, headings, schema, links, images and body copy. A new version is stored only when the content actually changed, so the history is a list of real edits — not a log of times we looked.
Read the diff, graded
Removed text struck through, new text highlighted, word by word. Each change is marked critical, warning, opportunity or notice, so on a page with fourteen edits you see the one that removed the canonical first.
Watch what the edit did
Changes are annotated onto your performance charts. The rewrite and the fortnight after it end up on the same timeline, which is the only way to tell a good edit from an expensive one.
It knows an edit from a rebuild
Content is compared on what the page says — title, headings, body, canonical, schema, links — not raw HTML. A new build id, a rotating token or a reordered script tag is not a content change. A rewritten paragraph is. Without that distinction every check on a modern site would report a change, and the feature would be noise.
Severity, so a busy site stays readable
A page that turned noindex or lost its canonical is critical. A rewritten title or vanished schema is a warning. A shorter meta description is a notice. A hundred edits a week is normal; the four that can cost you traffic need to be the four you see.
The full page, archived
Every stored version keeps the page's source, so you can see exactly what was live on any date you have a snapshot for — the answer to “what did this say before we touched it”, without asking anyone to remember.
On a schedule, with an email
Daily, weekly or monthly, with a summary when something moves. Useful whether you are watching your own team ship, an agency client who edits without telling you, or a CMS that quietly rewrites meta descriptions on save.
A canonical or a noindex slips into a template change and nothing tells you until the page falls out of the index
Titles and meta descriptions get rewritten by people who never see the ranking data
Every “what changed on this page” investigation starts in the Wayback Machine and ends in a guess
You ship a content rewrite and never find out, cleanly, whether it helped or hurt
Snapshots the pages you pick and stores a new version only when the content actually changed.
Grades every change — a lost canonical is critical, a trimmed meta description is a notice.
Writes each change onto your performance charts, so the edit and the traffic that followed sit on one timeline.
Connect your Search Console and get your first insight in under 2 minutes. Free plan, no card required.