Cloud Stacks

☁️ Authority Building — Cloud Stacks

Cloud Stacks is an authority-building feature in Search Atlas. If you are experiencing an issue with Cloud Stack creation or have questions about how the feature works, this article explains what to expect and how to get help. What are Cloud Stacks? Cloud Stacks is an authority-building tool within Search Atlas. If you have questions about how the feature works or what it does, our support team can provide guidance specific to your account and use case. What to expect during Cloud Stack creation The Cloud Stack creation process may take some time to complete. If your Cloud Stack appears to be taking longer than expected or you are unsure whether it completed successfully, our support team can look into the status on your behalf. If you need to escalate to support To help our team investigate your Cloud Stack issue as quickly as possible, please have the following ready when you reach out: - Your project name or the domain the Cloud Stack was created for - The approximate date and time you initiated the Cloud Stack - A description of the issue you are seeing (e.g., stuck in progress, properties not appearing, unexpected error message) - Any exact error messages displayed on your screen 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.

🛠️ Restore Incorrectly Charged HyperDrive Credits

💡 Understand when credits are charged HyperDrive Credits (HDC) should be consumed when a Cloud Stack is first published, not simply when it is generated. A saved draft that is deleted before its first publish should not count as completed usage. If your dashboard indicates billing at first publish but credits were deducted during Cloud Stack generation, the charge may require review and restoration. 🔍 Check whether a charge was incorrect 1. Open Authority → Cloud Stacks from the left sidebar. 2. Review the affected Cloud Stack drafts and confirm whether each one was ever published. 3. Compare the Cloud Stack activity with your HyperDrive Credit balance and usage history. 4. Record the number of credits charged, the affected drafts, and whether any draft was published. For example, if three drafts used 45 HDC in total and were deleted before publishing, those credits may be eligible for restoration. If 90 HDC was deducted for drafts that were never published, include the full amount in your review request. 🔄 Request a credit restoration review Do not recreate or publish the deleted drafts while the charge is being reviewed. This can create new usage and make the account history harder to reconcile. 1. Open the chat widget in the bottom-right corner of the platform. 2. Type human teammate to connect with a member of our team. 3. Share the Cloud Stack names or identifiers, creation and deletion dates, amount charged, and whether each draft reached first publish. 4. Explain whether you are requesting restoration for drafts deleted before publishing or for all credits charged before first publish. 🧾 What happens during review Our team compares the account’s usage records, Cloud Stack events, publish history, and billing information. If credits were deducted incorrectly, we restore the eligible amount to the account after reconciliation. Restoration is based on actual usage and account records. Credits used by a Cloud Stack that was published may not qualify for restoration, even if the Cloud Stack was later deleted. ✅ Prevent future confusion - Confirm the expected charge timing in the dashboard before generating multiple Cloud Stacks. - Keep a record of drafts that were generated, published, or deleted. - Review your HDC balance after generation and after first publish. - Report discrepancies promptly with the affected Cloud Stack details. 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.

☁️ Cloud Stacks Content Variation: What's Possible Today

🔍 What This Article Covers This article clarifies how Cloud Stacks handle content across hosting providers, whether per-provider content variation is available at publish time (including through the API), and what each option costs. It also outlines practical workarounds if you need different copy per provider. ☁️ How Cloud Stack Content Works Today When you create and publish a Cloud Stack in Search Atlas, the same content is distributed to all selected providers by default. The platform does not automatically generate unique, provider-specific copy. Every page in your stack receives identical content unless you take manual steps to differentiate it. This is expected platform behavior. If you have noticed that your published Cloud Stack pages contain identical copy across providers, that is correct — it is not a bug. To create a Cloud Stack, go to Left sidebar → Authority → Cloud Stacks and click New Cloud Stack. From there you can select your sites and apply a custom template, but content variation per provider is not configured at this stage automatically. 🚫 Is Per-Provider Variation Available at Publish Time? Currently, per-provider content variation at publish time is not a built-in feature of Cloud Stacks. This applies to all available routes: - Platform UI: There is no toggle, setting, or option to assign unique content to individual providers during the stack creation or publishing workflow. - API: The Search Atlas API does not currently expose a parameter or endpoint that generates or assigns provider-specific content variations at publish time for Cloud Stacks. - Custom Templates: The Custom Template option (available from Left sidebar → Authority → Cloud Stacks) allows you to define your own template structure, but it applies the same template uniformly across all providers — it does not enable per-provider content differentiation automatically. There is no additional cost tier or add-on that unlocks automated per-provider variation, because the feature does not currently exist in any form on the platform. 🛠️ Workarounds for Content Variation If your strategy requires different content on each provider page, the following manual approaches are available today: 1. Create separate Cloud Stacks per provider: Build individual stacks targeting one provider at a time. Write unique content for each stack before publishing. This gives you full control over what appears on each provider's page. 2. Use Custom Templates as a starting point: Navigate to Left sidebar → Authority → Cloud Stacks and select Custom Template. Draft a unique template for each provider group, then publish those stacks separately. 3. Edit content after publishing: Publish your stack and then manually update the content on individual provider pages outside the platform, if the provider's interface allows direct editing. These workarounds require more effort but are the only reliable paths to per-provider content differences at this time. 💰 Pricing and Plan Implications Because automated per-provider content variation is not a current feature, there is no associated cost or pricing tier for it. Cloud Stacks are available according to your existing plan limits. To review your current plan or explore available options, go to Top-right corner (avatar) → Billing → Plans & Top-ups tab and click Manage Subscription or Change Plan. If per-provider variation becomes available as a paid feature in the future, it will be documented here and communicated through the platform. 🗺️ Quick Reference Summary - Default behavior: All providers receive identical content. - Automatic per-provider variation: Not available. - API support for variation: Not available. - Custom Template support for variation: Not available automatically; manual stacks per provider required. - Cost to unlock variation: No paid option exists for this feature currently. - Best workaround: Create separate Cloud Stacks with unique content for each provider. 💬 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.

☁️ Cloud Stack Indexation: Why Google Indexes Only Some Sites

🔍 Overview If you have deployed a cloud stack and only a portion of the sites are showing as indexed in Google, this is expected behavior — not a sign that something has gone wrong. Partial indexing is a normal part of how Google processes large groups of new URLs, especially those hosted on cloud infrastructure. This article explains why it happens, what you should do next, and how batch deployment can improve your results. ☁️ What Is a Cloud Stack? A cloud stack is a group of web properties built on cloud platforms (such as Google Sites, Amazon AWS pages, or similar) and linked together to pass authority to your target URL. You can create and manage your cloud stacks inside Search Atlas by navigating to Authority → Cloud Stacks in the left sidebar. 📊 Why Does Google Only Index Some Cloud Stack Sites? Google does not index every page or property it discovers at the same time. When a large batch of new URLs is submitted or crawled together, Google's systems prioritize and process them gradually. Several factors influence which sites get indexed first: - Crawl budget allocation: Google assigns a crawl budget to each domain. New cloud properties compete for crawl attention alongside other content on those platforms. - Trust and authority signals: Pages that receive more internal links or external signals get crawled and indexed faster. - Platform-level throttling: Cloud hosting platforms may throttle how quickly new pages are made discoverable to search engines. - Content similarity detection: If multiple properties in your stack share very similar content or structure, Google may deprioritize indexing some of them temporarily. - Age of the property: Newer properties take longer to earn indexation than established ones. Seeing only a subset of your cloud stack indexed within the first days or weeks is completely normal. Indexation of the remaining properties typically continues rolling in over time as Google processes the queue. 🚫 Should You Delete Un-Indexed Sites? No. Do not delete or abandon un-indexed cloud stack properties. Here is why: - A site not yet indexed is not a failed site — it is a site still in Google's processing queue. - Deleting properties removes link equity that is already being passed, even before indexation is confirmed. - Re-creating properties restarts the clock on crawl discovery and trust signals. - Un-indexed properties still contribute to the overall network structure that supports indexed ones. The correct approach is to wait, monitor, and apply the indexation tips covered in the next section. ✅ How to Improve Indexation of Cloud Stack Sites Use these proven steps to accelerate and improve your cloud stack indexation rate: 1. Submit URLs to the URL Indexer: Use the URL Indexer tool inside Search Atlas to submit your cloud stack URLs and prompt faster crawling. 2. Use batch deployment strategically: Rather than deploying all cloud stack properties at once in a single burst, consider staggering deployments in batches. This helps avoid triggering platform-level throttling and allows Google to process each group before the next is submitted. 3. Build links to your cloud properties: Adding internal and external links pointing to your cloud stack properties improves their authority signals and encourages faster crawling. 4. Avoid duplicate content across properties: Differentiate the content or structure across your cloud stack sites where possible to reduce the chance of Google deprioritizing similar pages. 5. Be patient and monitor progress: Check indexation status periodically using Google Search Console or site search operators. Indexation is a gradual process for large batches of new URLs. 📦 When to Use Batch Deployment Batch deployment is recommended when you are building a large cloud stack. Deploying properties in smaller, spaced-out groups rather than all at once gives each batch time to be discovered and processed by Google before the next group is submitted. This strategy can result in higher overall indexation rates across your full cloud stack. 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.

🔍 Understanding the Indexing Process for Cloud Stacks and Press Releases in Landing Page Studio

