🔍 Overview
The Site Auditor generates detailed reports about technical SEO issues across your website. When you export that report — for example, as a Google Doc — you may notice data that looks unexpected, including unfamiliar URLs, issue descriptions that seem off, or formatting that makes it hard to match a specific URL to a specific problem. This is a known UX and export accuracy issue that our team investigates on a case-by-case basis.
⚠️ Why Exported Reports May Look Inaccurate
Export accuracy issues usually fall into one of these categories:
- Stale crawl data: The report reflects the last completed crawl. If your site has changed since then, the exported data will not match your current live site.
- Formatting limitations in Google Docs: Large tables with many URLs and issue types can lose column alignment or wrap text in ways that make it hard to read which URL is linked to which issue.
- Issue descriptions pulled from raw metadata: Some issue labels and descriptions are generated from page-level metadata (like meta titles, alt text, or heading tags). If your site contains typos or misspellings in those on-page elements, they will appear exactly as-is in the export — the auditor reports what it finds, not a corrected version.
- Multiple issues per URL: A single URL can trigger several different issue types. In an exported document, these may appear as separate rows, which can make it look like there are more affected pages than there actually are.
✅ What to Do If Your Export Looks Incorrect
Because this is a bug-category issue, resolution typically requires our team to investigate the specific data and export in question. To help us resolve this as quickly as possible, please have the following ready when you reach out:
- Your project name (the exact name as it appears in your Search Atlas account)
- A description of the unexpected data — for example, URLs you do not recognize, issue counts that seem wrong, or formatting problems in the exported document
- The date and time when you generated or exported the report
- A screenshot or copy of the exported report showing the problematic data
- Any error messages displayed during the export process, copied exactly as they appeared
📋 General Tips for Reading URL-Level Issues
While our team investigates, the following may help you work with your data in the meantime:
- Use the in-platform view first: The platform groups issues by type and lets you expand each one to see every affected URL. This is generally clearer than the exported document and can help you identify whether the issue is in the export itself or in the underlying crawl data.
- Check whether the data matches the in-platform view: If the in-platform view looks correct but the export does not, that difference is important information to share with our team when escalating.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.