Reports
Published immutable snapshots, share links, PDF download, white-label behavior, and what each report section contains.
What is a Report?
A Report is an immutable, period-scoped snapshot summarizing what changed in AI visibility, what optimizations were applied, and what outcomes were measured — for a specific client over a specific time window. Once published, a report's content is locked by database constraint. It is a historical record, not a live dashboard.
Report types
GeoScript produces three report types:
- Baseline — the initial snapshot taken shortly after onboarding, establishing the starting-point visibility picture.
- Weekly — covers a seven-day monitoring window.
- Monthly — covers a calendar-month monitoring window.
Reports are published at the end of each monitoring period. Once published, a report is a frozen historical snapshot.
Report contents
Each published report contains four narrative sections:
- What changed — changes in site coverage, content signals, and key observations during the period.
- What we did — optimizations applied (interventions, deployments) during the period.
- What happened — outcomes observed after the changes, grounded in real prompt-run data.
- What comes next — the open recommendation backlog for the coming period, derived from current signals.
All numbers in a report come from stored snapshot data at the time of publication. They do not update after publication.
The share link
Each published report has a unique share token. The share URL looks like: geoscript.ai/report/[token]
Send this link to your client. They can open it without a GeoScript account. The URL contains only the token — no agency ID or internal identifiers are in the URL.
The share link is permanent as long as the report exists. Published reports are not automatically deleted.
PDF download
From the share URL, the client can download a PDF of the report. The PDF is generated from the same locked snapshot data. It reflects the state at the time of publication.
White-label behavior
The public report page (geoscript.ai/report/[token]) displays the agency's name in the header, not GeoScript's. The client sees their agency's branding, not GeoScript's platform branding. GeoScript is not mentioned on the client-facing report surface.
Agency branding is based on the agency workspace record. If your agency name is not yet configured, contact support.
Immutability
Published reports are enforced immutable at the database level. No code path in GeoScript can update the snapshot data of a published report. This means:
- Historical reports remain accurate representations of the period they cover.
- Numbers in an older report will not silently change as new data arrives.
- If you find an error in a published report, contact support — it cannot be corrected through the UI.
What Reports do not do
Reports do not provide live, real-time data. They are snapshots of a completed period.
GeoScript reports do not currently include a raw data export or CSV download of individual observations.
Reports do not attribute visibility changes to specific GeoScript interventions with statistical certainty. The "What we did" section documents what was deployed; it does not claim that deployments caused observed changes.