Audience documentation
How Audience finds the topics worth writing about, judges them against your business, and carries the ones you approve to a reviewed draft.
Most content teams know they should publish more. The hard part is knowing what. Audience reads your website, your search data and your market, finds the topics worth writing about, judges each one against what you actually sell, and carries the ones you approve through research, outline, draft and review. The agent doing the work is called Scout. You make every decision that matters: which topics move forward, whether the outline is right, whether the draft goes out.
Start with
- What Audience does: the problem it solves and what stays with you.
- How Scout works: the loop from a topic to a reviewed draft.
- Set up your workspace: from a website address to a full queue.
- Reading the opportunity queue: what a score means and how to decide.
- Draft review: the screen where you approve or send back.
How the docs are organised
- Start here: what Audience is, how it works, the words it uses, and who does what.
- Set up: the five setup steps, the integrations and inviting your team.
- Home: the weekly briefing.
- Opportunities: what Scout found and how you decide.
- Content: research, outline, draft and review.
- AI visibility: what assistants say when your buyers ask.
- Playbook: what Scout believes about you and the rules it writes to.
- Reports: outcomes, page performance and operations.
- Automation and activity: what Scout does on its own, and when.
- Settings and administration: workspaces, members, integrations and your account.
- Reference: glossary, questions people ask, and reading these docs with a language model.
For language models
Every page is available as plain Markdown by adding .md to its address. The whole site is indexed at /llms.txt and reproduced in one file at /llms-full.txt. See Reading these docs with a language model.