Track the indexing status of your Cloud Stacks and press releases directly in Landing Page Studio, and use the Instant Indexing toggle on custom domains to submit URLs to Google the moment you click Publish. 🌐 Why Indexing Matters for Cloud Stacks and Press Releases Google must crawl and index a URL before it can appear in search results. Until indexing is complete, your Cloud Stack or press release won't contribute to search visibility. Search Atlas tracks each stage so you always know the current status of every URL. Note: Search Atlas manages submission and status tracking. The actual indexing decision belongs to Google and can take time regardless of how the URL was submitted. Open the Authority → Cloud Stacks section from the left sidebar at any time to check the current indexing status of any URL. 📨 Which Submission Path Applies to You Search Atlas uses two different submission mechanisms depending on where your content is hosted. Identify which path applies to your Cloud Stack or press release below. - All domains — automatic background submission: Every Cloud Stack and press release you publish is automatically submitted to Google through Search Atlas's indexing infrastructure. No action needed — submission happens in the background. - Custom domains only — optional Instant Indexing toggle: You can enable the Instant Indexing toggle in the Landing Page Studio publish flow to send the page for indexing after publishing finishes. The toggle is disabled until the site has an active custom domain. Content hosted on a Search Atlas subdomain will continue to use the standard background submission. Now that you know which path applies, you're ready to follow the indexing stages described in the next section. ⚙️ How the Indexing Process Works 1. Submission for Indexing When you publish content, Search Atlas submits the URL to Google through its indexing infrastructure. If your content is on a custom domain, you can also enable the Instant Indexing toggle in the publish flow to send the page for indexing after publishing finishes — see the Instant Indexing Toggle section below for details. 2. Content Indexing In Progress After submission, Google typically takes 1–3 weeks to index new content. During this window, your Cloud Stack section shows the status "Indexing." Note: The exact duration varies based on Google's crawling and indexing algorithms. 3. Final Status — "Indexed" When the status updates to "Indexed," Search Atlas has confirmed that Google indexed the URL. Your content is now eligible to appear in search results. ⚡ Instant Indexing Toggle (Custom Domains Only) The Instant Indexing toggle is an opt-in feature available when publishing Cloud Stacks or press releases on a custom domain through Landing Page Studio. Enabling it sends the page for indexing after publishing finishes. The toggle is disabled until the site has an active custom domain. How to Enable Instant Indexing 1. In Landing Page Studio, open the publish flow for your Cloud Stack or press release. 2. Locate the Instant Indexing toggle in the publish settings. 3. Enable the toggle, then click Publish. What Happens When the Toggle Is Enabled - Your URL is submitted to Google in real time at publish, instead of waiting for the standard background submission. - The Cloud Stack section will still show "Indexing" while Google processes the URL — the toggle accelerates the submission step only, not Google's indexing decision. - Final indexing timing (typically 1–3 weeks) is still controlled by Google. Requirements and Limitations - Custom domain required: Instant Indexing is only available for Cloud Stacks and press releases published to a custom domain. - Subdomains excluded: Content published on a Search Atlas subdomain uses the standard background submission and cannot use the Instant Indexing toggle. - Per-publish setting: The toggle applies to the current publish action only — select it each time you publish. Once the toggle is live, enabling it takes one extra click at publish time and requires no additional configuration. 🎯 You now know how Search Atlas submits and tracks indexing for your Cloud Stacks and press releases in Landing Page Studio — including how the Instant Indexing toggle on custom domains speeds up the submission step. If your content remains in "Indexing" status beyond three weeks, contact Search Atlas support for assistance.

☁️ Cloud Stack Generation, Approvals, and HDC Billing

☁️ Overview Cloud Stacks are multi-layered authority assets built from your Knowledge Graph data. Each stack consumes a set number of Hyperdrive Credits (HDC) from your plan. If a stack fails to generate, or if a charge appears higher than expected, this article explains the most common causes and how to resolve them. 🗺️ How the Cloud Stack Workflow Works Cloud Stacks follow a structured generation process before any content is produced or credits are consumed: 1. Knowledge Graph population: Your Knowledge Graph must be fully built before a Cloud Stack can generate. Confirm your stacks are linked to a complete Knowledge Graph before submitting an order. 2. Order submission: When you place a Cloud Stack order, the request enters a queue for internal review. 3. Manual generation trigger: Generation does not start automatically on submission -- you (or OTTO, if it created the stack) must manually trigger generation for each stack before content is produced. 4. Generation and delivery: Once approved, generation begins and the completed stacks are delivered to your account. ⚠️ Why Cloud Stacks Fail to Generate Even with a fully populated Knowledge Graph, stacks may appear stuck or show a failed status. Common reasons include: - Generation not yet triggered: The most frequent cause. The stack has been created but generation has not yet been manually started. This is expected behaviour, not an error. - Incomplete Knowledge Graph data: If required fields (such as business name, target URLs, or entity details) are missing or inconsistently filled, the generation process cannot proceed. Double-check all fields are complete before submitting. If your stacks show no progress after several business days, reach out for a status update. 💳 How HDC Credits Are Charged Understanding how HDC consumption maps to your plan prevents unexpected billing surprises: - Each Cloud Stack consumes a defined number of HDC upon approval and generation. - Your Authority Plan includes a set HDC allowance per billing cycle. Any stacks that require HDC beyond your included allowance are charged at the standard overage rate. - If you believe your HDC charges are higher than expected, check how many stacks were approved and generated within your current billing cycle and compare that against your plan's included HDC allowance. 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.

☁️ Cloud Stack Generation: Manual Trigger and Approval Workflow

🔍 Overview: Creation vs. Generation When you build Cloud Stacks through OTTO or directly in the Authority section, each stack passes through two distinct states: Created and Generated. These are not the same thing, and understanding the difference is the most common reason stacks appear to be "stuck" or failing. - Created — The stack record exists and your Knowledge Graph data is attached, but no AI content has been produced yet. - Generated — The AI generation button has been manually triggered, a target site has been selected, and content has been produced and accepted. A fully populated Knowledge Graph does not automatically start generation. You must manually trigger each stage of the workflow described below. 🗺️ The Full Cloud Stack Generation Workflow Follow these steps in order. Skipping any step will leave your stacks in a pending state. 1. Navigate to Cloud Stacks. Go to Left sidebar → Authority → Cloud Stacks. You will see a list of all stacks, each showing its current status. 2. Confirm your stacks are in Created status. Stacks that have not yet been generated display a status of Created or Pending Generation. This is expected and not a technical error. 3. Open the stack you want to generate. Click the stack name or its row to open the detail view. 4. Select your target site. Before generation can begin, you must choose which website this stack will be built around. Use the site selector inside the stack detail view to assign the correct domain. Generation cannot proceed without a site selection. 5. Click the AI Generation button. Once a site is selected, the Generate button becomes active. Click it to start the AI content creation process. This step must be performed manually for every stack — there is no bulk auto-trigger. 6. Review and accept the generated content. When generation completes, the platform presents the content for your review. Read through each section and click Accept to confirm the output. Stacks that are not accepted will not proceed to publishing. 7. Publish the stack. After acceptance, click Publish to make the stack live. Only published stacks contribute to your authority-building campaign. ⚡ Why Stacks Created in OTTO Require Manual Action When OTTO creates Cloud Stacks as part of an automated SEO workflow, it handles the creation stage — it populates the stack with Knowledge Graph data and queues the records. OTTO does not automatically trigger AI generation. This is intentional: the manual trigger gives you an opportunity to verify site selection and review content before HDC credits are consumed. If you see a batch of stacks in your Cloud Stacks dashboard that were created by OTTO but show no generated content, this is the expected workflow state — not a failure. Simply follow the generation steps above for each stack. 💳 Understanding HDC Credit Usage and Billing HDC (Hyperdrive Credits) are consumed at the point of generation, not at creation. This means: - Creating a stack through OTTO or manually does not deduct HDC credits. - Clicking the Generate button for a stack deducts the applicable HDC credits for that stack. - If you triggered generation for stacks beyond your plan's included HDC allocation, overage charges apply at the standard rate. If you believe your charges do not match your usage, here is how to reconcile them: 1. Go to Left sidebar → Authority → Cloud Stacks and review the status of all stacks. 2. Count the stacks showing a Generated or Published status — these are the stacks for which HDC credits were consumed. 3. Compare that number to the HDC allocation on your current Authority Plan. 4. Any stacks generated beyond your plan's included HDC count will appear as overage on your invoice. For example: if your Authority Plan includes a set HDC allocation and generation was triggered for a total that exceeds that amount, the difference is billed as overage. Review your generation history inside the Cloud Stacks dashboard to identify exactly which stacks consumed credits beyond your allocation. ✅ Quick Checklist Before Triggering Generation - Knowledge Graph is fully populated with accurate business information. - Target site is selected inside the stack detail view. - You have confirmed your remaining HDC credit balance to avoid unexpected overage charges. - You are ready to review and accept content immediately after generation completes. 🛠️ Troubleshooting Common Issues - Generate button is greyed out: A target site has not been selected. Assign a site in the stack detail view first. - Stack shows Created but no content: Generation has not been triggered. This is a workflow step, not a technical error. Click Generate. - Content is generated but stack is not live: The content review and Accept step has not been completed, or the Publish step was skipped. - Unexpected charge on invoice: Check how many stacks reached Generated status. Overage is charged per HDC consumed beyond your plan limit. 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 Remove a Published Cloud Stack

