Home 🛠️ Troubleshooting

🛠️ Troubleshooting

Camilo Aponte
By Camilo Aponte
• 62 articles

🤖 Search Atlas — AI Visibility (QUEST) Issues

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.

Last updated on Oct 26, 2026

🤖 Search Atlas — AI Visibility (QUEST) Troubleshooting

QUEST monitors how large language models mention and position your brand across AI-generated responses. This guide resolves scan failures, missing brand mentions, topic generation errors, and snapshot data gaps — including the automated backfill introduced in LLMV-460 for the May 12–18, 2026 incident. QUEST queries multiple AI systems and analyzes brand mentions, topical authority, sentiment, response frequency, and AI-generated positioning. Because results depend on third-party LLM providers, asynchronous query queues, and evolving AI training datasets, visibility scores can fluctuate over time and across providers. ⚠️ Error 1: QUEST Scan Not Completing — "All Submissions Failed" What's happening The OpenRouter AI submission queue (or upstream LLM provider) is overloaded. This high-severity queue failure appears most often during traffic spikes or large multi-query scans. Brands with many tracked entities, competitors, or broad topic coverage require significantly more processing time. Steps to try 1. Wait 30–60 minutes before retrying. 2. In the left sidebar, click Authority > PR Distribution > QUEST (AI Visibility). On the QUEST dashboard, locate the [Analyze query] button at the top-right of the page and click it to trigger a fresh scan. 3. Reduce the number of simultaneously tracked topics. 4. Avoid launching multiple QUEST scans at the same time. 5. Refresh the QUEST dashboard after restarting the scan. 6. Verify your internet connection remained stable during submission. 7. Check whether other AI-dependent modules are also slow. 8. Retry during off-peak hours: early mornings, late evenings, or weekends. Contact support if: - Scans fail repeatedly after 2 hours. - Multiple projects fail simultaneously. - Scans never move beyond "queued" status. - The failure persists after 24 hours, or a scan never progresses past 0%. Important notes - QUEST depends on third-party LLM provider availability. - Queue overload does not indicate account corruption. - Larger scans naturally require more processing time. - If a scan fails mid-run, LLMV-460's snapshot-gap detection automatically schedules a backfill for any missing days once the queue recovers — no manual action required. ⚠️ Error 2: Brand Mentions Not Appearing After a Successful Scan What's happening Your brand may be too new, insufficiently referenced online, or not yet strongly represented in current LLM training data. QUEST only reflects what AI systems already know or infer about your brand — it does not fabricate results. Steps to try 1. Confirm your brand has indexed content, backlinks, citations, and public mentions online. 2. Complete your Brand Vault fully: go to More Features → Brand Vault and add your company description, products/services, website URL, industry, and audience information. 3. Expand your tracked topic list and use broader query phrasing temporarily. 4. Add branded and non-branded topic combinations. 5. Publish additional blog content, PR mentions, social profiles, and directory citations. 6. Run scans again after new content gets indexed. 7. Compare visibility across different LLM providers. Known Issue — Resolved (Competitor Mentions) Between approximately early May 2026 and the LLMV-453 fix date in mid-May 2026, a parser bug in the CompetitorList component caused competitor brand mentions to be silently dropped when certain AI providers (notably meta-llama/llama-3.1-8b-instruct via OpenRouter) returned a top-level JSON array instead of the expected wrapped object format. This has been fixed. If your competitor data still appears incomplete for that window, run a manual rescan to repopulate the affected mentions. Contact support if: - Established brands consistently show zero mentions. - Scans return completely empty datasets. - Competitor mentions remain missing after a manual rescan. Important notes - QUEST does not fabricate brand visibility. - Newer brands naturally have weaker AI visibility footprints. - AI Visibility (formerly LLM Visibility) evolves gradually over time. ⚠️ Error 3: Topic Generation Fails or Returns Irrelevant Topics What's happening QUEST generates topic suggestions using AI, based on your brand and industry context. If generation fails or returns off-target results, the AI likely has insufficient brand context — most commonly because Brand Vault is incomplete or the brand category is too generic. Steps to try 1. Go to More Features → Brand Vault and verify all brand details are complete and accurate. 2. Add a specific industry category and a detailed audience description. 3. Manually enter topics that are directly relevant to your brand. 4. Remove overly broad topic suggestions and replace them with niche-specific queries. 5. Re-trigger topic generation after updating your Brand Vault. Contact support if: - Topic generation consistently fails after multiple attempts. - All generated topics are entirely unrelated to your industry. Important notes - Topic quality improves as your Brand Vault information becomes more complete. - Manually curated topics typically perform better than auto-generated ones for niche brands. 📅 Snapshot Gaps in Share-of-Voice and Sentiment Trend Lines What's happening A snapshot gap is a missing data point in your Share-of-Voice (SoV) or sentiment trend charts — caused by a queue outage, LLM provider downtime, or a scan that stalled without fully recovering. Before LLMV-460, these gaps were permanent and required manual intervention. LLMV-460: Automated Backfill (no action required) LLMV-460 ships an automated snapshot-gap detection and backfill mechanism. When the system detects a missing snapshot day, it automatically schedules a date-constrained Celery backfill task scoped to the affected date range. Your trend lines self-heal — no manual intervention needed. May 12–18, 2026 incident Between May 12 and May 18, 2026, the QUEST snapshot pipeline experienced a queue stall that interrupted daily snapshot generation for some projects. Affected customers would have seen missing daily data points, flat-lined visibility scores, or zero-data days in their SoV and sentiment trend lines during that window. LLMV-460's automated backfill will fill confirmed gaps within 24–48 hours depending on current queue load. If your data still looks wrong after backfill completes, contact support. Known limitation (LLMV-489, fix in release) For days within the May 12–18 window where a scan failed and an automatic retry is still pending, the gap-detection sweep may have scheduled a backfill concurrently with the live retry. This race condition can produce low-fidelity backfilled data alongside the retry result. If your data for those specific days still looks incomplete after 24 hours, contact support so an engineer can verify backfill vs. retry state for your account. Report Builder data alignment (RB-1252, resolved late May 2026) If you are embedding AI Visibility (formerly LLM Visibility) data in a Report Builder report and the numbers differ from the standalone QUEST dashboard, this was caused by a date-range and filter bug — the AI Visibility (formerly LLM Visibility) topic widget applied an unconditional +1 day offset to the end date and used an overly broad query_type filter. The bug is now fixed. Regenerate or refresh any saved Report Builder reports created before the late-May 2026 fix to get aligned figures. OpenRouter platform list cleanup (May 2026) If OpenRouter previously appeared in your tracked AI platforms list and is now absent, this was corrected automatically as part of a data cleanup in May 2026 — OpenRouter is the upstream routing layer and was never an intentionally selectable platform in QUEST. What you'll see during backfill - Affected date ranges appear as "Processing" in the QUEST dashboard until backfill completes. - Trend lines update automatically once backfill finishes — no manual refresh needed. - Backfilled scores reflect actual LLM response data, not interpolated values. Contact support if: - Gaps from May 12–18, 2026 are still visible after 48 hours. - New gaps appear outside a known outage window. - Trend lines show data but values appear inconsistent. - Report Builder numbers still disagree with the standalone QUEST dashboard after regenerating the report. 🎯 You now know how to resolve the most common QUEST issues — from scan queue failures and missing brand mentions to snapshot gaps that self-heal via LLMV-460's automated backfill. For questions about Brand Vault setup or LLM provider coverage, contact the Search Atlas support team.

Last updated on Oct 26, 2026

📊 Understanding 0% Visibility vs. Missing Data in AI Visibility Results

A 0% score in AI Visibility (formerly LLM Visibility) means your brand was not mentioned by that AI platform during the snapshot period. A dash or empty cell in that same column means the platform was unavailable and no data was collected — not that your visibility was zero. 📊 What a 0% Visibility Score Means When AI Visibility (formerly LLM Visibility) shows 0% for a platform, that platform responded successfully and returned results — but your brand did not appear in any of those responses during the snapshot period. A genuine 0% is an actionable signal: - The platform (for example, ChatGPT, Gemini, or Perplexity) was queried and returned responses. - Your brand was not cited or mentioned in any of those responses. - You have a confirmed visibility gap for that platform that content and optimization work can address. ⚠️ What Missing Platform Data Looks Like When a platform was unavailable during a snapshot — due to an outage, a provider failure, or no successful responses being collected — the dashboard displays a dash (—) or blank cell instead of a number. A missing-data indicator means: - The platform did not return usable results for that snapshot. - No visibility score — positive or zero — could be calculated. - The result is excluded from aggregated totals so it does not skew your overall visibility percentage. A dash is a data gap, not a performance measurement. Do not treat it as evidence that your brand visibility dropped. 💡 Why This Distinction Matters for Your Analysis Treating a data gap as a 0% result leads to incorrect conclusions: - False alarm: You may think a platform stopped mentioning your brand when it was simply offline for one snapshot cycle. - Skewed trend lines: If a collection failure were counted as 0%, your overall visibility trend would appear to drop even though no real measurement was taken. - Misdirected effort: Optimizing content for a platform that was merely unavailable wastes resources until accurate data confirms a genuine gap exists. Search Atlas separates these two states so your trend lines and aggregated scores reflect real brand mentions only — never unfilled data gaps. 🛠️ Common Causes of Missing Platform Data A platform entry shows missing data when any of the following occur during a scheduled snapshot: - Provider outage: The LLM provider (for example, OpenAI, Google, or Perplexity) experienced downtime during the snapshot window. - Data-collection failure: An upstream collection service experienced an error and could not retrieve responses for that platform during the snapshot run. - No successful response: The platform returned errors or rate-limit responses for every query attempt in that snapshot, leaving no usable data to score. These events are outside your control. Search Atlas retries failed snapshots automatically where possible and shows a missing-data indicator when no retry succeeded. 📋 What to Do When a Platform Shows No Data 1. Check adjacent snapshots. Open the date range picker and review the snapshots immediately before and after the gap. If neighboring periods show normal scores, the gap is an isolated collection failure — not a visibility trend. 2. Compare across platforms. If multiple platforms show missing data on the same date, a broader outage likely affected that entire snapshot, not just one platform. 3. Wait for the next scheduled snapshot. Search Atlas collects new platform data on your configured snapshot schedule. Once the next snapshot completes successfully, that platform's score updates automatically. 4. Contact Support if gaps persist. If a platform consistently shows missing data across multiple consecutive snapshots, contact the Search Atlas support team so they can investigate the collection pipeline for your account. You do not need to change any settings or trigger a manual snapshot — data collection resumes automatically on the next scheduled run. 🎯 You can now tell the difference between a genuine 0% visibility result and a platform data gap, so your optimization decisions are always based on real brand-mention data — not collection failures. For next steps, review your AI Visibility (formerly LLM Visibility) trend report to identify platforms where your brand consistently scores 0% and where content improvements will have the most impact.

Last updated on Oct 26, 2026

🔧 Fixing the "Query Failed - Creating Query Failed" Error in QUEST AI Visibility

If you use QUEST AI Visibility (formerly LLM Visibility) to track how your brand appears across AI assistants, you may occasionally see a "Query Failed - Creating query failed" error when adding or running a query. This message means the query could not be created or processed. In most cases, the cause is straightforward and can be fixed in a few minutes. This article explains why the error happens and walks you through the steps to resolve it. 🤔 Why This Error Happens The "Creating query failed" error usually appears for one of these reasons: - Formatting issues in the query text, such as unsupported characters, emojis, or extra line breaks. - A query that is too long or too short, falling outside the accepted character range. - Duplicate queries that already exist under the same topic in your project. - Plan or quota limits have been reached for the number of queries allowed. - The project or workspace is not fully set up (for example, a missing brand name, domain, or region). - The analysis timed out — very broad or complex queries can take a long time to process, and the request to the AI provider may time out and return a failure after an extended "analyzing" period. - A temporary connection issue between QUEST and the AI provider. 🛠️ How to Fix It Work through the steps below in order. Most customers resolve the issue within the first three steps. 🔄 Step 1: Refresh and Try Again 1. Refresh your browser page. 2. Re-enter the query and click Create or Run again. Many failures are caused by a brief, temporary connection issue, and a simple retry often resolves it. However, if a query keeps failing, avoid submitting it many times in a row: each failed attempt can use a query credit, and repeatedly retrying the same failing query can create duplicate entries. If one or two retries don't work, move on to the steps below or contact support rather than retrying repeatedly. ✍️ Step 2: Check Your Query Text 1. Remove any emojis, special symbols, or unusual punctuation. 2. Delete extra spaces and line breaks so the query is a single, clean sentence. 3. Make sure the query is a clear, natural-language question or phrase (for example, "What are the best project management tools?"). 4. Confirm the query is not too short (a single word) or excessively long, as queries that exceed the accepted length are a known rejection reason. 🔍 Step 3: Look for Duplicates 1. Open your list of existing queries in the project. 2. Confirm the query you are trying to add does not already exist under the same topic. 3. If it does, edit the existing query instead of creating a new one. ⚙️ Step 4: Confirm Your Project Setup 1. Open your QUEST AI Visibility (formerly LLM Visibility) project settings. 2. Make sure required fields are complete in Create Project (Settings → Use the new project setup experience), including Website domain, Market Location, and Language. 3. Save any changes, then try creating the query again. 📊 Step 5: Review Your Plan Limits 1. Check how many queries you have used against your plan's allowance. 2. If you have reached your limit, remove unused queries or upgrade your plan. 3. If a series of failed attempts seems to have reduced your available queries faster than expected, note this and contact support (see below) so we can review your account. 📨 If the Error Continues If you have completed all the steps above and the error still appears, please contact our support team so we can investigate further. To help us resolve your issue quickly, include the following details: - The exact query text you are trying to create. - The name of the project or workspace where the error occurs. - A screenshot of the error message. - The date and approximate time the error appeared. - The browser you are using. You can reach us through the in-app chat or by emailing our support team. Providing the information above allows us to reproduce the issue and respond faster. If repeated failed attempts have reduced your available queries, let our team know — we can review your account and restore query credits that were consumed by failed attempts. 💡 Tips to Prevent Future Failures - Keep queries clear, concise, and written in plain language. - Avoid copying text directly from formatted documents, which can carry hidden characters. - Keep queries focused rather than overly broad, since very large or complex queries are more likely to time out during analysis. - Periodically review and clean up unused queries to stay within your plan limits. - Complete all project setup fields before adding queries. Following these practices helps ensure your QUEST AI Visibility (formerly LLM Visibility) queries run successfully every time.

Last updated on Oct 26, 2026

🚧 Fixing the "No Available Quota for AI Visibility Analysis" Error

