Why teams search for this
Brand and SEO workflows can contain sensitive launches, competitor plans, customer context, and internal priorities that should not leak into public surfaces.
BrandWatch keeps public marketing content, private dashboard data, and operational integrations separated by design.
Use cases
| Use case | Need | BrandWatch action |
|---|---|---|
| Private dashboard | Keep workspace data behind authentication | Use the protected dashboard surface |
| Client operations | Respect confidential client context | Separate brand workspaces and access paths |
| Procurement review | Understand readiness posture | Review privacy, terms, and contact paths |
Workflow
- 1
Use public pages for product education.
- 2
Keep live workspace data in authenticated app routes.
- 3
Review privacy and legal terms before onboarding.
- 4
Route enterprise questions through sales or support.
- 5
Keep secrets in environment variables and platform secret stores.
Why BrandWatch fits
Private app routes
Dashboard pages are excluded from the sitemap and marked noindex.
Privacy policy
The site documents collection, retention, rights, and security posture.
Cloudflare deployment
The app is deployed on Cloudflare Workers with explicit bindings.
FAQ
Are dashboard pages public SEO pages?
No. Dashboard routes are intentionally noindex and excluded from the public sitemap.
Where should security questions go?
Use the contact page or security email listed in the privacy policy for specific security questions.