🔍 Overview Once a Cloud Stack is published, it is live on external hosting infrastructure and cannot be deleted directly from the Search Atlas dashboard. However, if your published Cloud Stack contains incorrect images, inaccurate information, or content that misrepresents your client's company, you can request its removal through our support team. This article explains what a published Cloud Stack is, why self-service deletion is not available, and exactly how to get one removed quickly. 📋 What Is a Published Cloud Stack? A Cloud Stack is a set of interlinked web properties — such as Google Sites, Web 2.0 pages, and cloud documents — designed to build authority and pass link equity to your target website. Once published, these pages are hosted on third-party platforms outside of Search Atlas, which is why they cannot be unpublished with a single dashboard button. ⚠️ When Should You Request Removal? You should request removal of a published Cloud Stack if any of the following apply: - The Cloud Stack contains images that do not belong to your client's website or brand. - The content misrepresents your client's company, products, or services. - Incorrect business information (name, address, URL) was used during creation. - The Cloud Stack was created for the wrong website or client by mistake. 🛠️ How to Request Cloud Stack Removal Because published Cloud Stacks are hosted on external platforms, removal must be handled by our support team. To get a Cloud Stack removed as quickly as possible, have the following information ready before you reach out: - The name of the Cloud Stack to be removed. - The target URL the Cloud Stack was built for. - A brief reason for removal (e.g., incorrect images, misrepresentation of client). Once you contact support with these details, our team will process the removal and confirm once the Cloud Stack has been taken down from all associated platforms. 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.

☁️ Cloud Stack Auto-Population from Knowledge Graph

🔍 Overview When you create a second or subsequent Cloud Stack in Search Atlas, you do not need to manually re-enter your business information. OTTO automatically pulls your existing business data from your Knowledge Graph and populates the required fields for you. This article explains how this works and what to expect during the Cloud Stack creation process. 📚 What Is the Knowledge Graph? The Knowledge Graph is a centralized repository of your business information inside Search Atlas. It stores details such as your business name, address, phone number, website URL, business category, and other entity data. This information is used across multiple features in the platform — including Cloud Stacks — to ensure consistency and save you time. 🤖 How OTTO Connects the Knowledge Graph to Cloud Stacks OTTO is the AI engine that powers automation across Search Atlas. When you initiate the creation of a new Cloud Stack, OTTO checks your Knowledge Graph for existing business data. If a Knowledge Graph has already been set up for your project, OTTO automatically transfers that information into the Cloud Stack setup fields. You will not be prompted to re-enter details that are already on file. This behavior applies from your second Cloud Stack onward. The first Cloud Stack is typically used to establish or confirm your Knowledge Graph data. Once that baseline is in place, all subsequent Cloud Stacks benefit from automatic population. 🧭 How to Create a Second Cloud Stack 1. In the left sidebar, click Authority. 2. Select Cloud Stacks from the expanded menu. 3. Click the button to create a new Cloud Stack. 4. OTTO will automatically detect your existing Knowledge Graph and pre-fill your business information into the relevant fields. 5. Review the pre-populated details to confirm they are accurate and up to date. 6. Make any necessary edits, then proceed through the remaining setup steps. 7. Submit your Cloud Stack for processing. ✅ What Gets Auto-Populated? The fields that OTTO populates from your Knowledge Graph typically include: - Business name - Business address - Phone number - Website URL - Business category or niche - Other entity-level details stored in your Knowledge Graph If any of this information has changed since your Knowledge Graph was last updated, you can edit the pre-filled fields directly within the Cloud Stack creation flow before submitting. ⚠️ When Auto-Population May Not Occur In some cases, business information may not auto-populate as expected. Common reasons include: - No Knowledge Graph exists yet: If a Knowledge Graph has not been created for the current project, OTTO has no data to draw from. You will need to complete the Knowledge Graph setup first. - Incomplete Knowledge Graph data: If key fields were left blank when the Knowledge Graph was created, those fields will also appear blank in the Cloud Stack form. - Project mismatch: Auto-population is scoped to the active project. Ensure you are working within the correct project before creating a new Cloud Stack. If you encounter any of these situations, navigate to the Knowledge Graph for your project, complete or update the relevant business information, and then return to Authority → Cloud Stacks to create your new Cloud Stack. 💡 Best Practices - Keep your Knowledge Graph up to date. Any changes to your business details should be reflected there first so that all future Cloud Stacks inherit accurate information. - Always review auto-populated fields before submitting. OTTO pulls the most recently saved data, but a quick review ensures nothing is outdated. - Use the same project for all Cloud Stacks related to a single business to maintain consistent entity data across your authority-building efforts. 💬 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.

☁️ Cloud Stacks Indexation and Indexing Tool Guide

🔍 Understanding Cloud Stack Indexation Cloud stacks are networks of web 2.0 properties built to support your link-building strategy. While Search Atlas creates and publishes these stacks on your behalf, indexation is not guaranteed — it depends on how quickly third-party search engines (like Google) discover and crawl the URLs. In some cases, this process can take weeks or even several months. This is normal behaviour and is not a sign that something has gone wrong with your cloud stack build. However, there are steps you can take to speed up and improve indexation rates. ⚙️ Why Cloud Stacks May Not Get Indexed - Crawl delay: Search engines prioritise well-established domains. New web 2.0 properties are often crawled less frequently. - No inbound signals: Pages with no external links or traffic signals are less likely to be discovered quickly. - Platform restrictions: Some third-party platforms used in cloud stacks limit search engine access at times. - Volume: Large stacks contain many URLs — indexation naturally takes longer across a high number of pages. 🛠️ How to Use the URL Indexer Tool Search Atlas includes a built-in URL Indexer tool specifically designed to help push your cloud stack URLs to search engines faster. Follow these steps to submit your URLs for indexing: 1. Log in to your Search Atlas account. 2. In the left sidebar, navigate to Authority → Indexer (URL Indexer). 3. Locate your cloud stack URLs. You can find these under Authority → Cloud Stacks — open the relevant stack and copy the list of generated URLs. 4. Paste your URLs into the URL Indexer input field. You can submit multiple URLs at once. 5. Click Index URLs to send the URLs to search engine crawlers. After submission, allow 7–14 days for search engines to process the request. Indexation is not instant, but submitting through the URL Indexer significantly improves your chances. 📊 Checking Your Indexation Progress To verify whether your cloud stack URLs are being indexed, use Google Search Console (if the properties are connected) or perform a manual check by entering site:yourcloudstackurl.com in Google Search. Repeat this check weekly after submitting through the URL Indexer. Keep in mind: - Not every URL in a large stack will index — a 40–70% indexation rate is considered healthy and normal. - Resubmitting unindexed URLs through the URL Indexer after 2–3 weeks can improve results. - Avoid submitting the same URLs more than once every two weeks, as over-submitting can be counterproductive. 💡 Best Practices to Improve Indexation - Build links to your cloud stacks: Sharing cloud stack URLs on social media, forums, or other indexed pages gives search engines a reason to crawl them. - Use the URL Indexer consistently: Make indexer submissions part of your regular workflow after each new cloud stack is created. - Allow adequate time: Set realistic expectations — full indexation of a large stack can take 2–4 months even with active submission. - Keep your stacks active: Cloud stack properties that receive occasional visits and signals tend to retain indexation better over time. 🚀 Where to Find Your Tools All the tools you need are located in the Authority section of your Search Atlas account: - Left sidebar → Authority → Cloud Stacks — view and manage your existing stacks and access their URLs. - Left sidebar → Authority → Indexer (URL Indexer) — submit URLs to search engines for faster indexation. 🙋 Need More Help? If you have submitted your URLs through the Indexer, waited the recommended time, and are still seeing very low indexation rates, our team is happy to review your specific stack. 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.

☁️ Create Cloud Stacks Using OTTO Knowledge Bases

🔍 Overview Cloud stacks let you publish authoritative, interlinked content across the web to strengthen your domain's authority signals. When you create a cloud stack inside an OTTO project, you can power the content with that project's existing knowledge base — keeping everything relevant and on-brand. This article explains what you need to know before contacting our team for guided assistance with this workflow. 🧭 Before You Begin Make sure the following conditions are met before you start: - You have an active OTTO project set up inside Search Atlas. - That OTTO project already has a knowledge base created and populated with your business information. - You have access to the Cloud Stacks section within Search Atlas. 🛠️ Creating a Cloud Stack Within an OTTO Project Creating a cloud stack that uses an OTTO project's knowledge base involves navigating to the Cloud Stacks section of Search Atlas and associating the cloud stack with your chosen OTTO project so that the project's knowledge base powers the generated content. Because the exact steps and available options in this workflow depend on your account configuration and the current state of the platform, our support team can walk you through the process in real time and confirm the correct settings for your specific setup. 📋 What to Have Ready When You Reach Out To get the fastest help, please have the following information on hand before contacting support: - The name of the OTTO project you want to use for the cloud stack. - Confirmation that the knowledge base for that project has been created and populated. - A description of where in the workflow you are getting stuck or have a question (for example, project selection, content settings, or any error messages you see). - Any exact error messages displayed on screen, including timestamps if available. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖼️ Upload and Preview Your CloudStack Logo