❓ What this error means The message "No available quota for AI Visibility (formerly LLM Visibility) Analysis" appears when every AI Visibility (formerly LLM Visibility) project slot included in your plan is already in use. Each plan includes a set number of slots (for example, 4), and the system blocks new analyses once all of them are occupied. This error is about project slots (how many AI Visibility (formerly LLM Visibility) projects you can track at once), not about LLM scan credits (which power each scan). Running out of credits can silently stop scheduled scans, but it does not produce this message. The most common point of confusion is this: you may see only 2 active projects on your dashboard but still be told that all 4 slots are taken. This almost always means that one or more slots are being held by projects that are not currently visible to you. 🔍 Why slots can be "used" when projects aren't visible A slot stays reserved as long as a project is attached to it, even if that project isn't shown in your main view. The usual causes are: - Archived or paused projects. Projects you archived still hold their slot until they are fully deleted. - Per-country versions of the same domain. AI Visibility (formerly LLM Visibility) tracks a separate project for each country (plus a "Worldwide" scope) for a given domain, and each tracked scope uses its own slot. Your dashboard usually shows only the project that matches your account's country, so siblings tracked under other countries can occupy slots without appearing in your main view. - Duplicate projects for the same domain. In some cases more than one tracked project can exist for the same domain on your account. Each duplicate consumes a slot, and the domain may not open from the project list (it may instead prompt you to create the project again). - Projects removed from Site Explorer or Keywords. Removing a domain from your Site Explorer or Keywords list does not always release its linked AI Visibility (formerly LLM Visibility) slot, so the project can stay tracked in the background and keep its slot. - Projects in another workspace or organization. If your account has access to more than one workspace, slots may be consumed by projects created elsewhere. - Projects created by a teammate. A colleague on the same plan may have set up projects that don't appear in your personal filtered view. - Recently deleted projects still releasing. When a project is deleted, its slot can take a short time to free up. - Filtered or hidden views. An active search, label, or status filter on your dashboard can hide projects that are still counted against your quota. 🕵️ How to find the hidden projects Follow these steps to locate every project consuming a slot: 1. Open the AI Visibility (formerly LLM Visibility) section from the left-hand menu. 2. Clear any active filters, labels, or search terms so that all projects are shown. 3. In OTTO SEO → All Sites (SEO Automation), switch the status tab to Active or Deep Frozen so paused and archived projects appear. 4. Check the AI Visibility (formerly LLM Visibility) module directly rather than relying on the Site Explorer label. A domain that already has an active project may still show "Add to LLM" in Site Explorer; opening the AI Visibility (formerly LLM Visibility) section confirms the true status. (A recent fix improved this indicator, so make sure you are on the latest version.) 5. If you belong to more than one workspace, use the workspace switcher at the top to check each one. 6. Count the total number of projects across all statuses and workspaces. This number should match your plan's slot limit. 🧹 How to free up a slot Once you have found the projects using your quota, choose the option that fits your needs: 🗑️ Delete a project you no longer need 1. Locate the project in the list (including archived ones). 2. Open its settings or use the action menu next to it. 3. Select Delete and confirm. 4. Wait a few moments for the slot to release, then create your new analysis. 🔄 Replace an existing project If all of your projects are still in use but priorities have shifted, delete the lowest-priority one to make room for the new one. Export any historical data you want to keep before deleting, as removal is permanent. 🔑 Restore access to a workspace slot If a slot is held in another workspace you can't see, ask the workspace owner or admin to delete the project there, or to grant you access so you can manage it. ♻️ Reclaim a slot held by a hidden or duplicate project Some slots are held by projects you cannot currently see or delete yourself — for example a per-country or "Worldwide" version of a domain, a duplicate of a domain that won't open from the list, or a project that stayed tracked after you removed the domain from Site Explorer or Keywords. These are known issues our team is actively addressing, and several related fixes have already shipped. If you suspect one of these is consuming a slot, contact support so we can untrack the hidden project and free the slot for you. 4️⃣ Using the 4th slot you are paying for If your plan includes 4 slots, all 4 are available to you, but a slot only becomes usable when no project is attached to it. To open the slot: - Confirm the true project count using the steps above (remember archived, per-country, and cross-workspace projects all count). - Delete or replace one project so the total active count drops below your limit. - Create your new AI Visibility (formerly LLM Visibility) analysis. The error should no longer appear. If you have confirmed that you have fewer projects than your plan allows and the error still appears, the slot may be stuck in a releasing state, or your quota may not be reading correctly. A known issue that caused the system to report a "maximum of 0" projects despite a correct quota has been resolved; if you still see the error after dropping below your limit, contact support. 📞 When to contact support Reach out to our support team if: - You have verified that your total project count (across all statuses and workspaces) is below your plan limit, but the error persists. - You cannot see or delete a project that appears to be using a slot — such as a per-country version of a domain, a duplicate, or a project that remained after you removed the domain from Site Explorer. - A deleted project has not released its slot after a reasonable wait. - You believe your plan should include more slots than are currently showing. To help us resolve the issue quickly, include your account email, your plan name, a screenshot of the error, and the names of the projects you can see.

Last updated on Oct 26, 2026

🔓 How to Free Up an AI Visibility Project Slot in Search Atlas

Delete an AI Visibility (formerly LLM Visibility) project to release its quota slot immediately. If the counter stays locked after deletion, follow the troubleshooting steps below or contact support for a manual reset. ⚙️ Option 1 — Delete an LLM Project (Immediate Slot Release) Deleting a project releases its LLM slot right away. Use this option whenever you need the slot freed immediately. Navigation: Search Atlas → OTTO SEO → Site Explorer / LLM Projects 1. Go to OTTO SEO → Site Explorer / LLM Projects. 2. Select the project you want to remove. 3. Click the three-dot menu (⋮). 4. Select Delete Project. 5. Confirm deletion. Once deleted, the LLM slot is available for a new project immediately. ❄️ Option 2 — Deep Freeze an LLM Project (14-Day Delay) Deep Freeze preserves your SEO data but does not release the LLM slot right away. - The project is frozen and SEO changes are preserved. - The LLM slot is released after 14 days. - The slot is not available immediately. If you need the slot freed right away, delete the project instead of using Deep Freeze. ⏱️ Why Your Quota May Still Show as Full After removing a project, you may still see all LLM slots used for any of these reasons: - The project was deep frozen, not deleted — the slot releases only after 14 days. - The 14-day Deep Freeze release window has not passed yet. - The page has not refreshed to reflect the updated quota. - Another hidden or archived project is still consuming a slot. - The quota counter is stuck due to a backend sync issue (see below). 🔄 Steps to Take When Slots Still Appear Full 1. Refresh your browser and revisit OTTO SEO → Site Explorer / LLM Projects. 2. Confirm the project was deleted, not deep frozen. 3. Check that no other sites are still assigned to LLM projects. 4. Wait a few minutes for the quota counter to update. 5. Log out and back in, then re-check the quota counter. If the slot is still occupied after completing all five steps, the quota counter is likely stuck — see the section below. 🛠️ Stuck LLM Quota After Deletion (Known Issue) In some cases, the AI Visibility (formerly LLM Visibility) quota counter stays locked at its maximum (for example, 2/2 used) even after you delete all LLM projects. When this happens: - You cannot add a new domain to AI Visibility (formerly LLM Visibility). - Existing projects may show partial or degraded functionality. - Refreshing, waiting, and re-logging in does not release the slots. This is a backend sync issue. Our technical team must manually reset your LLM quota. Once reset, you can add new projects immediately. 🚨 When to Contact Support Contact support if all of the following are true: - The project was fully deleted (not deep frozen). - No other LLM projects exist on your account. - The quota still shows all slots used after refreshing and waiting several minutes. Support will escalate to the technical team for a manual quota reset. To speed up resolution, include: - Your account email. - The domain(s) you are trying to add. - A screenshot of the quota counter showing it as full. - Confirmation that you deleted (not deep frozen) all previous projects. ❓ Frequently Asked Questions I removed a site — why didn't my LLM slot free up? The site was most likely deep frozen instead of deleted. Deep Freeze only releases the slot after 14 days. Delete the project to free the slot immediately. Does removing a Site Explorer project always free LLM quota? Yes, if the project is fully deleted. My LLM quota shows 2/2 (or full) even though I deleted all my projects — what do I do? This is a known stuck-quota issue. Contact support and reference the Stuck LLM Quota After Deletion section above. The technical team will manually reset your quota. How many LLM projects can I have? The number of LLM projects available depends on your plan's LLM quota. 🎯 You now know how to delete an AI Visibility (formerly LLM Visibility) project to free a slot immediately, how Deep Freeze differs from deletion, and how to escalate a stuck quota counter to support for a manual reset.

Last updated on Oct 26, 2026

⚠️ Grok Data Unavailable in AI Visibility — Active Issue

Grok ranking and visibility data in AI Visibility (formerly LLM Visibility) has returned 0% results since May 23, 2026, because xAI blocked our data provider's access to Grok. Your historical Grok data through May 23 remains accessible in the dashboard, and no action is required from you. 🔍 What's Happening with Grok in AI Visibility Since May 23, 2026, all Grok tracking in AI Visibility (formerly LLM Visibility) displays empty or broken results. This is not a configuration error on your account — xAI has blocked our data provider's access to Grok at the source, creating a complete data gap from that date forward. Search Atlas is removing Grok from AI Visibility (formerly LLM Visibility) tracking (see LLMV-593). This means: new Grok data cannot be collected, and Grok will be progressively removed from platform selection menus in Brand Insights, Prompt Simulator, and other dashboards. Your historical Grok data through May 23, 2026 will remain in archived reports for reference. Who is affected: Pro and Agency plan customers who currently track Grok in AI Visibility (formerly LLM Visibility). If Grok is not part of your tracking setup, your dashboard is unaffected. 🛠️ Workaround Steps No workaround is currently available. Because xAI's block is enforced at the data-provider level, Search Atlas cannot retrieve new Grok ranking or visibility data. You will not be able to add new Grok platforms to your tracking setup going forward. You do not need to take any action in your account settings. Your historical Grok data through May 23, 2026 remains fully accessible in archived reports and can continue to be used for reference and historical reporting. 📡 Engineering Status Our team is aware of this issue and is actively working to communicate the change to all affected Pro and Agency accounts. We are monitoring xAI's access policies and will restore Grok coverage if data-provider access becomes available again. This article will be updated when the status changes. 📞 When to Contact Support You do not need to contact support for this known issue — it affects all Pro and Agency accounts tracking Grok and is already being addressed. Reach out to support if: - AI Visibility (formerly LLM Visibility) shows errors or empty data for non-Grok models (ChatGPT, Gemini, Perplexity, Claude, etc.) - Your historical Grok data before May 23, 2026 is missing or inaccessible in the dashboard - You have billing questions related to Grok coverage on your plan 🌀 Your historical Grok data is preserved, your other AI Visibility (formerly LLM Visibility) tracking is fully operational, and our team is actively managing this change — affected Pro and Agency accounts will be contacted directly with further details.

Last updated on Oct 26, 2026

⚠️ AI Visibility — Active Service Disruption and Workaround

We are aware of an active issue affecting the AI Visibility (formerly LLM Visibility) module. Some customers are seeing a "Failed to fetch data, contact support" error and significantly delayed analysis results. Our engineering team has identified the root cause and has deployed a fix — the workaround below can help while the service fully stabilizes. 🔍 What's Happening The AI Visibility (formerly LLM Visibility) module is experiencing a service disruption that affects data retrieval and analysis processing. This impacts any customer using AI Visibility (formerly LLM Visibility) to run or review analysis during the active outage window. This was caused by a temporary capacity constraint with our LLM provider. We have deployed improved handling to prevent recurrence. Symptoms - A "Failed to fetch data, contact support" error appears in the AI Visibility (formerly LLM Visibility) module. - The module spins or loads for 10 minutes or more without returning results. - Analysis results are delayed or entirely unavailable. - The module may intermittently self-recover, then fail again shortly after. 🛠️ Workaround Steps Follow these steps in order to minimize disruption while the service is being restored: 1. Wait 10–15 minutes. The service may self-recover intermittently. Keep the tab open and allow the module time to load on its own before retrying. 2. Perform a hard refresh. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to reload the AI Visibility (formerly LLM Visibility) module and bypass your browser cache. 3. Do not trigger new analysis runs. Starting additional runs during the outage adds to the processing backlog and may delay recovery further for all customers. 4. If the error persists beyond 20 minutes, contact our support team (see below) so we can flag your account for priority resolution once the fix is deployed. 📡 Engineering Status Our engineering team has identified the root cause of this disruption and has deployed a fix (LLMV-592). This issue began on May 29 and was resolved by June 8. This article will be updated as the fix is rolled out. We sincerely apologize for the disruption and appreciate your patience while we work to restore full service. 📞 When to Contact Support Reach out to our support team if any of the following apply: - The "Failed to fetch data" error persists for more than 20 minutes after completing the workaround steps. - The AI Visibility (formerly LLM Visibility) module does not recover after a hard refresh and the full waiting period. - You have time-sensitive analysis needs that cannot wait for the service to self-recover. When you contact us, mention the AI Visibility (formerly LLM Visibility) outage so our team can prioritize your account for resolution as soon as the fix goes live. 🌀 Our engineering team has deployed a fix to resolve this disruption — we appreciate your patience and will update this article as progress is made. If the workaround does not help or you need immediate assistance, please reach out to our support chat and type "Human Teammate". One of our human agents will take care of the issue.

Last updated on Oct 26, 2026

🛠️ Inconsistent Decimal Places in AI Visibility Scores

This article explains a known cosmetic display issue in the AI Visibility (formerly LLM Visibility) tab where some scores show more decimal places than others, and confirms that a fix is already in progress. Your visibility and sentiment data is accurate and needs no action from you. 🔍 What's Happening in the AI Visibility Tab In the AI Visibility (formerly LLM Visibility) tab, visibility and sentiment scores display with inconsistent decimal precision on the same screen. The two card groups round numbers differently, which can make them look like they measure different things. 📊 Where the Difference Appears - Top mini-cards — Overall Visibility Score, Overall Sentiment, and Citations Found show whole numbers or one decimal place, such as 0, 65.9 %, or 2.4K. - Platform breakdown cards — Visibility by Platform and Sentiment by Platform, along with the delta and pts change indicators, show three decimal places, such as 49.138 or ↓ 7.013 pts. 👥 Who Is Affected This affects anyone viewing the AI Visibility (formerly LLM Visibility) tab. It is a display-only formatting issue: the extra decimals add false precision and visual noise, but the numbers themselves are correct. ✅ Your Data Is Accurate This issue only changes how the numbers are formatted on screen. The underlying visibility and sentiment data is calculated correctly and is unaffected. You can continue to rely on the values shown, including the platform scores and the points-change indicators. 🛠️ Workaround Steps No workaround is needed. Because this is a cosmetic formatting issue and the data is accurate, there are no steps to apply on your end. You can keep using the AI Visibility (formerly LLM Visibility) tab as normal. 📡 Engineering Status Our team is aware of this display issue and a fix is already in progress, awaiting release. The update will standardize every score across the visibility and sentiment cards to a single decimal place, so the top mini-cards and the platform breakdown cards match. Once the fix ships, values like 49.138 will display as 49.1. 📞 When to Contact Support You do not need to contact support for the decimal formatting itself, since it is a known issue with a fix on the way. Reach out to our support team only if you notice a separate problem, such as a score that appears clearly incorrect or data that fails to load. 🌀 Rest assured, our team is on it. The fix to standardize all AI Visibility (formerly LLM Visibility) scores to one decimal place is queued for release, and your visibility and sentiment data remains accurate in the meantime.

Last updated on Oct 26, 2026

📊 AI Visibility Data for Copilot Requires a Collection Period

After upgrading to Pro and enabling Copilot in AI Visibility (formerly LLM Visibility), your platform is correctly configured — Search Atlas just needs 2–3 weeks of data collection before trend statistics can appear. Note: Grok has been removed from AI Visibility (formerly LLM Visibility) due to upstream access restrictions by xAI — refer to the removal-notice banner in-product for the latest status. 📊 Why Copilot Data Is Not Showing After Your Pro Upgrade When you enable a new LLM platform in AI Visibility (formerly LLM Visibility), Search Atlas begins collecting data immediately — but it cannot generate trend statistics until enough historical data has accumulated. Platforms that have been tracked for months already have the data depth needed to produce reports; newly enabled platforms do not. This is expected behavior, not a bug or a misconfiguration. ⏳ How Long the Data Collection Period Takes AI Visibility (formerly LLM Visibility) requires 2–3 weeks of continuous data collection before meaningful trend statistics appear for a newly enabled platform. During this window: - Tracking is active and running in the background — no data is lost for supported platforms. Data collection depends on upstream data-vendor access and may be subject to change if a provider restricts access. - All data collected during the waiting period will be included in your reports once the threshold is reached. - Platforms you were already tracking before your Pro upgrade may show data sooner because they have had more time to accumulate history. If trend cards appeared blank immediately after enabling a platform and before the collection window elapsed, this was a known display bug that has since been fixed. If you still see blank cards after 2–3 weeks, contact support. ⚙️ How to Confirm Copilot Is Enabled Correctly Verify that your new platform is toggled on so tracking runs while you wait: 1. Go to Settings in your Search Atlas account. 2. Open the AI Visibility (formerly LLM Visibility) section. 3. Confirm that Copilot is enabled. If Copilot appears as enabled, your setup is correct. Data will appear automatically once the 2–3 week collection period is complete — no further action is needed. If data has not appeared after 3 weeks, contact support. ⚠️ If Data Does Not Appear After 3 Weeks If data has not appeared after 3 weeks, or if you see a platform removal notice in-product, the platform may no longer be supported. Contact support for current platform availability. 🎯 You now know that the 2–3 week data collection period is a normal part of onboarding any new LLM platform in AI Visibility (formerly LLM Visibility). Once that window passes, Copilot will appear in your reports alongside your other platforms — check back then to begin analyzing your trend data.

Last updated on Oct 26, 2026

⚠️ Grok Display Issue: Coverage Ended May 23, 2026

