Crystal Ball checks covered
UNVERIFIED_SNAPSHOT, RESPONSE_TIME_UNKNOWN, could not be verified
What the flag means
Crystal Ball uses “could not be verified†when it does not have enough reliable evidence to pass or fail a check. The signal may be missing, hidden, blocked, dynamic, or unavailable in the scan mode used.
This matters because an unverified finding should not be treated like a confirmed failure. It is a request for a better look, not a doom prophecy.
Common causes
Common causes include HTML snapshots, blocked live requests, timeouts, server errors, JavaScript-rendered content, CDN or firewall challenges, missing headers, redirects, unpublished pages, or signals that only appear after user interaction.
How to fix it
- Custom HTML/static: Re-run a live scan, check whether the page blocks bots, and confirm the signal exists in the source HTML or response headers.
- WordPress: Clear cache, rescan the live URL, and check security plugins, maintenance mode, noindex settings, and headers from the host or CDN.
- Shopify: Confirm the storefront is public and published. App-injected elements may not be verifiable from raw HTML, so keep core SEO signals in theme output.
- Wix: Publish the page and scan the live URL. Some dynamic features may need a rendered browser check rather than a source-only check.
- Webflow: Publish the site, clear custom-domain confusion, and check whether the signal appears in native page settings, custom code, or rendered embeds.
Need help?
If the fix gets murky, visit Support and send the details. Bug reports and Crystal Ball questions are free support. Implementation and development work may be paid support, but we will tell you clearly before anything becomes paid. No surprise invoices from the tower.