Overview This article explains how to upload a brand logo inside CloudStack and troubleshoot cases where the logo does not appear correctly in the live preview. How to Upload Your Logo in CloudStack To add or update your logo within the CloudStack editor, locate the logo upload area inside your CloudStack project. The exact location of this option may vary depending on your project configuration — look for a branding or logo-related section within the editor interface. Once you have found the upload area, select your logo file from your device and confirm your changes to set the logo. Fixing Logo Preview Display Issues If your logo has been uploaded but is not showing correctly in the live preview, try the following steps: - Hard-refresh the preview: Force your browser to reload the page and clear cached assets. - Re-upload the logo: Remove the existing logo and re-upload your file to force the preview to update. - Try a different browser: If the preview issue persists, open CloudStack in a different browser to rule out a browser-specific rendering problem. - Save and re-open the project: After uploading, save your settings, close the project, and reopen it to see if the logo now appears in the preview. What to Have Ready When Escalating If the steps above do not resolve your issue, a member of our support team will need to investigate further. Please have the following ready when you reach out: - The name of the specific CloudStack project where the logo issue is occurring. - A description of what you see instead of your logo (for example, a blank space, a placeholder, or an error message). - The exact error message or text displayed on screen, if any. - The file format and approximate file size of the logo you attempted to upload. - The timestamp of when you attempted the upload. 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 Add a Google Maps URL in Cloud Stack

