AI Visibility Features & Limits

🔗 Connecting Search Atlas to Data Warehouse Platforms

🔌 Search Atlas WordPress Plugin and AI Visibility Licenses

🌐 Domain Power Not Showing & Adding Domains

⚡ How to Understand UX Signals Score Fluctuation

This article explains why your UX Signals score can change between reporting periods — including jumping up one week and returning to a previous value the next. Because the exact calculation methodology and signal components can vary based on your account configuration, the guidance below focuses on what to check and what information to gather before reaching out to support. What to Do When You Notice a Score Change 1. Note the exact dates of the two reporting periods where the score changed. Make sure you are comparing equivalent time windows rather than overlapping or mismatched date ranges. 2. Check whether any changes were made to your site between the two periods — such as new pages published, layout edits, or third-party script additions — that could have affected page behavior. 3. Check whether a campaign, promotion, or external link drove an unusual traffic spike during the higher-scoring period, as atypical traffic patterns can influence engagement-based metrics. 4. Review the individual signal components shown in your UX Signals report to identify which specific metric shifted the most between the two periods. This helps narrow down the likely cause. 5. If the score returned to the same value it held before the spike, document the exact values and dates — this pattern is useful context for the support team to investigate. What to Have Ready When You Escalate If the steps above do not clarify the cause, please gather the following before contacting support so the team can investigate efficiently: - Your project name and the URL(s) where the score change was observed - The exact score values and the dates each was recorded - A brief description of any site changes or traffic events that occurred between the two periods - A screenshot of the UX Signals report showing the fluctuation, if available 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.

🤖 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.

🤖 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.

🚧 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.

🔓 Pro Plan Projects, AI Visibility, and Feature Access

📋 Overview The Search Atlas Pro plan includes access to up to 4 active projects at a time. Some features — including AI Visibility — are tied to your active projects. If you cannot access AI Visibility, the most common cause is reaching your project limit or having the wrong projects set to active. This article explains how to check, manage, and resolve this quickly. 🗂️ What Counts Toward Your Project Limit On the Pro plan, you can have a maximum of 4 active projects running simultaneously. Here is what you need to know about how this limit works: - Only active projects count toward your limit — inactive (disabled) projects do not. - Features like AI Visibility are available only for your active projects. - If all 4 project slots are occupied, you cannot add a new active project without first disabling an existing one. - You can create additional projects beyond 4, but they must remain inactive until a slot becomes available. 🔍 How to View Your Active Projects To see which projects are currently active on your account, follow these steps: 1. Log in to your Search Atlas account. 2. Navigate to the Projects section from your main dashboard. 3. Look for the Active tab or filter to display only your currently active projects. 4. Review the list to confirm how many of your 4 available slots are in use. If you see 4 active projects and need to use AI Visibility for a different project, you will need to disable one of the existing active projects first. ⚙️ How to Disable or Enable a Project Disabling a project frees up an active slot without permanently deleting any data. Your project settings, tracked keywords, and historical data are all preserved. To disable an active project: 1. Go to the Projects section in your dashboard. 2. Locate the active project you want to pause. 3. Select the project options (usually a three-dot menu or a settings icon next to the project name). 4. Choose Disable or Deactivate. 5. Confirm the action when prompted. To enable an inactive project: 1. Go to the Projects section in your dashboard. 2. Switch to the Inactive or All Projects view to find the project you want to reactivate. 3. Select the project options and choose Enable or Activate. 4. Confirm the action. The project will now count as one of your 4 active slots. 🤖 Why AI Visibility Requires an Active Project AI Visibility is a project-level feature, meaning it operates within the context of a specific active project. If AI Visibility appears locked or unavailable, check the following: - Is the project you want to use set to active? If the project is inactive, AI Visibility will not be accessible for it. - Have you reached your 4-project limit? If all 4 slots are taken by other projects, the project you need may have been pushed into an inactive state. - Is your plan current? Confirm your Pro plan subscription is active with no billing issues by checking your account settings. Once the relevant project is set to active and you have an available slot, AI Visibility should become accessible immediately — no additional steps required. 🔄 When Do HyperDrive Credits Reset? HyperDrive credits reset on your monthly billing cycle date — the same date each month that your subscription renews. To find your exact reset date: 1. Click your avatar in the top-right corner of the platform. 2. Go to Billing and then navigate to your subscription details (Plans & Top-ups/Services/Invoices/Activity Log). 3. Your next renewal date shown there is also your HyperDrive credit reset date. Unused HyperDrive credits included in your plan (and any recurring monthly HDC top-up) do not carry over to the next billing cycle. HDC purchased as a one-time top-up, however, roll over and stay on your account until used completely, so plan your usage accordingly before your reset date. 💡 Quick Troubleshooting Checklist - ✅ Check how many projects are currently active — you are allowed up to 4 on the Pro plan. - ✅ Confirm the specific project where you need AI Visibility is set to active. - ✅ If you are at the 4-project limit, disable a project you are not currently using to free up a slot. - ✅ Re-enable the project you need and verify AI Visibility is now accessible. - ✅ Check your billing renewal date to know when your HyperDrive credits reset. 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.

