Troubleshooting

🛠️ Troubleshoot Non-Clickable Loop Artifacts

🔍 What this issue means Some loop runs produce output artifacts that appear in Search Atlas but cannot be opened or clicked. This usually means the output is still loading, was not saved as an interactive artifact, or the page displayed an outdated session state. ✅ Check the loop output 1. Open the loop and wait for the run to finish completely. 2. Check whether the output is labeled as an artifact, result, or plain text. Only interactive artifacts include an openable destination. 3. Refresh the page once the run is complete. A refresh can restore the artifact when the first page load shows incomplete output data. 4. Open the loop again and check whether the artifact is now clickable. 🧭 Understand expected behavior Not every loop output is designed to open as a separate artifact. Text, status messages, evaluation results, and other informational output may be displayed without a link. Interactive outputs should provide a clickable target when the artifact has been successfully created and saved. ⚙️ If the artifact remains unavailable - Confirm that the loop run completed without an error. - Try refreshing the page and reopening the relevant workspace or issue. - Check whether the output appears consistently across repeated runs. - Record the loop name, run time, output type, and the URL of the affected page. - Take a screenshot showing the non-clickable output, if possible. Do not repeatedly regenerate the loop if the output is missing. Re-running may create a different result and make the original issue harder to investigate. 💬 Contact support If the output should be interactive but remains non-clickable after these steps, share the recorded details with our team so we can investigate the specific run. 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.

🐛 Fix: Co-worker Scheduled Jobs Now Manageable

A bug that blocked users from deactivating or deleting co-worker scheduled jobs has been fixed, restoring full control over scheduled job management. ✨ What's New Previously, co-worker scheduled jobs could not be deactivated or deleted, leaving users unable to manage or clean up automation tasks assigned to co-workers. This issue has been resolved — all scheduled jobs, including those associated with co-workers, can now be fully managed as expected. 🛠️ How to Use It 1. Navigate to the scheduled jobs section within your workspace. 2. Locate the co-worker scheduled job you wish to manage. 3. Use the available options to deactivate or delete the job as needed. 📋 What to Expect Deactivating a scheduled job will pause it without permanently removing it, while deleting it will remove it entirely. This fix applies to all co-worker scheduled jobs across your account. No additional configuration is required — the controls are available immediately. 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.

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

💬 How to Locate Missing Chat History

This article explains what to do when a previous chat session is not visible in the platform. If you believe you did not delete a conversation but it is no longer appearing, the steps below will help you locate it and escalate if needed. Common Causes of Missing Chat History - Account or workspace mismatch: You may be logged into a different account or workspace than the one where the original chat took place. - Browser or cache issue: A corrupted browser cache can sometimes prevent chat history from displaying correctly. Steps to Try 1. Confirm you are signed into the correct account. If you use multiple workspaces or email addresses, log out and sign back in with the account that was active during the original chat. 2. Perform a hard refresh of the page (press Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) to clear any cached display issues. 3. Clear your browser cache and cookies, then reload the platform and check whether the chat history reappears. 4. Try accessing the platform in a different browser or an incognito/private window to rule out a local browser issue. If the Chat History Is Still Missing If the conversation does not reappear after completing the steps above, please reach out to our support team with the following information ready so we can investigate on our end: - The approximate date and time of the missing conversation - The account email address or workspace name associated with the session - A description of where in the platform you expected to find the chat history 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.

Missing Skill in Your Migration Workflow

If a skill component appears to be missing while working through a multi-stage migration process in Search Atlas, use this article to collect the right information and get targeted help from our support team. ⚠️ Why This Happens Migration workflows may involve packaged skill files or templates that are applied across multiple stages. A missing component can occur for a number of reasons — including an incomplete download, a mismatch between your account configuration and the expected package version, or a feature that has not yet been enabled for your workspace. Because the root cause varies by account, there is no single universal fix, and our team will need to review your specific setup. The most commonly reported missing component is the migration-template-builder skill, which is expected at Stage 4 of the workflow. The v1.4 package (released 2026-06-23) has been confirmed in some cases to ship with only six skill folders, leaving this component absent. The underlying feature has been completed on the engineering side, so if this skill is missing from your package, the most likely cause is that it has not yet been enabled for your specific workspace — our support team can arrange this directly. 📋 Information to Collect Before Contacting Support Having the following details ready will help our team resolve your issue faster: - The name of the missing skill or template component, exactly as it appears (or should appear) in the workflow — for example, migration-template-builder at Stage 4 - The stage or step in the migration process where the issue occurred - Whether you received or downloaded a package or file as part of this workflow, and when — including the version number if visible (for example, v1.4) - A screenshot showing the missing element or any error message displayed on screen - Your account email address and the name of the affected workspace or project 🔄 Basic Troubleshooting Steps Before reaching out, try the following to rule out common session or cache issues: 1. Refresh your browser and re-open the migration workflow from the beginning. 2. Log out of your Search Atlas account completely, then log back in. 3. Try accessing the workflow in a different browser or in an Incognito / Private window. 4. If you downloaded a package or template file, confirm the download completed without errors. If uncertain, attempt to download it again from the original source. 5. If the skill is still missing after these steps, contact our live support team with the details gathered above. ⏱️ What to Expect From Support Our team will review your account and migration workflow configuration to identify why the skill component is not available. For issues that require a deeper investigation, your case will be escalated to the relevant product team. You will be kept updated throughout the process and notified once a resolution or workaround is confirmed. 💬 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.

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

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.

