Browser report library
Saved GEO Reports
Save Markdown reports from CiteKit tools in your browser, then copy, download, or remove them later. Reports stay on this device unless you export them.
Direct answer
Saved reports are stored in localStorage on your device. CiteKit does not receive these reports in the current static implementation, and clearing browser data can remove them.
Your saved reports
No saved reports yet. Generate a tool result, then choose Save report.
How to use this page
Use saved reports as working drafts for SaaS GEO audits, schema reviews, crawler checks, and alternatives briefs. Review all generated content before publishing it on a client or production website.
Report lifecycle
| Stage | What happens | What to check |
|---|---|---|
| Generate | A tool or workflow creates a Markdown-style audit draft in the browser. | Confirm the input page, brand, competitors, and source URLs are correct. |
| Save | The report is stored in localStorage for this browser profile. | Keep private notes out of the report if the device is shared. |
| Review | A human checks claims, schema fields, crawler findings, and recommendation priority. | Remove unsupported claims and mark follow-up questions. |
| Export | The report can be copied or downloaded into a client note, sprint ticket, or editorial brief. | Add screenshots, public source links, and owner names outside CiteKit. |
| Retest | The same prompt set or scorecard is run again after page changes. | Compare the new report with the original baseline instead of starting over. |
What belongs in a saved report
A saved report should preserve evidence, not just generated recommendations. Keep the prompt set, page URL, brand name, competitor list, cited URLs, schema notes, crawler diagnosis, answer-block changes, alternatives-page caveats, and the next review date. When a report is used for client work, add the human reviewer, the public sources checked, and the changes that were rejected.
- Include the exact prompt or page section that produced the observation.
- Include public source links for pricing, integrations, competitor claims, and product facts.
- Include a decision: publish, revise, investigate, or leave unchanged.
- Include a retest date so AI visibility checks become comparable over time.
Saved report review checklist
- Confirm every generated claim appears on the public page or in a reliable source.
- Remove private notes before sharing a report with a client or teammate.
- Compare follow-up reports against the same prompt set instead of changing the test every run.
- Download important reports because localStorage can be cleared by browser settings.
Local storage boundaries
Saved Reports is a convenience layer for a static site, not an account system. Reports are stored under the browser origin for CiteKit and can disappear when a user clears site data, changes browsers, uses private mode, or runs storage-cleanup tools. CiteKit does not currently sync reports, recover deleted local data, or receive saved report contents from this page.
Review queue workflow
Use this page as a lightweight review queue after running tools. A practical workflow is to save one baseline report, fix the highest-priority page issue, run the same check again after search systems have time to recrawl, then compare the new report with the old one. This turns generated output into a measurable editorial process.