📍 AI Visibility City-Level Targeting for Local Markets

📋 Overview Search Atlas's AI Visibility tool (QUEST AI Visibility) currently reports brand and keyword visibility at the nationwide level. If you run a local business in a specific city — such as Chattanooga, Tennessee — you may notice that city-level targeting is not yet available. This article explains why that limitation exists, what you can do in the meantime, and what is coming soon. 🔍 Why City-Level AI Visibility Is Not Yet Available AI Visibility data is gathered by querying large language models (LLMs) such as ChatGPT, Gemini, and Perplexity. These models generate responses based on broad training data and do not consistently apply geographic filters the same way a traditional search engine does when you select a location. As a result, returning reliable, reproducible city-level visibility metrics is technically complex and requires a dedicated infrastructure to ensure accuracy. To protect the integrity of your reporting, Search Atlas currently scopes AI Visibility results at the national level. Showing city-level numbers before the underlying data is dependable could lead to misleading insights — which would ultimately harm your strategy. 🗺️ What This Means for Your Local Business If your business serves a specific metro area or city, here is how the current limitation affects you: - Nationwide visibility scores reflect how often your brand or website appears in AI-generated answers across the entire country, not just your target city. - Local competitors may appear in your visibility data if they also rank nationally, even if they are not direct competitors in your market. - City-specific queries (for example, "best HVAC company in Chattanooga") can still be tracked as individual queries inside QUEST AI Visibility — the limitation applies to geographic scoping of the reporting dashboard, not the queries themselves. ✅ How to Get the Most Out of AI Visibility Right Now Even without city-level targeting, you can take steps to make your AI Visibility data more relevant to your local market: 1. Add hyper-local queries. Navigate to Left sidebar → Authority → QUEST AI Visibility and use the Analyze query action to submit queries that include your city name (for example, "plumber in Chattanooga TN" or "Chattanooga roof repair company"). This surfaces how visible your brand is in location-specific AI responses. 2. Track branded mentions. Monitor whether your business name appears in AI answers for local intent queries. Consistent appearances signal growing local AI authority. 3. Benchmark local competitors. Add your top local competitors to the same project so you can compare how often their brands appear versus yours in location-specific queries. 4. Strengthen your local signals. AI models surface brands that are well-cited online. Use Authority → PR Distribution to publish locally relevant press releases and build the citation footprint that LLMs rely on. 🚀 What Is Coming Soon The Search Atlas product team has city-level local AI Visibility tracking actively in development. The planned update will allow you to scope AI Visibility reporting to specific cities, making it far more actionable for local and multi-location businesses. A city allowlist and per-location tracking for franchise and multi-location accounts are part of this upcoming release. Once this feature is live, you will be able to select your target city directly within the QUEST AI Visibility dashboard and see visibility scores scoped to that geographic market. 💡 Tips While You Wait - Focus on submitting city-specific queries now so you have historical data to compare against once city-level scoping launches. - Use Authority → Cloud Stacks and Authority → PR Distribution to build topical and local authority that improves your chances of being cited by AI models in local responses. - Check back in the platform for product update announcements — new features are highlighted on the Home dashboard. 🛠️ 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 connected with a member of our team.

🚀 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.

➕ Add a New SEO Project Without Losing Data

