[Bots] Update Business Insights documentation

[Julez14]

Summary

• Rename Attribution Business Insights to Business Insights across the documentation, dashboard route metadata, and release notes.
• Define Outcome, Allowed, Blocked, and Partially blocked using HTTP response status semantics.
• Clarify that outcomes do not identify configured mitigations and direct investigations to Security Analytics.
• Add a permanent redirect from /bots/attribution-business-insights/ to /bots/business-insights/.
• Changelog coverage is included in [Bots] Rename Attribution Business Insights in launch changelog #32261.

Screenshots (optional)

Not included. This PR updates documentation to match the current dashboard terminology and behavior.

Validation

• pnpm run check
• pnpm run build
• pnpm exec tsm bin/validate-redirects.ts

Documentation checklist

• There is a companion changelog update in [Bots] Rename Attribution Business Insights in launch changelog #32261.
• The change adheres to the documentation style guide.
• Files which have changed name or location have been allocated redirects.

[cloudflare-docs-bot]

Review

💡 2 suggestions found in commit eb6057a.

👉 Fix in your agent 👈

Fix the following review findings in PR #32260 (https://github.com/cloudflare/cloudflare-docs/pull/32260).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.

The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.

---

## Code Review

### Suggestions (1)

#### CR-278ea3ee8fe1 · Potential duplicated or renamed feature documentation
- **File:** `src/content/docs/bots/business-insights.mdx` line 3
- **Issue:** The new page documents "Business Insights" with crawl-to-referral ratios, Cloudflare's updated bot classification taxonomy, and Allowed/Blocked/Partially blocked outcomes. These are the same capabilities described elsewhere as "Attribution Business Insights" (/bots/attribution-business-insights/) in the changelog, release-notes, and dashboard routes.
- **Fix:** Confirm whether Business Insights is a rename of Attribution Business Insights. If so, update or redirect the existing page and reconcile references in changelog/release-notes; if they are separate dashboards, clarify the distinction so users do not encounter two similarly named docs for the same feature.

---

## Style Guide Review

### Suggestions (1)

#### SG-d5c127f3bf14 · Use `refer to [link]` instead of `see [link]`
- **File:** `src/content/docs/bots/business-insights.mdx` line 40
- **Issue:** Line uses 'See [Verified bot classifications] for more information.'
- **Fix:** Replace with 'For more information, refer to [Verified bot classifications](/bots/concepts/bot/verified-bots/).'

Code Review

This code review is in beta and may not always be helpful — use your judgment.

Suggestions (1)

File

Issue

bots/business-insights.mdx line 3

Potential duplicated or renamed feature documentation — The new page documents "Business Insights" with crawl-to-referral ratios, Cloudflare's updated bot classification taxonomy, and Allowed/Blocked/Partially blocked outcomes. These are the same capabilities described elsewhere as "Attribution Business Insights" (/bots/attribution-business-insights/) in the changelog, release-notes, and dashboard routes. Fix: Confirm whether Business Insights is a rename of Attribution Business Insights. If so, update or redirect the existing page and reconcile references in changelog/release-notes; if they are separate dashboards, clarify the distinction so users do not encounter two similarly named docs for the same feature.

Conventions

_{No convention issues found.}

Style Guide Review

Suggestions (1)

File	Issue
bots/business-insights.mdx line 40	Use refer to [link] instead of see [link] — Line uses 'See [Verified bot classifications] for more information.' Fix: Replace with 'For more information, refer to Verified bot classifications.'

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit	Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review	Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.
/rebase	Rebases the PR branch against production. On conflict, attempts to resolve automatically using AI. Stops with an explanation if confidence is not high enough.

[jinhee-c-lee]

lgtm, includes redirects and name updates