False Positives and Confidence Levels
Every VisibilityIQ finding carries two scores: severity (how impactful the issue is if real) and confidence (how certain we are that it’s actually a problem). Understanding confidence helps you prioritize accurately and avoid chasing false positives.
Confidence levels
Section titled “Confidence levels”| Level | What it means |
|---|---|
| High | The evidence is unambiguous. This is definitively an issue. |
| Medium | The evidence strongly suggests an issue but relies on some inference. |
| Low | Heuristic-based detection. May be intentional or context-dependent. |
Low-confidence findings are not bugs — they’re VisibilityIQ flagging something that might be a problem but that requires human judgment to confirm. A soft 404 candidate, for example, might be a legitimately thin page (intentional) or a missing-content bug (unintentional).
Common false-positive scenarios
Section titled “Common false-positive scenarios”Render parity “differences” that are intentional
Section titled “Render parity “differences” that are intentional”Some sites intentionally serve different content to bots vs users (dynamic rendering). If you’re using dynamic rendering, some render-parity findings may be expected. You can suppress specific finding types at Project → Settings → Audit → Suppressed checks.
noindex on pages you intentionally exclude
Section titled “noindex on pages you intentionally exclude”If you intentionally noindex certain pages (admin interfaces, thank-you pages, search results), those findings are expected. Mark them as Intentional in the finding detail to remove them from the active findings count.
Canonical “chains” that are actually fine
Section titled “Canonical “chains” that are actually fine”If you have redirects for historical reasons and the canonical is set correctly at the final destination, VisibilityIQ may flag the intermediate as a canonical chain. Review whether the chain length is causing indexation problems in GSC before treating this as urgent.
AI bot blocking that’s intentional
Section titled “AI bot blocking that’s intentional”If you’ve made a deliberate decision to block GPTBot or ClaudeBot (e.g., for content licensing reasons), those findings reflect your intent. Mark them as Intentional.
Soft 404 false positives
Section titled “Soft 404 false positives”Thin pages that are intentionally thin (e.g., a simple landing page with minimal copy) may be flagged as soft 404 candidates. Review the page’s actual content and traffic data before acting on this finding.
Marking a finding as intentional
Section titled “Marking a finding as intentional”Open the finding and click Mark as intentional. Add a note explaining the reason (e.g., “Admin page — correctly excluded from indexation”). The finding will be moved to the Intentional bucket and won’t count against your active issue score.
You can review all marked-intentional findings under Audit → Findings → Intentional and unmark them if circumstances change.
Reporting a false positive
Section titled “Reporting a false positive”If you believe a finding is systematically wrong (not just intentional in your case), use the Report false positive button in the finding detail. This sends the finding data to our engineering team for review. We track reported false positives and use them to calibrate detection logic.