QUEST

🚀 Fix a Stuck Quest LLM Digital PR Campaign

🔍 Overview The Quest AI Visibility (formerly LLM Visibility) tool inside the Authority module lets you run AI-powered Digital PR campaigns that pitch your content to language models. If your campaign is stuck on Paused — even after a support team member has said the issue was resolved — this article walks you through the most common causes and the steps to fix them. 📍 How to Find Your Campaign 1. Open Search Atlas and click Authority in the left sidebar. 2. Select QUEST AI Visibility (formerly LLM Visibility) from the sub-menu. 3. Locate your campaign in the table. Check the status column for Paused. ⚠️ Common Reasons a Campaign Gets Stuck on Paused - Credit balance dropped below the required threshold — even briefly. The system pauses a campaign the moment credits fall short and does not always auto-resume when credits are topped up. - No active contacts selected — a campaign needs at least one valid contact assigned before it can run. - Campaign saved in draft state — if the setup wizard was closed before the final confirmation step, the campaign remains paused. - A recent platform update reset campaign states — UI and styling migrations can occasionally affect campaign status flags. Our engineering team actively monitors and resolves these cases. - Contact list issues — invalid, duplicate, or unverified contacts can prevent delivery and trigger an automatic pause. 🛠️ Step-by-Step Troubleshooting 1. Check your credit balance. Go to the top-right avatar → Billing (Plans & Top-ups) and confirm you have enough credits for the campaign scope. If your balance is sufficient but the campaign is still paused, continue to the next step. 2. Manually resume the campaign. In Authority → PR Distribution (Press Releases), find your release row and click the Resume link/button directly in that row. If the row is not visible, try refreshing the page — a recent fix addressed missing column headers in this table. 3. Verify your contact selection. Open the campaign and review the contacts assigned to it. Make sure at least one contact is active and verified. Remove any contacts marked as invalid or bounced. 4. Re-save the campaign. Open the campaign editor, review each step of the setup wizard, and click Save or Confirm on the final step. This forces the system to re-evaluate the campaign state. 5. Check the Campaigns sub-page. Navigate to Authority → Campaigns for a full list of all campaign statuses. Compare the status here with what you see in QUEST AI Visibility (formerly LLM Visibility) to rule out a display discrepancy. 6. Review Sent and Inbox logs. Go to Authority → Sent and Authority → Inbox to confirm whether any outreach was delivered before the pause. This helps identify exactly when the campaign stopped. 👥 How to Review and Update Contact Selection Correct contact selection is critical for a Digital PR campaign to run successfully. Follow these steps to audit your contacts: 1. Open your campaign from Authority → QUEST AI Visibility (formerly LLM Visibility). 2. Navigate to the Contacts or Sources step inside the campaign editor. 3. Confirm that all listed contacts have a verified status. Remove or replace any that are flagged as invalid. 4. Add new contacts if the list is empty. Use relevant, niche-specific contacts to maximise campaign reach. 5. Save your changes and attempt to resume the campaign. ✅ What to Do If the Campaign Is Still Paused If you have followed all the steps above and the campaign remains stuck on Paused, the issue may require a backend investigation by our team. This can happen after platform updates that affect campaign state flags — our engineering team resolves these on a case-by-case basis. 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. When you reach out, have the following ready to speed up the investigation: - Campaign name and the date it was last active - A screenshot of the current status in QUEST AI Visibility (formerly LLM Visibility) and in Campaigns - Your current credit balance - Any error messages displayed in the Actions menu or campaign editor

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

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

🔍 QUEST vs Real AI Search Query Data