Grok coverage in Search Atlas ended on May 23, 2026, but a display issue causes Grok to remain visible across several product surfaces where it will return no data. One fix (platform status updates) has been deployed; frontend fixes are in progress and will ship soon. Follow the steps in this article to avoid empty results and misconfigured projects. 🔍 What's Happening Grok data collection was discontinued on May 23, 2026. A display issue currently prevents the platform from fully removing Grok from its interface. The following behavior is expected and does not indicate a problem with your account or data: - Brand Insights card: A Grok row appears but will remain permanently empty — no data will ever populate it. - LLM Settings drawer: Grok appears as an option you can enable for a project. Enabling it will silently produce no data. - TopicsDrawer platform filter and LLM tabs: Grok is listed as a selectable platform, but no results will be returned for it. - Prompt Simulator: Grok appears as a selectable LLM option but produces no output when selected. - Pricing page: Grok-related imagery or references may appear, but Grok tracking is discontinued and is not available on any plan tier. All account types are affected by the display issues listed above. 🛠️ Workaround Steps Until the fix is deployed, follow these steps to prevent empty results or wasted project configuration: 1. Brand Insights: When viewing your Brand Insights, you may see a Grok data row. This row will remain permanently empty and will not populate with any data. You can safely disregard it when reviewing your insights from other sources. 2. LLM Settings: Do not enable Grok tracking on any project, as it will not generate data regardless of your account plan. Continue using other available LLM options for your projects. 3. TopicsDrawer and Prompt Simulator: When using the TopicsDrawer or Prompt Simulator, do not select Grok as a platform or LLM option. Exclude Grok from your platform filters and simulator sessions to ensure your results remain accurate. 4. Pricing page: If you see Grok-related information on the pricing page, note that Grok tracking is discontinued on all plan tiers. Do not make plan changes based on Grok availability. 📡 Engineering Status One platform status fix has been deployed. Our engineering team is actively working to remove Grok from all affected frontend surfaces (Brand Insights, LLM Settings drawer, TopicsDrawer, Prompt Simulator, and the pricing page). Your existing data, project configurations, and tracked keywords are not affected. This article will be updated once all fixes are deployed. 📞 When to Contact Support Reach out to our support team if any of the following apply: - You enabled Grok tracking before May 23, 2026, and want to confirm whether historical Grok data was captured for your projects. - You see behavior on your account beyond what is described in this article. 🌀 Our team is actively removing Grok from all platform surfaces in an upcoming release — the workaround steps above will keep your Brand Insights, LLM Settings, Prompt Simulator, and TopicsDrawer results accurate in the meantime.

Last updated on Oct 26, 2026

⚠️ LLM-Powered Analysis Features Stuck in Pending State

We are aware of an ongoing issue affecting LLM-powered analysis features — brand research, brand info, topics, queries, and competitor analysis — that began around May 29. Analyses may appear stuck in a pending or loading state and will not return results; no action is needed on your end. 🔍 What's Happening Since approximately May 29, the LLM analysis pipeline that powers several Search Atlas features has been interrupted. Affected features display results as permanently pending or loading with no output delivered. The following features are currently affected: - Brand Research - Brand Info - Topics - Queries - Competitor Analysis If you submitted any of these analyses on or after May 29, your job is queued and will be processed automatically once service is restored. You do not need to re-submit. 🛠️ Workaround Steps There is currently no workaround available for this issue. Do not re-submit your analyses — resubmitting will not resolve the problem and may create duplicate entries in the processing queue. All queued analyses will run automatically when the pipeline is restored. 📡 Engineering Status Our engineering team is investigating the root cause and is actively working to restore the pipeline. All analyses submitted since May 29 will be processed once service resumes — no data or requests will be lost. This article will be updated as soon as the fix is deployed and results begin delivering to affected accounts. We will provide an estimated timeline as soon as we have more information. 📞 When to Contact Support Reach out to our support team via the in-app chat if any of the following apply: - You have a time-sensitive deadline that cannot wait for the pipeline to restore. - You see no resolution or status update after 24 hours. - You are experiencing a separate issue not described on this page. When you contact support, include your account name and the date you submitted the affected analysis so the team can assist you faster. 🌀 Our team is fully engaged on restoring the pipeline and will process all queued analyses as soon as service resumes — we sincerely apologize for the disruption and appreciate your patience.

Last updated on Oct 26, 2026

LLM Visibility Sentiment Widget Fixed

The Sentiment widget in LLM Visibility has been updated to display corrected data. If you are seeing different numbers than before, or if something looks unexpected in the Sentiment section, this article explains what changed and what to do. What Changed Prior to this fix, the percentages shown in the Sentiment section were not calculated as a share of responses. The previous calculation method meant the figures could be inconsistent and did not reliably represent your brand's sentiment distribution. The widget has now been updated so that the percentages reflect the share of brand-mentioning responses per sentiment category, and the values across all categories will sum to 100%. As a result of this correction, the numbers you see now may look different from what was previously displayed. This is expected — it reflects the corrected calculation, not a change in your brand's actual sentiment performance. If Something Still Looks Wrong If after this update you are still seeing data that appears incorrect, inconsistent, or unexpected in the Sentiment section of LLM Visibility, take the following steps: 1. Refresh your browser and reload the LLM Visibility dashboard to ensure you are seeing the latest data. 2. Check whether the issue persists across different date ranges or filters. 3. Note what you are seeing — for example, percentages that do not appear to add up, or topics that seem to be categorized incorrectly — so you can describe it clearly when contacting support. 4. Reach out to our team directly using the steps below so we can investigate your specific account. What to Expect Going Forward The fix has been applied automatically and is live for all users. No action is required on your part to receive the update. If your data looks different than before, that is the result of the corrected calculation method now in place. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🐛 LLM Visibility Quota Shows Exhausted Incorrectly

Overview Some users see a "Quota Exhausted" error in LLM Visibility even though they have not filled all their allocated project slots. For example, you may have 3 active projects out of 4 allowed, yet the platform reports your quota as fully consumed. This is a known bug that affects certain accounts. The issue requires a fix applied directly to your account by our support team. What Causes This A backend bug can cause your LLM Visibility quota display to fall out of sync with your actual project usage. As a result, your quota may appear fully consumed even when you are within your plan's limits. How to Resolve It 1. Confirm the mismatch. Count how many LLM Visibility projects you have actively running and compare that number to the quota limit on your plan. If your active project count is lower than your plan limit but your quota still shows as exhausted, you are likely affected by this bug. 2. Check for duplicate or stuck projects. Review your project list for any entries that appear duplicated, are stuck in a pending or activating state, or were created more than once due to a failed setup attempt. Note the names and statuses of any suspicious projects, as this information will help the support team identify the root cause faster. 3. Do not delete active projects as a workaround. Removing legitimate projects is not necessary and may cause you to lose tracking history. 4. Contact support to request a quota reset. Because this issue requires a backend fix applied directly to your account, reach out to our support team and describe the mismatch you are seeing — your active project count versus the quota limit on your plan. Include any duplicate or stuck project names you identified in the previous step. The support team will escalate to engineering to correct your quota balance. 5. Confirm the fix is applied. After the support team processes your request, verify that you can now create or access projects up to your plan limit and that any quota exhaustion error is no longer displayed. If the error persists after the team confirms the fix, reply in the same support thread so the team can investigate further. What Happens After the Fix Once the support team applies the fix to your account, your quota balance will update to reflect your real usage. You will regain access to your remaining slots and any incorrect exhaustion errors will disappear. Tips to Avoid Confusion in the Future - If you see a quota exhaustion message unexpectedly, always compare the number of projects you can see in your project list against your plan's limit before taking any action. - Avoid creating the same project multiple times if a setup step appears to fail — this can contribute to quota tracking issues. Wait for confirmation before retrying. - If a project appears stuck during activation or returns an unexpected error, contact support before attempting to recreate it. Need Further Help? If your quota still shows as exhausted after reviewing the steps above, contact our support team directly via the live chat widget in the bottom-right corner of the platform — type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🛠️ Stale 'Ask' Results After Deleting BrandVault Images, Videos, or BrandVaults

If you deleted or edited a BrandVault image, video, or an entire BrandVault and still see it referenced in your 'Ask' (bv_ask) AI search results, this is a known issue with a fix already in our release pipeline. This article explains what is happening and how to get your account flagged for follow-up. 🔍 What's Happening in BrandVault 'Ask' Search BrandVault's 'Ask' feature (bv_ask) uses stored content chunks to generate AI answers. When you delete or modify certain assets, some of those chunks can be left behind, so the 'Ask' results still reference content that no longer exists or has changed. You may notice one or more of the following: - Deleted content still appears: images, YouTube videos, or whole BrandVaults you removed are still cited in 'Ask' answers. - Outdated or broken references: 'Ask' results point to assets you already modified, showing stale details. - Duplicate references after alt text changes: regenerating an image's alt text can surface two results that point to the same asset. Who Is Affected This affects customers who use the BrandVault 'Ask' (bv_ask) AI search feature and who have recently deleted or edited BrandVault images, videos, or BrandVaults, or regenerated image alt text. 🛠️ Workaround for Stale BrandVault 'Ask' References There is no self-serve workaround available at this time. Deleting or re-editing the asset again will not clear the orphaned reference, because the leftover chunk needs to be removed on our side. The upcoming fix will clear these orphaned references automatically once it ships, so no manual cleanup will be required from you. 📡 Engineering Status for the BrandVault 'Ask' Cleanup Fix Our team is aware of this issue and a resolution is already in the release pipeline. The fix will automatically clean up the orphaned content chunks left behind after BrandVault image, video, or BrandVault deletions and alt text regeneration. After the fix ships, deleted and modified content will stop appearing in your 'Ask' results, and duplicate references from alt text changes will be removed. 📞 When to Contact Search Atlas Support Reach out to our support team if the stale 'Ask' results are actively affecting your work and you would like priority follow-up. We can flag your account so it is reviewed once the fix is released. When you contact us, please include: - The BrandVault name where you see the stale results. - Whether the affected content is an image, a video, or a full BrandVault. - An example 'Ask' query that returns the outdated or duplicate reference. You'll receive confirmation that your account has been flagged for follow-up. 🎯 Your team isn't alone on this — we're actively on it. The fix to clear these orphaned BrandVault 'Ask' references is on the way, and reaching out to support ensures your account is reviewed as soon as it ships.

Last updated on Oct 26, 2026

⚠️ AI Visibility Charts Error on "Last 1 Year" Date Range

The AI Visibility (formerly LLM Visibility) report shows a loading error on Visibility Trend, Platform Insight, Average Sentiment Score, and Sentiment Comparison by Platform charts when the "Last 1 year" date range is selected on high-volume accounts. Switching to a shorter date range loads the charts successfully. 🔍 What's Happening Selecting "Last 1 year" in the AI Visibility (formerly LLM Visibility) report triggers the error "Something unexpected happened while loading your data" on these charts: - Summary tab: Visibility Trend and Platform Insight - Sentiment tab: Average Sentiment Score and Sentiment Comparison by Platform This only affects accounts with high data volumes. Shorter date ranges — such as "Last 90 days" or "Last 30 days" — load successfully for all affected accounts. 🛠️ Workaround Steps Follow these steps to load your AI Visibility (formerly LLM Visibility) charts while the fix is in progress: 1. Go to Site Explorer → AI Visibility (formerly LLM Visibility). 2. Open the affected chart: Visibility Trend, Platform Insight, Average Sentiment Score, or Sentiment Comparison by Platform. 3. Click the date range selector and choose Last 90 days (or any range shorter than one year). 4. The chart loads successfully. 📡 Engineering Status Our engineering team has completed a fix and is preparing it for release. No action is required on your end. This article will be updated once the fix is deployed. 📞 When to Contact Support The workaround above resolves the loading error for most affected accounts. Contact our support team if: - Shorter date ranges also fail to load for you. - You see this error on charts not listed above. - You require a full "Last 1 year" data export and need an alternative. 🌀 A fix is in final testing and will be released soon. We appreciate your patience and will update this article once the fix is deployed.

Last updated on Oct 26, 2026

🔍 Fix Missing AI Visibility Projects and Install the OTTO Pixel

🧭 Overview If your AI Visibility projects have disappeared from your dashboard, or if you are unable to install the OTTO pixel through Cloudflare, this article explains what happened and walks you through your available options to get back on track. ❓ Why Are My AI Visibility Projects Missing? AI Visibility projects are tied to verified OTTO pixel connections. If the pixel on your site becomes unreachable or has not been confirmed as active recently, the platform may remove or deactivate associated projects to maintain data accuracy. Common reasons this happens include: - The OTTO pixel was removed from your website or became unreachable after a site update - A plugin conflict or caching layer is blocking the pixel from being detected - The pixel was never fully verified after the initial installation attempt - Your site's DNS or proxy settings changed, causing the pixel connection to drop Once your pixel is reinstalled and OTTO is detected again, the same project is reactivated automatically with its history preserved — a new project is not created. 🛠️ How to Reinstall the OTTO Pixel Without Cloudflare Cloudflare is one installation method, but it is not the only option. If you do not have Cloudflare access, use one of the alternatives below. ⚙️ Option 1 — Install via WordPress Plugin If your site runs on WordPress, this is the recommended alternative to Cloudflare. 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (or navigate to /seo-automation-v3). 2. Open your OTTO project and locate the pixel installation section. 3. Select the WordPress Plugin installation method. 4. Install the Search Atlas (MetaSync) WordPress plugin on your site. 5. In WordPress, go to Search Atlas → Settings and paste your Search Atlas API key. 6. Paste your OTTO Pixel UUID and save. The plugin will handle the pixel installation. 7. Return to the platform to confirm the pixel status turns green. Note: If the plugin installation shows as partial or the pixel status does not update, the platform's diagnostic tool will surface the specific step that needs attention. Follow the on-screen guidance to resolve it. 💡 Option 2 — Install via AI-Assisted Prompt If you have access to an AI coding assistant or developer agent (such as ChatGPT, Cursor, or a similar tool), you can use the platform's built-in AI-assisted install path. 1. In your OTTO project's pixel installation section, click Copy AI Prompt or Open AI Agent. 2. Paste the copied prompt into your preferred AI coding tool. 3. Follow the instructions the AI provides to add the pixel to your site's code. 4. Return to the platform and check that your pixel status is verified. This method is ideal if you manage your site's code directly or work with a developer. 🖥️ Option 3 — Manual Code Installation You can add the OTTO pixel manually to your site's HTML if you have access to your theme files or a tag manager. 1. Copy your unique pixel snippet from the OTTO project settings. 2. Paste it into the <head> section of every page on your site, or use Google Tag Manager to deploy it site-wide. 3. Publish the changes and allow a few minutes for the platform to detect the pixel. 4. Refresh your OTTO project page and confirm the connection status shows as verified. ✅ How to Check Your Pixel Status After any installation method, always confirm the pixel is active before rebuilding your AI Visibility projects. - Navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar. - Open your OTTO project and review the pixel status indicator. - A green verified status means the pixel is connected and active. - If the status is pending or shows an error, use the on-screen diagnostic guidance to identify what is blocking verification. 🚀 Reactivating Your AI Visibility Projects Once your pixel is verified and OTTO is detected again, your existing AI Visibility project is reactivated automatically with its history preserved. 1. Go to AI Visibility in the left sidebar (or navigate to /llm-visibility). 2. Confirm your project is active again and review its preserved history. 3. Make sure the domain matches the site where your pixel is installed. 4. Allow time for data to resume populating. Tip: AI Visibility relies on Site Explorer data for onboarding. If your domain has not been crawled yet, initial data may take some time to appear after your project is created. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

📊 Fix Exhausted AI Visibility Report Quota

📋 Overview AI Visibility reports in Search Atlas let you track how your brand and content appear across AI-powered search engines and large language models. Each plan includes a set number of AI Visibility reports per billing cycle. When you reach that limit, the platform will show a quota exhausted message and prevent you from running additional reports until your quota resets or is upgraded. 🔍 Where to Find AI Visibility Reports To access your AI Visibility reports, navigate to the left sidebar and click AI Visibility. The direct URL is /llm-visibility. From this page you can view existing reports, create new ones, and check your current usage. ⚠️ What Does "Quota Exhausted" Mean? When your AI Visibility report quota is exhausted, it means your account has reached the maximum number of reports allowed under your current subscription plan for the active billing period. You may see a message such as "Report quota exhausted" or be blocked from generating new reports. This is a plan-level limit, not a technical error. - Reports already generated remain fully accessible — you will not lose any existing data. - New reports cannot be created until your quota resets or your plan is upgraded. - Quota limits reset automatically at the start of each new billing cycle. 🛠️ How to Resolve the Issue There are two main ways to get access to more AI Visibility reports: 1. Wait for your billing cycle to reset. Your quota refreshes automatically at the beginning of each billing period. If you are close to your renewal date, this may be the quickest option with no additional action required. 2. Upgrade your subscription plan. If you need more reports immediately or consistently hit the limit each month, upgrading to a higher-tier plan will increase your quota. To explore upgrade options, go to your account billing settings or contact our team via the live chat widget. 💡 Tips to Make the Most of Your Quota Follow these best practices to avoid hitting your AI Visibility report quota too quickly: - Prioritise high-value queries. Focus your reports on the keywords, topics, and competitors that matter most to your business goals. - Review existing reports before creating new ones. Older reports may already contain the insights you need. Check the AI Visibility section at /llm-visibility before generating a duplicate. - Schedule reports strategically. Spread your report usage across the billing cycle rather than running many reports at the start of the month. - Use the Reports section for broader analysis. For other reporting needs, navigate to Reports in the left sidebar (/report-builder/projects-list), which uses a separate quota and may have capacity available. ❓ Frequently Asked Questions Will I lose my existing AI Visibility data when the quota is exhausted? No. All previously generated reports remain visible and accessible. Only the creation of new reports is paused. Can I track how many reports I have left? Yes. Your current usage and remaining quota are displayed within the AI Visibility section. Review this periodically to plan your report usage. Does refreshing or re-running an existing report count against my quota? Re-running or refreshing a report may count as a new report generation depending on your plan. Check with our support team if you are unsure how this applies to your specific plan. What happens if I downgrade my plan? Downgrading may reduce your available quota. Any reports already created will remain accessible, but your ability to generate new reports will be limited to the lower plan's allowance. 🆘 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🔍 Fix LLM Visibility Projects Quota Overage

