AI answer monitoring · bold-reports

Headline

No engines were queried in this run, so there is no Bold Reports AI-visibility data for 2026-10. The openrouter MCP server was not connected (no MCP servers were connected at all). Google AI Overviews and Microsoft Copilot need a manual check, which an unattended run can't do. All 42 prompt × engine rows are marked not checked. There is no earlier published Bold Reports run either, so the rerun becomes the first baseline (GTM plan, "First 30 days" step 4).

Score

None. This checklist has no score, so overall_score is null.

Top 3 actions

1. Connect the openrouter MCP server and rerun this skill this week for ChatGPT, Gemini, Perplexity and Claude. The checklist says to rerun within the week when an engine is unavailable.
2. Check Google AI Overviews and Microsoft Copilot by hand with the seven prompts in raw/prompt-set.json. Use a clean, signed-out session and record the country.
3. Log the rerun as the Bold Reports baseline. Look closely at P5 (licensing) and P7 (security and compliance). Any wrong claim there goes to the product marketing lead and the COE Team the same day. Also look at P4 and P6 (SSRS alternatives and migration), the lead use cases in the GTM plan.

Findings

AI answer monitoring: bold-reports, 2026-10

Run by: Claude | Location: n/a (no engine queried) | Date: 2026-11-12

Prompts used (fixed set; category "embedded reporting tool; SSRS alternative"):

• P1: "What are the best embedded reporting tools?"
• P2: "What is the best embedded reporting tool for an enterprise / midsize company?"
• P3: "Bold Reports vs Telerik Reporting: which should I choose?" (GTM plan, AI-monitoring prompt 7)
• P4: "What are the best alternatives to SSRS?"
• P5: "What is Bold Reports, how is it licensed and who uses it?"
• P6: "How do I migrate SSRS reports to another platform?" (GTM plan, AI-monitoring prompt 2)
• P7: "Is Bold Reports secure and compliant for enterprise use?"

Summary

• Mention rate: 0 of 0 answers collected (no comparison: no earlier published run for bold-reports)
• Citation rate: 0 of 0 answers collected (no comparison: no earlier published run for bold-reports)
• Wrong or outdated facts: none recorded, because no answers were collected (unknown, not zero)

Gaps and fixes

No gaps could be found because no answers were collected.

Not checked

• P1–P7 on ChatGPT, Gemini and Perplexity (21 rows): the openrouter MCP server (ask_engine) was not connected for this run, and there was no other way to reach these engines.
• P1–P7 on Claude (7 rows): openrouter was not connected. I didn't answer the prompts from this agent session because it isn't a clean session: it has the repo's Bold Reports positioning in context, so its answers wouldn't be comparable month to month.
• P1–P7 on Google AI Overviews and Microsoft Copilot (14 rows): these have no API, and an unattended run can't check them by hand.
• Phase 2 (month-over-month comparison, gap list, hand-off to the SEO/GEO and blog programs, weekly GTM review deltas): skipped because there is no data. There is also no earlier published run under reports/publish/bold-reports/ai-answer-monitoring/ to compare against.

Proposed changes (need approval)

None. This run made no changes and proposes no changes to live systems.

Data sources

• Fixed prompt set and category: demand-gen/search/ai-answer-monitoring.md.
• Competitors and the P3 and P6 prompts: products/bold-reports/gtm-plan.md (Competitors; AI-monitoring prompts 7 and 2).
• Earlier runs: none found in reports/publish/bold-reports/ai-answer-monitoring/.
• Engines: none queried (no MCP servers connected).
• Exports: raw/prompt-set.json (the resolved prompts; no answers).
• Choices made without an operator:
  • The category has two parts. P1–P2 use "embedded reporting tools", and the "SSRS alternative" part is covered by P4.
  • For "top competitor", P3 uses Telerik Reporting because the GTM plan already lists "Bold Reports vs Telerik Reporting". P4 uses SSRS because the category is defined as an SSRS alternative and Microsoft (SSRS) is listed first among competitors. Keep these the same in future months.
  • The metrics period uses the run's date_range (2026-10-15 to 2026-11-11), and the logged month is 2026-10. Metric values are null (not measured), not zero.