🤔 What This Article Covers Customers sometimes ask whether Search Atlas can surface the exact phrases real users are typing into AI search engines like ChatGPT, Perplexity, or Claude. This article clarifies what QUEST is designed for, what it cannot do, and where to look if you need real user keyword data. ⚠️ The Key Distinction: Simulation vs. Real User Data There are two very different things a customer might be looking for: - Real user query data — the actual phrases people type into AI platforms like ChatGPT, Claude, Gemini, or Perplexity. This data originates inside those closed platforms and is not publicly accessible. - Simulated AI behavior analysis — running prompts through an AI engine inside a tool to see how that AI responds, which sources it cites, and how your brand or content appears in those responses. QUEST only does the second. It does not have access to real prompt data from any external AI platform. 🧪 What QUEST Actually Does QUEST is Search Atlas's AI search simulation tool. It is designed to help you understand how AI engines behave when responding to queries — not to reveal what queries real users are submitting. Specifically, QUEST allows you to: - Submit a prompt and see how an AI search engine constructs its response - Identify which websites, sources, and brands the AI cites or recommends - Test whether your own content or brand appears in AI-generated answers - Compare how different prompt variations affect the AI's response - Analyse the structure and tone of AI answers for content optimisation QUEST is a powerful tool for AI visibility and brand presence analysis. It is not a keyword research tool for AI platforms, and it cannot tell you what phrases your target audience is actually searching for inside ChatGPT or similar tools. 🚫 What QUEST Cannot Do - Access or export real user prompts from ChatGPT, Claude, Gemini, Perplexity, or any other AI platform - Show search volume or trending query data from AI engines - Provide data on how frequently a specific phrase is used in AI searches - Replace traditional keyword research for understanding user intent at scale No third-party tool currently has licensed access to real user query data from closed AI platforms. This is a platform-level restriction, not a Search Atlas limitation. 🔎 How to Find Real User Search Phrases If your goal is to discover the phrases and topics your audience is searching for — whether on Google or AI-assisted search — the best approach is to use Search Atlas's keyword research tools. Keyword Magic — Navigate to Left sidebar → Keywords → Keyword Magic. Enter a seed topic or keyword to generate thousands of related phrases, questions, and long-tail variations based on real search data. This is the most direct way to uncover how users phrase their queries around a given topic. Rank Tracker — Navigate to Left sidebar → Keywords → Rank Tracker. Use this to monitor how your content performs for specific keyword targets over time, helping you refine which phrases drive real traffic. Keyword Gap — Navigate to Left sidebar → Keywords → Keyword Gap. Compare your keyword coverage against competitors to identify high-value phrases you may be missing. These tools draw on real search engine data and are the recommended starting point for any keyword discovery workflow. ✅ Recommended Workflow: Combining Both Approaches For the most complete picture of how users search for your topics — and how AI engines handle those topics — use both capabilities together: 1. Use Keyword Magic (Left sidebar → Keywords → Keyword Magic) to identify real, high-volume search phrases around your topic. 2. Take the most relevant phrases and enter them as prompts in QUEST to see how AI engines respond to those queries. 3. Analyse which sources and brands appear in QUEST's AI-simulated results. 4. Optimise your content to increase the likelihood of being cited in AI-generated answers for those phrases. This combined approach bridges traditional SEO keyword research with AI search visibility — giving you both the demand-side data (what people search) and the supply-side insight (how AI answers it). 💬 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.

🤖 Search Atlas — AI Visibility (QUEST) Troubleshooting

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

🚀 Set Up Quest LLM Digital PR Campaign