Understanding Your Options If you want to track a new domain in Search Atlas, you may not need to replace or delete any existing project. Whether you can simply add a new project alongside your existing ones depends on how many project slots your current plan includes and how many you have already used. Before taking any action, check your plan's project limit and how many slots are currently occupied. That determines which path below applies to you. How to Check Your Project Slots Log in to Search Atlas and navigate to your account or subscription settings. Look for information about your SEO project limit and how many projects you currently have active. If the number of active projects is lower than your plan's limit, you have an open slot and can add a new domain without touching any existing project. If you are unsure where to find this information in your account, our support team can look this up for you. Option 1 — Add a New Project (Slot Available) If you have an open slot, you can create a new project for the additional domain without affecting any existing project or its data. Navigate to the SEO Projects area of the platform and look for the option to create or add a new project, then follow the on-screen prompts to enter your new domain and complete setup. Your existing projects remain fully intact with all their historical data, tracked keywords, backlinks, and reports. Option 2 — Replace a Project (No Slots Available) If every slot on your plan is occupied, you have two options: upgrade your plan to gain more slots, or remove an existing project to free up a slot for the new domain. Important: Deleting a project permanently removes all data associated with it, including keyword rankings, site audit history, and backlink records. This action cannot be undone. Before deleting any project, export any reports or data you want to keep using the export options available within the relevant tools. To replace a project, delete the project you no longer need through that project's settings or management options, then add the new domain as a fresh project in its place. Option 3 — Upgrade Your Plan If you need to keep all your current projects and still want to add a new domain, upgrading your plan is the cleanest solution. You keep every existing project and its data while gaining additional project slots. You can explore upgrade options by clicking your avatar in the top-right corner, selecting Billing, and opening the Plans & Top-ups tab (Billing). What to Have Ready If You Need Help If you are unsure about your current slot usage, cannot locate the project management area, or run into any issues adding a new project, our team can assist. Please have the following ready: your account email, the domain of the new project you want to add, and the names of any existing projects you are concerned about preserving. 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.

AI Visibility Account Limits and Plan Upgrades

What Are AI Visibility Accounts? An AI Visibility account (also called a project) is a tracked website or brand within the AI Visibility tool. Search Atlas monitors how your sites appear across AI-powered search engines and large language models (LLMs). Each plan includes a set number of these accounts, and the limit determines how many domains you can track simultaneously. How Many AI Visibility Accounts Does My Plan Include? The number of AI Visibility accounts available depends on your current subscription plan. Plan tiers differ in how many AI Visibility projects they include. To find out exactly how many accounts your plan includes, check your in-platform billing section or reach out via the chat widget for confirmation of your specific limit. What Happens When I Reach My Account Limit? Once you reach the maximum number of AI Visibility projects allowed on your plan, you will not be able to add new accounts without upgrading. If you need to track additional sites, you have two options: 1. Remove an existing project to free up a slot and add a new site in its place. 2. Upgrade your plan to increase the number of accounts available to you. Do I Need a Higher Plan for More Sites? If you need to track a large number of AI Visibility accounts beyond what your current plan allows, an upgraded plan may be the appropriate tier. Higher-tier plans can offer increased project limits tailored to your team's scale. To get an accurate quote or to discuss upgrading your plan, have the following information ready: - Your current plan name - The number of AI Visibility accounts (sites/domains) you need to track - Your account email or organization name How to Prepare for Escalation If you are unsure of your current plan's AI Visibility account limit or need to take action, here is what to do: 1. Check your subscription confirmation email or in-platform billing section for your current plan name and tier. 2. Determine how many sites you currently need to track and whether you are at or near your limit. 3. Decide whether removing an existing project frees up enough capacity, or whether a plan upgrade is required. 4. If you need to upgrade or confirm your exact limit, have your plan name, account email, and the number of projects you need ready before reaching out. 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.

📊 Managing AI Visibility Project Slots and Plan Limits

