Migration Proof & Provenance Watch
Migration Proof and Provenance Watch are two Livada SEO verifications that
replace a promise with proof: Migration Proof compares the published HTML <head>
before and after a migration, line by line; Provenance Watch then continuously identifies which plugin,
theme, or extension actually wrote each tag on a WordPress page.
This page summarizes two verifications already published and sourced from Livada SEO's real code — not a new measurement. Technical detail and the exact plugin version are in each article cited below.
← Back to the migration hubTwo verifications, two moments
| Migration Proof | Provenance Watch | |
|---|---|---|
| When | At migration time — before/after | Continuously, after the migration |
| Verifies | That no published tag silently disappeared | Which plugin, theme, or extension writes each tag |
| Proof produced | Dated before/after diff, line by line | Responsible file and component, resolved via PHP Reflection |
| Documented example | Migrating from Yoast, Rank Math or SEOPress to Livada | Duplicate canonical caused by Elementor Pro |
A successful import isn't a successful migration.
Yoast, Rank Math, SEOPress and Livada can all import your data. What none of the first three does:
verify that what was published before the migration is still published after. Migration Proof
captures the page's real <head> before the import, then after,
and compares both versions.
Nothing disappeared. 1 tag reworded, 0 lost.
Two canonical tags. Google keeps one, at random.
A standard SEO audit will say "duplicate canonical detected" — that's the symptom. Provenance Watch traces back through WordPress's execution chain to identify which component produced the tag, in which file, and at what priority it ran.
Read the full example: finding the real culprit →Frequently asked questions
Does Migration Proof flag a reworded title as a loss?
No. It distinguishes a tag that disappeared from text reworded by your new templates — only a silent disappearance is flagged as an issue.
Does Provenance Watch only run during a migration?
No. Migration Proof compares before/after at migration time; Provenance Watch then takes over continuously, across all your pages.
How far does Provenance Watch trace a tag?
Down to the file and responsible component, resolved by the PHP engine (Reflection) — not an exact line number within that file.
Both verifications fit a broader doctrine: every public claim on livada.io is classified Verified, Observed, or Supported — never a superlative on its own. See the detail on the migration hub →