📋 Overview Quest LLM Digital PR automates outreach to journalists and publishers using AI-driven story angles. This article walks you through campaign creation, contact selection, and common reasons a campaign may remain in Paused status. 🛠️ Create a New Campaign 1. From the left sidebar, go to Authority → QUEST AI Visibility (formerly LLM Visibility). 2. Click Create Campaign to open the wizard. 3. Step 1 — Sources: Choose the content sources (press releases, blog posts, product pages) that will feed story angles. 4. Step 2 — Angles: Review AI-suggested angles or add custom ones. Each angle becomes a pitch variant. 5. Step 3 — Contacts: Select target contacts (see Contact Selection below). 6. Step 4 — Schedule & Launch: Set send dates, frequency, and click Launch. 🎯 Contact Selection Choosing the right contacts determines deliverability and response rates. - Use verified lists: Filter by Verified badge to ensure email accuracy. - Match niche: Apply topic tags (e.g., SaaS, FinTech) so pitches reach relevant journalists. - Limit per campaign: Start with 50–100 contacts for better personalization and lower bounce risk. - Exclude opted-out: The system auto-excludes contacts who unsubscribed or bounced previously. ⚠️ Why a Campaign Stays “Paused” If your campaign shows Paused for more than a few minutes, check these common causes: - Insufficient credits: Even with a positive balance, a campaign needs enough credits for the full contact list. Open Authority → Campaigns and verify the Credits Required column. - Missing required fields: Every angle must have a subject line, body, and at least one merge tag. Incomplete angles keep the campaign paused. - Contact list empty: If all selected contacts are filtered out (unverified, opted-out, or bounced), the campaign cannot start. - Scheduling conflict: A start date in the past or a frequency that exceeds daily send limits will pause the campaign. - System maintenance: Rare platform updates may temporarily hold campaigns. Check the status banner at the top of the dashboard. ✅ Quick Fix Checklist 1. Confirm credit balance covers the entire contact list. 2. Open the campaign, review each angle for completeness, and save. 3. Re-check contact count after filters; add more verified contacts if needed. 4. Adjust schedule to a future date and reasonable daily limit. 5. Click Resume on the campaign row. 📈 Monitor Performance After launch, track opens, replies, and placements in Authority → Inbox and Sent. Use the Reports tab for aggregate metrics. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 Search Atlas — AI Visibility (QUEST) Issues

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

📧 Configure Email Sender for Quest LLM Visibility Campaigns

🔍 Overview When running outreach campaigns inside Quest LLM Visibility, you need a verified sender email configured before the email option becomes available in the campaign builder. This setting is not managed inside Cloud Stacks or any other Authority sub-section — it lives in a specific area of your account settings. If the email option appears greyed out or missing even though your integrations are connected, this article will walk you through the correct setup path. 🗺️ Where to Find Quest LLM Visibility Quest LLM Visibility is a sub-section of the Authority module. To navigate there: 1. Open Search Atlas and look at the left sidebar. 2. Click Authority. 3. Select QUEST LLM Visibility from the expanded sub-menu. This is separate from Cloud Stacks, URL Indexer, Campaigns, Inbox, and Sent — all of which appear in the same Authority sub-menu but serve different purposes. ✅ Prerequisites Before Configuring a Sender Email Before the email sender option becomes active in Quest LLM Visibility, make sure all of the following conditions are met: - An email integration is connected. Go to your Account Menu (avatar, top-right) → Settings → Email Settings and confirm your email provider (e.g., Gmail, Outlook, SMTP) shows a green Connected status. - The connected account has send permissions. Some integrations connect successfully for read access but lack send permissions. Re-authorise the integration if you are unsure. - Your account plan supports outreach. Confirm that your current subscription includes the Quest LLM Visibility outreach feature. If the section is visible but email is locked, contact support using the chat widget below. ⚙️ How to Configure Your Sender Email Follow these steps to add or update your sender email information for Quest LLM Visibility campaigns: 1. Click your profile avatar or name in the top-right corner of the platform. 2. Select Settings from the dropdown menu. 3. Navigate to the Integrations tab. 4. Locate your email provider under the Email section and click Connect or Manage if already listed. 5. Complete the authorisation flow for your email provider (OAuth for Gmail/Outlook, or SMTP credentials for custom providers). 6. Once the status shows Connected, return to the left sidebar and go to Authority → QUEST LLM Visibility. 7. Open or create a campaign. Inside the campaign builder, the Email channel option should now be active and selectable. 8. Click the Email option and confirm your sender name, sender email address, and reply-to address are populated correctly. 9. Save your changes before launching or scheduling the campaign. 🛠️ Troubleshooting: Email Option Still Missing If you have connected an integration but the email option is still unavailable inside Quest LLM Visibility, work through the following checks: - Refresh the page. After a new integration is connected, a hard refresh (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) is sometimes needed before the platform reflects the new connection. - Reconnect the integration. Go back to Settings → Email Settings, disconnect the email account, and reconnect it from scratch. This resolves token or permission issues that can occur silently. - Check for multiple workspaces. If your account has more than one workspace, integrations connected in one workspace are not automatically available in others. Make sure you are in the correct workspace and repeat the integration setup there. - Verify the integration type. Only email integrations (Gmail, Outlook, or SMTP) unlock the email channel in outreach. Other integration types such as CRM or analytics connectors will not enable the email sender option. - Check browser console errors. If the option appears but cannot be clicked, a browser extension (such as an ad blocker) may be interfering. Try in an incognito window or a different browser. 💡 Key Differences: Integrations Page vs. Campaign Dashboard A common point of confusion is expecting to configure the sender email directly inside the Quest LLM Visibility campaign dashboard. Here is how the two areas relate: - Settings → Email Settings: This is where you authorise your email account and grant Search Atlas permission to send on your behalf. Without completing this step, no email option will appear anywhere in outreach. - Authority → QUEST LLM Visibility → Campaign Builder: This is where you select and customise your sender details (name, address, reply-to) for a specific campaign. These fields only appear after a valid integration exists. Think of the Integrations page as the unlock step, and the campaign builder as where you apply what was unlocked. 💬 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 a Quest LLM Digital PR Campaign Stuck on Paused

