Authority Building

💡 Understanding Hyperdrive Credits and Authority Building Usage

🔍 What Are Hyperdrive Credits? Hyperdrive Credits (HDC) are a dedicated credit currency used exclusively by Search Atlas Authority Building tools. They are separate from your general platform credits and are consumed whenever you use features such as PR Distribution, Cloud Stacks, and the URL Indexer. Previously labeled simply as "Credits" inside the Authority section, these have been officially renamed to Hyperdrive Credits (HDC) across the platform so you can always tell them apart from other credit types. ⚙️ Which Actions Consume Hyperdrive Credits? The following Authority Building actions deduct HDC from your balance: - PR Distribution — Creating or resuming a press release campaign consumes HDC based on the distribution scope selected. - Cloud Stacks — Building a new Cloud Stack or applying a custom template triggers an HDC charge proportional to the number of sites and assets generated. - URL Indexer — Each URL submitted for indexing deducts 1 HDC per URL. Large batches can therefore add up quickly. For example, submitting 100,000 URLs would consume 100,000 HDC. - QUEST AI Visibility — Running visibility analyses draws from your HDC quota as shown in the Quotas panel. - Campaigns — Active outreach campaigns may trigger ongoing HDC usage depending on their configuration. If you noticed a sudden, large drop in your credits — for instance, 100,000 HDC disappearing — the most common cause is a bulk URL Indexer submission or a large Cloud Stack build that ran in the background after being initiated. 🔎 How to Review Your Credit Activity To identify exactly what consumed your Hyperdrive Credits, follow these steps: 1. Click your avatar in the top-right corner of the platform. 2. Select Billing from the dropdown menu. 3. Open the Activity Log tab. 4. Review the timestamped entries — each HDC deduction is logged with the associated action, tool, and amount consumed. This log is the fastest way to pinpoint which action caused an unexpected credit drop. Filter by date to narrow down the timeframe in question. 📊 Checking Your Current HDC Balance and Quotas To see your current Hyperdrive Credit balance and remaining quotas: 1. Go to Left sidebar → Authority → QUEST AI Visibility. 2. Click Quotas to view your HDC allocation and remaining balance. 3. Alternatively, navigate to Avatar → Billing → Plans & Top-ups and click Quota model details for a full breakdown of all credit types on your plan. 🌐 Can My Plan Support Two More Authority-Focused Websites? Whether your current plan can accommodate additional websites focused on Authority Building depends on two factors: - Website slot limit — Your plan may cap the number of projects or domains you can manage simultaneously. Check your plan details under Avatar → Billing → Plans & Top-ups. - Hyperdrive Credit allocation — Authority Building tools are HDC-intensive. Adding two more websites running PR Distribution, Cloud Stacks, or the URL Indexer will increase your monthly HDC consumption significantly. Review your current usage trend in the Activity Log before scaling up. If your plan's HDC allocation is already being fully consumed by your existing website(s), you can purchase additional credits via Avatar → Billing → Plans & Top-ups → Add Payment Method or explore a higher-tier plan that includes a larger HDC quota. ✅ Best Practices to Avoid Unexpected Credit Usage - Before submitting URLs to the Indexer, double-check the batch size — each URL costs 1 HDC. - When creating a new Cloud Stack, review the site count and template scope on the confirmation screen before finalising. - Set a habit of checking the Activity Log weekly to catch unexpected usage early. - If you plan to scale Authority Building across multiple domains, contact our team in advance to ensure your plan's HDC allocation is sufficient. 🛠️ Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ GMB Automation, Authority Building, and Site Management

Overview This article covers four key workflows in Search Atlas: setting up GMB post automation, understanding how auto-posting displays, building domain authority, cleaning up blog content, and removing websites from your account. Because the specific steps for each of these workflows may vary based on your account configuration, the guidance below outlines what each feature is designed to do and what to have ready when contacting support. GMB Post Automation — Scheduling and Frequency Search Atlas automates your Google Business Profile (GMB) posting through the OTTO workflow. Key things to know: - How to enable automation: Navigate to Local → Posts (GBP Posts) in your Search Atlas account and activate it for your website. - Post content: OTTO generates post copy automatically based on your business information and target keywords. You do not need to write individual posts manually. - Scheduling display: Auto-generated GMB posts may not appear with a visible "Scheduled" label inside the platform. If you do not see one, this does not necessarily mean posts are not queued — OTTO manages the publishing cycle internally. If you are unsure whether your GMB automation is active or posts are being published correctly, contact support with your website/project name and a description of what you are seeing so the team can check the status directly. OTTO Content Generation and Template Management OTTO handles content generation for GMB posts automatically. If you need to stop a specific post type from being used, or if you want to edit content before it publishes, reach out to support with your project name and the specific post or template in question so the team can assist. Building Authority — Integrated Features Search Atlas provides several tools to build domain and local authority alongside your GMB automation, including Press Releases, Cloud Stacks, Wildfires, and Digital Outreach. These tools are accessible within your Search Atlas account. - Press Releases: Publish keyword-rich press releases to create brand signals and support new GMB campaigns or site launches. - Cloud Stacks: Create a network of web properties that link back to your site to strengthen domain trust. - Wildfires and Digital Outreach: Additional authority-building tools available in your account to support broader link-building and local SEO campaigns. If you are unsure how to access or configure any of these features for your account, contact support with your project name and the specific feature you need help with. Blog Cleanup and Website Removal If you need to clean up blog posts generated by OTTO or remove a website from your account entirely, these actions may require backend assistance depending on your account setup. When contacting support, have your project name and a description of what you need removed or cleaned up ready so the team can assist efficiently. 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.

