Verification & What Changed
Verified, Partially verified, Not yet verified, Cannot verify
What each Verification Loop status means, and why marking something implemented doesn't automatically verify it.
Short answer
These four statuses describe whether a later, comparable rescan actually confirmed your fix — not whether you said you made it. "Verified" = every check that could be evaluated passed. "Partially verified" = some passed, some didn't. "Not yet verified" = checks exist but none have passed yet. "Cannot verify" = there wasn't enough comparable evidence to check at all.
What this means
Marking an action "Implemented" only records that you did the work — it never automatically becomes "Verified." Verification requires a new scan of the same website, in the same scan mode, that Growthract can directly compare against the original. This is a different "Verified" from the entity-match label you may see elsewhere in a report (a Wikidata match) — that one confirms a database entity match, not a fix.
Why this happens
"Cannot verify" usually means there's no comparable prior scan yet (a different scan mode, or no earlier scan at all) — not that anything failed. A failed verification check means the condition Growthract was checking for still didn't hold on the later scan.
What to do
After marking something implemented, run a new scan of the same website in the same scan mode to let Growthract check it. If you see "Cannot verify," that's a data-availability issue, not a failure — run a comparable scan to get a real result.
Still not working?
If a fix you're confident about keeps coming back "Not yet verified" after a comparable rescan, double-check the acceptance condition shown for that action — it may be checking something slightly different than what you changed.