🧭 Overview If your Quest LLM Digital PR campaign has been sitting on Paused even after you've confirmed your credits are available, a common cause is that no contacts have been selected for the campaign. Without at least one contact assigned, the platform has no recipients to send outreach to, which can prevent the campaign from activating. This article explains why this happens and what you need to do to get your campaign running. 🔎 Why Does This Happen? A Quest LLM Digital PR campaign requires contacts to be selected before it can move out of a Paused state. Credits and configuration may be set up correctly, but if no contacts have been added as recipients, the campaign may not be able to proceed. This step is easy to overlook if the campaign was saved before contacts were added. ✅ How to Resolve It To get your campaign out of the paused state, you need to ensure at least one contact is selected for the campaign. Here is what to do: 1. Open your Quest LLM Digital PR campaign in the platform. 2. Check whether any contacts have been added as recipients. If none are present, this may be the cause of the paused status. 3. Add the contacts you want to include in this outreach campaign. 4. Once contacts have been selected, the campaign should be able to proceed out of the paused state. If you have added contacts and your campaign remains stuck on Paused, or if you are unsure how to locate the contact selection area in your account, please use the chat widget at the bottom of this page to reach our support team and we will be happy to walk you through it.

🏷️ Use QUEST to Discover How GPTs and LLMs See Your Website

In this guide, you’ll learn how to use QUEST, the Search Atlas visibility tool for LLMs. It helps you trace the source documents referenced by GPTs, benchmark your AI visibility, and launch outreach campaigns to influence those documents. 🔍 What to do Use QUEST to: - Find out whether your domain, brand, or topics are visible in models like GPT. - Identify source documents that inform LLM-generated answers. - Launch targeted digital PR campaigns to modify those sources and increase brand mentions. 🌟 Why it matters The SEO paradigm is shifting to AEO (Answer Engine Optimization). With LLMs generating billions of pieces of content: - If your content isn’t indexed in GPT, you won’t appear in AI-generated answers. - QUEST enables AI Visibility (formerly LLM Visibility) benchmarking, helping you optimize for AI-generated content ecosystems. - Influence what ChatGPT, Claude, and others say—at the source level. 🛠️ How to do it 1. Go to Search Atlas and navigate to Authority → AI Visibility (formerly LLM Visibility) QUEST → Visibility. 2. Enter a topic, brand, or keyword (e.g., “best cat treats”, “plant-based protein powder”). 3. QUEST will: - Run your query across LLMs. - Extract the full AI answer. - Identify the source URLs informing that answer. 4. Review the list of source documents. 5. Click “Create Campaign” to: - Find contact info for authors, editors, or contributors. - Launch email or SMS outreach sequences. - Use prebuilt templates or custom messages. ⚠️ Common mistakes to avoid ❌ Assuming real-time LLM data: Most GPTs (e.g., ChatGPT) are trained on data that’s 6–24 months old. ❌ Relying on a single model: Cross-check your visibility across GPT, Claude, XAI, and others. ❌ Misreading hallucinations: Occasionally, root docs may be incorrect. QUEST flags known cases. 🧠 Interpretation Tips - Focus on recurring sources: If multiple LLM answers cite the same domains, prioritize them. - Look for brand mentions vs. non-brand documents: Not all citations include your brand; identify relevant editorial angles. - Target contributors: QUEST helps you find not just site editors, but also guest authors with wide presence. 💡 Pro Tip QUEST is deeply integrated with the Publisher Exchange and Digital PR tools in Search Atlas. You can cross-filter sites by: - AI Visibility (formerly LLM Visibility) - Inclusion in Google News - Indexation via Bing, Common Crawl, and others Use this to prioritize outreach where AI already shows semantic trust. ✅ Once done You’ll know: - Whether your brand is visible in GPTs. - Which content is shaping LLM output. - Who you need to contact to improve or correct that visibility. If any contacts bounce or sources appear invalid, update your campaign or use QUEST’s contact enrichment workflows. 📚 Useful Official Resources - QUEST | How Do GPTs and LLMs See Your Website - Search Atlas: What is Answer Engine Optimization (AEO)?