🔗 Auditing Links and Understanding Conversions in Actions

📋 Overview Conversion actions in Search Atlas serve two related but distinct purposes: tracking meaningful user interactions and attributing cost efficiency through CPA (Cost Per Acquisition). This article explains how to audit or review the links embedded within your conversion actions, and clarifies exactly what counts as a conversion versus a lead — and why that distinction matters for your CPA metrics. 🔍 What Is a Conversion Action? A conversion action is a defined event you want users to complete — such as clicking a tracked link, submitting a form, or reaching a destination URL. Conversion actions are managed inside the Ads section of the platform (left sidebar → Ads for Google Ads/Meta Ads campaign tools) and are commonly used within Campaigns to track outreach performance. Each conversion action can contain one or more links. Auditing those links means verifying that the URLs are correct, active, and pointing to the intended destinations before or after a campaign runs. 🗂️ How to Audit Links Within a Conversion Action 1. In the left sidebar, navigate to Ads → Google Ads (Campaign Hub). 2. Locate the campaign that contains the conversion action you want to review and open it. 3. Find the conversion action associated with that campaign. This is typically listed in the campaign details or settings panel. 4. Open the conversion action to view its full configuration, including all URLs or links attached to it. 5. Review each link for the following: the destination URL is correct and resolving, the link matches the intended landing page or tracked asset, and no redirects or broken paths are present. 6. If you need to update a link, edit it directly within the conversion action and save your changes before the action is used in an active campaign. If you are reviewing links in actions connected to outreach sequences, also check the relevant submenu items under Authority (Press Releases) — such as Authority Building, PR Distribution, Cloud Stacks, Indexer, or Link Building Exchange to confirm that links in delivered messages match your intended conversion action configuration. ⚠️ Note: This Is Not Backlink Auditing Auditing links within conversion actions is different from auditing backlinks pointing to your website. If you arrived here looking for backlink analysis — such as reviewing referring domains or toxic links — that functionality is available in the Site Explorer tool, not in Authority Campaigns. This article specifically covers links that live inside your conversion action setups. 📊 Conversions vs. Leads: What Is the Difference? Understanding this distinction is essential for interpreting your CPA correctly. - Lead: A lead is a raw contact or response — for example, a person who replied to an outreach email, filled out a form, or expressed interest. A lead represents an interaction, but it has not yet been qualified or confirmed as a desired outcome. - Conversion: A conversion is a completed, goal-aligned action that you have defined in your conversion action settings. Not every lead becomes a conversion. A conversion only occurs when the specific criteria you configured — such as clicking a tracked link, reaching a confirmation page, or completing a defined step — are met. In short: all conversions involve a lead-level interaction, but not all leads are conversions. The conversion is the subset that meets your defined success criteria. 💰 How Conversions Affect CPA CPA (Cost Per Acquisition) is calculated based on conversions, not total lead count. This means: - If a campaign generates 50 leads but only 10 meet your conversion action criteria, your CPA is calculated using those 10 conversions — not 50. - A high lead count with a low conversion count will result in a higher CPA, signalling that the campaign is generating interest but not completing the desired goal efficiently. - Optimising your conversion actions — ensuring the right links are in place, the criteria are accurately defined, and the tracked steps are realistic — directly improves your CPA over time. Always verify that your conversion action is correctly configured before launching a campaign. Misconfigured links or overly broad conversion criteria can skew your CPA data and make it harder to assess true campaign performance. ✅ Quick Checklist Before Running a Campaign - Open the conversion action and confirm all links resolve correctly. - Verify the conversion trigger matches your actual goal (link click, page visit, form submission, etc.). - Confirm you understand which interactions count as conversions versus general lead responses. - Check the relevant submenu under Authority (Press Releases) — such as Authority Building, PR Distribution, Cloud Stacks, Indexer, or Link Building Exchange — after sending to verify delivered links match your conversion action setup. 💬 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.

🔎 Authority Building — URL Indexer