🔍 What Are AI Visibility Projects? AI Visibility projects let you track how your brand and content appear across large language models (LLMs) such as ChatGPT, Gemini, and Perplexity. Each project monitors a specific domain or topic set, and the number of projects you can run at the same time depends on your current Search Atlas plan. 📋 How Many AI Visibility Projects Does My Plan Include? The number of active AI Visibility projects available to you is determined by your subscription tier. Current plan limits are as follows: - Starter plans: 0 AI Visibility projects - Growth plans: 2 AI Visibility projects (with 100 LLM Visibility queries) - Pro plans: 4 AI Visibility projects (with 100 LLM Visibility queries) - Agency plans: Additional project slots — check your plan details inside the platform for the exact number included Only active projects count toward your quota. If a project is paused or deleted, that slot is freed up and can be reused. ⚠️ What Happens When I Reach My Project Limit? Once you have used all available project slots on your current plan, you will not be able to create new AI Visibility projects until you either: - Delete or deactivate an existing project to free up a slot, - Purchase additional project slots as a quota top-up through the platform's top-up checkout, or - Upgrade your plan to unlock additional project slots The platform will display a notification when you attempt to add a project beyond your current limit, prompting you to review your options. 🚀 How to Add More AI Visibility Projects If you need more than your current plan allows, you can either purchase extra project slots as a quota top-up through the platform's top-up checkout without changing your plan, or upgrade your plan by following these steps: 1. Click your account name or avatar in the top-right corner of the platform to open the Account Menu. 2. Select Billing from the dropdown menu. 3. Navigate to the Plans & Top-ups page. 4. Review the available plans and locate one that includes the number of AI Visibility projects you need. 5. Click Change Plan on your chosen plan and complete the checkout process. Your additional project slots will be available immediately after your upgrade is confirmed. ♻️ Free Up Slots Without Upgrading If you do not need all of your existing projects, you can free up slots without changing your plan: 1. Go to the AI Visibility section in the left-hand navigation menu. 2. Open the project you want to remove. 3. Select Delete Project from the project settings or options menu. 4. Confirm the deletion. The slot will be released instantly. Note: Deleting a project permanently removes all associated tracking data. Make sure you export any reports you need before deleting. 💡 Tips for Managing Your AI Visibility Projects Efficiently - Consolidate related topics into a single project where possible to make the most of each slot. - Prioritise high-value domains — focus your active projects on the sites or brands that matter most to your current campaigns. - Review inactive projects regularly so unused slots do not go to waste. 🛠️ Troubleshooting Common Issues My project count looks wrong in the dashboard. A recent fix was applied to ensure that deleted or inactive projects no longer count toward your active quota. If your quota still appears incorrect, try refreshing your browser. If the issue persists, contact our support team using the instructions below. AI Visibility availability looks different between Settings and my Summary widget. This display inconsistency has been resolved for Growth plan users. If you are still seeing conflicting information, a browser refresh should correct it. If not, reach out to our team for assistance. ❓ 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.

⚡ AI Visibility Project Limits and Upgrade Options

Overview This article explains what happens when you reach your plan's AI Visibility project limit and how to expand your capacity by upgrading your plan. AI Visibility Project Limits by Plan Search Atlas plans include a set number of active AI Visibility projects. Each project tracks how a brand appears across AI-powered search and answer engines. If you have reached your plan's project limit, you will not be able to create additional AI Visibility projects until you either remove an existing project to free up a slot, purchase extra project slots as a quota top-up, or upgrade to a higher-tier plan. What Happens When You Hit the Limit Once you have used all available AI Visibility project slots on your current plan, the platform will prevent you from creating new ones. At that point your options are: - Remove an existing project to free up a slot on your current plan. - Purchase extra AI Visibility project slots as a quota top-up through the platform's top-up checkout, without upgrading your plan. - Upgrade your plan to one that includes a higher or unlimited number of AI Visibility projects. How to View Pricing and Upgrade Your Plan To review available plans and their AI Visibility project allowances, navigate to the billing or subscription section of your Search Atlas account. From there you can compare plans and initiate an upgrade. The exact project limits and pricing for each plan tier are displayed in that section. If you are unsure which plan is right for your needs or have questions about what is included in a specific plan, our support team can provide accurate, up-to-date details tailored to your account. Frequently Asked Questions - Can I buy individual extra AI Visibility projects as an add-on? Yes. You can purchase extra AI Visibility project slots as a quota top-up through the platform's top-up checkout without upgrading your plan. - Will I lose my existing projects if I upgrade? Upgrading your plan should not remove your existing AI Visibility projects. Our team can confirm the specifics for your account before you proceed. - Can I downgrade after upgrading? You can change your plan from the billing section of your account at any time. Keep in mind that downgrading may reinstate a lower project limit, which could affect projects above that number. 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 connected with a member of our team.

🔓 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.

📘 MCP for AI Visibility

