The problem this solves
A proper site audit is five audits wearing one name. Technical SEO lives in one tool, page speed in another, backlinks in a third, deliverability in a fourth, and how AI systems read and cite your site in a fifth discipline that most teams have never audited at all. Assembling the full picture means a senior person spending days running tools, exporting findings, and reconciling formats, which is why the full picture gets assembled roughly once, before a redesign, and then never again.
The second half of the ritual is worse: turning the findings into something a stakeholder will actually read. Raw audit output is a wall of issues without hierarchy, so someone has to prioritize, translate, and design a deck, and that someone is usually the same senior person whose week the audit already consumed. Between the analysis and the presentation, the freshness drains out; the stakeholder finally sees findings that are weeks old the day they arrive.
Run as a mission, the whole chain compresses into one instruction: audit everything, build the deck, send it. Every figure in the deck traces to the specific tool call that produced it, which changes the conversation the deck creates. When a stakeholder questions a finding, the answer is the evidence itself rather than a promise to double-check, and the audit becomes something worth running on a schedule instead of once a redesign.
How the mission runs
- Crawl and audit the site. Site Audit crawls the domain and catalogs the technical findings: indexation problems, metadata gaps, structured-data coverage, rendering and speed issues per template. Findings are recorded with the affected URLs, so every claim in the eventual deck points at specific pages rather than general impressions.
- Assess AI citability. AI Visibility evaluates how the site reads to AI systems: whether answers engines can parse, extract, and cite the content, where the site appears in AI-generated answers today, and which structural choices are suppressing citability. For most stakeholders this is the first time this dimension has ever been measured.
- Check deliverability and the link profile. Email Deliverability verifies the domain's sending posture - authentication records, reputation signals - while Backlinks maps the link profile: what points at the site, what quality it carries, and where it concentrates. Both feed the same picture of how the domain stands in the wider graph.
- Prioritize into a narrative. The raw findings are ranked by impact and effort, then organized into a storyline a stakeholder can follow: what is healthy, what is quietly costing traffic or trust, and what to fix first. Each prioritized item keeps its link back to the underlying evidence, so the narrative never floats free of the data.
- Build the Gamma deck. The findings become a presentation in Gamma: an executive summary up front, one section per audit dimension, and a prioritized fix list at the end. The deck is built for a reader who was absent from the analysis, which is exactly the reader stakeholder decks actually get.
- Send it through Gmail. The finished deck goes to your stakeholder via Gmail with a short covering note stating scope, headline findings, and the recommended next step. You are copied, so the delivery is visible, and the mission ends with the deck in the one inbox it was always meant to reach.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A stakeholder-ready Gamma deck covering all five audit dimensions - technical SEO, AI citability, deliverability, backlinks, and speed - with an executive summary, prioritized fixes, and every figure traceable to the tool call that produced it. Delivered by Gmail to the person you named, with you copied. The underlying findings stay available in the mission thread, so any slide can be interrogated down to the affected URLs.
Make it yours
- Run it against a competitor's domain as well and add a comparison section, turning the audit into a gap analysis your stakeholder can act on.
- Schedule it quarterly to the same recipient; the deck's summary slide becomes a trend line, showing whether the fix list is actually shrinking between runs.
- Narrow the scope to two dimensions, such as technical SEO and AI citability, when the stakeholder conversation is specific and a five-part deck would bury the point.
Frequently asked questions
Can I review the deck before it goes out?
Yes. Ask for a review gate and the mission pauses after the deck is built, sharing the Gamma link for your approval before Gmail sends anything. Teams sending to external stakeholders almost always keep this gate; teams sending to themselves usually let it flow straight through.
Where do the numbers in the deck come from?
Every figure traces to the specific tool call that produced it: crawl findings to Site Audit, citability scores to AI Visibility, link metrics to Backlinks, sending posture to Email Deliverability. Nothing is estimated to fill a slide, and any claim can be walked back to its evidence in the mission thread.
How long does a full audit take to run?
It depends on site size, since the crawl is the long pole, but the mission runs unattended from the single instruction and delivers when everything is verified. The practical difference is calendar time: work that spreads across weeks when done by hand lands as one finished deck without you touching a tool.