🔗 Fix ClickUp Connector Stuck After OAuth Approval

🔍 What Is This Issue? When connecting ClickUp to your Search Atlas Coworker workspace, you may encounter a situation where the OAuth authorization window appears, you approve the connection, and then the screen shows a waiting or loading state with no further progress. The connector does not complete setup, and ClickUp remains disconnected. ⚠️ Why This Happened This was a confirmed bug in the ClickUp integration within the Coworker connector flow. The issue was reproduced by our support team and escalated to engineering. The root cause involved problems with the OAuth handling and real-time notification delivery during the connection attempt. Engineering resolved this through a series of backend fixes, including updates to the ClickUp OAuth flow, improved timeout handling, and real-time status notifications for connector attempts. ✅ Current Status This issue has been resolved. The engineering fixes have been deployed, and the ClickUp connector should now complete the OAuth authorization flow successfully. No action is required on your end beyond attempting the connection again. 🛠️ Steps to Reconnect ClickUp 1. Log in to your Search Atlas account and navigate to the Coworker section. 2. Go to the Connectors area and locate the ClickUp integration. 3. Start the connection process. The OAuth authorization window will open. 4. Approve the requested permissions in the ClickUp authorization window. 5. Wait a few seconds for the platform to confirm the connection. The connector should now show as connected without hanging. 6. If the connector shows as connected, you are all set and can begin using ClickUp within Coworker. 🔄 If the Issue Still Occurs While this bug has been marked resolved, if you are still experiencing a hanging or stuck state after completing OAuth approval, try the following before contacting support: - Refresh the page after approving access and check whether the connector status has updated. - Clear your browser cache and cookies, then attempt the connection again in a clean browser session. - Try a different browser to rule out a browser-specific compatibility issue. - Check your pop-up blocker settings to ensure the OAuth window is not being silently blocked or interrupted mid-flow. - Revoke the Search Atlas app permissions in your ClickUp account settings, then retry the connection from scratch to start with a clean authorization state. 💬 Need More Help? If you have followed all the steps above and the ClickUp connector is still not connecting, our team wants to hear from you so we can investigate further. 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.

Fix GBP Lock Errors and Missing Social Fields

🔍 Overview Two common issues can interrupt your GBP Golden Loop progress in Search Atlas: a lock error that prevents your profile from staying locked, and a validation blocker when a client does not have every social media account or optional attribute listed in the checklist. This article explains why these happen and what to do next. ⚠️ Understanding the GBP Lock Error When you attempt to lock a GBP project in Search Atlas, you may encounter errors or find that the lock does not hold as expected. These issues can be caused by Google-side restrictions on certain address fields or by platform-level behaviour affecting how location data is saved. Because the exact cause can vary by account and location, our team will need to investigate your specific project. 🛠️ What to Do When the GBP Lock Fails If you are experiencing a GBP lock error or the lock is not persisting on your project, please escalate to our support team so we can investigate. To help us resolve this as quickly as possible, have the following ready before reaching out: - The name of the affected GBP project in Search Atlas. - The exact error message you are seeing (copy it word for word if possible). - The timestamp or approximate time when the error first occurred. - Whether the lock appears to save initially but then resets, or whether it fails immediately. - Any recent changes made to the address or profile fields before the error appeared. 📋 Handling Missing Social Media Accounts The Golden Loop checklist may include social media profile URLs (such as Facebook, Instagram, X, LinkedIn, or others) as required fields. If a client does not have one or more of these accounts, the checklist item may block you from marking the profile as complete. Because the available options for handling missing fields depend on how your specific checklist is configured, our team can advise on the correct approach for your account. When escalating, please include: - The name of the GBP project and the specific checklist field that is causing the blocker. - Whether the client has confirmed they will not be creating the missing social account. - A screenshot of the checklist item and any options currently visible to you. 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.

🔧 Fix Stalling Approvals in Slack and Dashboard

