Analyze a competitor’s strengths
Find a competitor’s strong topics and changing visibility, then inspect answers and citations to select an opportunity.
When to use this workflow
“Where is competitor A gaining, and where can we catch up?”
Before fetching
Resolve the competitor to a brand ID and fix the owned brand, platform, dates, and shared prompt cohort. A tracked competitor set does not represent the whole market.
Complete the CLI quickstart and confirm the workspace with orc workspace current --json. Replace example IDs, URLs, dates, and settings. Apply only approved mutations.
1. Resolve competitors and the prompt cohort
Read brands, topics, and prompts to establish a comparable cohort.
orc brands list --json
orc topics list --json
orc prompts list --json2. Compare brands within each topic
Fetch brand rows for the same topic and dates. Repeat for comparison periods, then read answers around material changes. Interpret brand rows as mentioned comparison brands, not prompt owners.
orc reports visibility get --scope topic --scope-id YOUR_TOPIC_ID --dimensions brand --metrics visibility_rate,mention_count,share_of_voice --date-range '{"period":"7d"}' --json
orc answers list --topic-id YOUR_TOPIC_ID --json3. Inspect the supporting answers and sources
Read complete answers for the competitor’s winning prompts and inspect source gaps. A cited source is evidence to investigate, not proof of what caused growth.
orc answers get YOUR_ANSWER_ID --json
orc sources gaps list --jsonDeliverable
Deliver winning topics, comparison periods, answer IDs, source URLs, and feasible opportunities with reasons.
On fetch failure, retain the error and request scope. Do not count empty data, incomplete pagination, or missing permissions as a completed investigation.
Next steps
If a failure remains, report it and verify the fix, including this workflow and the failed step.