Reports and client packaging
Decision packs with revocable share links, weekly digest webhooks, and one-zip exports for SEO and GEO priorities without rebuilding decks from screenshots.
Reporting in EZ SEOS is packaging for people who need next steps, not another vanity dashboard. Three shipped workflows cover most of that:
- A decision pack with a revocable share link of current priorities
- A weekly digest delivered to a webhook URL, with preview and test send
- A one-zip export of ranks, Search Console queries, GEO actions and citations, audit summary, and the Do Next queue (caps live in the export manifest)
Commercial overview: reports (/features/reports).
Decision pack (shareable)
The decision pack is a client-ready package of current priorities. Think "here is what we should do next," not "here is every chart we can screenshot."
You get a revocable share link. The token is shown once, so treat it like a credential: share it on purpose, revoke it when the engagement ends or the link leaked. The pack ties to Do Next and opportunity-style priorities. It is a share package of current decisions, not an open edit surface for the client to rewrite your roadmap in place.
Weekly digest webhooks
The weekly digest is a configurable summary sent to a webhook URL. Preview it. Test send it. Point the webhook at whatever endpoint your ops stack uses (chat tools, automation glue, client pipelines). Contents are a weekly summary of project SEO and GEO movement: rankings, GEO actions, opportunities-style progress, the kinds of movement a stakeholder can scan without a meeting.
Any webhook endpoint that can receive the digest works. You are not limited to one chat vendor.
One-zip project export
One download can bundle ranks, GSC queries, GEO actions and citations, audit summary, and the Do Next queue. Use it for offline analysis, handoff, or backup-style archives. Row and size caps are documented in the export manifest inside the product. Read the manifest instead of guessing limits from old decks or blog posts.
How agencies use packaging with projects
One project per client keeps packs and exports scoped cleanly (/docs/projects). The agent can help draft priorities that feed packs (/docs/the-agent). You still own judgment and what you actually send.
How this ties to Proof and Do Next
A decision pack should reflect the current Do Next and Visibility priorities, not a stale list from last quarter. When you tell the story of what changed, Proof and remeasure on the GEO loop matter (/docs/geo).
Costs
Packaging features ship with the product. Paid signals underneath still run on credits, with cost shown when you generate them. Free reads stay free. See credits (/docs/credits).
| Package | Best for | Key control |
|---|---|---|
| Decision pack | Share priorities with a client or stakeholder | Revocable link; token shown once |
| Weekly digest | Recurring ops or client automation | Webhook URL; preview and test send |
| Export zip | Full offline handoff | Manifest caps |