This article covers brand tracking, mention data, visibility scores, and QUEST reports. ## ⚠️ Error 1: Brand tracking shows zero mentions after setup **What's happening:** QUEST runs on a schedule — data doesn't appear instantly after setup. **Steps to try:** - Wait 24–48 hours after initial setup before expecting results. - Confirm brand tracking is enabled: **Left Sidebar → AI Visibility → Check the brand tracking is active.** - Check that your **Brand Vault** is fully populated — **QUEST** uses it to identify relevant mentions: **More Features → Brand Vault → Open Your Vault or Click + Create a Brand Vault.** If your Brand Vault data (e.g., social profiles or business info) appears incorrect after autofill, manually review and correct all fields before running QUEST, as autofill can occasionally pull data from similarly-named domains or alt-TLD twins. - Try tracking your product category rather than just your brand name to confirm QUEST is working. Add a broader category-level term (e.g., "SEO software" or "project management tool") as a tracking term under **Left Sidebar → AI Visibility → Tracking Settings**. A working result means at least one mention appears in the tracking dashboard within 24–48 hours of adding the term. - Contact support if tracking still shows zero results 72 hours after setup for a well-known brand. ## ⚠️ Error 2: QUEST analysis fails with an error message **What's happening:** An LLM provider (OpenAI, Gemini, Claude, Perplexity) was temporarily unavailable when the analysis ran. **Steps to try:** - Wait 10 minutes and try again — LLM provider availability fluctuates. - Try with fewer queries in a single run — we recommend 5–10 queries per run, as batches of 20+ have a higher failure rate. The query count is configured in the AI Visibility (formerly LLM Visibility) analysis settings before starting a run. - Try a different LLM provider if a provider selector is available. - If AI Visibility (formerly LLM Visibility) fails to load data across multiple projects simultaneously, skip standard browser troubleshooting (clearing cache, incognito mode) and contact support immediately, as this typically indicates a backend issue requiring engineering action. - Contact support with the exact error message if the analysis consistently fails. ## ⚠️ Error 3: My visibility score seems too high or too low **What's happening:** AI Visibility (formerly LLM Visibility) is highly query-dependent and varies significantly between providers. **Steps to try:** - Use the provider filter to see your score broken down by individual LLM (ChatGPT, Claude, Gemini, Perplexity). Cross-provider variance of 20–40% is normal — each model is trained on different data and surfaces different brands. - Review the actual mention examples — QUEST shows the real LLM responses where your brand appeared. - Compare trends over time rather than a single snapshot. - Add more varied query types to your tracking — visibility is only as accurate as the queries you're testing. - No action needed if the score matches the mention examples — cross-provider variance is normal. ## ⚠️ Error 4: Topic suggestions never generate **What's happening:** Topic suggestion generation involves live LLM queries and depends on your Brand Vault being populated. **Steps to try:** - Wait up to 3 minutes — topic suggestions are slower than static analysis. - Confirm your Brand Vault has substantive content in all sections. - Complete at least one brand tracking analysis before requesting topic suggestions. - Refresh and try again. - Contact support if topic suggestions have never worked on your account. ## ⚠️ Error 5: QUEST monthly report stays "Generating" **What's happening:** Monthly reports aggregate large amounts of mention data and take time. **Steps to try:** - Allow up to 2 hours — monthly reports are resource-intensive. - Ensure you have at least 2 weeks of tracking data before generating a monthly report. - Try generating a 7-day report first to confirm the feature works. - Refresh after 2 hours and check the report status again. - Contact support if generation has been in progress for more than 4 hours. ## ⚠️ Error 6: Competitor visibility shows 0% for all competitors **What's happening:** Competitor data takes time to populate after being added. **Steps to try:** - Wait 24–48 hours after adding a competitor — this is the standard data population window. - Verify competitor names are entered exactly as they're known to AI tools — use formal brand names, not abbreviations. - Test with a well-known global brand (e.g., "HubSpot") to confirm competitor tracking is working. - Confirm competitor tracking is included in your plan. - Contact support if a well-known competitor shows zero data after 72 hours. ## ⚠️ Error 7: QUEST is tracking the wrong brand — mentions belong to a different company **What's happening:** Your brand name is ambiguous and matches another well-known brand. **Steps to try:** - Add brand disambiguation in Brand Vault: **More Features → Brand Vault → Business Info** — include your industry, founding year, and what makes you unique. - Add more specific query variations that include your industry: "What is [Brand] the SEO tool?" instead of just "[Brand]." - Review captured mentions and use the Exclude option on off-topic mentions. - Contact support with examples of incorrect mentions — our team can adjust your tracking configuration. ## ⚠️ Error 8: Scheduled QUEST reports aren't arriving by email **What's happening:** Emails may be going to spam or the notification address needs updating. **Steps to try:** - Check spam for emails from our **Intercom chat** (click the messenger icon — type **Human Teammate** when Voodoo responds to reach a human agent). - Add our **Intercom chat** (click the messenger icon — type **Human Teammate** when Voodoo responds to reach a human agent) to your safe senders list. - Confirm notifications are enabled in your account settings and that the notification email on file is correct. - Verify the report schedule is active and hasn't been paused. - Contact support if scheduled reports continue to be missed after these steps. ## ⚠️ Error 9: Cited pages fail to load / stuck on spinner for large brands **What's happening:** This is a known loading issue affecting high-citation-volume brands in **Site Explorer → AI Visibility (formerly LLM Visibility)**. The cited pages panel can stall on the spinner when there are too many citations to render. **Steps to try:** - Apply a shorter date range filter (e.g., last 7 days instead of last 30/90 days) if a date filter is available — narrowing the result set usually allows cited pages to load. - Refresh the page and wait a few minutes for the panel to populate. - If you see a **"Domain not found"** error for a domain that appears elsewhere in Search Atlas, this is a known routing issue — contact support with the exact domain name for manual resolution. - Contact support with your domain if the spinner persists beyond a few minutes. ## ⚠️ Error 10: I see a quota / no-access error for a brand I am already tracking **What's happening:** You may see a "No available quota for AI Visibility (formerly LLM Visibility) Analysis" message even on a brand you are actively tracking. This is usually a quota-routing issue where the UI resolves your session to a non-tracked sibling project instead of the brand you're trying to view. **Steps to try:** - Navigate directly to the brand's AI Visibility (formerly LLM Visibility) URL rather than entering through the project switcher. - Confirm the brand is present in your tracked projects list. - **Note:** Purchasing OTTO top-ups increases your LLM analysis quota but does **not** increase the number of sites/projects you can track with AI Visibility (formerly LLM Visibility). Site-count limits are determined by your subscription plan — contact support or upgrade your plan to track additional sites. - Contact support if the error persists on an actively tracked domain — they can provide a direct corrected link to your brand's AI Visibility (formerly LLM Visibility) page. ## ⚠️ Error 11: "Competitor management is only available for user-tracked projects" **What's happening:** This error typically appears when quota routing resolves your session to a sibling project that is not in your tracked list, even though the brand you're trying to manage competitors for is tracked. The competitor management UI then refuses the action because the resolved project doesn't qualify as user-tracked. **Steps to try:** - Open the brand's AI Visibility (formerly LLM Visibility) page via its direct URL and retry the competitor action from there. - Confirm the brand appears in your tracked projects list. - Contact support to request a direct corrected link to your brand's AI Visibility (formerly LLM Visibility) page if the error persists. ## **Additional Notes** Locate the [Analyze query] button at the top-right of the Authority → PR Distribution → QUEST dashboard to trigger a fresh scan. Also retry during off-peak hours (early mornings, late evenings, or weekends) to avoid OpenRouter queue overload. If scans fail repeatedly after 2 hours or multiple projects fail simultaneously, contact support.