🔍 QUEST — Authority Research & AI Visibility (Search Atlas)

Purpose Identify authority opportunities and visibility gaps by analyzing SERP queries and extracting structured questions, answers, and authoritative sources consumable by LLMs and outreach workflows. Primary Function Transform a search query into: - Structured question–answer pairs - Source-level authority signals - Actionable inputs for Digital PR and AI Visibility (formerly LLM Visibility) campaigns UI Entry Point Left Sidebar → Authority → AI Visibility (formerly LLM Visibility) → QUEST Inputs 1. Search query (free-text) 2. SERP-derived data sources 3. Platform query quota 4. Optional project or campaign context (downstream) Core Actions 🔎 Query Analysis Action: Analyze a search query to extract authority-relevant information. User actions: - Enter query in the input field - Click Analyze query Execution characteristics: - Query is processed against live SERP data - Results are stored as a retrievable analysis unit - Each query analysis is tracked independently 🧠 Question & Answer Extraction Action: Generate structured Q&A pairs aligned with authoritative SERP patterns. User actions: - View extracted questions - Review AI-generated expert-style answers - Toggle Highlight Sources per question Execution characteristics: - Questions reflect real SERP and content patterns - Answers are designed for citation, reuse, and outreach - Source highlighting controls attribution visibility 🌐 Source Identification Action: Surface authoritative domains and URLs used to construct answers. User actions: - View source list in right-side panel - Select or deselect individual sources - Select all or clear all sources Execution characteristics: - Sources are derived directly from SERP analysis - Source selection directly affects downstream campaign creation 📣 Campaign Bridging Action: Convert QUEST analysis into a Digital PR campaign. User actions: - Select one or more sources - Click Create Campaign with X Domains Execution characteristics: - Selected sources are passed as campaign targets - No outreach is executed at this stage - Campaign creation occurs in Digital PR State Changes Query Lifecycle - New → Analyzed → Stored - Stored queries appear in QUEST history table Campaign Association - Query remains available after campaign creation - Campaign linkage is additive, not destructive Outputs 1. Structured Q&A datasets 2. Authority-aligned answer blocks 3. Curated list of authoritative domains 4. Campaign-ready source targets 5. LLM-consumable visibility inputs Dependencies 1. QUEST outputs are commonly consumed by: - Digital PR campaigns - Outreach targeting logic - AI Visibility (formerly LLM Visibility) strategies 2. QUEST does not require: - Email connections - Templates - Publishing or indexing actions Non-Goals 1. QUEST does not: - Send outreach emails - Publish content - Build backlinks directly - Modify existing authority assets 2. QUEST is not a content editor or CMS Notes & Tips - 📝 Use QUEST queries that reflect how users actually ask questions, not just keywords. - 📝 Source selection determines outreach scope downstream. - 💡 QUEST is most effective when used before Digital PR execution, not after. - 📝 Queries can be reused across multiple campaigns without re-analysis. QUEST defines the research and intelligence layer of Authority in Search Atlas. It converts unstructured search queries into structured authority signals that can be reused across visibility, outreach, and AI-driven workflows. No execution occurs within QUEST. Its sole function is to produce clean, source-aligned inputs that downstream systems can act upon with precision and control. For execution and distribution, refer to Authority Building and Digital PR documentation.