Skip to main content

Issues

When Auditoro scans your site, it creates issues for each problem detected. This page explains how to view, manage, and resolve issues.

Issue Overview​

Each issue includes:

  • Type - What kind of problem (e.g., "Missing Title", "Broken Link")
  • Severity - How serious the problem is
  • Affected pages - Which URLs have this issue
  • Details - Specific information about the problem
  • Status - Current state of the issue

Severity Levels​

Critical​

Significant problems that should be fixed immediately.

Examples:

  • Missing page titles
  • Broken internal links
  • HTTPS errors
  • JavaScript console errors

Impact: High - directly affects SEO, user experience, or security.

Caution​

Issues that should be addressed but aren't emergencies.

Examples:

  • Duplicate meta descriptions
  • Missing alt text
  • Redirect chains
  • Missing security headers

Impact: Medium - affects rankings or user experience over time.

Advisory​

Recommendations for improvement.

Examples:

  • Missing cache headers
  • Pages not in sitemap
  • Spelling errors
  • Missing favicon

Impact: Low - incremental improvements.

Issue Statuses​

Open​

The issue is active and affects your health score. Open issues should be reviewed and either fixed or marked with another status.

Ignored​

You've acknowledged the issue but chosen not to fix it. Ignored issues:

  • Don't affect your health score
  • Remain visible in the issues list (filtered)
  • Won't trigger notifications
  • Can be reopened if you change your mind

When to ignore:

  • Intentional design decisions
  • Issues outside your control
  • Low-priority items you'll address later

False Positive​

The issue was incorrectly detected. False positives:

  • Don't affect your health score
  • Help improve Auditoro's detection
  • Won't appear in future scans (for the same instance)

When to mark as false positive:

  • Correct spelling flagged as error (use custom dictionary instead)
  • Valid structured data flagged as invalid
  • Working links flagged as broken

Resolved​

The issue was detected in a previous scan but not found in the latest scan. This indicates you've fixed the problem.

Resolved issues:

  • Automatically detected when the issue disappears
  • Don't affect your health score
  • Show your progress over time

Managing Issues​

Viewing Issues​

From the site dashboard:

  1. Click Issues to see all issues
  2. Filter by severity, status, or type
  3. Sort by severity, count, or type

Filtering Issues​

Use filters to focus on specific issues:

  • Severity - Show only Critical, Caution, or Advisory
  • Status - Show Open, Ignored, or False Positive
  • Type - Show specific issue types (e.g., only SEO issues)
  • Search - Find issues by URL or description

Bulk Actions​

Select multiple issues to:

  • Mark all as Ignored
  • Mark all as False Positive
  • Export to CSV

Issue Details​

Click any issue to see:

  • Full description of the problem
  • List of all affected pages
  • Guidance on how to fix it
  • When it was first and last detected

Issue Lifecycle​

New Issues​

When a scan finds a problem for the first time, it's created as an Open issue.

Fixed Issues​

When a subsequent scan no longer finds the issue, it's automatically marked as Resolved.

Regressions​

If a resolved issue reappears in a later scan, it's reopened and marked as Open again.

Notifications​

You can receive notifications about issues:

  • New critical issues - Immediate email when critical issues are found
  • Scan completion - Summary of new issues after each scan
  • Weekly digest - Regular summary of site health

Configure notifications in your account settings.

Exporting Issues​

Export your issues for:

  • Reporting to stakeholders
  • Sharing with development teams
  • Tracking in external systems

Export formats:

  • CSV - Spreadsheet-compatible
  • PDF - Formatted report (coming soon)

Best Practices​

  1. Focus on Critical first - Fix the most impactful issues first
  2. Fix related issues together - Group fixes by page or type
  3. Rescan after fixes - Verify your changes worked
  4. Use Ignored sparingly - Don't hide problems you should fix
  5. Review False Positives - They may indicate unusual content patterns