Are Brandloop docs public?

Yes. These docs are public and crawlable so buyers, search engines, and agents can understand Brandloop before signing in.

Are Search Console and Bing Webmaster Tools configured here?

No. This code documents the setup boundary. Provider-side verification is separate and should be recorded only after checking those accounts directly.

Docs

Brandloop public documentation

Brandloop docs explain the public product surface without requiring a sign-in. They cover Brand DNA, developer contracts, MCP boundaries, security, provider connections, and measurement setup boundaries for search and agent evaluation.

Public reference

https://brandloop.app/docs

Agent-readable index

Start with the product loop

Brandloop starts with reviewed brand context, then uses that context for campaign generation, approval, assets, calendar planning, and developer automation.

Brand DNA is the reviewed source of truth for generation.
Generated content stays reviewable before scheduling or publishing.
Developer and agent workflows use Brandloop contracts, not raw provider credentials.

Measurement setup boundary

Code can expose crawlable pages, sitemap entries, robots rules, and referral-safe links. Provider-side setup for Google Search Console, Bing Webmaster Tools, crawler logs, and privacy-friendly analytics still has to be verified separately.

Search Console and Bing are provider account setup tasks.
ChatGPT referral analysis depends on server or analytics readbacks for `utm_source=chatgpt.com` and referral domains.
Browser analytics scripts remain consent-gated and are not enabled by these docs.

Machine-readable resources

Agents can use visible pages plus `/llms.txt`, `/product.md`, `/pricing.md`, `/security.md`, `/comparison-data.json`, `/developers/api`, and `/openapi.json` for public evaluation.

Limitations and boundaries

These public docs do not expose private app routes, customer data, provider secrets, service-role credentials, or billing mutation paths.
Public docs are not a compliance attestation, security audit, or proof that provider-side webmaster tools are configured.
Robots rules and sitemap entries are crawler hints and discovery aids, not authorization controls.

Common questions

Are Brandloop docs public?: Yes. These docs are public and crawlable so buyers, search engines, and agents can understand Brandloop before signing in.
Are Search Console and Bing Webmaster Tools configured here?: No. This code documents the setup boundary. Provider-side verification is separate and should be recorded only after checking those accounts directly.

Continue with related references

APIScoped API keys, the implemented OpenAPI contract, and distribution boundaries.MCPAgent workflow boundaries for MCP clients and automation.Brand DNAHow source-backed brand context becomes reviewed rules.WebhooksWebhook boundaries, private callbacks, and future events.SecurityPublic-safe security, privacy, and crawler boundaries.Provider connectionsHow Brandloop separates product flows from provider access.llms.txtOptional agent-readable index for public resources.PricingVisible catalog-backed plan and credit information.