Overview Some users have experienced a frustrating issue where approval actions sent through Slack or the Search Atlas Dashboard appear to stall indefinitely — hitting approve has no effect, and the workflow never moves forward. This article explains what caused the issue, how it was resolved, and what to do if you encounter similar behavior. What Caused This Issue This problem was traced to a confirmed engineering bug affecting the approval flow for AI agent and Coworker workflows. The bug caused approval actions to fail silently: the system appeared to accept your approval, but nothing executed behind the scenes. No status update was sent to Slack or the Dashboard, leaving the workflow stuck with no indication of what went wrong. This issue has since been identified and resolved by the engineering team. Current Status The engineering team has completed the fix. If you were affected by this bug, approval actions through both Slack and the Search Atlas Dashboard should now work reliably. No action is required on your end to apply the fix — it was deployed automatically. Steps to Verify Everything Is Working 1. Open the Search Atlas platform and navigate to your AI agent or Coworker workflow area. 2. Trigger or locate a pending approval action in your workflow. 3. Submit your approval and wait a moment for the system to respond. 4. Check whether the workflow advances as expected — either in the Dashboard or in your connected Slack channel. 5. If the action completes successfully, no further steps are needed. If You Are Still Experiencing Stalling If approval actions are still not moving forward after the fix, try the following before contacting support: - Refresh your browser and retry the approval. Occasionally a stale session can cause the interface to appear unresponsive even when the backend is functioning. - Clear your browser cache and reload the platform, then attempt the approval again. - Check your Slack connection within the Search Atlas Dashboard to confirm your Slack integration is still active. If it appears disconnected, use the available option to reconnect it. - Try approving from a different surface — if the action is stalling in Slack, attempt it directly from the Search Atlas Dashboard, or vice versa. - Wait a few minutes and retry. Transient network or service interruptions can occasionally delay responses. If the action processes after a short wait, no further action is needed. What to Include If You Need Further Help If you are still experiencing stalling after trying the steps above, please reach out to our support team. Include your account details, a description of the workflow involved, and the surface where the stalling is occurring (Slack, Dashboard, or both). If you need assistance, you can contact us through the Search Atlas support channel.

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

🔍 Fix LLM Visibility Activation Permission Errors

🧩 What This Article Covers If you see an error saying you have reached your LLM Visibility project limit — even though your account appears to have available quota — the most common cause is a user permission issue, not a quota issue. This article explains what causes the error and how your account admin can resolve it. ⚠️ Why This Error Happens Search Atlas enforces role-based permissions on all project actions. If your user seat is set to Viewer, you have read-only access to the platform. This means you cannot activate, create, or modify projects — including LLM Visibility tracking — regardless of how much quota your account has available. When a Viewer attempts to activate LLM Visibility, the system may surface a quota or limit error instead of a clear permissions message. This can make it appear as though the account has run out of LLM Visibility project slots, when in reality the action is simply blocked by your access level. ✅ How to Resolve the Issue To fix this, your account administrator must update your user role. Viewers cannot make this change themselves — only an admin can adjust team member permissions. 1. Ask your account admin to log in to Search Atlas. 2. Have them navigate to the account settings area and locate the section where team members and user roles are managed. 3. The admin should locate your user account in the list. 4. The admin should change your role from Viewer to a role that includes project activation permissions (such as Editor or Admin, depending on what your plan supports). 5. Save the changes. 6. Once your role has been updated, log out and log back in to your account. 7. Navigate to the LLM Visibility section of the platform and attempt to activate LLM Visibility for your project again. 💡 How to Check Your Current Role If you are unsure what role your user seat currently has, ask your account admin to check the team members area in your account settings. Your role will be displayed next to your name or email address. Only users with a role above Viewer can perform activation actions on projects. 👤 Who Is the Account Admin? The account admin is typically the person who originally created the Search Atlas account or the person who invited you to join the workspace. If you are not sure who the admin is, check any invitation emails you received when you were added to the account — the sender is usually the admin. 🔄 After Permissions Are Updated Once your role has been changed to an appropriate access level, you should be able to activate LLM Visibility tracking for your project without encountering the limit error. If the error persists after your role has been updated, it is possible that your account has genuinely reached its LLM Visibility project quota for your current plan, in which case you can either purchase additional project slots as a quota top-up or upgrade your plan.

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.

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.

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

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

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

🔧 Fix GA4, GSC & LLM Visibility Report Issues