🧭 Overview Your LLM Visibility Projects quota tracks only the domains you have actively set up as tracked projects. Competitor domains you analyse on the fly do not count toward this limit. If your quota shows more projects used than you can find in your dashboard, one or more orphaned projects may be silently consuming a slot. An orphaned project is a project entry that still holds a quota slot even though it no longer appears as an active, visible project in your dashboard. This can happen due to a stale internal reference created during project deletion or duplication. Search Atlas engineering has resolved the underlying system bug, but you may still need to take action to free up your slots. ✅ Step 1: Count Your Tracked Projects Before taking any action, confirm exactly which domains are counted against your quota. 1. Navigate to the left sidebar → AI Visibility to view your project list. 2. Review every entry listed. Only domains you have explicitly added as tracked projects consume quota — competitor look-ups do not. 3. Write down every tracked domain you can see. Compare this number to the quota usage shown on the page. If the number used is higher than the visible projects, you likely have an orphaned project. 🗑️ Step 2: Delete Any Project You No Longer Need If you can identify a domain you no longer need to track, delete it to free up a slot. 1. In the left sidebar → AI Visibility, locate the project you want to remove. 2. Open that project's options and delete it. 3. After deleting, clear your browser cache or open a new incognito / private window and reload the page. This ensures the quota counter refreshes correctly and does not display a stale count. 👻 Step 3: If a Project Persists After Deletion (Orphaned Project) Sometimes a project appears to be deleted but continues to occupy a quota slot. This is the orphaned-project scenario. If after deletion and a cache clear your quota count does not decrease, the project reference has not been fully removed on the back end. In this situation self-service deletion is not sufficient and the orphaned slot must be cleared by the Search Atlas team. Please contact support as described at the bottom of this article so the team can locate and remove the stale reference from your account. ⚙️ Step 4: Check for Duplicate Domain Entries A known issue caused some accounts to count the same domain twice when it was saved with different country settings (for example, once with no country code and once with a country code such as "US"). If you notice what looks like the same domain appearing more than once, or if your quota is inflated by exactly one extra slot per domain, this duplication may be the cause. 1. In the left sidebar → AI Visibility, scan your projects for any duplicate domain entries that may differ on country settings. 2. Delete the duplicate entry you do not need, then clear your browser cache or use an incognito window to confirm the quota count decreases. 3. If the duplicate cannot be deleted or the quota does not update, contact support so the team can remove the stale entry on the back end. 📬 Still Need Help? If your quota overage persists after following the steps above, our support team can manually clear orphaned or duplicate project references from your account. Contact us via the chat widget in your dashboard and include the affected domain(s) and the quota count you are seeing so we can resolve it as quickly as possible.

Last updated on Oct 26, 2026

🔧 Fix LLM Tool and Topic Monitoring Access Issues

🧭 Overview If you cannot add topics to monitor AI search performance or the Search Atlas LLM tool appears locked or non-functional, the cause is almost always one of four things: your subscription tier does not include the feature, the feature has not been enabled on your account, your user role lacks the required permissions, or a setup step was missed during onboarding. This article walks you through each scenario so you can identify and fix the issue quickly. 📋 Before You Begin Gather the following information before running through the steps below. This will save time if you need to escalate: - Your current plan name and monthly cost - The email address on the account - The exact error message or behavior you see (screenshot recommended) - Whether other users on the same account have the same problem ✅ Step 1: Confirm Your Subscription Includes These Features The Search Atlas LLM tool and AI search topic monitoring are not available on all plans. These are advanced AI features included in mid-tier and above subscriptions. 1. Click your Avatar Menu (👤) in the top-right corner of the platform. 2. Select Billing from the dropdown (Plans & Top-ups tab). 3. Review the features listed under your active plan. If the LLM tool and topic monitoring are not listed, your current plan does not include them. You will need to upgrade to gain access. If you believe your plan should include these features based on what you were told at sign-up, proceed to Step 5 to escalate. 🔍 Step 2: Check Whether the Features Are Enabled on Your Account Even on eligible plans, features sometimes need to be manually enabled by the Search Atlas team after account creation. A feature can appear greyed out or return an access error even when your plan covers it. 1. Navigate to OTTO SEO → SEO Automation using the left sidebar (URL: /seo-automation-v3). 2. Look for the LLM tool and topic monitoring sections within this area. 3. If you see a message such as "Feature not available", "Upgrade to access", or the section is completely missing, the feature may not be toggled on for your account. This is a common cause of access issues for customers on newer accounts or accounts migrated from a previous plan. It requires account-side activation by the Search Atlas team — see Step 5. 👤 Step 3: Verify Your User Role and Permissions If you are a team member on a shared account, your user role may restrict access to certain features. Only account owners and administrators can access all platform features by default. 1. Ask your account owner or administrator to log in and check whether they can access the LLM tool and topic monitoring. 2. If the account owner can access the features but you cannot, your role needs to be updated. 3. The account owner should navigate to Settings → Team Members, locate your user profile, and adjust your permissions to grant access to AI features. If you are the account owner and still cannot access the features, your issue is not permissions-related — continue to Step 4. ⚙️ Step 4: Check for Common Setup Errors Run through this checklist to rule out configuration issues that frequently block access to these specific features: - No project or domain connected: Topic monitoring requires an active project with a connected domain. Go to Site Metrics → Site Explorer in the left sidebar and confirm at least one property is listed and verified. - Browser cache or extension conflict: Hard-refresh the platform (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) or try an incognito window. Some ad-blockers and browser extensions interfere with AI feature rendering. - Incomplete onboarding: If your account was recently created, some features unlock only after completing the initial setup wizard. Check for any pending onboarding prompts on your dashboard. - Workspace mismatch: If your account has multiple workspaces, confirm you are in the correct workspace where your plan and features are active. Switch workspaces using the dropdown at the top of the left sidebar. 🚨 Step 5: When to Escalate to the Billing or Account Team Escalate immediately — do not continue troubleshooting on your own — if any of the following are true: - Your plan billing page shows a charge consistent with a plan that should include these features, but the features are locked. - You were explicitly told at sign-up or by a sales representative that your plan includes the LLM tool and topic monitoring. - You completed Steps 1–4 and the features are still inaccessible. - You see a billing discrepancy or your plan details do not match what you agreed to at purchase. In these cases, our team needs to review your account configuration directly and can resolve feature activation issues or billing mismatches on the spot. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

LLM Visibility Quota Showing Fully Used Incorrectly

Overview Some accounts have encountered a bug where the LLM Visibility quota appears fully used even when no active projects exist. This false quota-exhausted state prevents users from adding new sites for tracking. The root cause is a system-level issue — not actual usage on the account. Search Atlas engineering is aware of this issue and has worked to resolve it. If you are still experiencing this problem, follow the steps below to confirm the symptoms and get it resolved. Symptoms of This Bug - Your LLM Visibility quota appears at or near 100% used. - You have no active LLM Visibility projects, or far fewer than the quota limit suggests. - You are blocked from adding new sites for tracking. - The quota usage does not decrease even after removing projects. Steps to Self-Resolve or Report the Issue 1. Navigate to the LLM Visibility section of your account and confirm whether your quota still appears fully used despite having no active projects. 2. If the quota appears incorrectly exhausted, try refreshing your browser and logging out then back in to rule out a display caching issue. 3. Check whether any recently removed projects are still reflected in your quota count. If so, wait a few minutes and refresh again, as counts can take a short time to update. 4. If the quota still shows as fully used after these steps and you are certain you have no active projects consuming it, this indicates a system-level issue that requires a manual review on your account. 5. Contact our support team via the live chat widget in the bottom-right corner of the platform — type human teammate to be connected with a member of our team. Include the following details so the team can escalate your case quickly: your account email address, the domain(s) you are trying to add, a description of what your quota display shows versus how many active projects you have, and a screenshot of the quota display if possible. What to Expect After You Contact Support When this issue is escalated, the engineering team will investigate your specific account, correct the quota data manually if needed, and confirm once your quota accurately reflects your actual usage. You will be notified when the fix has been applied so you can resume adding sites. If you have questions or are not sure whether your symptoms match this bug, reach out to our support team via the live chat widget in the bottom-right corner of the platform — type human teammate to be connected with a member of our team, and we will help you confirm and resolve the issue.

Last updated on Oct 26, 2026

Fix Duplicate LLM Visibility Project Quota Drain

🧩 What Is This Issue? Some accounts have the same website being tracked twice inside LLM Visibility — once with a specific country code (for example, US) and once with a blank or global country code (effectively a Worldwide entry). Because the platform counts each tracking entry separately, one domain ends up occupying two quota slots instead of one, which can consume up to 50% or more of your available LLM visibility quota unexpectedly. This was a confirmed platform-level bug affecting accounts across Search Atlas. Engineering resolved the root cause (ticket LLMV-770), but if you are still seeing symptoms today, follow this article to understand what happened and how to get it corrected. ⚠️ Signs You Are Affected - Your LLM visibility quota appears fully or heavily consumed, but you have fewer active projects than expected. - The same domain appears listed more than once — for example, once for a specific country and once with no country or a Worldwide label. - Your website blocks traffic from certain regions (such as non-USA visitors), yet a global or Worldwide tracking entry still exists and is counting against your quota. - Removing one entry does not free up the expected quota because a duplicate entry persists. 🔍 Why This Happens The duplication occurs when a domain is registered in the LLM Visibility system with both an empty country code ("") and an explicit country code (such as US) at the same time. The platform treats these as two separate projects even though they point to the same website. This means the domain is triggered twice during quota calculations, doubling its consumption. This affected a significant number of accounts simultaneously and was not something individual users caused or could prevent. 🛠️ What Was Fixed Search Atlas engineering resolved the underlying bug that caused duplicate tracking entries to persist. The fix addressed cases where the same domain held both a blank and a country-specific tracking record, and also cases where orphaned LLM Visibility projects were consuming quota slots despite no active reports being visible in the dashboard. If your account was affected, the duplicate entry should have been removed and your quota restored automatically as part of this fix. ✅ Steps to Take If You Still See the Problem 1. Check your current LLM Visibility quota usage. If it still appears fully consumed or higher than expected given the number of projects you have set up, the duplicate may not have been cleared for your account yet. 2. Review the list of domains currently being tracked. Look for any domain that appears more than once, especially if one entry shows a specific country and another shows a different or blank geographic scope. 3. If you confirm a duplicate entry is still present, delete the unwanted duplicate entry yourself — specifically, remove the entry that has the blank or Worldwide country scope if your site is only intended to be tracked for a specific country (or vice versa). Keep only the single entry that matches your intended geographic targeting. 4. After deleting the duplicate entry, refresh your QUEST AI Visibility dashboard and verify that your quota usage has decreased accordingly. The freed slot should be reflected in your available quota immediately or within a few minutes. 5. If both entries appear identical and you are unsure which one to remove, delete the one with the blank or empty country code, as this is the entry most commonly created erroneously by the underlying bug. 6. If after deleting the duplicate your quota still does not update, or if you are unable to delete either entry from your dashboard, contact the Search Atlas support team via the chat widget. Share the affected domain name and describe which entries appear duplicated so the team can manually clear the orphaned record and restore your quota.

Last updated on Oct 26, 2026

Fix LLM Visibility Analysis Access and Project Quota

Overview LLM Visibility Analysis gives you insight into how AI-powered search engines reference your content. If you cannot access this feature, or if your quota appears fully used despite no active reports showing, this article will help you identify and resolve the issue. If the steps below do not resolve your situation, please contact the Search Atlas support team via the chat widget in the platform. Step 1: Check Which Projects Have LLM Visibility Enabled Your account may have LLM Visibility Analysis enabled on some projects but not others. To see the status for all your sites, review your list of projects within the platform and check which ones have LLM Visibility active. This gives you a clear picture of where the feature is active and where it is not, so you can make adjustments or identify which projects are consuming your quota. Step 2: Understand Your LLM Visibility Quota LLM Visibility Analysis is subject to a project quota — meaning there is a limit to how many projects can have it active at the same time on your plan. Here are the key things to know: - Quota slots are tied to active projects. Each project with LLM Visibility enabled occupies one quota slot. - Quota may appear fully consumed with no active reports visible. If your dashboard shows all quota slots occupied but you do not see any active reports, your quota count may be out of sync and may require a manual correction by the support team. Step 3: Free Up Quota to Add a New Project If all your quota slots are occupied and you want to enable LLM Visibility on a new project: 1. Review your projects within the platform and identify which ones currently have LLM Visibility active. 2. Disable LLM Visibility for any project where you no longer need the feature. 3. Return to the project where you want to enable it and activate the feature. If disabling LLM Visibility on existing projects does not free up a slot, or if your quota counter still shows as fully consumed, this requires a manual correction by the support team. When to Contact Support Reach out to the Search Atlas support team via the chat widget in the platform if: - Your quota count does not decrease after disabling LLM Visibility on a project. - Your quota appears fully consumed but you have no active LLM Visibility reports. - You are unable to access LLM Visibility Analysis and cannot identify a cause from the steps above.

Last updated on Oct 26, 2026

🔍 Understanding LLM Visibility Data Gaps and Chart Artifacts

🧭 Overview If your LLM Visibility chart shows data before your project's first scan, a long flat line, or a sudden drop with no recovery, you are likely seeing a combination of two things: a UI display artifact and the natural consequence of when your first scan ran. This article explains both so you can interpret your data with confidence. 📅 Why There Is No Data Before a Certain Date LLM Visibility data is only generated when a scan runs. If your project was created weeks or months before its first scan was executed, there is simply no data for that earlier period — the platform has nothing to display because no scan occurred. In the example that prompted this article, a project was created in early March but was not scanned until May 5. As a result: - May 5 is the earliest real data point. - No LLM Visibility data exists for March or April, because no scans ran during that time. To find out when your project's first scan ran, review the scan history inside your project. Your earliest real data point is the date of that first completed scan. 📈 Why the Chart Shows Data Before the First Scan This is a known UI interpolation artifact. When the dashboard has only one data point — or a limited number of data points at the start of a project — it visually extends that earliest value backwards across the chart timeline. The flat line you see before your first scan date is not fabricated data and it is not a measurement of zero visibility. It is simply the chart repeating the earliest known value to fill the empty space on the left side of the graph. The same behavior can appear between scan dates: if scans were sparse, the chart carries the most recent known value forward visually until the next real scan result appears. In short: any portion of the chart that appears as a flat horizontal line before your first scan date, or between widely spaced scans, reflects this display behavior — not an actual measurement from that time period. 📉 Why the Data Dropped Sharply and Did Not Recover A sudden drop in your LLM Visibility chart — especially one that stays flat at a low value with no recovery — is most commonly explained by one of the following: - The drop marks the end of the interpolated region. When a new real scan runs after a long gap, the chart transitions from the repeated early value to the actual scan result. If real visibility is lower than the interpolated value, this appears as a sharp decline. - Scan frequency changed. If scans became less frequent or stopped temporarily, the chart may hold a low value flat until the next scan provides a new result. - A genuine change in LLM visibility. Real drops in how often AI-powered search tools surface your brand are also possible and would appear the same way on the chart. To distinguish a UI artifact from a real visibility change, check the dates of your actual scans. If the drop aligns with the first real scan after a long gap, it is likely the artifact transition point. If scans were running regularly before and after the drop, the change is likely real. ✅ How to Verify Your Real Data Points 1. Open your LLM Visibility project from Left sidebar → AI Visibility. 2. Review the scan history for your project to identify the dates on which real scans completed. 3. Cross-reference those dates with the chart. Data that falls on a real scan date is a genuine measurement. Data that appears as a flat line before or between scan dates is the UI interpolation artifact. 4. Focus your analysis on the period from your first real scan date onwards to ensure you are working with accurate information. 🛠️ What the Engineering Team Has Addressed The Search Atlas engineering team has already shipped a fix to improve how the Visibility Score chart handles projects with a single data point, reducing the visual impact of this interpolation artifact. Additional improvements to the LLM Visibility frontend are also complete. If you are still seeing unexpected chart behavior after reviewing the scan history steps above, the issue may require further investigation. 💬 Still Have Questions? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🔍 Fix Your LLM Visibility Quota Showing Zero

