Plans, Credits & Limits

⚡ Atlas Brain 'Out of Credits' Error Troubleshooting

Understanding the Error Some users see an 'out of credits' message in Atlas Brain even though their account still shows a remaining credit balance. This is a known issue that our team is aware of and investigates on a per-account basis. Because the root cause can vary between accounts, there is no single self-serve fix that applies in all cases. The most effective path to resolution is to contact our support team directly so they can review your specific account and identify what is causing the mismatch. What to Have Ready When You Contact Support To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - Your Search Atlas account email address or project name. - The exact error message you are seeing (a screenshot is helpful). - Your current visible credit balance as shown in your account. - Approximately when the error first appeared. - Any recent changes to your account, such as a plan change or payment update. 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 Atlas Brain and AI Quota Errors

🔍 Overview If you see a 'No available quota for AI Visibility Analysis' error or find that Atlas Brain is unresponsive, the cause is almost always a mismatch between your visible AI quota and the features actually included in your current plan. This article explains why this happens and how to fix it. ⚙️ Why This Error Occurs Your account dashboard may show an AI quota balance (for example, 500 credits), yet Atlas Brain still refuses to run. This contradiction usually happens for one of the following reasons: - Plan downgrade or change: Your subscription was changed to a plan that no longer includes the Atlas Brain feature or LLM Visibility Analysis, even though leftover quota credits are still displayed. - Feature not included in current plan: AI quota credits and Atlas Brain access are separate entitlements. Having quota credits does not automatically unlock every AI-powered feature — Atlas Brain must be explicitly included in your plan. - Billing cycle reset: A recent renewal or plan modification may have reset feature access before your quota was fully refreshed, creating a temporary mismatch. - Account configuration error: In rare cases, a backend sync issue can incorrectly flag your account as ineligible for a feature you should have access to. 🚀 How to Troubleshoot Step by Step 1. Check your current plan: Go to Avatar (top-right) → Billing → Plans & Top-ups and confirm which plan you are on. Look specifically for whether Atlas Brain or LLM Visibility Analysis is listed as an included feature. 2. Review your AI quota details: On the same page, expand your quota breakdown. Confirm that the quota shown is allocated to the feature you are trying to use — not just a general credit pool. 3. Log out and log back in: A fresh session forces your account entitlements to resync. After logging back in, retry Atlas Brain before taking further steps. 4. Clear your browser cache: Stale cache can cause the dashboard to display outdated quota or feature data. Clear your cache, reload the platform, and try again. 5. Try a different browser or incognito mode: This rules out browser extensions or local storage issues interfering with feature access. 6. Confirm no recent plan changes were made: If someone else manages billing on your account, verify no downgrade or seat change occurred recently that may have removed Atlas Brain access. 💡 Understanding AI Quota vs. Feature Access It is important to understand the difference between AI quota credits and feature access: - AI quota credits are the numerical allowance consumed each time an AI-powered action runs (such as generating content or running an analysis). - Feature access is a plan-level permission that determines which tools and modules are available to your account at all. Think of it this way: quota credits are the fuel, but feature access is the key that starts the engine. If Atlas Brain is not included in your plan, having credits will not unlock it. You need both to use the feature successfully. 🔄 How to Restore Atlas Brain Access If you confirm that Atlas Brain or LLM Visibility Analysis is missing from your current plan, here are your options: - Upgrade your plan: Navigate to Avatar (top-right) → Billing → Plans & Top-ups and select a plan that includes Atlas Brain. Changes take effect immediately after checkout. - Contact our team to review your account: If you believe Atlas Brain should already be included in your plan based on your purchase, our team can investigate and correct any configuration errors on the backend. 🛡️ Preventing This Issue in the Future - Before changing or downgrading your plan, review the feature comparison table to confirm Atlas Brain remains included. - If multiple team members manage billing, communicate plan changes in advance to avoid unexpected feature loss. - Bookmark the Avatar (top-right) → Billing → Plans & Top-ups page so you can quickly verify your entitlements whenever an unexpected error appears. 🤝 Still Need Help? If you have followed all the steps above and Atlas Brain is still not working, or if your plan appears correct but the error persists, our team is ready to investigate your specific account. 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 Coworker Quota & Usage Limits

