What Agents are for
- Draft page fixes and FAQ blocks so answer engines can cite you
- Write a blog article from a monitoring signal + a competitor URL
- Pull live page, citation, and visibility data into a run
- Hand finished work to an Opportunity for placement and Apply
Live templates
Coming next: competitor-gap brief, content refresh, and blog-pillar inject.
Those stay labeled until they run for real.
Typical flow
- From an Opportunity, press Run with Agent — that builds a ready-to-run Agent from the plan (page + buyer question). Or open Optimize → Agents and pick a template.
- Confirm the Start inputs.
- Run. Steps light up as scrape, scorecard, LLM, and delivery finish.
- Review the output. Execute handoff writes back to the same Opportunity. Hub templates create a new one. Slack delivery is optional on the End node.
Canvas
The canvas is linear: Start → middle nodes → End. You can insert or remove middle steps (scrape, scorecard, Visibility Score, web search, prompt probe, LLM, conditions). Visibility Score pulls the same Monitoring appearance / share-of-voice numbers you see on Overview. Pick a metric, a date range (with timezone), and optional engine / region / competitor filters. It does not invent a composite score. Downstream nodes can read{{visibility_snapshot}} (JSON) or
{{visibility_score}} (the number).
Ends today:
Apply for a page fix still runs from the Opportunity after you approve
placement — not from a Deploy button on the canvas.