🧭 Overview If your LLM Visibility quota displays 0 out of 0 and you cannot create or run an LLM Visibility project, your account's LLM Visibility feature has been deactivated — most commonly due to a payment issue or a lapsed subscription that included this feature. This article explains why this happens and walks you through the steps to restore your quota. ❓ Why Does This Happen? Your LLM Visibility quota is tied directly to an active, paid plan that includes this feature. The quota drops to 0 out of 0 — rather than showing a used/remaining split — when: - A payment failed or was declined, causing your plan to deactivate. - Your subscription was cancelled or expired. - The plan you downgraded to does not include LLM Visibility. - A billing cycle lapsed before a renewal payment was processed. A quota of 0 out of 0 means the feature is not allocated to your account at all, not simply that you have used up your allowance. Re-enabling the feature requires reactivating or upgrading your plan. 🔎 Where to Find Your LLM Visibility Tools Search Atlas provides LLM Visibility access in two places. Make sure you are looking in the right location before assuming there is a billing issue: - AI Visibility dashboard: Left sidebar → AI Visibility (URL: /llm-visibility). This is the primary hub for tracking how your brand appears in AI-generated answers. - QUEST LLM Visibility (Authority): Left sidebar → Authority → QUEST LLM Visibility. This sub-tool runs targeted LLM visibility projects and reports. If both locations show a quota of 0 out of 0, the cause is almost certainly a plan or payment issue. 🛠️ How to Restore Your LLM Visibility Quota 1. Check your payment method. Go to your account's billing settings and confirm that your credit card or payment method is valid, not expired, and has sufficient funds. 2. Resolve any failed payments. If a payment failed, update your payment details and manually retry the charge. Your plan should reactivate automatically once payment succeeds. 3. Confirm your plan includes LLM Visibility. Review your current subscription tier. If you recently downgraded, your new plan may not include this feature. Upgrading to an eligible plan will restore the quota. 4. Allow a few minutes for the quota to refresh. After a successful payment or plan change, wait 2–5 minutes and then refresh your browser. The quota should update to reflect your new allowance. 5. Navigate back to LLM Visibility. Go to AI Visibility in the left sidebar or Authority → QUEST LLM Visibility and confirm your quota now shows a non-zero value. ✅ Confirming the Fix Worked Once your plan is active and payment is resolved, you should see: - Your quota updated from 0 out of 0 to a number that reflects your plan's allowance (for example, 0 out of 5). - The ability to create and run new LLM Visibility projects without hitting an access error. - All previously created projects restored and accessible in both the AI Visibility dashboard and Authority → QUEST LLM Visibility. 🚫 Common Mistakes to Avoid - Do not create a duplicate account to work around the quota issue — this will not carry over your existing project data. - Do not assume the quota resets on a daily basis. The 0 out of 0 state is a feature access issue, not a usage cap that refreshes automatically. - Do not confuse 0 out of 0 with 0 remaining. If you had, for example, a quota of 5 and used all 5, you would see 5 out of 5 used — not 0 out of 0. The latter always indicates the feature is not included in your current active plan. 💬 Still Need Help? If you have resolved your payment issue but the quota still shows 0 out of 0, or if you are unsure which plan includes LLM Visibility, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🔍 Fix LLM Visibility Data Not Updating

🔍 Overview If your LLM Visibility data has stopped updating — for example, showing no new data since a specific date — this is almost always caused by a change in your plan access. Specifically, if the QUEST LLM Visibility feature has been removed from your subscription, the tool will stop collecting and refreshing data until access is restored. ⚙️ How LLM Visibility Data Works Search Atlas tracks how your brand and content appear across large language models (LLMs) such as ChatGPT, Gemini, and Perplexity. This tracking runs continuously in the background — but only while your plan includes active access to the LLM Visibility feature. If that access lapses or is removed, data collection pauses immediately and your dashboard will reflect the last date data was successfully gathered. 🛠️ Check Your Plan Access Before troubleshooting anything else, confirm that your current plan includes QUEST LLM Visibility: 1. Log in to Search Atlas. 2. In the left sidebar, navigate to Authority → QUEST LLM Visibility. 3. If you see a prompt to upgrade or a message indicating the feature is unavailable, your plan no longer includes this tool. 4. Alternatively, go to AI Visibility via the left sidebar (URL: /llm-visibility) and check whether your dashboard shows a data gap or an access restriction notice. ✅ How to Restore Data Refreshing Once you confirm the cause, here is how to get your data updating again: - Upgrade or modify your plan: If QUEST LLM Visibility was removed from your subscription, contact our team to re-add it. Once access is restored, data collection resumes automatically — no manual action is needed. - Allow up to 24 hours: After access is reinstated, the system needs time to re-establish tracking. Your dashboard should begin showing fresh data within 24 hours. - Note on historical data: Data from the period when access was removed will not be back-filled. Tracking resumes from the point access is restored, so acting quickly minimises any gaps in your reporting. 📊 What You Will See After Access Is Restored Once your plan is updated and tracking resumes, you can expect the following: - Your AI Visibility dashboard (left sidebar → AI Visibility) will begin populating with new data points. - The QUEST LLM Visibility page (left sidebar → Authority → QUEST LLM Visibility) will show updated mention tracking, sentiment, and citation data. - Date filters and trend charts will reflect the new data as it accumulates over time. 💡 Tips to Prevent This Issue - Review your plan features periodically, especially after a billing cycle change or plan downgrade. - If you share your account with team members, ensure that no administrator unintentionally modifies plan features that affect active tools. - Set a reminder to check your QUEST LLM Visibility dashboard at least once a week so you catch any data gaps early. 🆘 Still Seeing Issues? If your plan already includes QUEST LLM Visibility and your data is still not updating, there may be a technical issue on our end that requires investigation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🛠️ Fix an Incorrect Wikipedia Link in Your Knowledge Graph

🔍 What This Article Covers Sometimes a Knowledge Graph entity may display an incorrect Wikipedia link or unrelated topic categories (such as references to a completely different industry or subject). If you have tried to remove these entries yourself and the change does not persist, this article explains the situation and how to get it resolved quickly. ⚠️ Known Limitation: Some Fields Cannot Be Self-Removed There is a known issue where certain Knowledge Graph field deletions — including Wikipedia URLs — appear to save in the interface but are not permanently removed from the underlying database. This means the incorrect information may reappear after you attempt to delete it. Because of this, manual removal by the Search Atlas team is currently required for these specific fields. 📋 Before You Contact Support To help the support team resolve your request as quickly as possible, gather the following information before reaching out: - Knowledge Graph entity ID or business name — for example, the domain or company name associated with the entity. - The incorrect field value — the exact Wikipedia URL or topic category that needs to be removed (e.g., a Wikipedia page for an unrelated subject such as mathematics or abstract algebra). - Confirmation that you have already attempted removal — let the team know if you tried deleting the entry and it reappeared, so they can skip straight to the manual fix. 🚀 How the Support Team Resolves This When you report an incorrect Wikipedia link or unrelated topic reference in your Knowledge Graph entity, a member of the Search Atlas team will: 1. Identify the specific Knowledge Graph entity using the ID or business name you provide. 2. Manually remove the incorrect Wikipedia URL and any associated unrelated topic references directly from the database. 3. Confirm with you once the removal is complete and the correct information is in place. This process is straightforward and is typically completed quickly once the support team has the details they need. 💡 Tips to Prevent Incorrect Data in Your Knowledge Graph - When adding or editing a Wikipedia URL in your Knowledge Graph, double-check that the linked page matches your actual business, brand, or topic — not a similarly named concept from an unrelated field. - If you notice incorrect topic categories appearing automatically, report them promptly. The longer incorrect data remains, the more it may influence AI-generated outputs tied to your entity. - After a manual fix has been confirmed by the support team, revisit the entity to verify the information looks correct on your end as well. 🙋 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🔧 Fix LLM Visibility Quota Not Reflecting Active Projects

🔍 Overview Some customers have experienced a situation where their LLM Visibility quota appears fully consumed, yet the projects they want to track are not shown as active. This is caused by a known issue where the quota counter does not always update correctly after projects are deleted or changed. This article explains what is happening and the fastest path to resolution. ⚠️ What Causes This Issue A confirmed bug can cause LLM Visibility quota counters to drift from the actual number of active projects. Specifically: - Deleting an activated LLM Visibility project may not immediately free up a quota slot. - Bulk updates or hard-deletes can leave the quota counter out of sync with your real usage. - As a result, the platform may show your quota as fully used even when fewer than your allowed number of projects are actually active. Engineering has resolved the core quota-sync issues in recent updates, including auto-refresh of quota after project deletion. However, accounts affected before these fixes were deployed may still show incorrect quota counts and require a manual correction. 📌 Understanding What Counts Toward Your Quota Before troubleshooting, it is worth confirming what actually consumes a quota slot. Competitor domains analysed on the fly do not count toward your LLM Visibility quota — only explicitly added tracked projects consume quota slots. If you see unexpected quota usage, confirm the projects consuming slots are ones you intentionally added rather than domains reviewed ad hoc. This distinction can sometimes explain apparent overages before any bug is involved. 🛠️ Steps to Get This Fixed To get your quota corrected and your intended projects activated as quickly as possible, follow these steps before contacting support — providing this information upfront allows the team to action your request immediately without back-and-forth: 1. List the exact projects you want active. Write down the exact project names or domains you need enabled under your LLM Visibility quota, up to the number of slots your plan allows. For example: example.com, mybrand.io, clientsite.net. 2. Note which projects currently appear active. Review your account and note which projects (if any) are currently active under your LLM Visibility quota, along with any quota details you can see. This documents the discrepancy clearly for the support team. 3. Check whether a page refresh resolves the counter. Hard-refresh your browser (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) and revisit the LLM Visibility settings. In some cases the quota counter updates on its own after a short delay. If your available slots now reflect your actual active projects, no further action is needed. 4. If the quota is still incorrect after refreshing, contact our support team via the chat widget with your list of desired domains and your noted quota details. A support agent can manually activate LLM Visibility on your specified projects and reset your LLM Visibility credits when the issue is confirmed to be caused by the quota sync bug — so you can continue using the tool without interruption. You do not need to delete any projects or make other changes beforehand. ✅ What Support Will Do Once you contact the team with your project list and quota details, a support agent can: - Manually activate LLM Visibility on your specified projects and reset your LLM Visibility credits when the issue is confirmed to be caused by the quota sync bug — so you can continue using the tool without interruption. If you have any questions or need further assistance, please open the chat widget in the bottom-right corner of the platform and type human teammate and we will be happy to help.

Last updated on Oct 26, 2026

🛠️ Fix False LLM Visibility Project Quota Errors

🔍 What This Issue Looks Like You may see an error message stating you have reached the maximum number of LLM Visibility projects for your plan — even though your dashboard shows fewer active projects than your plan allows. This is a known backend issue where a ghost or inactive project is still counted against your quota, incorrectly blocking new activations. In some cases, GSC data may also fail to import alongside this error. The quota issue and the GSC import issue are separate problems; this article addresses the quota error specifically. ⚙️ Steps to Try First 1. Clear your browser cache and cookies, then reload the platform. 2. Try opening the platform in a private or incognito window to rule out a cached session causing the display error. 3. Check your Left sidebar → AI Visibility section and count the number of projects currently showing as active. If the number is genuinely below your plan limit, the problem is on the backend, not on your account settings. 4. Review all projects for any that may be partially deleted or deactivated. Navigate to your Left sidebar → AI Visibility project list and look for any projects with an inactive, paused, or error status. If you find one, try fully deleting it — open the project, look for a delete or remove option, confirm the deletion, and then refresh the page before attempting to activate a new project. 5. Attempt to activate a new project again after each step above. In some cases, removing a stale project or refreshing the session is enough to clear the quota gate without needing engineering intervention. ⚠️ Why This Happens The quota gate that controls how many LLM Visibility projects you can activate sometimes counts projects that are no longer visible in your dashboard — for example, a project that was deleted or deactivated but was not fully cleared from the backend. This causes the system to enforce a limit that is lower than your actual plan allocation, blocking new activations even when slots should be available. This is not something you can always fix by changing your plan settings or removing existing projects manually. If the steps above do not resolve it, it requires a backend correction by the Search Atlas engineering team. 📋 How to Get This Resolved Quickly If the self-service steps above did not clear the error, the next step is to contact our support team so a backend correction can be made. To help the team investigate and fix it as quickly as possible, please have the following ready before you reach out: - A screenshot or screen recording showing the error message you received. - A list of the projects currently visible as active in your Left sidebar → AI Visibility area, along with their names or URLs. - Your plan name or the maximum number of projects your plan should allow. - Confirmation of which self-service steps you already tried (cache clear, incognito, manual project deletion). Our team will confirm whether a hidden backend project is incorrectly consuming your quota and remove it so your activation can proceed. 💬 Contact Support If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🐛 LLM Visibility Bug Fixes July 2026

A focused round of bug fixes resolves display and activation issues in LLM Visibility, ensuring project statuses, country selections, and navigation highlights all behave correctly. ✨ What's New This release ships six bug fixes targeting reliability and accuracy across the LLM Visibility experience: - Status column blank for Site Explorer projects: The Status column in the AI Visibility list was showing "—" for Site Explorer projects that had no country code stored. This has been corrected so a valid status is always displayed. - Activation blocked for eligible customers: Some customers who were entitled to AI Visibility platforms were incorrectly blocked by a "Platforms not in your plan" error during activation. Eligible customers can now activate without interruption. - Projects incorrectly shown as removed: Active projects were displaying a "removed" status when a Site Explorer ID lookup failed. The fallback logic has been fixed so active projects retain their correct status. - Navigation rail highlight falling back to Site Metrics: Inside a project's AI Visibility page, the navigation rail was incorrectly highlighting "Site Metrics" instead of the AI Visibility section. The correct item is now highlighted. - Country selection resetting to US: When navigating from Site Explorer to LLM Visibility, a UK country or location selection was being overwritten and reset to US. Country selections are now preserved across navigation. 🛠️ How to Use It 1. Open AI Visibility from the left sidebar. 2. Review your project list — the Status column should now display correctly for all projects, including those linked to Site Explorer. 3. If you were previously blocked from activating AI Visibility platforms, attempt activation again — eligible customers will no longer see the "Platforms not in your plan" error. 4. Navigate between Site Explorer and LLM Visibility and confirm your country or location selection is retained. 📋 What to Expect These fixes are applied automatically — no action is required on your end. Project statuses, activation eligibility, navigation highlighting, and country selections now reflect accurate data. If you previously encountered any of these issues, they should be resolved upon refreshing the platform. If a problem appears to persist after refreshing, it is likely unrelated to these specific fixes. To help distinguish a lingering bug from expected behavior: a persisting issue would be one where the exact same symptom described above (blank status, activation error message, incorrect "removed" label, wrong nav highlight, or country resetting to US) continues to appear after a full page reload. If you see a different error or unexpected behavior not listed here, that is a separate issue. When reaching out, please have your project name, the exact error message or status label you are seeing, and the approximate time the problem occurred. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🛠️ Brand Vault Generic Preview Text Appearing for Your Business