Overview Two separate but commonly related issues can disrupt your reporting in Search Atlas: GA4 and GSC integrations disconnecting, and shared LLM Visibility & Sentiment report links showing blank or missing data. This article explains what is known about each issue and the steps you can take. Why GA4 and GSC Connections Disconnect GA4 and GSC connections can stop working for a variety of reasons. When a disconnection occurs, metrics that depend on a live GA4 or GSC connection may stop updating. How to Reconnect GA4 and GSC To restore a disconnected GA4 or GSC integration, navigate to your integrations settings within the platform and locate the disconnected connection. Re-authenticate using the Google account that has access to the relevant GA4 property and GSC site, and grant all requested permissions when prompted. Once reconnected, allow some time for data to refresh before checking your reports. Why Shared LLM Visibility Report Links Show Blank Data When you share an LLM Visibility & Sentiment report using a shareable link, the recipient may see a blank report or missing data. Known contributing factors include date range settings and sharing configuration limitations. If recipients see blank data, try adjusting the date range on the shared link to ensure it covers the period when your LLM Visibility tracking was active. If the issue persists after adjusting the date range, it may relate to how the report was shared or to a platform-side limitation. In that case, please reach out to the support team for review. OTTO Integration and Reporting If you are using OTTO alongside GA4, GSC, or LLM Visibility reports and notice data discrepancies or unexpected behavior, please contact the support team with your project name and a description of the issue so it can be investigated. 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.

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

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

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

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

🔧 Fix LLM Visibility Project Slot Discrepancies

Why Your Slot Count May Look Off If your AI Visibility quota shows fewer available slots than you expect — or appears fully used when you haven't created that many projects — a discrepancy in how slots are counted is likely the cause. This article explains what may be happening and what to have ready when you contact support. Common Causes of Quota Discrepancies Quota discrepancies in the AI Visibility (LLM Visibility) area can occur for a variety of reasons. Because this type of issue typically requires a backend investigation to identify and correct the exact cause for your account, our team will need to look into your specific slot count on your behalf. Steps to Take If Your Quota Looks Wrong 1. Note the exact quota figure currently shown on your AI Visibility page (for example, 4/4 slots used). 2. Count how many projects you believe you have actively created or are aware of on your account. 3. Note the difference between the two numbers — this is the discrepancy to report. 4. Gather your account or workspace name so our team can locate your account quickly. 5. Contact support with this information so the team can investigate and correct the slot count on the backend. 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.

🔧 Fix Content Genius Mismatches and Understand LLM Visibility

Overview This article covers two common questions: why Content Genius sometimes generates articles that don't match your intended topic, and how Search Atlas calculates LLM Visibility metrics. Both issues are closely related — strong topic alignment in your content directly influences your visibility scores across AI-powered search engines. Why Content Genius Generates Off-Topic Articles Content Genius uses your inputs — such as your keyword, topic brief, audience, and intent — to generate article drafts. When the output doesn't match your expected topic, it is typically caused by one of the following: - Vague or broad seed keyword: Using a keyword that is too general gives the AI too much room to interpret direction. Use specific, intent-driven phrases that clearly reflect the exact topic you want to cover. - Missing or thin brief: If the topic brief is left empty or contains only a few words, Content Genius may drift from your intended topic. - Conflicting inputs: A mismatch between your keyword and your brief can cause the AI to blend both signals, producing an unfocused draft. - Incorrect content type selection: Choosing the wrong format for your topic can skew the article structure and narrative direction. How to Fix a Topic Mismatch in Content Genius 1. Open Content → Content Genius (What are we writing today?) in Search Atlas. 2. Start a new article rather than re-running the same settings that produced the mismatch. 3. Enter a specific, long-tail keyword that clearly reflects the exact topic you want to cover. 4. Write a clear topic brief — 2–4 sentences describing the article's goal, target audience, and the main question it should answer. The more precise your brief, the more accurate the output. 5. Select the content type and search intent options that best match your goal. 6. Generate the draft and review it. If a section still drifts off-topic, try rewriting that section's input with a more specific instruction. How Search Atlas Calculates LLM Visibility Metrics LLM Visibility metrics measure how prominently your brand or content appears across AI-powered search engines and large language models. To understand and improve your LLM Visibility score, you can take the following self-serve steps: - Check your LLM Visibility dashboard: Navigate to the LLM Visibility section in your Search Atlas project to see your current score and any available breakdown of contributing factors. - Review your tracked brand mentions and citations: The dashboard surfaces how often your brand or content is referenced in AI-generated responses. Look for gaps in coverage across the AI engines being tracked. - Strengthen topical authority: Publishing comprehensive, well-structured content on topics relevant to your niche helps AI models recognize your site as an authoritative source. Use the Content Planner and Topical Maps tools in Search Atlas to identify and close content gaps. - Run an on-page audit: Use the On-Page Audit tool to ensure your existing pages meet quality and relevance standards that support AI citation signals. - Allow time for score updates: LLM Visibility scores reflect data gathered from AI engines over time. If you have recently published or updated content, allow some time before expecting the score to update. If your score does not reflect recent changes after sufficient time has passed, or if you need clarification on a specific metric in your account, escalate to support with your project name and the specific score or metric you have questions about. 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.

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

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

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

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

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