Export and share reports
Export LLMIC audit evidence and reports while preserving the website, filters, dates and limitations needed to interpret the results.
A useful report explains what was checked, which pages or records it covers and what should happen next. LLMIC provides exports on supported views, with available formats depending on the tool and plan. Standard reports are included in Solo and Pro; executive PDFs require Pro. Use the export control in the relevant view rather than assuming every dashboard offers the same file formats.
What this guide helps you do
A useful SEO report gives its reader the finding, supporting page evidence and next action. This guide explains LLMIC’s available exports, what each format contains and what to remove before sharing client data.
Prepare the view before exporting
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.
Choose the available format
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.
Check the exported file
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.
Include context for the reader
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.
Share only the intended information
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
Next, interpret the evidence, review fix exports, understand local files. Return to the documentation home to explore other guides. If the result differs from these instructions, contact support with your app version and the relevant steps. Remove private information from screenshots and never include API keys or passwords.
Frequently asked questions
Export LLMIC audit evidence and reports while preserving the website, filters, dates and limitations needed to interpret the results.
Load a completed crawl that includes the pages you need to inspect. Confirm the crawl scope, capture time, rendering choice, and any filters before interpreting the result.
Review the affected URL, measured field, source or rendered evidence, and the rule that raised the item. Inspect nearby pages and templates because one shared component can create the same pattern across many URLs.
Create a task with the affected URL, observed evidence, intended outcome, smallest safe change, owner, and verification method. Keep the measured finding separate from the proposed fix.
Publish the approved change, run a fresh compatible crawl, and compare the new evidence with the saved result. A resolved local finding confirms the implementation changed; search performance requires separate observation over time.
The check cannot guarantee rankings, indexing, traffic, conversions, inclusion in an AI answer, or a future search-engine action. Interpret it with site context, search performance, and editorial judgment.
Save or export the evidence, assign the approved action, and use the related guides linked on the page for the next check. After implementation, repeat the same workflow against a fresh crawl so the result is comparable.