This article explains how Search Atlas Coworker usage counts against your Search Atlas plan quota and what to expect when limits are reached. Does Search Atlas Coworker Use My Search Atlas Quota? Yes — requests that involve Search Atlas data (keyword research, site audits, GSC queries, etc.) count against the same quota as equivalent actions performed in the Search Atlas dashboard. Using Search Atlas Coworker does not give you additional quota on top of your plan. What Counts as a Request - Data lookups (rankings, GSC performance, keyword data) — counted the same as dashboard usage - Site audits — counted as an audit run, same as triggering one from the dashboard - OTTO recommendations — applying a recommendation via Search Atlas Coworker counts the same as applying it from the dashboard - Connector actions (actions in third-party apps) — do not consume Search Atlas quota; they use the connected app's own limits - Routine runs — each scheduled routine execution counts the same as the equivalent manual request What Does Not Count Against Quota - Conversational messages that do not query Search Atlas data (greetings, help questions, explaining capabilities) - Web search results - Image analysis What Happens When Quota Runs Out If your plan quota is exhausted, Search Atlas Coworker will inform you in Slack when you make a request that would exceed it. Active routines that require quota-consuming actions will be paused automatically and will resume at the start of your next billing cycle when quota resets. Checking Your Remaining Quota Ask Search Atlas Coworker: "How much of my quota have I used this month?" for a real-time usage summary, or check your avatar → Billing → Plans & Top-ups page in the Search Atlas dashboard. Upgrading Your Plan If you consistently hit quota limits through Search Atlas Coworker usage, consider upgrading your Search Atlas plan. Contact support or visit the top-right corner (avatar) → Billing → Plans & Top-ups tab (Billing) for available options.

⚡ CoWorker Plugin, OTTO Quota, and Multi-Domain Testing

Overview The Search Atlas CoWorker WordPress plugin and OTTO are two separate tools that can work independently of each other. A common point of confusion is whether activating the CoWorker plugin on a domain requires an OTTO project, and whether it uses up your available OTTO site slots. This article clarifies both questions and explains how multi-domain testing relates to your quota. Does CoWorker Require an OTTO Project? No. The CoWorker WordPress plugin does not require an OTTO project to function. You can install and activate CoWorker on any WordPress site purely as a standalone integration — including on a staging or test domain — without creating an OTTO project for that domain at all. The two workflows are distinct: - CoWorker only: Install the plugin on your WordPress site and connect it to your Search Atlas account independently. No OTTO setup is needed and no OTTO quota is consumed. - CoWorker + OTTO: Create an OTTO project for a domain, then connect CoWorker to that same domain so OTTO can push optimisations directly to your WordPress site. This workflow does consume one OTTO site slot. Does the CoWorker Plugin Count Against My OTTO Quota? Only if you connect the plugin to an active OTTO project. Here is a simple breakdown: - CoWorker plugin installed, no OTTO project created: Zero OTTO quota consumed. - CoWorker plugin connected to an OTTO project: One OTTO site slot is used for that domain. This means installing CoWorker on a test or staging domain without creating an OTTO project for it leaves your OTTO site slots completely untouched. Multi-Domain Testing and Switching to Production Because CoWorker and OTTO are independent, you can safely install CoWorker on a staging domain to verify it is working, and later install it on your production domain, without affecting your OTTO quota at any point during that process. Only when you choose to create an OTTO project and link it to a specific domain will a slot be consumed for that domain. If you are unsure how to connect CoWorker to your Search Atlas account, or how to link an OTTO project to CoWorker once you are ready for production, our support team can walk you through the exact steps for your account setup. When You Are Ready to Add OTTO to Production If you later decide to activate OTTO on your production domain to automate on-page optimisations, you will need to create an OTTO project for that domain and link it to CoWorker. At that point, one OTTO site slot will be consumed. If you need help with this step, reach out to our team with your project name and the domain you want to activate OTTO on, so we can confirm the correct setup for your account. 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.

