Export and share reports
Updated
A report should help someone decide what to do next.
Before exporting, choose the evidence that answers their question: the affected URLs, the relevant period and the findings they need to review.
This guide helps you select an available format, check the file and share it with enough context to be useful. Standard reports are included in Solo and Pro; executive PDFs require Pro.
Make the export useful to its reader
- Select scope
Website, crawl, dates, filters and rows. - Choose an available format
CSV, XLSX or PDF depends on the view and plan. - Open and check the file
Confirm representative URLs and evidence. - Share with context
Include limitations and remove private information.
An exported file is a snapshot of evidence or instructions, not proof of implementation.
1. Decide what the reader needs to see
Choose the correct website or client and confirm the active crawl. Set the filters, selected rows and reporting dates that match your question.
Review the visible evidence and note whether it is complete, partial or unavailable. A large file is not necessarily a better report: a focused set of affected pages can be more useful to the person responsible for implementing a fix.
2. Choose a format the view supports
Use CSV for supported row-based data when you need to inspect it in a spreadsheet. Where a tool offers XLSX, review the workbook sheets and column descriptions.
Use a supported PDF report for a readable summary. A Pages CSV and an executive report serve different purposes, so check that the chosen export actually contains the details the recipient needs.
3. Open the file and check a few records
Open the file after saving and inspect a few representative records. Confirm that URLs, recommendations and dates match the task you intended to share.
Check the actual selection and scope in the export rather than assuming a hidden filter was applied. If a field is unavailable, retain that status instead of replacing it with zero or an inferred value to make a chart look complete.
4. Explain the scope and limitations
Explain the website, source, crawl date or provider date range, relevant filters and any coverage limitation alongside the report. Separate confirmed findings from recommendations and draft fixes.
An export from Fix Generator is implementation material, not proof of deployment. If comparing periods, label both periods and avoid suggesting that all observed movement was caused by the changes you made.
5. Remove information the recipient does not need
Review exported material for private URLs, client information and unnecessary personal data before sending it. Files saved in Finder are outside the app’s account-switching interface and may remain accessible in the folder you selected.
Do not include API credentials in a handover. Keep an unchanged copy of the evidence you used so later verification can refer back to the original audit scope.
Quick reference
| Output | Typical purpose |
|---|---|
| Supported CSV | Inspect rows in a spreadsheet |
| Supported XLSX | Review structured workbook evidence |
| Standard report | Share core audit findings |
| Executive PDF on Pro | Summarize supported executive reporting |
| Fix export | Implement reviewed changes, then verify |
Continue learning
Ready for the next step? Start here: interpret the evidence, review fix exports.
If you still need help, contact support with your app version and the steps you tried. Leave out passwords, API keys and private account details.
Published by LLMIC. Documentation reviewed on 24 September 2026.