Overview This article covers: URL submission workflows, Left sidebar → Authority → Indexer (URL Indexer), CSV imports, indexation delays, quota handling, pending URLs, Google Search Console verification issues, quota balance corruption, and schema deployment failures. The URL Indexer submits pages to Google's indexing systems, but final indexation decisions are controlled entirely by Google. Because Google evaluates content quality, crawlability, authority, canonical structure, and technical SEO signals, successful submission does not guarantee immediate crawling, indexation, or rankings. ⚠️ Error 1: URL submission shows "Queued" for more than 24 hours What's happening The Indexer submits URLs through Google's Indexing API. When daily quotas are reached, submission volume spikes, or multiple properties compete for requests, URLs remain queued until the quota resets. Steps to try - Wait for the daily quota reset at midnight UTC. - Refresh the queue status periodically. - Avoid resubmitting the same URLs repeatedly. - Prioritize critical URLs first. - Submit urgent pages manually using Google Search Console → URL Inspection. - Verify the domain is connected properly to GSC. - Remove low-priority URLs from bulk queues. - Break large submissions into smaller batches. - Confirm the URLs are publicly accessible. - Contact support if the queue remains frozen across multiple days. Important Notes Queued status does not mean failure. Processing resumes automatically after quota resets. If the quota balance itself appears corrupted (negative, doubled, or not updating after submissions), see Error 4 — this requires manual correction by support and will not self-resolve at the daily reset. ⚠️ Error 2: URLs show as "Submitted" but are not appearing in Google Search What's happening "Submitted" only confirms the request was sent to Google. Google still independently decides whether to crawl, index, delay, or ignore the page. Steps to try - Use Google Search Console → URL Inspection. - Check the page's actual indexation status. - Confirm the page is not blocked by robots.txt. - Verify no noindex tags, canonical conflicts, or redirect loops exist. - Improve thin or duplicate content. - Add internal links pointing to the page. - Build supporting backlinks to increase crawl priority. - Ensure the page loads correctly in incognito mode. - Wait several additional crawl cycles. - Re-submit only after underlying issues are fixed. Important Notes Submission alone does not guarantee indexation. Google prioritizes quality and authority signals. ⚠️ Error 3: Bulk URL import from CSV is failing What's happening CSV uploads fail when formatting is invalid, unsupported characters exist, headers are included, or URLs are malformed. The importer expects strict formatting. Steps to try - Open the CSV file in a plain text editor. - Ensure one URL per line, no headers, no blank rows, no extra columns. - Confirm every URL begins with https://. - Remove all http:// URLs. - Delete hidden formatting characters if present. - Save the file as UTF-8 plain text. - Avoid Excel auto-formatting whenever possible. - Re-upload the cleaned file. - Test with a smaller batch first. - Contact support if correctly formatted files still fail. Important Notes CSV formatting errors are the most common import issue. UTF-8 encoding prevents hidden character corruption. ⚠️ Error 4: Quota balance is corrupted, negative, or blocks a valid batch submission What's happening In rare cases, the URL Indexer quota balance becomes corrupted — for example, showing a negative credit total, double-charged submissions, or a balance that does not update after Atlas Brain processes new activity. When this happens, even valid batch submissions (e.g., a 141-URL batch) may be blocked even though the user has sufficient credits. This is a back-end sync issue and will NOT self-resolve at the daily quota reset. Steps to try - Confirm the issue is not a normal quota exhaustion (see Error 1). - Note the exact credit balance shown, the expected balance, and any recent submissions that may have been double-charged. - Record a Jam or screen video showing the corrupted balance and the blocked batch attempt. - Contact support and request a manual quota correction — this must be done by a senior agent. - Once support confirms the total has been corrected, retry the batch submission. Important Notes Manual quota corrections are tracked and require senior-agent involvement. Do not repeatedly retry the batch while the balance is corrupted — this can compound the issue. Support has successfully restored credits in cases of double-charging (example: ~267 credits restored on a blocked 141-URL batch). ⚠️ Error 5: Schemas show "pending" and fail to deploy despite API success messages What's happening In some cases, the schema deployment API returns a success response, but schemas remain in a "pending" state and never actually deploy to the live site. This has been observed with large schema queues (e.g., 97 pending schemas) and is a back-end deployment issue, not a user configuration problem. Steps to try - Verify the site connection and authentication are still valid. - Confirm the schemas appear as "pending" rather than "failed" or "error." - Record a Jam video reproducing the deployment attempt and the pending state. - Contact support and request escalation to the dev team. - Reference the existing tracking ticket: Linear OTTO-1827. Important Notes This is a known, dev-tracked issue. An API success response does not always mean the schema deployed — always verify deployment on the live page. Do not bulk re-submit pending schemas, as this can compound the queue and complicate dev troubleshooting.