This article explains why short Google Maps links (like https://maps.app.goo.gl/...) are rejected in the Cloud Stack builder and what format you need to use instead so your map embeds correctly. 🔍 Common Causes The Cloud Stack Google Maps field does not accept shortened or redirected URLs. The two formats that cause this error are: - Short share links — e.g. https://maps.app.goo.gl/k5vf28ep5cenzbwt7 - Standard browser URLs — e.g. https://www.google.com/maps/place/... The field requires a raw iframe embed code generated directly from Google Maps, not a link copied from your browser or the share button. 🛠️ Step-by-Step 1. Go to Google Maps (maps.google.com) and search for the business or location you want to embed. 2. Click the business listing or pin to open its detail panel on the left side of the screen. 3. Click the Share button (the icon that looks like an arrow pointing outward). 4. In the Share dialog, select the Embed a map tab — do not use the "Copy link" tab. 5. Choose your preferred map size from the dropdown (any size is acceptable). 6. Click Copy HTML. This copies the full <iframe> embed code to your clipboard. It will look similar to: <iframe src="https://www.google.com/maps/embed?pb=..." width="600" height="450" ...>``</iframe> 7. Paste the full iframe embed code into the Google Maps field inside your Cloud Stack property builder. ✅ How to Confirm It Worked After pasting the iframe embed code, the Cloud Stack builder should accept the input without showing a validation error. To verify the map is rendering correctly: - Save or publish the Cloud Stack property. - Open the live Cloud Stack URL in your browser. - Scroll to the map section — you should see an interactive Google Map displaying the correct location, not a broken image or blank space. - If the map is visible and the location pin is accurate, the embed has been applied successfully. 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.

☁️ Cloud Stacks Indexing Timeline and Best Practices

🔍 Overview After publishing a cloud stack in Search Atlas, you may notice that your pages are not yet appearing in Google's search results — even after several weeks. This is completely normal. Indexing is controlled entirely by Google, not by Search Atlas. This article explains what to expect and what steps you can take to encourage faster indexing. ⏱️ How Long Does Indexing Take? There is no fixed timeline for Google to index a newly published cloud stack. However, here are general benchmarks to keep in mind: - Typical timeline: Most cloud stack pages begin indexing within a few weeks of publication. - Extended timeline: In some cases, indexing can take six weeks or longer. A wait of around one to two months is within the normal range and does not indicate an error. - No guarantee: Google does not index every page it discovers, and the pace at which it crawls new content varies based on your site's overall authority, crawl budget, and the signals pointing to the page. If your cloud stack has not indexed after several weeks, it does not mean something has gone wrong — but there are proactive steps you can take to improve the chances of indexing. 🗺️ Where to Find Your Cloud Stacks You can review your published cloud stacks and their associated URLs inside the Search Atlas platform. Search Atlas also provides a URL Indexer tool that allows you to submit specific URLs for indexing consideration. Refer to the in-platform navigation or reach out to our support team if you need help locating these sections. ✅ Best Practices to Encourage Indexing While Google ultimately decides when and whether to index a page, the following actions send strong signals that your content is valuable and worth crawling. Apply as many of these as possible after publishing a cloud stack. 1. Submit to Google Search Console: Open Google Search Console, paste the cloud stack URL into the URL Inspection tool, and click Request Indexing. This is the most direct signal you can send to Google and should always be your first step. 2. Add internal links: Link to your cloud stack URL from existing pages on your main website — for example, from blog posts, service pages, or your homepage. Internal links help Google discover and prioritise new pages. 3. Mention it in a blog post: Publish a blog post on your website that references or links directly to the cloud stack. Fresh content with outbound links accelerates discovery. 4. Share on social media: Post the cloud stack URL on your social media profiles (LinkedIn, X/Twitter, Facebook, etc.). Social signals and external clicks indicate to Google that the content exists and is being engaged with. 5. Earn or build backlinks: Seek opportunities to have other relevant websites link to your cloud stack URL. 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.

☁️ Cloud Stack Provider Deployment Status Explained

🔍 Overview When you deploy a Cloud Stack, Search Atlas pushes your content to multiple providers simultaneously. Most providers go live within minutes, but Cloudflare has a longer propagation window due to its global network architecture. Seeing Awaiting next to Cloudflare while all other providers show Live is completely normal and does not indicate a failure. This article explains each deployment status, why Cloudflare takes longer, and what steps to take if the delay exceeds the expected window. 📋 Understanding Deployment Statuses Each provider in your Cloud Stack will display one of the following statuses: - Live — The provider has successfully published your content and it is publicly accessible. - Awaiting — The deployment request has been sent and is in queue or propagating. This is a normal, expected state — not an error. - Failed — The provider encountered an error during deployment. This status requires action and is visually distinct from Awaiting. **Important:**Awaiting and Failed are two different statuses. If your Cloudflare provider shows Awaiting, your deployment is progressing normally. Do not attempt to rebuild or re-trigger the deployment while this status is active. ⏱️ Why Cloudflare Shows 'Awaiting' Longer Than Other Providers Cloudflare operates one of the largest content delivery networks in the world. When Search Atlas pushes a deployment to Cloudflare, the following happens: 1. The deployment request enters Cloudflare's provisioning queue. 2. Cloudflare validates and distributes the content across its global edge nodes. 3. DNS propagation completes and the status updates to Live. This process typically takes 15 to 45 minutes but can occasionally extend to a few hours depending on Cloudflare's network conditions. All other providers in your Stack — such as the 13 providers already showing Live on your deployment — operate on faster individual pipelines, which is why they resolve first. ✅ What To Do While Cloudflare Shows 'Awaiting' Follow these steps to confirm everything is on track: 1. Verify that the status shown is Awaiting and not Failed. The labels are clearly differentiated in the interface. 2. Check the timestamp of your deployment. If it has been less than 2 hours, no action is needed — allow propagation to complete. 3. Refresh your Cloud Stack dashboard after 30 minutes to check for a status update. 4. If the status remains Awaiting after 4 hours, proceed to the escalation steps below. Do not use any rebuild or re-deploy action while the status shows Awaiting. Triggering a rebuild during active propagation can cause duplicate deployment conflicts and further delay the process. 📊 Track Keyword Rankings While You Wait While your Cloudflare provider finishes propagating, you can begin setting up rank tracking for your domain so you are ready to monitor performance as soon as the full Stack goes live. 1. In the left sidebar, navigate to Keywords → Rank Tracker (Keyword Rank Tracker). 2. Enter your domain (e.g., hugehealthfitness.com) and add the target keywords you want to monitor. 3. Set your preferred location and search engine settings. 4. Save your configuration — tracking will begin on the next scheduled crawl cycle. Having your Rank Tracker configured in advance means you will capture baseline data immediately once all Cloud Stack providers, including Cloudflare, are fully live. 🚨 When 'Awaiting' Might Actually Be a Problem In rare cases, a status can become stuck. Look for these signs that something may require investigation: - Cloudflare shows Awaiting for more than 6 hours with no change. - The deployment timestamp shows the job was initiated more than 24 hours ago. - Other providers that were Live have reverted to a different status. If any of these conditions apply, document your Stack ID (e.g., Stack ID 24055) and the exact duration before contacting support. Do not rebuild — our team will investigate the deployment job directly. 💬 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.

🗑️ Cloud Stacks Campaigns: Deletion and Content Removal

🔑 Key Facts Before You Begin Cloud Stacks campaigns distribute your content to independent third-party web properties. Once content is submitted and published to those properties, it exists outside of Search Atlas and cannot be retracted, edited, or removed — by Search Atlas or by you. This is a hard platform limitation, not a process gap. Deleting a Cloud Stacks campaign inside Search Atlas does not remove or unpublish content that has already been sent to publishers. 📋 What Happens When You Delete a Campaign Deleting a campaign in Search Atlas removes it from your dashboard and stops any future submissions associated with that campaign. It does not: - Take down content that has already been published to web properties - Send removal or unpublish requests to any third-party platform - De-index pages from Google, Bing, or any other search engine - Give you or Search Atlas access to those third-party sites to modify content To delete a campaign, go to Left sidebar → Authority → Cloud Stacks, open the relevant campaign, and use the delete option. This action only affects your Search Atlas records. 🌐 Why Content Cannot Be Removed When a Cloud Stacks campaign is submitted, content is distributed to external web properties operated by independent publishers. Search Atlas does not own, control, or have editorial access to those sites. Because of this: - Search Atlas has no ability to log in to those properties and delete pages on your behalf - There is no contractual or technical mechanism to issue a takedown to these publishers after submission - Search Atlas support cannot contact individual cloud providers to request removal This is the same situation you would face with a guest post or press release published on an external site — once it is live, the publishing platform controls the content. 🔍 What About Indexed Pages in Search Engines? If pages from your Cloud Stacks campaign have already been crawled and indexed by search engines, Search Atlas cannot request de-indexing on your behalf because we do not have verified ownership of those third-party domains. Standard webmaster de-indexing tools (such as Google Search Console's URL removal tool) require verified site ownership. Since you do not own the cloud web properties, those tools are not available to you for this content. Over time, search engines may naturally drop low-authority or thin pages from their index, but this is not guaranteed and cannot be accelerated through Search Atlas. ⚠️ Important: Plan Before You Submit Because published Cloud Stacks content is permanent and irreversible, please review the following before launching any campaign: - Content accuracy: Confirm all URLs, brand names, anchor text, and facts are correct before submission. - Target URLs: Make sure the pages you are promoting are live, correctly optimised, and intended to be associated with the distributed content long-term. - Brand representation: All published content will be publicly visible and associated with the links and entities you include, indefinitely. Once you click submit, the campaign content moves to external publishers immediately and the process cannot be reversed. ✅ What You Can Still Do While you cannot remove already-published content, here are the actions that remain available to you: - Delete the campaign record in Search Atlas (Left sidebar → Authority → Cloud Stacks) to stop tracking it and prevent any unsent submissions from being processed. - Pause or stop future submissions if the campaign has scheduled or pending content that has not yet been sent. - Create a new campaign with corrected content to build additional signals if the original content contained errors. - Review campaign history via Left sidebar → Authority → Campaigns to see the status of all past submissions. 💬 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.

🎨 Cloud Stacks Color Customization: Limitations Explained

🌐 What Is Cloud Stacks? Cloud Stacks is a link-building feature inside Search Atlas that automatically generates and publishes optimized web properties across a network of cloud-based platforms. Each published property includes structured content, internal links, and a visual design — all generated automatically to support your authority-building campaigns. 🎨 Can You Change the Colors in Cloud Stacks Content? No. Cloud Stacks does not currently support manual color customization. The colors displayed in your generated content are determined by preset templates used during the publishing process. Custom brand colors cannot be applied at this time. This is a platform-level constraint, not a bug or misconfiguration on your account. 📐 Why Are Templates Preset? The use of preset templates is an intentional platform design decision. Custom color inputs are not supported in the current version of Cloud Stacks. 🔍 Does Color Affect SEO Performance? For Cloud Stacks web properties, color customization is not a factor in SEO outcomes. These properties function as supporting authority assets rather than brand-facing landing pages, so visual styling to match your main site is not their intended purpose. If you have questions about color options or template behavior in your specific Cloud Stacks setup, our team can help clarify what is available 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.

☁️ What Are Cloud Stacks (SEO Entity Stacking)?

☁️ What Is a Cloud Stack? A Cloud Stack is a network of interlinked, branded web properties hosted on high-authority cloud platforms — such as Google Sites, Microsoft Azure, Amazon Web Services, and similar platforms. Each property in the stack references your main website and reinforces your brand as a trusted entity across the web. This technique is also known as SEO Entity Stacking because it signals to search engines that your brand is a real, established entity with a consistent presence across multiple authoritative domains. When these properties link to one another and to your primary site, they pass authority signals that can strengthen your overall search visibility. 🎯 Why Use Cloud Stacks? - Boost domain authority: Links from high-trust cloud platforms carry strong authority signals to your website. - Reinforce brand entity: A consistent brand presence across multiple platforms helps search engines validate your business as legitimate. - Diversify your backlink profile: Cloud Stacks add a natural variety of referring domains without relying solely on traditional link outreach. - Support local and national SEO: Cloud Stacks work for both local businesses looking to rank in specific areas and broader campaigns targeting national or global audiences. - Complement other authority strategies: Cloud Stacks pair effectively with press releases and link-building campaigns to create a layered authority-building approach. 🗺️ How Cloud Stacks Work in Search Atlas Search Atlas automates the creation of Cloud Stacks inside the Authority section. The platform builds your branded web properties, populates them with relevant content, interlinks them, and points them toward your target URL — all without requiring any technical setup on your part. Cloud Stacks are created using credits. The exact credit cost may vary depending on the scope and options you select during setup. Review the credit cost displayed before confirming your order. 🚀 How to Create a Cloud Stack To get started with Cloud Stacks, navigate to the Authority section of Search Atlas and look for the Cloud Stacks feature. From there you will be able to enter your target URL and brand details — accurate brand information helps the platform create consistent, entity-rich properties. Review any cost or configuration options shown on screen, then confirm your selections to begin the automated build process. Once your Cloud Stack is complete, you will be able to review the properties that were created directly within the Cloud Stacks area of the platform. 🛠️ Need Help Getting Started? If you have questions about how to set up a Cloud Stack, what information to provide, or what to expect from the process, our team is happy to walk you through it. 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.

⚡ Cloud Stack Submission Best Practices and Field Guidelines

What Is a Cloud Stack? A Cloud Stack is a set of interconnected web 2.0 and document-sharing properties built around your brand. Each property is interlinked and pointed toward your target URL, creating a powerful authority signal for search engines. Getting the fields right from the start ensures every submission is as effective as possible. How to Access Cloud Stacks To open the Cloud Stacks tool, navigate to the Cloud Stacks section within the Authority area of the platform. From here you can start a new submission or review existing ones. Business Description Field Guidelines The Business Description is one of the most important fields in your Cloud Stack submission. Because the source conversations for this article did not include confirmed character limits or specific formatting rules, the exact field specifications are not yet documented here. General best practices that have been communicated to customers include: - Do not include a URL link in the description: Your target URL is captured in its dedicated field — leave the description as plain brand and service copy only. - Write naturally and avoid keyword stuffing: Mention your primary keyword where it fits naturally, but do not force it into every sentence. FAQ Section Guidelines Cloud Stacks include an FAQ section that adds topical depth to your properties. The following general guidance has been confirmed in resolved support conversations: - Write questions the way a real customer would ask them. - Keep answers concise and factual. Short, natural answers are easier for the platforms to index. - Weave keywords in where they fit naturally — do not force a keyword into every answer. Specific confirmed counts for how many FAQ entries to include have not been documented in the source conversations. If you need the current recommended FAQ count or any other specific field limit, please reach out to our team directly so they can confirm the up-to-date guidelines for your submission. Should You Use Extra FAQs? If you have additional relevant questions beyond the standard FAQ section, you can add more entries to build further topical depth. Avoid padding with low-quality or repetitive content, as this can reduce the quality of the authority signal. Need Help With Your Submission? If you are unsure about any field requirement — including character limits, recommended counts, or formatting rules — our team can confirm the current guidelines before you submit. When reaching out, please have your project name and the specific field or question you need clarified ready so we can assist you quickly. 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 Edit the Target URL in a Draft Cloud Stack

📋 Overview The Target URL is the destination page your Cloud Stack points to and builds authority toward. When you create a Cloud Stack, this URL is used to generate the linking structure and anchor text across the stack. Occasionally you may need to change the Target URL — for example, if you entered the wrong page, updated your site structure, or want to redirect authority to a different landing page. As long as your Cloud Stack is still in draft mode (not yet published), you can edit the Target URL directly. 🧭 Where to Find Your Draft Cloud Stack All of your Cloud Stacks live inside the Authority section of the platform. To locate your draft: 1. In the left sidebar, click Authority. 2. Select Cloud Stacks from the sub-menu. 3. Find the Cloud Stack you want to edit in the list. Drafts are labeled with a Draft status. 4. Click on the Cloud Stack to open it. ✏️ How to Edit the Target URL Once your draft Cloud Stack is open, follow these steps to update the Target URL: 1. Open the draft Cloud Stack you want to modify. 2. Navigate to the Target URL field in the setup or configuration step. 3. Clear the existing URL and enter the new destination URL. Be sure to include the full URL, starting with https://. 4. Click Save to apply your changes. 5. Review the rest of the stack to confirm your anchor text and linking structure reflect the updated Target URL. Because the stack is still in draft, your edits are applied before any content is generated or published, so you can adjust freely without affecting a live campaign. ⚠️ Important Things to Know - Only drafts can be edited freely. Once a Cloud Stack has been published, the Target URL is locked because links and content have already been generated around it. - Save before leaving the page. If you navigate away without clicking Save, your Target URL change will not be retained. - Use a valid, indexable page. For best results, point your Target URL to a live, publicly accessible page so the host page URL can be properly indexed by Google. - Check your anchor text. After changing the Target URL, review the anchor text mix to ensure it still aligns with the new destination and your keyword strategy. 🛠️ Troubleshooting: My Changes Aren't Applying If you edit the Target URL but the change does not seem to save or take effect, try the following: - Confirm you clicked Save after entering the new URL. - Verify the Cloud Stack is still in Draft status — published stacks cannot be edited. - Make sure the URL is correctly formatted, including the https:// prefix, with no extra spaces. - Refresh the page and reopen the draft to confirm the new URL is displayed. - Clear your browser cache or try a different browser if the field appears unresponsive. 💬 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.

✏️ Edit Target URL in a Draft Cloud Stack

🔍 Overview When you create a Cloud Stack, you set a Target URL as part of the initial setup. If you need to change that URL before the stack goes live, you can do so while the Cloud Stack remains in draft status. This article walks you through how to find and update the Target URL without starting over. 🧭 How to Navigate to Your Draft Cloud Stack 1. Log in to your Search Atlas account. 2. In the left sidebar, click Authority. 3. Select Cloud Stacks from the expanded menu. 4. Locate the Cloud Stack with Draft status in your list. 5. Click on the Cloud Stack name to open it. ✏️ How to Edit the Target URL 1. Once inside the draft Cloud Stack, look for the Target URL field. This is typically displayed in the first step or the settings section of the stack setup. 2. Click the Target URL field to make it editable. 3. Clear the existing URL and type or paste your new Target URL. 4. Review any other settings you want to confirm before publishing. 5. Click Save or Update to apply your changes. Your updated Target URL will now be used when the Cloud Stack is published and the links are built. ⚠️ Important Things to Know - Draft status only: You can only edit the Target URL while the Cloud Stack is in draft mode. Once a stack has been submitted and is being processed or is live, the Target URL cannot be changed. - URL validation: Make sure your Target URL is a valid, publicly accessible page. Invalid URLs may cause errors during publishing. - Impact on content: If AI-generated content has already been created referencing your original URL, you may want to review and regenerate that content after updating the Target URL to ensure consistency. - Anchor text: After changing the Target URL, review your anchor text settings to make sure they still align with the new destination page and its keywords. 🛠️ Troubleshooting - Field appears locked or greyed out: Confirm the stack is still in Draft status. If it has moved to a processing or live state, editing is no longer available. - Changes are not saving: Refresh the page and try again. If the issue persists, clear your browser cache or try a different browser. - Target URL field is not visible: Navigate to the first step of the Cloud Stack setup using the step indicators at the top of the page — the Target URL field is located in Step 1. 💬 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.

🗑️ Deleting Cloud Stacks Campaigns and Removing Indexed Content

🔍 Overview When you publish a Cloud Stacks campaign, Search Atlas distributes your content across a network of web properties that are not directly managed by you. This means that deleting a campaign inside the platform does not automatically remove content that has already been published and indexed by search engines. This article explains what happens when you delete a campaign and what steps you can take to address indexed content. 📋 What Happens When You Delete a Cloud Stacks Campaign Deleting a campaign in Left sidebar → Authority → Cloud Stacks removes it from your Search Atlas dashboard and stops any further publishing activity. However, the following should be noted: - Content that was already published to web properties before deletion remains live on those properties. - Pages that search engines have already crawled and indexed will remain in search engine indexes until those engines re-crawl and process a removal signal. - You do not have direct access to the third-party web properties where the content was published, so you cannot edit or delete the content yourself. 🛠️ How to Request Content Removal Because the web properties used in Cloud Stacks are managed by Search Atlas, content removal must be handled by our team. Follow these steps to submit a removal request: 1. Navigate to Left sidebar → Authority → Cloud Stacks and locate the campaign containing the content you want removed. 2. Note the campaign name and any relevant details such as the target URLs or keywords associated with the published content. 3. Open the live chat widget in the bottom-right corner of the platform and type human teammate to reach our support team. 4. Provide the campaign name and details of the content you need taken down. Our team will coordinate removal from the web properties on your behalf. ⏱️ What to Expect After a Removal Request Once our team processes your request and removes the content from the web properties, search engines will eventually de-index those pages during their next crawl cycle. Keep in mind: - Search engine de-indexing is not instant. It can take days to weeks depending on how frequently the search engine crawls those pages. - Our team can submit expedited removal requests through Google Search Console and equivalent tools where applicable, which can speed up the process. - You will be notified by our team once the content has been taken down from the web properties. ✅ Best Practices Before Publishing To avoid needing to remove content after publishing, we recommend reviewing the following before launching a Cloud Stacks campaign: - Confirm that all target URLs, anchor text, and content are finalised and approved before publishing, as changes post-publication require a manual removal process. - Review your campaign settings carefully in Left sidebar → Authority → Cloud Stacks before clicking publish. - If you are unsure whether a campaign is ready to go live, save it as a draft and consult our support team before proceeding. 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.

CloudStack: Keywords, Knowledge Pages, and Crawling

Overview CloudStack uses your website's knowledge pages and keyword inputs to power AI-driven content and SEO workflows. Two common points of confusion are: (1) why CloudStack sometimes does not pull data from your knowledge page, and (2) whether long-tail keyword phrases are acceptable inputs. This article addresses both questions directly. Why CloudStack May Not Pull from Your Knowledge Page CloudStack crawls your designated knowledge pages automatically, but certain conditions on the page itself can prevent it from accessing or indexing the content correctly. Common reasons include: - Noindex tags: If the page contains a noindex meta tag or header, CloudStack will respect that directive and skip the page. Check your page's HTML <head> section for <meta name="robots" content="noindex"> and remove it if you want the page crawled. - Blocked by robots.txt: If your robots.txt file disallows crawling for the relevant path, CloudStack cannot access the page. Review your robots.txt at yourdomain.com/robots.txt and ensure the path to your knowledge page is not disallowed. - JavaScript-rendered content: Pages that load content exclusively via JavaScript may not be fully accessible to CloudStack's crawler. If your knowledge page relies on client-side rendering, consider providing a static or server-rendered version of the content. - Incorrect URL entered: Double-check that the knowledge page URL entered in your CloudStack configuration exactly matches the live page URL, including any trailing slashes or subdirectory paths. To diagnose the issue, start by visiting the knowledge page URL you entered in CloudStack, confirming it loads correctly, and then checking for noindex tags and robots.txt restrictions. Using Long-Tail Keywords in CloudStack CloudStack accepts long-tail keyword phrases as valid inputs — you are not limited to single words or short two-word combinations. Long-tail keywords (typically three or more words that reflect a specific search intent) are supported in CloudStack's keyword input fields. To use them correctly: 1. Navigate to your CloudStack keyword configuration panel. 2. Enter the full long-tail phrase as a single keyword input (for example, "best project management software for small teams"). 3. Avoid splitting a long-tail phrase across multiple separate keyword fields — enter it as one complete phrase per field. 4. Save your configuration and allow CloudStack to process the updated keyword list before evaluating results. If your keyword inputs are not being recognized or your knowledge page continues to be skipped after following the steps above, please have the following ready when contacting support: your knowledge page URL, any error messages shown in CloudStack, and the exact keyword phrases you are trying to use. 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.

☁️ Cloud Stacks Inside OTTO vs Standalone

🔍 Overview Search Atlas gives you two ways to create a Cloud Stack: directly inside OTTO SEO, or independently through the Authority → Cloud Stacks section. These two methods are not interchangeable. Each serves a different purpose, and understanding the distinction will help you get the most out of your Cloud Stack and avoid a common point of confusion — an empty Knowledge Graph. ☁️ What Is a Cloud Stack? A Cloud Stack is a network of authoritative web properties (Google Sites, cloud documents, social profiles, and more) built to strengthen your domain's authority signals. When connected to a Knowledge Graph, the Cloud Stack inherits structured entity data about your business, making the authority signals far more relevant and powerful. ⚙️ Method 1: Creating a Cloud Stack Inside OTTO When you create a Cloud Stack from within OTTO SEO, it is automatically tied to the OTTO project for that domain. Here is how to do it: 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (or navigate to /seo-automation-v3). 2. Open the relevant OTTO project for your domain. 3. Locate the Cloud Stack task card inside OTTO and follow the on-screen prompts to generate your Cloud Stack. Because OTTO already holds your project's configuration, the Cloud Stack created this way is linked to that project context. However, it is important to understand that the Knowledge Graph connected here is scoped to OTTO's own Knowledge Graph for that project — not your full, standalone Knowledge Graph profile. If you have built out a rich Knowledge Graph profile separately, that data will not automatically flow into the OTTO-scoped Cloud Stack. 🛠️ Method 2: Creating a Standalone Cloud Stack You can also create a Cloud Stack independently, without going through OTTO: 1. Click Authority in the left sidebar. 2. Select Cloud Stacks from the sub-menu. 3. Click the button to create a new Cloud Stack and complete the setup form. A standalone Cloud Stack gives you direct control and allows you to associate it with your complete Knowledge Graph profile. This is the recommended path when you want the Cloud Stack to reflect the full set of entity information you have already built. 💡 Why Does the Cloud Stack Knowledge Graph Appear Empty? This is the most common question customers ask about Cloud Stacks. Here is what causes it and how to resolve it: - OTTO uses its own scoped Knowledge Graph. When a Cloud Stack is generated inside OTTO, it pulls entity data from OTTO's internal Knowledge Graph for that project. If you have not populated that specific Knowledge Graph inside OTTO, the Cloud Stack will have little or no entity data to work with — even if your main Knowledge Graph profile is fully built out elsewhere. - Standalone Cloud Stacks are not automatically linked. Creating a Cloud Stack through Authority → Cloud Stacks does not automatically import your existing Knowledge Graph. You need to actively associate your Knowledge Graph during or after setup to populate the entity fields. - The fix: populate or link the correct Knowledge Graph. If you are working inside OTTO, fill in the Knowledge Graph fields within the OTTO project before generating the Cloud Stack. If you are working standalone, ensure you select and connect your complete Knowledge Graph profile during the Cloud Stack creation process. ✅ Which Method Should You Use? - Use OTTO → Cloud Stack when you want a streamlined, project-managed workflow and are happy to populate entity data directly inside OTTO. - Use Authority → Cloud Stacks (standalone) when you want to leverage a fully built Knowledge Graph profile and have more direct control over the Cloud Stack configuration. Both methods produce a functional Cloud Stack — the key is making sure the right Knowledge Graph data is connected before the stack is built, so the authority signals are as relevant and complete as possible. 💬 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.

🆕 Cloud Stack: Expanded to 25 Publishing Destinations

🚀 What's New This Week We've enabled 5 new providers in the Cloud Stack publishing network, bringing the total number of available publishing destinations to 25. More providers means: - 🌎 Broader reach - 🔗 Stronger backlink diversity - 📈 Better Cloud Stack performance 🆕 New Providers Added - 🗂️ Filebase - 🔥 Firebase Hosting - ⚡ Amplify - 🦊 GitLab - 🎨 Render ☁️ Complete Cloud Stack Provider List (25 Total) 🌐 Existing Providers (20) - ☁️ Cloudflare - 🔷 Azure - ▲ Vercel - 🐙 GitHub - ⚙️ Scaleway - 🐉 Tencent - 🟧 AWS - 🌊 DigitalOcean - 🐰 Bunny - ⬆️ UpCloud - 🖥️ Contabo - ❄️ Exoscale - 💾 Wasabi - 📦 Backblaze - 🌐 Netlify - 🏢 IBM Cloud - 🌍 IONOS - ⚡ Vultr - 🚫 Neocities (disabled) - 🚀 Surge 🆕 New Providers (5) - 🗂️ Filebase - 🔥 Firebase Hosting - ⚡ Amplify - 🦊 GitLab - 🎨 Render 🎯 Why This Matters By distributing your Cloud Stack pages across a larger network of high-authority providers, you gain: 🌎 Broader Reach Access a wider variety of cloud infrastructure providers and publishing environments. 🔗 Stronger Backlink Profile Build authority signals from a more diverse set of trusted domains. 📈 Better Performance Leverage increased provider diversity to maximize the SEO impact of your Cloud Stack campaigns.

How It Works: Cloud Stacks

☁️ What Cloud Stacks Are Cloud Stacks let you create AI-generated web pages and publish them across multiple high-authority cloud domains. Each page links back to your target URL from these trusted providers, helping increase your site's visibility and authority. ⚙️ What You Need Before creating a Cloud Stack, gather the following: 🏢 A Brand Vault — provides business identity, brand voice, and context for content generation 🤖 An OTTO or GBP project — to bind the cloud stack to 🔗 A target URL — the page the cloud stack content will link to 🎨 An HTML template — the visual design for the generated page 🎯 SEO keywords — up to a few core terms the content should target 💳 Hyperdrive Credits (HDC) — to cover generation and publishing costs 🚀 The Workflow 1️⃣ Create Choose your project (OTTO or GBP), then provide: 🔗 Target URL 🎯 SEO keywords ✍️ AI instructions (tone, focus, key points) 🎨 HTML template from the available library Brand information from your Brand Vault informs the content generation. 2️⃣ AI Builds the Content The AI generates a fully styled HTML page based on your instructions, keywords, brand information, and template. Each cloud provider receives a unique version of the page to maintain editorial diversity. 📊 Status: Pending → Generating → Generated 3️⃣ Review & Edit Preview the generated page and: 👀 Review the copy 🎨 Make visual edits through the editable preview URL 🔄 Regenerate content if you want to refine the instructions 4️⃣ Choose Cloud Providers Select which cloud providers to publish to. Each provider hosts your page on its own trusted domain and creates a separate live URL that links back to your target URL. 5️⃣ Publish Confirm your content and review the HDC cost before deploying to your selected providers. 📊 Status: Publishing → Published When publishing completes, all live URLs appear in your dashboard. 📈 What You Get ☁️ Multiple live pages hosted on high-authority cloud domains 🔗 Links to your target URL from trusted cloud providers 🏢 Increased brand visibility across credible cloud infrastructure 📊 Authority signals from diverse, high-quality sources 🎯 Topical authority reinforcement for your target page 📋 A centralized dashboard tracking every live URL and status ✅ Best Practices 🏢 Keep your Brand Vault complete and up to date for consistent, on-brand content 🎨 Choose a template that matches your page's purpose (service page, location page, product page, etc.) 🎯 Use focused, intent-aligned keywords rather than broad terms ✍️ Write detailed AI instructions, including desired tone, key messages, and topics to emphasize or avoid 👀 Always review the generated page before publishing 🌐 Distribute across multiple providers to maximize link diversity and reach

📘 MCP for Cloud Stack

Cloud Stack allows you to build and publish cloud-based structures from templates, which are used as part of SEO and link-building workflows. Through MCP, your AI assistant can create stacks, publish them, and track their status. This article explains how to create, build, and manage cloud stacks using MCP. 🧠 What You Can Do Using MCP with Cloud Stack, you can: - Create cloud stacks from templates - Build cloud stack structures - Publish cloud stacks - Track build and publication status - Monitor quota usage 👉 Cloud stacks are used as part of broader SEO workflows, particularly in link-building strategies. ✅ Prerequisites & Plan Requirements Before using Cloud Stack via MCP, please note: - MCP access to Cloud Stack tools is included in plans that have the Cloud Stack add-on or feature enabled. If you are unsure whether your plan includes Cloud Stack MCP access, contact your account manager or Search Atlas support. - Certain Cloud Stack capabilities (such as specific providers or higher-volume publishing) may be restricted by plan tier or require special enablement on your workspace. - If an MCP endpoint is not enabled for your plan, your AI assistant will return an access or permission error when invoking the tool. ☁️ Supported Cloud Providers & Templates Cloud stacks are created from provider templates. Search Atlas currently supports 15+ cloud providers, including recently added git-based and sandbox providers such as: - GitLab Pages - AWS Amplify - SourceForge - Glitch - CodeSandbox 👉 When you ask your AI assistant to create a cloud stack, you can specify which provider template to use. If you do not specify one, the assistant may list available providers or pick a default based on your workflow. ⚙️ Step-by-Step: Create a Cloud Stack Step 1 Open your MCP-connected AI assistant Step 2 Ask to create a cloud stack Examples: - “Create a cloud stack” - “Set up a cloud stack from a template” - “Create a cloud stack on GitLab Pages” (or any supported provider) Step 3 The assistant creates the stack from the chosen provider template 👉 Stacks are always created from one of the supported provider templates listed above. Step 4 Confirm stack details ⚠️ Note (upcoming change): The separate cs_create and cs_build MCP tools may be merged into a single cs_create action. Once that change ships, the Create and Build steps below may be combined into one command — your AI assistant will handle creation and build in a single step. 🏗️ Step-by-Step: Build the Cloud Stack 💡 Build vs. Publish: Building compiles and prepares the stack structure (assembling files, configuration, and template content) so it is ready to deploy. Publishing takes the built stack and makes it live/publicly accessible at its provider URL. Both steps are currently required; they may be merged into a single step pending an upcoming release. Step 1 Ask your assistant: - “Build my cloud stack” Step 2 The assistant initiates the build process Step 3 Wait for completion 👉 Building prepares the stack for publishing — the stack is not yet live at this point. 📤 Step-by-Step: Publish the Cloud Stack ⚠️ Important — publishing is potentially immediate and not easily reversible. Once a stack is published, it becomes live at its provider URL. Always review your stack content and configuration before issuing a publish command. Step 1 Ask your assistant: - “Publish my cloud stack” Step 2 The assistant prepares the publication Step 3 Approve the action (if required) When approval is triggered, your AI assistant will display a confirmation dialog or return an MCP response that requires acknowledgment before the publish call is executed. To proceed, reply with an explicit confirmation such as “Yes, publish” or click the approve button in your assistant's confirmation prompt. To cancel, reply “No” or “Cancel” — the stack will remain unpublished. Whether the approval prompt appears depends on your MCP client's configuration: some clients are configured to auto-approve tool calls, in which case the publish may execute immediately. If you want to ensure a manual approval step every time, configure your MCP client to require confirmation for Cloud Stack publish actions. Step 4 The stack is published 👉 Publishing makes the cloud stack active and accessible at its provider URL. 📊 Step-by-Step: Track Status Step 1 Ask your assistant: - “Show my cloud stack status” Step 2 The assistant retrieves status data Step 3 Review: - build status — whether the stack has been compiled and prepared for publishing (e.g., pending, in progress, completed, failed) - publication status — whether the stack is live at its provider URL (e.g., unpublished, publishing, published, error) - progress updates — incremental updates while build or publish operations are running Step 4 Interpret the result and take next steps: - If build status shows failed, ask your assistant for the error details and re-run the build after addressing the issue. - If publication status shows published, your stack is live — verify it at the provider URL. - If status appears stuck, wait a moment and ask your assistant to refresh the status. 📈 Monitoring Quota Usage Cloud Stack actions consume Search Atlas quota. To check your usage via MCP: - Ask your assistant: “Show my Cloud Stack quota” or “How much Cloud Stack quota do I have left?” - The assistant will return your current quota balance and usage for Cloud Stack operations. Quota limits depend on your plan and any add-ons. Creating, building, and publishing stacks each may consume quota, and certain providers may consume more than others. ⚠️ Note: The quota displayed in the Search Atlas dashboard may not always reflect what is accessible via MCP. If a specific endpoint is restricted on your plan, the MCP tool may return an access error even when the dashboard shows available quota. Contact support if you see a mismatch. ⚠️ Important Notes 1. Creating and building stacks may consume Search Atlas quota 2. Publishing may involve additional resource usage 3. Actions may require approval depending on execution 4. Cloud stacks are part of broader SEO workflows 5. Publishing via MCP is potentially immediate and not easily reversible — always review your stack before issuing a publish command 🔁 How This Fits Into MCP Workflows A typical workflow: 1. Create cloud stack 2. Build stack 3. Publish stack 4. Track status 👉 This supports infrastructure-based SEO execution. 🧠 Best Practices 1. Confirm configuration before building 2. Review stack content before issuing a publish command — publishing is potentially immediate 3. Monitor status after publishing 4. Use cloud stacks as part of larger SEO strategies 5. Track results alongside other SEO tools MCP for Cloud Stack allows you to create and deploy cloud-based SEO structures through conversation. By building and publishing stacks from templates, your AI assistant can execute infrastructure-level SEO actions using the same capabilities available in Search Atlas.

☁️🔧 Cloud Stacks

Cloud Stacks Cloud Stacks are digital entities within Search Atlas designed primarily as tools for generating backlinks, which contribute to improving the visibility and ranking of web content in search engine results. This documentation covers the technical implementation details for working with Cloud Stacks via the API. Authentication All API requests require Bearer token authorization: Authorization: Bearer <API_TOKEN> Cloud Stack Pricing Each Cloud Stack is priced at 15 Hyperdrive credits (equivalent to $15). Credits are deducted once, at the time of Cloud Stack creation (the content generation phase), prior to publishing. - No additional credits are charged when you later select sites and publish the stack. - Generated content consumes credits even if it is not published later. - Credits are non-refundable once used. - If a generation attempt fails and is retried, verify your HDC ledger to confirm only successful creations were billed. Cloud Stack Status Flow Pending → Generating → Generated → Publishing → Published Unpublished: Removed after publication Provider Status: - HTML_CREATED: Publishing content - PUBLISHED: Successfully published - PUBLISHING_FAILED: Failed to publish - INDEXING: Indexation in progress - INDEXED: Published and indexed successfully - INDEXER_SYNC_FAILED: Indexing failed - NOT_INDEXED: Could not index content Creating a Cloud Stack Create a new Cloud Stack associated with either a Knowledge Graph or OTTO Project. Endpoint: POST https://sa.searchatlas.com/api/cg/v1/cloud-stack-contents/ Payload Example: { "target_url": "https://example.com/about-us/", "keywords": ["SEO"], "knowledge_graph": "knowledge_graph_id" // Alternatively, "otto_project": 267 } Manual Workflow Required After Creation Creating a Cloud Stack does not automatically generate, approve, or publish content. After creation you must complete the following steps: 1. Trigger AI content generation via the Build endpoint. 2. Review and approve the generated content. 3. Select target sites (cloud stack providers) for deployment. 4. Deploy to publish. Stacks that appear stuck or 'failed' often simply require manual approval. If you have many stacks, increase the results-per-page in the UI to locate any awaiting approval. Building Cloud Stack Content Trigger content generation via AI. Endpoint: POST https://sa.searchatlas.com/api/cg/v1/cloud-stack-contents/:cloud_stack_id/build/ Deploying Cloud Stack Content Deploy content to specified providers. No additional HDC are charged at this step. Endpoint: POST https://sa.searchatlas.com/api/cg/v1/cloud-stack-contents/:cloud_stack_id/deploy/ Payload Example: { "cloud_stack_providers": [1, 2, 3, 4, 5] } Retrieving Cloud Stack Content Retrieve detailed cloud stack information. Endpoint: GET https://sa.searchatlas.com/api/cg/v1/cloud-stack-contents/:cloud_stack_id List Cloud Stack Providers List available cloud stack providers. Endpoint: GET https://sa.searchatlas.com/api/cg/v1/cloud-stack-providers Troubleshooting - Repeated generation failures with a populated Knowledge Graph: Check whether the affected stacks are actually awaiting manual approval rather than failed. Adjust pagination/results-per-page filters in the UI to locate them. - HDC overcharge concerns: Credits are charged only at the moment of Cloud Stack creation. Selecting sites and publishing will not consume additional HDC. If your total deduction does not match the number of successfully created stacks × 15 HDC, contact support with the affected stack IDs. - Stacks stuck in 'Generating': Confirm the Build endpoint was triggered and that the Knowledge Graph is fully populated; retry generation if needed. Postman Collection Available in the OTTO Cloud Stacks Postman collection. See the Search Atlas Knowledge Base for additional details.

🗑️ How to Remove Published and Indexed Cloud Stacks Content

📘 About Cloud Stacks Content Cloud Stacks lets you publish content to web properties (such as cloud storage entities and other hosted pages) to support your SEO strategy. Because this content is hosted externally and can be crawled by search engines, it may become indexed and appear in search results. This article explains what happens when you delete a Cloud Stacks campaign and how to remove content that has already been published or indexed. 🧩 What Happens When You Delete a Campaign Deleting a Cloud Stacks campaign removes the campaign and its management from your Search Atlas dashboard. However, deletion behaves differently depending on where the content lives: - Content managed by Search Atlas: Pages published and controlled through the platform are taken down when the campaign is deleted. - Content on external properties you own: Files pushed to your own connected accounts or storage may remain live until they are manually removed from those accounts. - Search engine index: Deleting a campaign does not instantly remove content from Google or other search engines. The index updates on its own schedule. In short, taking a page offline and removing it from search results are two separate steps. 🚀 How to Delete a Cloud Stacks Campaign 1. Log in to your Search Atlas account. 2. Open the Cloud Stacks tool from the main menu. 3. Locate the campaign you want to remove in your list of campaigns. 4. Select the campaign options menu and choose Delete. 5. Confirm the deletion when prompted. Once confirmed, the campaign is removed from your dashboard along with the content Search Atlas directly manages. 🌐 Removing Content From Web Properties If content was published to properties you own or connected, you may need to remove it at the source: - Sign in to the connected account or storage service where the content was published. - Locate the published files or pages created by the campaign. - Delete the files so the URLs return a 404 (Not Found) or 410 (Gone) status. Returning a 404 or 410 status is important, because it signals to search engines that the page no longer exists, which speeds up removal from the index. 🔍 Removing Already-Indexed Content From Search Results Even after a page is taken offline, it can linger in search results until search engines recrawl it. To speed this up: 1. Confirm the page is offline. Visit the URL and verify it returns a 404 or 410 error. 2. Use Google Search Console. If you own or can verify the property, submit a removal request through the Removals tool. This temporarily hides the URL while the index updates. 3. Wait for recrawling. Once search engines revisit a dead URL, they drop it from the index automatically. This can take days to a few weeks. 🔑 What to Do When You Have No Access to the Sites Customers often ask how to remove indexed content when they do not control the hosting property or its Search Console. If you cannot access the site directly, consider these options: - Request removal through Search Atlas. If the content was published through a Search Atlas-managed property, our team can help take it down. Start a live chat and share the campaign name and the affected URLs. - Use Google's public removal tools. For outdated or removed content on pages you do not own, Google offers a public Remove Outdated Content tool. This works once the page is already offline and returns an error. - Contact the property owner. If a third party controls the hosting, they may need to delete the files before the content can leave the index. ⏱️ How Long Removal Takes Timelines vary based on how often search engines crawl a page: - Search Console removal requests: Content is typically hidden within hours, then permanently dropped after recrawling. - Natural recrawling: Removal from the index usually takes a few days to several weeks. - High-authority or frequently crawled pages: These may be updated faster. ✅ Best Practices Before Deleting - Make a note of every URL published by the campaign before you delete it, so you can track and confirm removal later. - Take content offline first, then submit removal requests once the URLs return errors. - Keep a record of which properties you own versus those managed on your behalf. 💬 Need More Help? If you need further assistance, click the chat icon in the bottom-right corner of the platform to start a live chat with a member of our team. Please have your campaign name and the affected URLs ready so we can help you remove the content quickly.