Audit Shows No Issues or Empty Results

Symptoms

• An audit completes but shows no issues, or only a handful.
• Dashboards and panels render empty where you expected data.
• A connector reads Connected but its findings or metrics never appear.

A clean result is sometimes genuine — a small, healthy site really can have nothing critical. More often, an empty audit means the crawler reached very few pages, browser rendering was off, or the external data that powers certain findings isn’t connected yet. Work through the causes below before assuming the site is flawless.

Likely causes

• The crawl was blocked. robots.txt (matching VisibilityIQ or *) or a WAF challenge kept the crawler from fetching pages. VisibilityIQ respects robots.txt for every user-agent and won’t bypass a block, so a blocked site finishes with 0 or near-0 pages.
• The site requires authentication. Only public, unauthenticated URLs are crawled. A login wall hides everything behind it.
• Render parity is disabled. With browser rendering off, raw-vs-rendered findings can’t be produced.
• Connectors aren’t linked. Some findings only exist when external data is present.
• Sync drift. A connector that silently stopped updating leaves its findings stale or absent even though it still shows connected.
• The crawl is still running. Large sites take time; results are incomplete until the crawl completes.

How to fix it

1. Read the crawl log. Audit → Crawl log shows pages fetched. If it’s 0 or close to it, the crawl was blocked — open yourdomain.com/robots.txt and look for a disallow rule. For testing, add User-agent: VisibilityIQ / Allow: /, or allowlist the crawler IP range in your WAF (contact support for the current range).
2. Account for login walls. If pages sit behind authentication, the crawler can’t reach them. Contact support to discuss options for auditing authenticated pages.
3. Enable browser rendering. Turn on Project → Settings → Crawl → Enable browser rendering and re-run the audit to surface render-parity findings.
4. Check connector coverage. In Project → Connectors, confirm the sources that power the findings you expect are active:
   • GSC canonical reconciliation requires Google Search Console.
   • Traffic-weighted severity upgrades require GA4.
   • CrUX-based performance findings require the CrUX connector.
5. Look for sync drift. Check each connector’s Last synced timestamp. If a connector hasn’t updated in days, disconnect and reconnect to re-establish the sync. See Connector auth errors for the re-consent flow.
6. Confirm the crawl finished. In Project → Audits, wait for status to leave In progress before judging the results, and check the Info and Low buckets — clean sites still carry minor observations.

Still stuck?

If the crawl fetched a healthy number of pages, rendering is on, the right connectors are linked, and you still see nothing meaningful, email support@visibilityiq365.com with your project name and site URL. We’ll inspect the crawl log and connector state. See also Crawl not completing and Audit score dropped unexpectedly.