Common setup mistakes
The setup problems that most often skew GetIntel's AI visibility numbers, how to spot each one in your account, and how to fix it fast.
A few setup problems account for most numbers that look wrong. Check these first; each takes a minute.
1. The wrong country
Section titled “1. The wrong country”Symptom: competitors you have never heard of, or answers that talk about another market.
Why: questions are asked from your market’s country. A UK business measured from the US sees US answers.
Fix: pick the right market during setup. On Pro and Growth, change it in Settings → Markets; questions are rewritten for the new market on the next scan.
2. Competitors that aren’t really rivals
Section titled “2. Competitors that aren’t really rivals”Symptom: a leaderboard led by huge brands you don’t compete with, or a real rival missing.
Why: competitors are found automatically from the brands AI names and from sites that rank for the same things as yours. Adjacent brands can slip in.
Fix: in Competitors, remove brands that aren’t rivals and Add competitor for any that are missing.
3. A vague product description
Section titled “3. A vague product description”Symptom: buyer questions that feel generic or off-target.
Why: your questions and topics are built from your product profile. A thin description produces thin questions.
Fix: in Settings → Product & audience, describe what the product does, who it is for and the problems it solves. Then Add prompt for any question your buyers really ask that is missing.
4. Judging scores on day 1
Section titled “4. Judging scores on day 1”Symptom: a topic swings a lot between the first days.
Why: topic scores use a rolling 7-day window, and early on there are only a few answers behind them.
Fix: wait for a full week before comparing. See Your first week.
5. Expecting Claude on Pro
Section titled “5. Expecting Claude on Pro”Symptom: no Claude column.
Why: Claude is included on Growth only, and refreshes weekly.
Fix: nothing is broken. Upgrade to Growth if Claude matters to your buyers.
6. A Cloudflare token without the right access
Section titled “6. A Cloudflare token without the right access”Symptom: AI crawlers stays empty after connecting, or shows “Last sync failed”.
Why: the token needs both Zone · Analytics · Read and Zone · Zone · Read, limited to your site’s zone.
Fix: create a new token with both permissions and choose Use a different token. See Cloudflare.
7. An MCP token for the wrong brand
Section titled “7. An MCP token for the wrong brand”Symptom: your agent reports another brand’s data.
Why: an MCP token only sees the brand that was selected when it was created.
Fix: switch to the right brand, create a new token and update your agent’s config. See Connect over MCP.