🔍 What Is This Issue? Some users have noticed that Brand Vault auto-populates preview text that is completely unrelated to their business — for example, copy referencing cloud project management or password resets appearing for landscaping or construction companies. This is a platform-level bug, not a configuration error on your end. If you are experiencing this problem, the steps below will help you confirm the issue and get it resolved quickly. 📋 Before You Contact Support Take a moment to confirm that what you are seeing matches this known bug: - Brand Vault is generating preview text that has no connection to your industry, products, or services. - The issue appears regardless of which project or site you are viewing. - You have not recently changed your brand settings in a way that might explain the mismatch. If all of the above apply, this is likely the same issue our support team has seen reported by other users. Continue to the next section. ⚙️ Steps to Try While this is a platform-level bug, you can try the following general steps to see if they help refresh your Brand Vault content: 1. Refresh your browser and log out, then log back in to your Search Atlas account. 2. Navigate to your Brand Vault settings and check whether any brand information has been saved for your business. 3. If your brand details appear incomplete or missing, re-enter your business name, niche, tone, and key messaging to give the platform the correct context. 4. Save any changes and allow Brand Vault a moment to regenerate its preview content. 5. Check whether the auto-populated text now reflects your actual business. Ensuring your brand profile is complete and accurate is a good general practice — the more specific your brand inputs, the more relevant the AI-generated content will be across the platform. ✅ If the Issue Persists If you complete the steps above and still see irrelevant or incorrect auto-generated content, please reach out to our support team so they can investigate your account directly. Before reaching out, it helps to have the following ready: - Note the specific text that is appearing and which business or site it is connected to. - Take a screenshot if possible — this will help the team investigate faster. - Be ready to confirm whether you tried updating your brand profile and whether that changed anything. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our support team.

Last updated on Oct 26, 2026

🔍 Fix LLM Visibility No Data Found Error

Overview If your LLM Visibility dashboard previously displayed data but now shows No data found — even after recrawling or re-adding your site — this guide walks you through the steps to restore your data. Before You Begin This article is for customers who have already completed the initial LLM Visibility setup and are experiencing a sudden or persistent No data found state. If you have never successfully seen data in LLM Visibility, please refer to the LLM Visibility Getting Started guide instead. Confirm the following before proceeding: - Your site was previously returning data in LLM Visibility. - You have already attempted at least one recrawl without success. - The error persists after waiting some time following your most recent recrawl attempt. Step-by-Step Troubleshooting 1. Stop recrawling repeatedly. Multiple rapid recrawl attempts in a short window can cause delays. Wait before attempting another recrawl. 2. Clear your browser cache and cookies. A stale browser cache can cause the dashboard to display an outdated or empty state even when data exists in the backend. Clear your cache, close the browser completely, and reopen Search Atlas before checking again. 3. Open LLM Visibility in a private or incognito window. Navigate to Left sidebar → AI Visibility (LLM Visibility) in your dashboard. If data appears in the private window but not in your normal browser window, the issue is browser-side caching. Clearing your cache should resolve it permanently. 4. Verify your site is still added correctly. Inside the LLM Visibility dashboard, confirm your domain is listed and shows an active status. If the domain is missing or flagged, remove it and re-add it once, then wait for the crawl to complete before checking results. 5. Allow time for the crawl to finish. Depending on site size and current crawl queue load, a full refresh may take some time. Avoid re-adding or recrawling again during this period, as doing so may reset your queue position. If Data Still Does Not Appear If you have followed every step above and the No data found error still persists, this may indicate an account-level sync issue that cannot be resolved through the interface alone. When reaching out to support, please have the following ready: your project or site name, the domain you added to LLM Visibility, and a description of when the issue began and what steps you have already tried. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

Fix LLM Tool and Topic Monitoring Access

Overview If you are unable to add topics to monitor AI search performance or the Search Atlas LLM tool is not responding as expected, this guide covers what to check and how to get help quickly. Self-Triage Steps to Try First Before contacting support, work through the following checks — many access issues can be resolved without assistance: 1. Verify your plan includes these features. The LLM tool and AI search topic monitoring are not available on all subscription tiers. Log in to your account, navigate to your plan or subscription settings, and confirm that these features are listed as part of your current plan. 2. Check your account permissions. If you are a member of a team workspace, you may not have the role required to add topics or use the LLM tool. Ask your workspace administrator to confirm your permission level. 3. Refresh your session. Log out of Search Atlas completely, clear your browser cache, and log back in. Some access restrictions are caused by stale session data. 4. Try a different browser or disable extensions. Browser extensions — especially ad blockers or script blockers — can interfere with platform features. Test in a clean browser profile or incognito mode. 5. Check whether the issue is project-specific. If you have access to multiple projects or domains, test whether the problem occurs across all of them or only one. This helps narrow down whether it is an account-wide issue or tied to a specific configuration. What to Do If the Issue Persists If none of the steps above resolve the problem, the support team can review your account directly and help determine whether the issue is related to your current plan, a configuration setting, or something that needs to be escalated for a fix. Do not attempt to change plan or billing settings on your own while troubleshooting, as this may complicate the investigation. When you reach out, please have the following information ready so the team can investigate and resolve your issue as quickly as possible: - Your Search Atlas account email address. - The name of the project or domain you are working with. - A description of exactly what you are trying to do (for example, adding a topic to monitor or using the LLM tool). - A description of what happens — including any error messages you see, word for word. - The date and approximate time when the issue first occurred. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

LLM Visibility Quota Not Resetting After Billing Date

🔍 Overview Each billing cycle, your LLM Visibility quota should reset automatically on your renewal date. In some cases, a known platform issue can prevent this reset from firing correctly, leaving your quota appearing fully consumed even after your billing date has passed. This article explains what to check and how to get the issue resolved quickly. ⚠️ Is This Happening to You? You are likely affected if you notice all of the following: - Your LLM Visibility quota appears fully used up. - Your billing cycle renewal date has already passed. - You have not been able to run new LLM Visibility reports despite the new billing period starting. - No new quota has been credited to your account after the expected reset date. This is a known backend issue that has affected a number of paying customers. It cannot be resolved by making changes within your account settings — it requires a manual reset performed by the Search Atlas Billing and Accounts team. 🛠️ What You Should Do Follow these steps to confirm the issue and gather the information our team needs to perform the manual reset on your behalf as quickly as possible: 1. Confirm your billing renewal date. Click your avatar in the top-right and select Billing (Billing page) to note the exact date your cycle was supposed to renew. This helps our team verify the discrepancy on the backend. 2. Note how many days have passed. Record today's date and how many days it has been since the expected reset. Our team will need this context. 3. Check for active projects. Review your LLM Visibility reports to confirm whether active projects are genuinely consuming your quota, or whether the quota appears consumed with no active reports visible. Make a note of what you find. 4. Gather your account details. Have your account email address or workspace name ready, along with the information collected in the steps above. 5. Contact our support team. Reach out to the Search Atlas support team through the contact method available to you (such as the in-platform chat or your account's support channel). Share your billing renewal date, how many days the quota has been stuck, and whether any active reports are visible. The support team will escalate to the Billing and Accounts team, who will perform the manual backend reset and restore your quota. 📋 What to Include in Your Message To help our team resolve this without unnecessary back-and-forth, include the following details in your message: - Your account email address or workspace name. - The date your billing cycle was expected to renew. - Today's date and how many days have passed since the expected reset. - Whether active LLM Visibility reports are visible in your account or whether the quota appears consumed with no active reports showing. Once our Billing and Accounts team is notified and has this information, they can perform the backend reset and restore your quota promptly.

Last updated on Oct 26, 2026

🔍 Fix LLM Visibility Project Infinite Loading

🧭 Overview Some users experienced an LLM Visibility project that would load endlessly and never display results. This was caused by a confirmed platform bug affecting the analysis status endpoint, which has since been identified, fixed, and deployed to production by the Search Atlas engineering team. If you are still seeing an infinite loading screen or a 404 error in your LLM Visibility project, follow the steps below to resolve it. 🛠️ How to Fix the Infinite Loading Issue Because the underlying bug has been resolved on the platform side, the most effective fix is to force your browser to load the latest version of the platform by clearing cached data. Follow the steps below in order. 1. Clear your browser cache and cookies. Open your browser settings, navigate to the privacy or history section, and clear cached files and cookies. The exact steps vary by browser, but this option is typically found under Settings → Privacy → Clear browsing data. 2. Reload the platform. After clearing your cache, close the browser tab completely, then reopen Search Atlas and log back in. 3. Navigate back to your LLM Visibility project and check whether the loading issue is resolved. 4. If the issue persists, try an incognito or private window. Open a new incognito or private browsing window (Ctrl+Shift+N on Chrome, Ctrl+Shift+P on Firefox), log in to Search Atlas, and open your LLM Visibility project again. This rules out any remaining cached data or browser extension interference. ✅ What Was Fixed The Search Atlas engineering team investigated and resolved several related issues that caused LLM Visibility projects to fail: - An infinite loading state triggered by 404 errors on the analysis status endpoint. - Malformed favicon URLs causing 404 errors for every domain in the project. - 404 errors displayed instead of a proper empty state when no LLM data was available yet. - Loading failures affecting duplicate projects created without a country setting. All of these issues have been marked as resolved and the fixes have been released to production. 🔄 When to Expect Results Once you have cleared your cache and reloaded the platform, your LLM Visibility project should load normally. If your project was newly created or is still being analysed, allow a few minutes for data to populate before refreshing again. 💬 Still Need Help? If you have followed all the steps above and your LLM Visibility project is still stuck loading, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🚀 Increase Your AI Visibility Project Limit

🔍 Overview When setting up multiple AI Visibility (formerly LLM Visibility) projects, you may encounter an error stating that your plan needs to be upgraded or that you have reached the maximum number of AI Visibility (formerly LLM Visibility) projects allowed. This article explains why this happens and how to get your limit increased. ⚙️ Why This Happens Each Search Atlas account has a quota that controls how many AI Visibility (formerly LLM Visibility) projects you can create. This quota is set at the account level and may not always be reflected clearly in your billing dashboard. Even if your subscription appears active and up to date, you can still hit a project cap that requires a manual adjustment by the Search Atlas team. Common signs of this issue include: - An error message saying your plan needs to be upgraded when creating a new AI Visibility (formerly LLM Visibility) project. - A message stating you have reached the maximum number of AI Visibility (formerly LLM Visibility) projects for your plan. - No clear indication in the billing dashboard of which limit has been reached or how to increase it. 📊 Where to Find AI Visibility You can access the AI Visibility (formerly LLM Visibility) tool by navigating to Left sidebar → Authority → QUEST AI Visibility (formerly LLM Visibility). This is where your projects are listed and where you will see the error if your quota is exhausted. 🛠️ How to Get Your Limit Increased This quota increase cannot be completed through the billing dashboard on your own — it requires the Search Atlas team to update your account limit directly. Here is what to do: 1. Note how many AI Visibility (formerly LLM Visibility) projects you need to create (for example, 50 projects). 2. Open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. 3. Let the agent know your current situation: how many projects you are trying to set up, the error message you are seeing, and the total quota you need. 4. The team will escalate internally and update your AI Visibility (formerly LLM Visibility) project quota. Once updated, you will be able to create new projects without further errors. 💡 Things to Keep in Mind - The billing dashboard may not show quota details. The AI Visibility (formerly LLM Visibility) project limit is separate from your general subscription tier and is managed at the account level. - Quota increases are incremental. The team will set a new limit based on your needs. If you reach that limit again in the future, you can request a further increase the same way. - Quota may appear consumed with no active projects. If your quota shows as fully used but you do not see active projects in the dashboard, this is a known issue. Contact support so the team can review and correct your quota count. 📞 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🔍 Fix LLM Visibility Scan Failures and Errors

🧭 Overview If your LLM Visibility scan is failing or not completing, you may see an error message indicating the scan could not be saved or finished. These issues are typically caused by temporary platform-side problems that require backend investigation. This article explains what you can try on your end, and what information to have ready if you need to escalate to our support team. 🛠️ Basic Troubleshooting Steps 1. Navigate to LLM Visibility. Open the LLM Visibility section of your Search Atlas account and locate the affected website or project. 2. Check the scan status. Note whether the scan shows a failed state, an empty last-scan indicator, or a specific error message. Write down the exact wording of any error you see. 3. Re-save your scan settings. Open the settings for the affected website and save them again without making changes. This can sometimes re-register your configuration and allow the scan to proceed. 4. Trigger a new scan manually. If your LLM Visibility section allows you to start a scan manually, do so. Wait several minutes and then refresh the page to check whether the scan completed. 5. Clear your browser cache. If the error persists, clear your browser cache and cookies, log back in, and attempt the scan again. ⚠️ When the Issue Is on the Backend LLM Visibility scan failures are often caused by backend processing issues that cannot be resolved through the steps above. In these cases, our engineering team needs to investigate and resolve the problem on the platform side. There is no further action required from you while this is being resolved. 📋 What to Have Ready When Escalating If the troubleshooting steps above do not resolve your scan failure, please contact support and have the following information ready: - Project or website name — the exact name of the site or project where the scan is failing. - Exact error message — copy the full text of any error message displayed on screen. - Timestamp — when the failure first occurred or when you last attempted a scan. - Steps already tried — let us know which troubleshooting steps you have already completed so we can avoid asking you to repeat them. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🔄 LLM Visibility & URL Indexer Credits Not Resetting

🔍 Overview Each billing cycle, your LLM Visibility credits and URL Indexer credits should reset automatically. In some cases, a known platform issue can prevent this reset from firing correctly, leaving your quota stuck at its previous allocation cap even after your billing date passes. This article explains what to check and how to get it resolved quickly. ⚠️ Is This a Known Issue? Yes. Our engineering team has investigated and resolved several related bugs affecting monthly credit resets for LLM Visibility and URL Indexer features. These fixes are now deployed. However, if your credits were already stuck before the fix was applied, your quota may need to be manually reset by our support team. ✅ How to Confirm Your Credits Have Not Reset 1. In the platform, navigate to the URL Indexer section and review your current credit status. 2. Navigate to the LLM Visibility (QUEST AI Visibility) section and review your current quota. 3. Check whether your available credits reflect your full monthly allocation or appear stuck at a consumed or near-zero level despite a new billing cycle having started. 4. Confirm your billing date has passed by checking your account billing details. 🛠️ What You Should Do Because this issue requires a manual quota reset on the backend, it cannot be resolved through the platform interface alone. To get your credits restored as quickly as possible, contact our support team through the chat option available in the platform. Our team will apply the manual reset directly to your account — no further action is required from your side once you have reached out. When you contact us, please include the following information so the team can action your reset immediately without needing to follow up: - Your account email address - The specific credits affected (LLM Visibility, URL Indexer, or both) - Your billing date or the date you expected the reset to occur - A brief description of what you are seeing in your quota (e.g. fully consumed with no active usage) Once our team has the above details, they will apply the quota reset to your account and confirm when it is done. Resets are applied directly on the backend and take effect immediately — you do not need to log out or refresh your plan. 📊 After the Reset Is Applied Once our team confirms your quotas have been reset, return to the URL Indexer and LLM Visibility sections in the platform to verify your credits now reflect your full monthly allocation. You should be able to resume indexing URLs and running AI Visibility analyses immediately after the reset is confirmed. 💡 Preventing Confusion in the Future - Monitor your quota levels a day or two after each billing date to catch any reset failures early. - If your quota appears fully consumed but you have no act

Last updated on Oct 26, 2026

🔍 Fix Incorrect Domain Data in LLM Visibility

🧭 Overview The LLM Visibility feature in Site Explorer analyzes how often and how accurately large language models (LLMs) reference your brand or domain. If the tool appears to be pulling data for the wrong domain, it is likely related to how the domain is configured in your project. This article explains what to do if you encounter this issue. ⚠️ Why the Wrong Domain May Be Tracked LLM Visibility analysis is tied to the domain associated with your Site Explorer project. If the domain configured in your project does not match the exact URL you intend to track — for example, due to a subdomain mismatch or a different top-level domain — the visibility data may reflect a different entity than expected. 🛠️ What to Do If You See Incorrect Domain Data If your LLM Visibility report appears to be tracking the wrong domain, this is a known issue that requires investigation by our support team. Because the resolution depends on your specific project configuration, our team will need to look into the backend details to identify the cause and apply the correct fix. To help our team resolve this as quickly as possible, please have the following information ready when you reach out: - The name of the affected Site Explorer project. - The domain that is currently being tracked (as shown in the project). - The correct domain you expected the project to track. - Any relevant timestamps or screenshots showing the incorrect data. ✅ What to Expect Once our team reviews your project, they will advise on the appropriate next steps based on your specific configuration. Do not attempt workarounds that could affect your project data before speaking with support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🔍 Claude Missing From AI Visibility Results