🔍 Atlas Agent Meta Tag Verification Limits Explained

🤖 What Atlas Agent Can Do with Meta Tags Atlas Agent can read and analyse the meta tag data that Search Atlas has already crawled and stored for your pages. This includes your title tags, meta descriptions, Open Graph tags, and canonical tags as they appeared during the most recent crawl of your site. Within the platform, Atlas Agent can: - Report the current meta tag values stored in Search Atlas for any crawled URL - Flag tags that exceed recommended character limits - Identify missing or duplicate meta tags across your site - Suggest optimised meta tag copy based on your target keywords ⚠️ What Atlas Agent Cannot Do Atlas Agent does not fetch live meta tags in real time directly from your website during a conversation. When you ask Atlas Agent to verify a meta tag, it is reading from the most recent crawl snapshot — not pulling the current live version of your page. This means: - Changes you made after the last crawl will not be reflected in Atlas Agent's response - Atlas Agent cannot confirm whether a tag update has gone live on your server - Atlas Agent cannot resolve discrepancies between what your CMS shows and what is actually served to search engines or social platforms 🔎 Why Clipped-Preview Errors Occur A clipped-preview error happens when a meta description or title tag is longer than the character limit that search engines or social platforms display. Common thresholds are approximately 155–160 characters for meta descriptions and 50–60 characters for title tags, though these can vary. These errors can appear in Atlas Agent's analysis for two reasons: 1. The tag genuinely exceeds the limit in the crawl data Search Atlas holds for your page. 2. The crawl snapshot is outdated, and the value stored differs from what is currently live on your site — sometimes a previously long tag was not yet corrected at crawl time. Because Atlas Agent works from crawl data rather than a live fetch, it may report a clipped-preview error for a tag you have already fixed, or miss one that was introduced after the last crawl. ✅ How to Reliably Verify Your Live Meta Tags To confirm the exact meta tag values currently served on your live page, use one of these manual methods: 1. View page source: Open your page in a browser, right-click, and select View Page Source. Use Ctrl+F / Cmd+F to search for meta name="description" or og:title to locate the relevant tags and copy their content values. 2. Google's Rich Results Test: Paste your URL into Google's Rich Results Test to see what Googlebot fetches live from your page. 3. Facebook Sharing Debugger: Use the Facebook Sharing Debugger to check Open Graph tags and force a fresh fetch of your URL. 4. LinkedIn Post Inspector: Use LinkedIn's Post Inspector tool to verify how your tags render on LinkedIn previews. Once you have confirmed the correct live values, return to Search Atlas and trigger a manual recrawl of the affected URLs. This updates the crawl snapshot Atlas Agent uses and clears outdated clipped-preview flags. 🔄 How to Trigger a Manual Recrawl in Search Atlas 1. Go to Site Metrics in the left navigation menu. 2. Select your project and open Pages. 3. Find the URL you want to recheck using the search bar. 4. Select the URL and click Recrawl (or Recrawl Selected if updating multiple pages). 5. Wait for the crawl to complete, then reopen the page details to confirm the updated meta tag values are now reflected. After a successful recrawl, any clipped-preview errors tied to tags you have already corrected will be resolved in the platform automatically. 📋 Quick Reference: Recommended Meta Tag Length Limits - Title tag: 50–60 characters (under 580 pixels rendered width) - Meta description: 120–158 characters for desktop; aim for under 120 for mobile safety - OG title: Under 60 characters - OG description: Under 200 characters Staying within these ranges reduces the likelihood of clipped-preview errors appearing in both Search Atlas and external preview tools. 🙋 When to Escalate to a Human Teammate Contact the support team if you experience any of the following: - A manual recrawl does not update the meta tag values shown in Search Atlas after 24 hours - Atlas Agent is consistently reporting clipped-preview errors for tags that are within the correct character limits on your live page - You need help setting up automated crawl schedules to keep your snapshot data current - You suspect a technical issue with how Search Atlas is crawling a specific URL or domain 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.

Atlas Brain Zero-Quota Bug Blocking LLMv Queries

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