Brand Context and Website Crawler
The context layer that makes Octo smarter about your brand: a crawler you point at your properties, plus the context you add. That includes brand guidelines, audience notes, catalog, partner rules, policies, technical notes, and legal paper, all of which Octo reads before every proposal.
Brand context is everything Octo knows about your company before it proposes anything. The website crawler reads your properties and extracts the brand kit, page types, categories, content sources, sign-in, and partners. It keeps them current on a schedule.
This capability arrives as a proposal when your network needs it, filled in from your brand context, and goes live when you confirm it. It's part of Octo, and Octo operates your Brand Control Center: Octo proposes, you approve explains how context shapes each proposal.
When to use it
Start on day one. The more Octo knows, the closer its first proposal is to what you'd have built. Re-crawl after a redesign or a catalog change.
| Context you add | Example | What it shapes |
|---|---|---|
| Audience notes | "Our listeners are first-time home buyers" | Classification and the hub layout |
| Partner rules | "No competitors of X" | The partner edges Octo proposes in Add brand partners and demand partners |
| Technical notes | "We use a cookie named x on web and a JWT in the app" | The auto login exchange, written against your real setup |
| Policies | Legal constraints and past incidents | Moderation and guidelines |
| Legal paper | MSAs, DPAs, and procurement rules | Agreement drafts, with conflicts flagged before your legal team sees them |
| Brand guidelines | A PDF or a link | Captions, titles, and partner-facing copy |
How it works
- The crawler reads only properties you approve. Page types and categories it learns per site are what your grid is drafted from, as Register your placements on the Hierarchical Grid shows.
- Octo writes a brand summary from the crawl and the context you add.
- Every approval and inline edit teaches Octo too.
- Context sources are set per brand. In a Business Account with several brands, they're shared across brands where you allow it.
Set it up
Octo proposes the crawl with these steps already done. You review the result and confirm it.
- Under Brand > Context, choose Crawl my site and approve the properties to crawl. Octo proposes a schedule: daily for news, weekly for catalogs. Connect your website, app, and podcast feed covers how properties are verified.
- Add guidelines, audience notes, partner rules, policies, and technical notes as files, links, or plain text. Octo confirms what it learned in one paragraph.
- Review Octo's brand summary and correct it. Corrections are weighted above the crawl.
Settings
| Setting | What it controls |
|---|---|
| Crawl scope | Which verified properties the crawler reads |
| Crawl schedule | How often each property is read again |
| Context sources | What each brand's context includes, and whether brands in your Business Account share it |
| Infer or ask | What Octo can infer on its own and what it must ask you |
Change all four under Brand > Context, which also holds Technical notes, Policies, Partners, and Legal.
What it reports
Octo reports what it knows and how that changed its work. How Octo gets smarter explains the loop.
- Context coverage score: a score for how complete Octo's context is.
- Proposals changed by context: the proposals your context shaped.
- Re-crawl history: when each property was crawled again.
- What Octo learned this week: a weekly summary of new context.
Connect your systems
Brand context and the crawler run in Brand Control Center and need no code. For your integration, Environments, credentials, and test data covers the environments and credentials your developers use.
The context and crawl calls in the Business Account API are proposed, not live. Live API today and the Business Account API roadmap maps what you can call now to what's planned.