🧭 Overview If you have noticed that Claude (Anthropic's AI assistant) is not listed in your AI Visibility results, this is a known issue that our team is aware of. This article explains what to expect and what information to have ready if you need to escalate. ❓ Why Claude Is Not Showing in Results Claude is currently not appearing in AI Visibility results. This is a known issue that has been reported to our team. At this time, the root cause is under investigation, and no self-serve workaround is available to restore Claude data within the AI Visibility feature. - Your account data is not lost. All other LLM results remain intact. - No action is needed on your end while our team investigates. - This affects Claude specifically. Other LLMs tracked in AI Visibility should continue to display normally. 📊 Which LLMs Are Currently Tracked AI Visibility tracks brand mentions and responses across the major supported language models. Log in and navigate to the AI Visibility section of the platform to see the full list of LLMs actively monitored for your domain. The feature is continuously updated as new models become reliably trackable. 📋 What to Have Ready When Escalating Because Claude's absence from AI Visibility requires backend investigation, please have the following information ready when you contact support: - Your project name and the domain you are tracking. - The date and approximate time you first noticed Claude missing from results. - A screenshot of your AI Visibility dashboard showing the missing data. - Confirmation of whether other LLMs are displaying correctly or are also affected. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

Atlas Brain Zero-Quota Bug Blocking LLMv Queries

Overview Some users encounter a situation where Atlas Brain blocks them from deploying LLMv queries, displaying a zero-quota error — even though their account has quota available. This is a known bug caused by a mismatch between your actual available quota and the quota value Atlas Brain reads internally. Because this issue requires a manual backend correction applied by the Search Atlas team, please reach out to support as soon as you encounter it so it can be resolved promptly. What Causes This Issue This problem involves a mismatch between your actual available quota and the quota value that Atlas Brain reads internally. In affected cases, Atlas Brain may prevent new LLMv queries from being deployed even when your plan includes sufficient quota. The fix must be applied directly to your account by the Search Atlas support team. How to Get This Resolved 1. Confirm the symptom: You are attempting to deploy an LLMv query in Atlas Brain and receive a zero-quota error, but you believe your account still has quota remaining on your current plan. 2. Contact Search Atlas support: Use the chat widget below to reach the support team. In your message, include your account email, the name of the project where you are seeing the error, and a brief description of the zero-quota error you are encountering. 3. Support will apply the fix: The support team will investigate the quota mismatch on the backend and apply the appropriate correction to your account. Once the fix is in place, you will be able to deploy LLMv queries as expected. If you need further assistance, please contact our support team through the chat widget below — we're happy to help.

Last updated on Oct 26, 2026

🧠 LLM Visibility Reliability Improvements

We've made a series of improvements to the LLM Visibility experience, addressing issues with navigation, project tracking, and copy accuracy to ensure everything works smoothly as you monitor your AI presence. ✨ What's New The following improvements are now live in LLM Visibility: - More accurate navigation tracking: When you open an AI Visibility project from the list view, the platform now correctly records that you arrived from the list — ensuring your in-app experience reflects how you're actually navigating. - Legacy deep link support: Older bookmarked or shared links that used the previous tab URL format will now automatically redirect you to the correct tab in the updated interface, so no saved links are broken. - Reliable project selection: The projects list now identifies each project by its unique identity rather than its position in the list. This means selecting, sorting, or reordering projects will no longer cause the wrong project to be highlighted or acted upon. - Corrected Sentiment tab description: A grammatical error in the Sentiment page description (AI Visibility → Sentiment) has been fixed, so the text now reads clearly and correctly. 📋 What to Expect These changes are all automatic — no action is needed on your part. If you previously bookmarked a link to a specific AI Visibility tab, that link will now redirect you to the correct destination. Project selection behavior in the list view is now consistent regardless of how your projects are ordered. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🐛 Platform Bug Fix: AI Visibility Filter Issue Resolved

This article explains a known bug with the platform filter in the AI Visibility Topics & Queries area, what caused it, and what you should know now that it has been resolved. What Was the Issue? A bug existed where changing a platform filter inside a Topic or Query drawer in the AI Visibility Topics & Queries area caused that filter change to apply beyond the drawer — unexpectedly affecting the broader Topics & Queries view. This could result in the main Topics & Queries list reflecting a platform selected only inside a drawer, leading to confusing or inaccurate data in your project. Is This Affecting Me? If you noticed that switching the platform filter inside a Topic or Query drawer caused your main Topics & Queries view to change unexpectedly, this bug was likely the cause. Common signs include: - The platform shown in the main Topics & Queries list changing after you closed a drawer - Data in the main view appearing to reflect a different platform than the one you selected at the top level - Filter state feeling inconsistent between the drawer and the broader view This bug has been resolved in a backend fix. No action is required on your end. How the Platform Filter in AI Visibility Should Work The intended behavior is that platform filter changes made inside a Topic or Query drawer should only affect data within that drawer and should not carry over to or alter the broader Topics & Queries view. Now that the fix is live, the main Topics & Queries list should remain unaffected when you switch platforms inside a drawer. What to Do If You Still See Unexpected Filter Behavior If you are still experiencing platform filter issues in AI Visibility Topics & Queries after this fix, please escalate to our team. To help us investigate as quickly as possible, have the following ready before reaching out: - Your project name - A description of the unexpected filter behavior you are seeing - The approximate date and time the issue occurred - Any screenshots that illustrate the filter state before and after the unexpected change If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🔍 Fix Incorrect Competitors in LLM Visibility

🧩 Why This Happens LLM Visibility uses an auto-discovery process to identify competitors based on signals that large language models associate with your brand. In some cases, the AI may surface companies that are unrelated to your actual industry or niche. This is a known classification issue affecting auto-discovered competitor lists in LLM Visibility. Our engineering team is actively working on a resolution. ⚠️ Known Bug Status Our team has confirmed this as an active bug where auto-discovered competitors may pull in unrelated companies instead of true industry rivals. A fix is currently being worked on by our engineering team and will roll out automatically once ready; no action is required on your end to receive it. 🛠️ How to Correct Your Competitor List Right Now While the permanent fix is being deployed, you can manually remove incorrect competitors and add the right ones directly inside your LLM Visibility project. Navigate to your active LLM Visibility project and find your competitor list. From there: 1. Identify any incorrectly listed companies and remove or exclude them from your analysis. 2. Manually add the correct competitor domains that are genuinely relevant to your niche. Important: If excluded competitors reappear after an automated refresh, re-exclude them — the engineering fix will address this once fully released. ✅ Best Practices to Improve Competitor Accuracy - Be specific with your brand description. A clear, niche-specific brand description helps LLMs classify your business correctly. - Add true competitors proactively. Manually adding your known competitors gives the system accurate reference points. - Review your competitor list periodically. Until the fix is fully live, check your competitor list regularly to catch and correct any misclassified entries. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🌍 Verify and Troubleshoot Geo-Targeting Configuration

🎯 Overview If you're seeing traffic from regions you didn't target, the issue is usually one of two things: a misconfigured geo-targeting setting in your project, or bot and crawler activity being counted in your analytics. This guide helps you identify which problem you're facing and resolve it. 🔍 Step 1: Check Your Project Geo-Targeting Settings First, verify that your geo-targeting configuration matches your intended audience. In your Search Atlas project settings, review which countries or regions are currently selected as your targets. Confirm that only your intended markets (for example, United Kingdom) are active. If you see unexpected regions listed, remove them and save your changes. If you are unsure where to find your geo-targeting options or cannot locate the relevant settings in your project, please reach out to our support team — they can verify your current configuration and correct it on your behalf. 🤖 Step 2: Distinguish Bot Traffic from Geo-Targeting Issues Unexpected traffic from regions such as China or Singapore often signals bot or crawler activity rather than misconfigured targeting. Use these checks to confirm: - Check traffic source: Review the referrer data for the suspicious traffic. Legitimate visitors arrive from search engines, direct URLs, or referral sites. Bots often show no referrer or a generic crawler identifier. - Look for engagement metrics: Bot traffic typically has zero pages per session, zero time on page, and a 100% bounce rate. Real users show varied engagement patterns. - Review device and browser data: Bots often appear as headless browsers or unknown device types. Real traffic includes standard browsers like Chrome, Safari, or Firefox on recognisable devices. - Compare spike timing: If traffic spiked suddenly on a specific date, check whether it correlates with a recent content update, backlink acquisition, or PR event. Legitimate traffic spikes follow such events; bot spikes are often random and unrelated to your activity. 📊 Step 3: Report Suspected Bot Traffic for Review If you have confirmed that the suspicious traffic appears to be bot or crawler activity, escalate it to our support team so they can investigate and apply the appropriate filtering or exclusions on your project. To help them resolve this quickly, have the following ready: - Your project name and URL - The specific regions or countries generating the unexpected traffic - The approximate date the traffic spike began - Any patterns you noticed (referrer data, device types, engagement metrics) Our team will review the traffic data and advise on the correct next steps, including whether any backend filtering needs to be applied. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🔍 Fix AI Summary Accuracy for Your Domain

🎯 Why Your AI Summary May Seem Inaccurate If the AI-generated summary for your site appears off-base or seems to be analysing the wrong domain, the most common cause is a misconfigured or unverified domain in your Site Explorer profile. New sites with limited data history can also produce summaries that feel generic until enough crawl data accumulates. This article walks you through how to confirm the correct domain is being analysed, how to interpret keyword difficulty for newer sites, and what SEO progress timelines you should realistically expect. ⚙️ Step 1 — Verify Your Domain Is Configured Correctly Before trusting any AI summary, confirm that Search Atlas is pointing at the exact domain you intend to analyse. 1. In the left sidebar, click Site Metrics (Site Explorer). This opens your site list at /site-explorer/list. 2. Locate your site in the list. Check that the domain shown matches your live site exactly — including whether it uses www or non-www, and https vs http. A mismatch here is the single most common cause of inaccurate AI summaries. 3. If the domain is wrong, remove the incorrect entry and add your site again using the precise URL format your site uses in the browser address bar. 4. Once corrected, allow up to 24–48 hours for the platform to re-crawl and refresh your data before re-reading the AI summary. 🔎 Step 2 — Check Keyword Data in Keyword Magic The AI summary draws heavily on keyword data associated with your domain. Thin or missing keyword data will make the summary less precise. 1. Navigate to Left sidebar → Keywords → Keyword Magic. 2. Confirm that keywords are being attributed to the correct domain. If no keywords appear, your site may be too new or may not yet have enough indexed pages for robust data. 3. Use the Keyword Gap tool (Left sidebar → Keywords → Keyword Gap) to compare your domain against competitors. This gives the AI more contextual signals to work with and often improves summary relevance. 📊 Understanding Keyword Difficulty for New Sites Keyword Difficulty (KD) scores tell you how hard it will be to rank for a given term based on the authority of pages currently ranking. For new sites, this context is essential. - KD 0–29 (Low): Best targets for new domains. Realistic ranking potential within weeks to a few months with quality content. - KD 30–59 (Medium): Achievable for newer sites with strong on-page SEO and some backlink growth. Expect 3–6 months. - KD 60–79 (High): Competitive. Usually requires established domain authority and a link-building strategy. Plan for 6–12+ months. - KD 80–100 (Very High): Dominated by high-authority domains. Not recommended as primary targets for new sites. You can review keyword difficulty scores at any time by going to Left sidebar → Keywords, which opens the Keyword Researcher at /research/keyword-researcher. Filter by KD range to build a realistic target list aligned with your current domain authority. 🚀 Realistic SEO Timeline Expectations SEO is a long-term investment. Understanding what to expect at each stage helps you interpret your AI summary and Site Explorer data accurately. - Weeks 1–4: Site gets crawled and indexed. AI summaries may be sparse. Focus on technical SEO fixes and publishing foundational content targeting low-KD keywords. - Months 2–3: Early ranking signals appear for low-competition keywords. Rank Tracker (navigate to Left sidebar → Keywords → Rank Tracker) will begin showing movement. AI summaries become more accurate as more data is collected. - Months 4–6: Consistent publishing and link acquisition start compounding. Medium-KD keyword rankings become achievable. AI summaries reflect a clearer competitive position. - Months 6–12+: Domain authority grows. High-KD keywords become realistic targets. AI summaries are most reliable and actionable at this stage. 💡 Tips to Improve AI Summary Accuracy Right Now - Ensure your sitemap is submitted and your robots.txt file is not blocking important pages. - Add as many of your target keywords as possible to the Rank Tracker — this enriches the data the AI uses to generate your summary. - Re-visit your AI summary weekly rather than daily; meaningful data shifts happen over days, not hours. - If your site recently migrated to a new domain or switched from HTTP to HTTPS, delete the old domain entry in Site Explorer and re-add the new URL to avoid mixed-data summaries. 🛠️ Still Seeing Inaccurate Results? If you have followed all the steps above and your AI summary still appears to analyse the wrong domain or shows clearly incorrect data, there may be a data ingestion issue on the platform side that our team can investigate directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🔍 New LLM Platforms Showing No Visibility Data Yet

🤔 Why Is There No Data for Grok or Copilot? If you recently upgraded your plan to access AI Visibility (formerly LLM Visibility) data for platforms like Grok or Microsoft Copilot, it is expected that those platforms may show no results yet — this is not a bug. Upgrading your plan unlocks access to newly supported LLM platforms, but it does not generate historical data retroactively. Search Atlas begins collecting visibility data for a platform from the point it becomes active in our system. Because these platforms were added recently, the data collection window is short and results are still accumulating. ⏳ When Will Data Start Appearing? Data for newly added LLM platforms typically begins populating within a few business days of a platform going live. Results will grow over time as Search Atlas continues querying those platforms on your behalf. Refreshing the page or re-saving your project will not speed up this process — data is collected on a scheduled background cycle. - Plan upgrade — unlocks platform access immediately. - Data collection — begins automatically once the platform is live in our system. - Visible results — typically appear within a few business days and grow incrementally from there. 🔎 How to Check Your AI Visibility Data Once data starts populating, you can view it by navigating to Left sidebar → Authority → QUEST AI Visibility (formerly LLM Visibility). From this screen you will see all supported LLM platforms and their visibility metrics for your tracked keywords. 1. Go to Left sidebar → Authority → QUEST AI Visibility (formerly LLM Visibility). 2. Review the list of LLM platforms displayed on the screen. 3. Select a platform such as Grok or Copilot to view its data. 4. If the platform appears in the list but shows no results, data collection is still in its early phase — check back in a few business days. ✅ Confirming Your Plan Includes These Platforms Not all Search Atlas plans include every LLM platform. Before troubleshooting further, verify that your subscription covers the specific platforms you want to track. - If a platform is visible at Left sidebar → Authority → QUEST AI Visibility (formerly LLM Visibility) but shows no data yet, your plan includes it and collection has already started. - If a platform is not listed at all, it may not be included in your current plan. Consider upgrading or contact support via the chat widget to confirm what is covered. 💡 Tips While You Wait - Check back every few business days — results grow incrementally as collection cycles complete. - Use LLM platforms that already have data to benchmark your current performance while newer platforms populate. - Avoid repeatedly re-adding your project or toggling settings, as this will not accelerate data collection. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🖼️ Fix and Disable AI Alt Text Errors

🔍 Overview When using the AI alt text feature inside Search Atlas, you may occasionally see an error message during generation, or you may simply prefer to write alt text manually. This article explains what to do when you encounter an AI alt text error and how to request that AI generation be turned off for alt text. ⚠️ What to Do When You See an AI Alt Text Error If an error message appears when the platform attempts to generate alt text for your images, try the following general troubleshooting steps before escalating: 1. Note the exact wording of the error message you are seeing — this will be important if you need to contact support. 2. Refresh your browser and navigate back to the AI alt text feature. 3. Confirm you are connected to the internet and that your session has not timed out. 4. Clear your browser cache, then reload the platform. 5. Try a different browser (Chrome or Edge recommended) to rule out a browser-specific conflict. 6. If the error persists across multiple images or multiple attempts, wait a few minutes and try again, as the issue may be temporary. If the error continues after completing these steps, please contact our support team with the exact error message text, the name of the project or page affected, and a description of what you were doing when the error appeared. 🚫 How to Disable AI Generation for Alt Text If you prefer to write alt text manually and want to stop the platform from triggering AI generation automatically, our support team can help you with this. When reaching out, let the team know which project or workspace you would like this changed for, and whether you want AI generation disabled for all images or for a specific page. 📋 What to Have Ready When You Contact Support To help our team resolve your issue as quickly as possible, please have the following information available: - The exact error message text as it appears on screen - The name of the project, page, or URL where the error occurred - The approximate date and time the error first appeared - A description of any steps you have already tried If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🎓 Fix a Zero Factuality Score in Scholar

🔍 Overview If your Scholar grader is showing a factuality score of 0, this article explains what may be happening and what information to have ready when contacting support. Because this issue requires investigation on the backend, the most effective next step is to reach out to our support team directly. 🤔 What Does a Zero Factuality Score Mean? A factuality score of 0 typically indicates that Scholar was unable to complete the grading process for that content. This can happen for a number of reasons, such as the content not being processed correctly or a temporary issue with the grading pipeline. Our support team can investigate the specific cause directly on your account. 🛠️ Before Contacting Support — Steps to Try First 1. Reload the page and reopen the Scholar report to check whether the score updates. 2. Run the Scholar grader again on the same content to see if the zero score persists on a fresh run. 3. Check whether the zero factuality score affects only one report or multiple reports in your account, as this helps identify whether the issue is isolated or broader. 4. Confirm that the content you submitted is not empty and meets the minimum length requirements for Scholar analysis. 📋 What to Have Ready When You Contact Support If the zero score persists after trying the steps above, please have the following ready when you reach out: - The project name or URL of the Scholar report showing the zero score. - The exact scores displayed (e.g. Factuality: 0). - Whether the issue affects one report or multiple reports. - The date and approximate time you first noticed the issue. - Any steps you have already tried, including whether re-running the grader made any difference. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

💡 Fix Unexpected LLM Visibility Subdomain Projects

🔍 Overview Some customers notice an LLM Visibility project has been created for a subdomain they never intentionally added — for example, go.yoursite.com — and that this project is consuming UC credits and occupying one of their quota slots. This article explains why this happens and what steps to take. ⚙️ Why Does This Happen? LLM Visibility projects were previously linked to Site Explorer, meaning that any domain or subdomain you explored through Site Explorer could be automatically added as a tracked project in LLM Visibility. This behaviour has since been corrected — LLM Visibility now manages its own independent project list — but projects created before this fix may still appear in your dashboard and continue consuming credits. Common symptoms include: - A subdomain project (e.g. go.yoursite.com) appearing in your LLM Visibility dashboard that you did not manually add. - Your UC credit balance depleting faster than expected. - All quota slots showing as occupied, preventing you from adding new projects. - The quota counter showing as fully consumed even though no active reports are visible. 🛠️ How to Remove the Unintended Project 1. Log in to your Search Atlas account and navigate to AI Visibility from the left sidebar. 2. Review the list of tracked projects and identify any subdomains or domains you did not intentionally add. 3. Select the unintended project and choose the option to deactivate it (reversible, stops scheduled analysis while keeping all historical data and settings) or delete it from your tracked projects. 4. Confirm your choice. Either action frees the quota slot immediately. 5. Verify that your quota slot count has decreased and that the project no longer appears in your dashboard. Once the unintended project is removed, that quota slot becomes available for a project you actually want to track. 💰 Can I Get a Refund for Wasted Credits? If UC credits were consumed by an unintended subdomain project that was added automatically rather than by your own action, you may be eligible for a credit adjustment. Our support team reviews these cases individually and can investigate the credit usage tied to the unintended project. To request a review, open the chat widget and provide the following details: - The subdomain or domain name of the unintended project. - The approximate date range during which it was active. - Your account email or account ID to help locate the usage records. 🚫 How to Prevent This in the Future - Periodically review your LLM Visibility project list to confirm all tracked projects are ones you intentionally added. - Avoid browsing subdomains in Site Explorer if you do not want them tracked — even though the automatic link has been removed, it is good practice to audit your project list after any Site Explorer activity until you confirm no unexpected projects have appeared. - Monitor your UC credit balance regularly from your account dashboard so you can spot unexpected consumption early. 📊 Understanding Your LLM Visibility Quota Each Search Atlas plan includes a set number of LLM Visibility quota slots. Every tracked project — whether added manually or automatically — occupies one slot and consumes UC credits each time it runs a visibility report. If all slots are occupied, you will not be able to add new projects until an existing one is removed. Removing an unintended subdomain project is the fastest way to free up capacity. 🆘 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🤖 AI Visibility Fixes and Improvements

We've resolved a number of issues in AI Visibility that affected how information was displayed and how certain actions behaved, making the experience more accurate and reliable. ✨ What's New The following improvements are now live in AI Visibility: - Credits pop-up: The credits pop-up now displays the correct copy and can be closed using the Escape key as expected. - Rank table tie-breaking: When two companies previously tied in rankings, both could appear as the same position (e.g., two entries both showing as #2). Rankings now correctly differentiate tied positions so each company has a distinct rank. - Formatting across the platform: Numbers, units, plural forms, and dates are now displayed consistently and correctly across cards, lists, and settings. - Summary card and Re-run button styling: The summary card heading and the Re-run Analysis confirmation button now display with the correct visual styling. - Re-run Analysis daily limit message: If you've reached your daily analysis limit and attempt to re-run, you'll now see a clear message explaining the limit rather than the action failing without any feedback. 📋 What to Expect These changes take effect automatically — no action is needed on your end. If you previously encountered any of the issues described above, they should now be resolved. Rankings, formatting, and interactive elements in AI Visibility will behave as intended going forward. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

Fix Ghost Competitors in AI Visibility Manager

🔍 What Is a Ghost Competitor? A ghost competitor is a domain that appears in your AI Visibility summary or reports but is missing from the competitor management area — meaning you cannot select or delete it through the normal interface. This is a known bug that can affect any tracked site. For example, a competitor like hardscaping.com may show up in the AI Visibility summary for your client's site, yet be completely absent when you open the competitor management area to remove it. 🧭 How to Navigate to AI Visibility Competitor Management 1. Log in to Search Atlas and select the correct client project. 2. In the left sidebar, click AI Visibility (URL: /llm-visibility). 3. Open the competitor management area within the AI Visibility dashboard. 4. Review the list of competitors displayed. If a domain shown in the summary is missing here, you are experiencing the ghost competitor issue. ⚠️ What Is Happening This is a platform-side bug in which a competitor domain becomes visible in the AI Visibility summary but is blocked from appearing in the competitor management area. As a result, the domain cannot be removed through the standard interface. Our team needs to investigate and resolve this on the backend. 🛠️ How to Escalate This Issue Because this is a backend bug, it cannot be resolved through self-serve steps. To get it fixed as quickly as possible, please have the following information ready before contacting support: - The exact domain name of the ghost competitor (e.g. hardscaping.com). - The name of the affected client project in Search Atlas. - The date and approximate time you first noticed the competitor appearing in the summary. - A screenshot showing the domain in the AI Visibility summary and its absence from the competitor management area, if possible. ✅ What to Expect Once you contact support with the details above, our team will investigate the data mismatch on the backend and remove the ghost competitor from your account. You will be notified when the issue has been resolved and the competitor no longer appears in your AI Visibility summary. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

⏳ Grok, Copilot or New LLM Platforms Not Showing Data Yet

📋 Overview If you recently upgraded to the PRO plan and enabled new LLM platforms such as Grok or Microsoft Copilot, you may notice that visibility data has not appeared yet — even after refreshing. This is expected. Newly added platforms require time to collect and process data before results appear in your dashboard. ⏱️ Why Data Is Not Showing Immediately When a new LLM platform is activated, Search Atlas begins tracking visibility data from that point forward. The initial data population is not instant — the system needs time to crawl, analyze, and aggregate results. This process typically takes up to 24–48 hours from the moment your plan upgrade and platform activation are both in place. ✅ What to Do 1. Confirm your PRO plan is active in your account billing settings. 2. Confirm platforms are enabled in your AI Visibility (formerly LLM Visibility) settings (Left sidebar → Authority → QUEST AI Visibility (formerly LLM Visibility)). 3. Look for the processing indicator — when a platform is newly activated, the dashboard displays a processing/loading state while analysis runs. This confirms that data collection has started and the platform is being analyzed. 4. Wait 24–48 hours after both steps above are complete. 5. Refresh your dashboard after the wait period to check for updated data. 📌 Important Notes - Data collection begins from the moment a platform is activated — historical data is not backfilled. - If you recently created a new brand or project and the dashboard shows empty data, a known bug that prevented country analysis from running at project creation has been resolved. If the dashboard still shows empty data for a new project after 48 hours, contact support for investigation. - Anthropic Claude and Google AI Overview are not yet available as tracked platforms — they are planned additions and cannot yet be selected in AI Visibility (formerly LLM Visibility) settings. - If data still does not appear after 48 hours with confirmed settings, contact support for investigation. 💬 Still need help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🔍 Fix Wrong Competitors in LLM Visibility

🤔 Why Are Unrelated Companies Appearing as My Competitors? When you first run an analysis in AI Visibility, the platform automatically discovers competitors by scanning how large language models (LLMs) reference brands in response to queries related to your site. This process works well in most cases, but it can produce unexpected results when your brand name or domain is associated with multiple industries. This happens because LLMs associate certain words with more than one industry. The auto-discovery engine picks up those overlapping associations and may classify unrelated brands as competitors based on brand name rather than your actual industry. This is a known limitation of the current auto-classification system, and the team is actively improving competitor classification at the extraction stage so brands are categorised more accurately from the start. 🛠️ How to Replace Incorrect Competitors Manually You can override the auto-discovered competitor list at any time from within the AI Visibility section. Follow the steps below. 1. In the left sidebar, click AI Visibility. 2. Navigate to your project's competitor list. 3. Remove any companies that are not relevant to your actual industry by clicking the remove or delete option next to each entry. 4. Add your real competitors by entering their brand names or domains where the platform allows you to add competitors. 5. Save your changes and re-run the analysis to refresh the data with your updated competitor set. Once you have saved a manual competitor list, the platform will use those entries for your reports going forward. 💡 Tips for More Accurate Auto-Discovery Here are a few steps you can take to improve competitor classification accuracy: - Use a specific, industry-focused domain or brand name when setting up your project. Generic or ambiguous names increase the chance of cross-industry mismatches. - Review any queries associated with your project and remove low-quality or irrelevant entries. Junk queries can influence which competitors are surfaced by the auto-discovery engine. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🌐 Domain Power Not Showing & Adding Domains

📋 Overview This article covers two common questions about AI Visibility in Search Atlas: why the Domain Power metric may not appear for your domain, and how to add additional domains to your AI Visibility project. ⚠️ Why Is Domain Power Not Displaying? If Domain Power shows a dash, zero, or is completely missing for your domain, this is a known issue that our team can investigate on your behalf. There is no single self-serve fix confirmed for this scenario — the cause will depend on your specific account and domain configuration. When reaching out, please have the following ready so our team can assist you as quickly as possible: - The exact domain name that is not showing Domain Power data. - The name of the AI Visibility project the domain is associated with (if applicable). - A screenshot or description of what you currently see (e.g., dash, zero, blank field). - Approximately when you first noticed the metric was missing. 🌐 How to Add Multiple Domains to AI Visibility If you want to track more than one domain in AI Visibility, this is possible within Search Atlas. Our team can confirm the correct steps for your specific plan and account setup. When contacting support about adding domains, please have the following ready: - The domain(s) you want to add. - The name of your existing AI Visibility project or account. - Your current Search Atlas plan, if known. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🔍 Fixing AI Visibility Project Activation Errors

❗ What This Error Means When you try to add a project in AI Visibility, you may see this message: "Failed to activate AI Visibility. Missing project reference, please reload and try again." It means the platform could not tell which project you were trying to activate AI Visibility for. This is usually a temporary loading issue, a project that was not fully created or selected, or an account limit that has been reached. Most cases can be fixed in a few minutes with the steps below. 🔄 Quick Fixes to Try First Work through these steps in order. Test AI Visibility again after each one. 1. Reload the page. Refresh your browser so the project data loads again. 2. Select your project again. Use the project selector to choose the project you want. If you are on a general dashboard with no project selected, the platform may not have a project reference to use. 3. Log out and log back in. This refreshes your session and your account details. 4. Clear your browser cache and cookies. Old saved data can cause projects to load incorrectly. 5. Try a different browser or a private window. This also helps rule out browser extensions such as ad blockers. 6. Confirm the project exists. Open your project list and check that the project was created and has a name and a website or domain attached. If it was only partly created, delete it and create it again. 📦 Understanding Project Limits Each Search Atlas plan includes a set number of projects and a set amount of AI Visibility usage. When you reach that limit, the platform may not be able to activate AI Visibility on a new project. Sometimes the only sign is a generic error message like the one above. To check whether a limit is the cause: - Open your project list and count how many active projects you have. - Open your plan or billing page and compare your usage with your plan allowance. - Look for old, unused, or duplicate projects that are still taking up space. If you are at your limit, you have two options. You can remove or archive projects you no longer need to free up space, or you can upgrade your plan for a higher allowance. ⏳ How Quota Resets Work Some AI Visibility allowances are usage-based, which means they are tracked over a period of time. Once you use your allowance, you may need to wait for the next reset before you can add more. Resets usually follow your billing cycle, so check your plan or billing page for your renewal date. Keep these points in mind: - Deleting a project does not always give back usage that has already been counted for the current period. - Upgrading your plan may raise your allowance right away, but you may need to reload the platform before the change appears. - If your quota should have reset but still shows as used, reload the platform and check again. If it still looks wrong, contact our team and mention your renewal date. 📍 If Your Project Involves a Google Business Profile (GBP) If the project you are adding is linked to a Google Business Profile location, a few extra checks can help: - Make sure the Google account you connected has owner or manager access to the profile. - Reconnect your Google account if the connection has expired or access was changed. - Confirm that the business name and website on the profile match the project you are setting up. If you still get the error after these checks, tell our team that the project involves a GBP. They can look into the connection and, if needed, escalate it internally as a ticket so it can be followed up properly. 🧾 What to Share When You Contact Us The details below help our team find the cause faster, so please include them in your first message: - The exact error message you see - The name and domain of the project you are trying to add - Whether you have reached your project limit or quota - Whether the project is linked to a Google Business Profile - The browser you are using, and the steps you have already tried - A screenshot of the error, if possible 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. ✅ Quick Checklist - Reload the page and select your project again - Log out, log back in, and clear your cache - Try another browser or a private window - Check your project count against your plan limit - Check your quota and your next reset date - Confirm your Google Business Profile access, if relevant - Chat with a human teammate if the error continues

Last updated on Oct 26, 2026

🛠️ Fix Manual Competitors Not Adding in AI Visibility

🔍 Overview In an AI Visibility project, you can track competitors alongside your own brand. Some customers report that when they add a competitor manually, the domain field clears but the domain never shows in the list, and the Save changes button stays grey. This article explains what to check and how to work around it. ⚠️ What You Might See - You open Manage Competitors and type a domain (for example, parksprings.com) in Add competitor domain. - You click Add and the field clears. - The domain does not appear in the competitor list. - Save changes remains grey and cannot be clicked. The grey button usually means the platform does not see any pending change to save. In other words, the domain was not accepted into the list, so there is nothing to save. ✅ How to Add a Manual Competitor Correctly 1. Open your AI Visibility project. 2. Open Manage Competitors. 3. Click into the Add competitor domain field. 4. Enter the domain only, for example parksprings.com. Do not include https://, www, a trailing slash, or any page path. 5. Click Add or press Enter. 6. Check that the domain now appears in the competitor list. 7. Click Save changes once it becomes active. 🔎 Common Reasons the Domain Does Not Appear - The domain is formatted unexpectedly. Full URLs, extra spaces, or pasted text with hidden characters can cause the entry to be rejected. Retype the domain by hand. - The competitor is already in the list. If it was auto-suggested or added earlier, it may not be added a second time. Scroll through the full list and check any suggested or hidden sections. - The domain matches your own site. You cannot track your own domain as a competitor. - The page has not fully loaded. If the page was open for a long time or your connection dropped, the list may not refresh properly. - A browser extension or cached data is interfering. Ad blockers and privacy tools can sometimes block parts of the page. - Your account role may not allow edits. If you are a team member on someone else's account, you may need edit access to the project. 🧰 Troubleshooting Steps 1. Refresh the page and open Manage Competitors again. The domain may have been added but not displayed. 2. Retype the domain in lowercase without www or https://, then click Add. 3. Try a different domain format, such as the root domain only (example.com), if you used a subdomain. 4. Test another competitor to see whether the issue affects every domain or only one. 5. Disable browser extensions temporarily, or try an incognito or private window. 6. Clear your browser cache or try a different browser such as Chrome, Edge, or Firefox. 7. Confirm your access level with the account owner if you are a team member. 8. Sign out and back in, then try again. 💡 Tips for Managing Competitors - Add one competitor at a time and confirm it appears before adding the next. - Use the main root domain of each competitor for the most consistent tracking. - Keep your competitor list focused on the brands that matter most to your market. - After saving, reopen Manage Competitors to confirm your changes were kept. 💬 Still Not Working? If the domain still does not appear and Save changes stays grey after the steps above, our team can investigate. To help us resolve it faster, please have these details ready: - The name of your AI Visibility project - The exact domain you are trying to add - The browser you are using - Whether the issue happens with other domains too - Any message shown on screen If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 26, 2026