How to Interpret Audit Findings

Overview

Once CrawlSage completes a website scan, it compiles a detailed report. Instead of presenting a raw lists dump, our engine groups findings by severity, maps them across categories, and generates code-level recommendations. This page explains how to read and interpret these reports.

Prerequisites

• A completed audit run on your project domain.

Step-by-Step Guide

1. Analyze the Overall Health Score:

   Your Health Score (0-100) is displayed at the top of the report. This is a weighted metric computed by subtracting penalty points for each unresolved issue relative to total sitemap size. A score above 90 represents strong technical SEO health.

2. Classify Found Issues:

   Issues are grouped into three distinct severity tiers:

   • Critical (Red): Major indexing blockages, redirect loops, broken sitemaps, or critical security vulnerabilities. Resolve these immediately as they directly prevent search engine crawler indexation.
   • Warning (Amber): Ranking and user experience degradation items. These include missing meta descriptions, duplicate title tags, missing alt attributes, or Core Web Vitals bottlenecks.
   • Notice (Blue): Structural best practices. These include missing JSON-LD schema objects or minor performance optimizations.
3. Filter by Category Reports:

   Use the tabs at the top of the findings grid to isolate checks by technical feature:

   • SEO: Meta attributes, headers structure, indexability.
   • Performance: Image optimization, Core Web Vitals loading metrics.
   • Security: SSL certificate checks, security headers.
   • Structured Data: JSON-LD schema formats.
4. Inspect Recommendation Cards:

   Click on any issue line to open the details card. Review the parameters:

   • Why this matters: Brief technical explanation of the issue's impact on search indexing.
   • Current Value vs. Recommended: Displays what our crawler detected versus the suggested correction.
   • Confidence Level: The AI engine's calculated confidence in the auto-generated code patch.

Expected Result

You will have a clear, prioritized list of technical SEO issues ranked by severity, allowing your team to identify critical search bottlenecks.

Best Practices

• Focus on Critical Blocks First: Never spend time editing alt text notices if your sitemap has duplicate canonical loops or 404 errors. Focus resources on critical red checks.
• Review the Confidence Scores: If a recommendation's confidence level is under 80%, review the code diff carefully in the editor before deploying.

Common Mistakes

• Aiming for a 100/100 score immediately: A high score is the goal, but minor notices (like missing non-essential JSON-LD tags) will not block your rankings. Focus on resolving critical errors and warnings.
• Ignoring sitemap paths shifts: If you change a page structure, older crawl logs remain in history. Always run a new scan to verify your changes are correctly tracked.

Troubleshooting

• Audit shows 0 pages crawled:
  1. Confirm the target domain was entered correctly in project settings.
  2. Check your robots.txt file to ensure it doesn't block crawler bots. See the robots.txt Blockages manual.