The AI Visibility (formerly LLM Visibility) toolset tracks how your brand is represented in answers from AI systems such as ChatGPT, Claude, Perplexity, Gemini, and other LLM-powered search surfaces. Through MCP, your AI assistant can help you create projects, run visibility checks, review trends, and analyze how your brand is being cited and described. This article explains what you can do with MCP for AI Visibility (formerly LLM Visibility), how the workflow works, what kinds of outputs to expect, and what to keep in mind when using this capability. 🧠 What You Can Do with MCP for AI Visibility Using MCP for AI Visibility (formerly LLM Visibility), you can: - track how your brand appears in AI-generated answers - manage visibility projects - review queries and tracked topics - compare your visibility against competitors - review citations and sources referenced by AI systems - monitor visibility trends over time - analyze share of voice - review sentiment and prompt-level analysis In practical terms, this means MCP can help you move from “How are AI platforms talking about my brand?” to a structured workflow where your assistant retrieves data, compares trends, and helps you interpret what is happening. 🔍 What AI Visibility Measures The source describes AI Visibility (formerly LLM Visibility) as the Search Atlas product area that tracks how a brand appears in answers from AI-powered search systems. It specifically references platforms such as: - ChatGPT - Claude - Perplexity - Gemini - other LLM-powered search surfaces This is not just a one-time lookup. It is a structured project-based system that can monitor: - visibility trends - share of voice - sentiment - citations - prompt-level analysis That means the workflow is broader than simply “search my brand.” It can be used to understand how often your brand shows up, how it is described, how competitors compare, and which sources are influencing those AI-generated answers. ⚙️ Step-by-Step: Start an AI Visibility Workflow Step 1 Open your MCP-connected AI assistant. This could be any MCP-compatible client already connected to Search Atlas through the MCP endpoint. The actual actions run through your Search Atlas account and follow your plan entitlements and quota rules. Step 2 Ask your assistant to work with your AI Visibility (formerly LLM Visibility) data. Examples of customer-facing requests could include: - “Show me my AI Visibility (formerly LLM Visibility) projects” - “Check how my brand appears in AI search” - “Compare my brand against competitors in AI answers” - “Show me visibility trends for my brand” These are user-intent examples aligned to the capability described in the source. The source itself states that AI Visibility (formerly LLM Visibility) manages visibility projects, queries, topics, competitors, and citations. Step 3 The assistant retrieves or works with your AI Visibility (formerly LLM Visibility) project data. According to the source, the product area supports: - visibility projects - queries - topics - competitors - citations At this stage, the assistant is identifying the relevant project or dataset and pulling the information needed to answer your request. Step 4 Review the returned results. Depending on the request, results may include: - visibility trends - share of voice - sentiment - citations - prompt-level analysis Step 5 Continue the workflow by refining the question. Once initial results are available, you can narrow the workflow further. For example: - focus on a competitor - focus on one topic - look at citations only - review trend changes over time - inspect how AI systems describe your brand in a specific context This is where the conversational nature of MCP becomes especially useful: you can progressively narrow the analysis instead of manually navigating multiple tools. 📊 Step-by-Step: Review Brand Visibility Trends Step 1 Ask your assistant to show your brand’s visibility performance over time. Examples: - “Show my AI Visibility (formerly LLM Visibility) trends” - “How has my brand visibility changed over time?” - “Show trend data for my AI search visibility” The source explicitly states that AI Visibility (formerly LLM Visibility) returns visibility trends. Step 2 The assistant retrieves the trend data from your AI Visibility (formerly LLM Visibility) project. Step 3 Review how your brand presence is changing. Trend analysis helps answer questions such as: - Is visibility increasing or decreasing? - Are more AI systems referencing the brand? - Are results becoming more favorable or less favorable over time? These are natural interpretations of the source’s “visibility trends” capability, without inventing new product behavior. Step 4 Use follow-up prompts to go deeper. For example: - “What changed most recently?” - “Which competitor gained share of voice?” - “Which topics show the strongest visibility?” 🏆 Step-by-Step: Compare Share of Voice Against Competitors Step 1 Ask your assistant to compare your brand with competitors. Examples: - “Compare my brand’s AI visibility against competitors” - “Show share of voice for my competitors” - “Who appears more often than my brand in AI answers?” The source explicitly includes competitors and share of voice in the AI Visibility (formerly LLM Visibility) product area. Step 2 The assistant retrieves competitor comparison data. Step 3 Review the share of voice results. This helps you understand how visible your brand is relative to others competing for the same space in AI-generated answers. Step 4 Use follow-up prompts to refine the analysis. For example: - “Which competitor is strongest on this topic?” - “Show me which topics my competitor dominates” - “Where is my brand underrepresented?” 💬 Step-by-Step: Review Sentiment Step 1 Ask your assistant to show sentiment analysis for your brand. Examples: - “Show sentiment for my brand in AI answers” - “How are AI systems describing my brand?” - “What is the sentiment trend for my visibility project?” The source states that AI Visibility (formerly LLM Visibility) returns sentiment. Step 2 The assistant retrieves sentiment results from your visibility data. Step 3 Review how your brand is being described. This can help you understand whether visibility is positive, negative, or mixed across AI-generated responses. Step 4 Ask follow-up questions to identify patterns. Examples: - “Which topics have negative sentiment?” - “Which prompts lead to weaker brand representation?” - “How does sentiment compare with competitors?” 🔗 Step-by-Step: Review Citations and Sources Step 1 Ask your assistant to show citations connected to your brand’s AI visibility. Examples: - “Show me the citations behind my brand visibility” - “What sources are AI systems using?” - “Which citations are associated with my AI Visibility (formerly LLM Visibility) project?” The source explicitly states that the product area manages and returns citations. Step 2 The assistant retrieves source and citation data. Step 3 Review which cited sources are influencing AI answers. This is especially useful for understanding: - which sources are shaping brand representation - whether the sources are accurate - whether competitor sources are appearing more strongly These are direct use cases implied by the citation-tracking feature described in the source. Step 4 Use the results to guide next actions. For example, if the source mix is weak or incomplete, that can inform broader SEO, content, brand, or PR work inside Search Atlas. 🧪 Step-by-Step: Use Prompt-Level Analysis Step 1 Ask your assistant to review how your brand appears for specific prompts or topics. Examples: - “Show prompt-level analysis for my visibility project” - “How does my brand appear for this topic?” - “Which prompts produce the strongest visibility?” The source specifically includes prompt-level analysis. Step 2 The assistant retrieves the relevant prompt-level results. Step 3 Review how responses vary by prompt or topic. This helps you understand whether your brand is consistently visible or only appears in certain contexts. It also helps identify which kinds of prompts are stronger, weaker, or more competitor-dominated. Step 4 Continue with targeted follow-up analysis. For example: - “Show me prompts where competitors appear instead of my brand” - “Which topic has the weakest visibility?” - “Where does my brand sentiment drop?” 🔁 How the AI Visibility Workflow Fits Together A typical MCP workflow for AI Visibility (formerly LLM Visibility) may look like this: Step 1 Start with a visibility project or brand-level request. Step 2 Review high-level visibility data. Step 3 Compare against competitors. Step 4 Inspect sentiment. Step 5 Review citations and sources. Step 6 Go deeper with prompt-level or topic-level analysis. This sequence mirrors the structure of the capability described in the source: projects, topics, competitors, citations, trends, sentiment, share of voice, and prompt-level analysis. ⚠️ Important Notes MCP does not create a new visibility system The MCP gives your assistant conversational access to the AI Visibility (formerly LLM Visibility) product area already available in Search Atlas. It does not create new capabilities outside what your Search Atlas account already supports. Access still depends on plan entitlements As with the rest of MCP, access depends on your Search Atlas plan and permissions. If your account does not include this capability, the assistant cannot execute it successfully. Quota still applies where relevant The source groups AI Visibility (formerly LLM Visibility) alongside work-producing actions such as prompt submission and visibility workflows, which means related quota rules still apply where the product uses them. Results are part of a larger strategy AI Visibility (formerly LLM Visibility) is most useful when combined with the rest of the Search Atlas ecosystem — especially content, brand, SEO, PR, and competitive research. The source positions it as one product area among the broader MCP tool catalog. 🧠 Best Practices Start broad, then narrow Begin with overall visibility, then drill into competitors, citations, sentiment, and prompts. Use trend data, not one-off snapshots A single result can be useful, but trends are more valuable for understanding whether visibility is improving or declining over time. The source explicitly includes visibility trends for this reason. Pair citation review with brand and content work If citations are weak or inconsistent, the right response may involve improving your broader content and brand authority inside Search Atlas. Use competitor comparison as context Share of voice is more meaningful when viewed against named competitors, not in isolation. The source explicitly includes competitors and share of voice as core elements of the AI Visibility (formerly LLM Visibility) toolset. MCP for AI Visibility (formerly LLM Visibility) gives you a conversational way to understand how your brand appears across AI-powered search environments. By combining visibility projects, competitor comparisons, sentiment, citations, and prompt-level analysis, your AI assistant can help you move from simple monitoring to structured insight — using the same Search Atlas capabilities, permissions, and quota rules already tied to your account.

⚠️ 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.

⚠️ 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.

⚠️ 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.

⚠️ 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.

📊 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.