Exporting Your Audit Data: CSV, JSON, and HTML Reports
How to export verifications to CSV, dashboard summaries to JSON, client HTML reports, entity data, and competitor benchmark reports. All data stays local.
BearAudit keeps all crawl and verification data on your machine. When you need to share it or feed it into another tool, use the built-in exports.
Verifications to CSV
From the Verifications view for a property:
- Filter or scroll to the set of pages you care about (e.g. all pages, or only those with “meta” issues).
- Use Export (or Save verifications CSV). BearAudit opens a native save dialog; choose where to save the file.
- The CSV includes the data you see in the list: URL, issue category, message, severity, and related fields. Encoding is UTF-8 with a BOM so Excel opens it correctly.
Use it for: Handing a list of fixes to developers, sending a report to a client, or importing into a spreadsheet for tracking.
Dashboard summary and client report
From the Dashboard for a property:
- Summary (JSON) — Aggregate metrics: total pages, issues, non-200 count, word counts, links, redirects, response times, and issue count by category. Useful for BI scripts and before/after snapshots.
- Client report (HTML) — A styled HTML document suitable for stakeholders; includes health overview and key metrics from the dashboard export flow.
Entities export
On the Entities page, export extracted entities to CSV for content audits, topic maps, or competitor gap workshops.
Competitor HTML report
On Competitors → Setup, click Export report after competitor crawls complete. BearAudit saves a single HTML file via the native dialog (entity gap, quality, templates, schema, linking comparisons). This replaces older multi-file markdown/CSV bundles that did not work reliably in the desktop WebView.
Your data stays local
Exports are generated from data already stored by BearAudit. Nothing is sent to a server. Re-crawl and export again for updated snapshots—useful for monthly or quarterly audits.