Troubleshooting: Cloud Stacks Issues

📍 Fix Cloud Stack Google Maps URL Errors

If Cloud Stack won't accept a Google Maps short link (like a maps.app.goo.gl URL) or even a full Google Maps URL, this is expected — Cloud Stack does not read map links directly. Instead, it requires the actual iframe embed code from Google Maps. This article shows you exactly where to get that code and where to paste it. 📍 Where to Find It You'll add your map inside Left sidebar → Authority → Cloud Stacks, using the New Cloud Stack or Select Sites options to open the location where your map field lives. 🛠️ Step-by-Step 1. Open Google Maps in a browser and search for the exact business location you want to display. 2. Click the Share button for that location. 3. In the Share window, choose the Embed a map tab — not "Send a link." This tab generates an HTML iframe snippet, not a URL. 4. Click Copy HTML to copy the full iframe embed code. 5. Go to Left sidebar → Authority → Cloud Stacks and open the Cloud Stack you're editing (or start a New Cloud Stack). 6. Find the map/location field for the stack and paste the copied iframe embed code directly into it — do not paste a short link or full Google Maps URL here. 7. Save your Cloud Stack. ✅ How to Confirm It Worked After saving, reopen the Cloud Stack entry and check that the map preview renders visually (an embedded map, not an error message or blank field). If your Cloud Stack has a preview or view report option, use it to confirm the map displays correctly on the live output before considering the task complete. 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 Stuck Partially Published Fix

🔍 Overview Some users reported that their Cloud Stacks (Google stacks) stopped publishing partway through deployment — for example, showing 12 of 15 sites completed — and remained stuck in that state for many days despite having active credits. This was caused by a platform-level publishing bug that prevented stacks from completing the final publication stage automatically. Engineering investigated the issue (tracked internally as SPE-1014) and released a fix that is now live in production. If your stacks were affected, they should now resume and complete normally. ✅ What Was Causing This A bug in the Cloud Stacks publishing pipeline caused certain stacks to get stuck before the final publish stage. Affected stacks included those that had been in a partially published or generating state for an extended period — in some cases more than two weeks — without any progress. This was not caused by insufficient credits or an account configuration issue. It was a backend platform defect that has since been resolved. 📋 Steps to Check Your Cloud Stacks Status 1. Navigate to the Cloud Stacks section of the platform. 2. Review the list of your stacks and check the publication progress for each one (for example, how many of the total sites have been published). 3. If any stacks are still showing as incomplete, note how long they have been in that state. 4. Refresh the page and wait a few minutes — now that the fix is live, stacks that were previously stuck should begin completing automatically. 5. If progress resumes and all sites publish successfully, no further action is needed. ⚠️ When to Reach Out for Help The engineering fix is live and should resolve stacks that were stuck at the time of the incident. However, if you check your stacks and notice any of the following, contact our support team directly: - A stack has not made any progress for more than 48 hours after the fix was released. - Your stack count is still not reaching the expected total (for example, remaining at 12 of 15 with no movement). - You see an error message or an unexpected status on a stack you recently created. 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 Fix an Incompatible Google Maps URL in Cloud Stack

This article explains what to do when a Google Maps URL you enter in Cloud Stack is flagged as incompatible or fails to load correctly — and how to resolve the format issue so your report data populates as expected. 🔍 What Causes the Incompatible URL Error Cloud Stack requires a specific Google Maps URL format to correctly pull location data. If you paste a URL directly from your browser's address bar after searching on Google Maps, the format may include parameters (such as search query strings or shortened redirect URLs) that Cloud Stack cannot parse. This mismatch causes the URL to be rejected or the location data to fail to load. 🛠️ Step-by-Step: Use the Correct Google Maps URL Format 1. Go to Google Maps and locate the business you want to add. Search for the business and open its full listing page. 2. Copy the URL from the address bar only after the page has fully loaded and the listing is open. The correct URL should point directly to the place listing, not to a search results page. 3. Avoid using shortened URLs (e.g. maps.app.goo.gl links) or URLs copied from a Google Search results page. These formats are not supported by Cloud Stack and will trigger the incompatibility error. 4. Paste the correctly formatted Google Maps URL into Cloud Stack. If the URL is in the supported format, Cloud Stack will accept it and begin pulling location data. 5. If the URL still shows as incompatible, double-check that you are on the place's dedicated listing page in Google Maps (not a search results view or directions page) before copying the URL. ✅ How to Confirm It Worked After entering the correctly formatted URL, Cloud Stack should accept the entry without an incompatibility error and begin loading the associated Google Maps location data. If you continue to see an error, note the exact URL you used and the exact error message displayed, then escalate to support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

☁️ Fix Cloud Stack GBP Selection and Chat Widget

🔍 Overview Two common frustrations when working in Cloud Stacks are: the project setup pulling in the wrong Google Business Profile (GBP), and the live chat widget overlapping navigation elements. This article walks you through both fixes so you can build your Cloud Stacks accurately and navigate the platform without interruption. 🗺️ How to Navigate to Cloud Stacks To access Cloud Stacks, follow these steps: 1. Log in to your Search Atlas account. 2. In the left sidebar, click Authority. 3. From the expanded menu, select Cloud Stacks. 📍 Selecting the Correct Google Business Profile When creating a new Cloud Stack, Search Atlas automatically suggests a GBP based on your project settings. If the wrong profile appears, it is usually because the GBP linked to your project needs to be updated before you start the Cloud Stack setup. Follow these steps to make sure the correct GBP is selected: 1. Before creating a Cloud Stack, confirm which GBP you want to use by checking your project settings. 2. On the Cloud Stacks page, click New Cloud Stack. 3. In the setup form, locate the Google Business Profile field. 4. Click the dropdown and review the list of available profiles. If multiple profiles are connected to your account, make sure you choose the one that matches the business you are optimising. 5. If the correct GBP does not appear in the dropdown, it may not be connected to your Search Atlas account yet. Connect it first through your account settings, then return to Cloud Stacks to complete setup. 6. Once the correct profile is selected, continue filling in the remaining Cloud Stack details and click Save or Create. Tip: Double-check the business name, address, and phone number shown in the preview before finalising. This confirms you have selected the right profile. 💬 Managing the Chat Widget Position The live chat widget sits in the bottom-right corner of the platform by default. In some views — particularly when working inside Cloud Stacks or browsing the left sidebar — the widget can overlap buttons or navigation links. Here is how to work around this: - Minimise the widget: Click the chat icon to open the widget, then click the minimise or close button (×) at the top of the chat window. This collapses it to a small icon that takes up less space. - Scroll past the widget: If the widget covers a button at the bottom of the page, try scrolling the page content up slightly so the button clears the widget area. - Use keyboard navigation: Press Tab to move focus through interactive elements on the page, which can help you reach buttons that are visually overlapped by the widget. - Zoom out your browser: Reducing your browser zoom level (for example, from 100% to 90%) can give you enough extra space so the widget no longer covers navigation controls. Note: The widget position is fixed by the platform and cannot be permanently moved or disabled, as it is the primary support channel. Minimising it when not in use is the most reliable way to keep your workspace clear. ⚠️ Common Issues and Quick Fixes - GBP dropdown shows no profiles: Your Google account may not be connected. Go to your account settings and authorise the Google Business Profile integration, then retry. - Wrong GBP keeps defaulting: Check whether another user on your team has set a default project GBP. Update the project-level GBP setting first, then create the Cloud Stack. - Chat widget covers the Create button: Minimise the widget or use browser zoom-out (Ctrl/Cmd + minus key) to push the button above the widget overlap zone. - Cloud Stack saves with wrong GBP: Delete the Cloud Stack, correct the GBP connection in settings, and rebuild. Changes to the GBP field cannot be made after a Cloud Stack is saved. 🆘 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes This field may auto-populate based on your most recently used project. / If the wrong profile keeps appearing, it usually means a different GBP is set as the default, or the wrong project was selected during setup.

☁️ Fix Cloud Stacks That Won't Index

🔍 Overview Cloud stacks are designed to support your link-building and authority strategy, but Google does not guarantee indexation for any URL — including cloud stack pages. If your cloud stack URLs have not been indexed after several months, this article explains why that happens and what you can do about it, including how to use the built-in Indexing Tool to manually submit URLs to Google. ⚠️ Why Cloud Stack URLs May Not Get Indexed Google crawls and indexes URLs at its own discretion. Even well-structured cloud stack pages can go unindexed for a variety of reasons: - Low crawl priority: New or low-authority domains are crawled less frequently by Googlebot. - Lack of inbound links: Pages with no external links pointing to them are harder for Google to discover. - Crawl budget constraints: On large sites or networks, Google may not allocate crawl budget to every page. - Content thinness: Pages that appear low-value or duplicative may be deprioritised or skipped entirely. These factors can delay indexation by weeks or even months, regardless of how the cloud stack was built. ✅ What You Can Do: The Indexing Tool If your cloud stack URLs have not been indexed after a reasonable amount of time, the most direct solution is to use the Indexing Tool inside Search Atlas. This tool lets you manually submit URLs to Google for indexation rather than waiting for organic discovery. To access the Indexing Tool, go to Left sidebar → Authority → Indexer (URL Indexer). 📋 How to Submit URLs with the Indexing Tool 1. Navigate to Left sidebar → Authority → Indexer (URL Indexer). 2. Click Index URLs on the page. 3. Paste the cloud stack URLs you want to index, one per line. 4. Review the list to confirm all URLs are correct. 5. Click Index URLs to send the URLs for indexation. 6. Monitor the status column over the following days to track whether each URL has been picked up by Google. Each URL push costs approximately $0.10 per URL. This cost is deducted from your account credits. Make sure your account has sufficient credits before submitting a batch of URLs. 💡 Tips for Better Indexation Results - Prioritise your most important URLs first. Submit cloud stack pages that are closely tied to your target keywords or anchor text strategy. - Combine the Indexing Tool with linking. URLs that also receive inbound links — from blog posts, social profiles, or other authority assets — tend to get indexed faster and stay indexed longer. - Avoid re-submitting too quickly. If a URL has been pushed recently, wait at least 7–10 days before pushing it again to avoid wasting credits. - Check for technical issues first. Before submitting, verify that the cloud stack URL loads correctly and is not returning an error code such as 404 or 503. 🔎 How to Check Whether a URL Is Already Indexed Before spending credits, confirm a URL is genuinely not indexed. The quickest way is to paste the full URL into Google search using the format site:yoururl.com/page. If no result appears, the page is not currently indexed and is a candidate for the Indexing Tool. You can also review indexation status directly within the URL Indexer dashboard, which displays the last known status for each submitted URL. 📍 Where to Find Your Cloud Stack URLs If you are unsure which URLs to submit, navigate to Left sidebar → Authority → Cloud Stacks to view all cloud stacks associated with your account. From there you can copy the individual page URLs and paste them into the URL Indexer. 🕐 What to Expect After Submitting Submitting a URL via the Indexing Tool signals Google to crawl and consider that page for indexation. Most URLs submitted this way are crawled within a few days, though actual indexation is still at Google's discretion. You should see meaningful progress within 7–14 days of submission. If a URL remains unindexed after 14 days despite being pushed, it may indicate a content or technical issue with the page itself that is preventing Google from indexing it. 🆘 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.

🛠️ Troubleshooting Cloud Stack Generation Failures

If you're seeing the message "Cloud stack generation failed. Please try generating again," this article walks you through the specific causes of this error and the exact steps to resolve it. Cloud stack failures are most commonly linked to image upload issues or asset problems that prevent the generation process from completing. 📍 Where to Find It Cloud Stacks is located at Left sidebar → Authority → Cloud Stacks. This is where you initiate generation and where any error messages will appear. 🛠️ Step-by-Step 1. Check your uploaded images before generating. The most common cause of this error is an incompatible or corrupted image file. Make sure every image you upload meets the following requirements: - File format: JPG, JPEG, or PNG only - File size: keep each image under 5 MB - Avoid images with special characters in the file name (e.g., #, &, %) - Do not upload screenshots taken directly from a browser — export or save the image file properly before uploading 2. Remove and re-upload your images. If you already uploaded images before the error occurred, delete them from the upload area and re-upload fresh copies that meet the requirements above. 3. Clear your browser cache and reload the page. Navigate away from Left sidebar → Authority → Cloud Stacks, clear your browser cache (or open a private/incognito window), then return to the page before attempting generation again. 4. Try a different browser. If the error persists after re-uploading, attempt the generation in a different browser (Chrome or Firefox are recommended) to rule out a browser-specific conflict. 5. Retry the generation. Once your images are confirmed to be in the correct format and size, click the generate button again. Do not click multiple times in quick succession — allow the process to fully run before retrying. 6. Check for platform status issues. If none of the above resolves the error, the issue may be a temporary infrastructure problem. Wait a few minutes and try again before escalating. ✅ How to Confirm It Worked A successful cloud stack generation will show a status change from "Failed" or "Pending" to "Complete" within the Cloud Stacks dashboard at Left sidebar → Authority → Cloud Stacks. You should be able to view and access your generated cloud stack assets directly from that page. If the status does not update within a few minutes of retrying, or if the failure message reappears immediately, the issue likely requires hands-on support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Troubleshooting Agent Mode Cloudstacks Not Appearing

This article explains what to do when cloudstacks you created through Agent mode are not visible in your main dashboard. If you are experiencing this issue, our support team will need to investigate your account directly to identify the cause and resolve it. 🛠️ What to Do Because the resolution for missing Agent mode cloudstacks requires backend investigation, there are no self-serve steps that reliably surface the missing items. To get this resolved as quickly as possible, please have the following information ready before contacting support: - The name of the project you were working in when you launched the Agent mode job - An approximate date and time when you submitted the cloudstack job - Any confirmation message, job name, or task reference you received at the time of submission - A description of what you expected to see and where you expected to see it in the dashboard ✅ What to Expect Once you contact support with the details above, a member of our team will be able to look into your account, locate the Agent mode job, and advise on next steps — including whether the cloudstack needs to be re-submitted or whether it can be surfaced through a backend action. 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.

🛠️ Troubleshooting Cloud Stack Generation Failed Error

This article helps you fix the "Cloud stack generation failed. Please try generating again" error that can appear when uploading images inside your GBP Project. This error is typically triggered by an issue with the image file itself or a temporary platform hiccup — not always the number of images selected. The steps below give you the specific checks and actions needed to resolve it and confirm the upload succeeded. 📍 Where to Find It Navigate to Left sidebar → Local → GBP Projects, then open the relevant project. The cloud stack image upload option is available within the project's posting or overview area. 🛠️ Step-by-Step 1. Refresh and retry immediately. The error is sometimes caused by a momentary connection issue with the cloud service. Close the dialog, wait 30 seconds, and attempt the generation again before making any other changes. 2. Check your image file format. Only use widely supported formats such as JPG, JPEG, PNG, or WebP. Files in HEIC, TIFF, BMP, or other formats can trigger this error even if the image count is within the limit. 3. Verify image file size. Each image should be under 5 MB. Large files may cause the cloud stack process to fail silently. Compress or resize any image that exceeds this threshold before re-uploading. 4. Confirm you are selecting fewer than 4 images. Even if you believe you have selected fewer than 4, deselect all images and reselect them one at a time to rule out a selection state error in the UI. 5. Check image dimensions. Very small images (under 250 × 250 px) or unusually large canvases can cause processing failures. Use images with standard dimensions appropriate for Google Business Profile posts. 6. Try a different browser or clear your cache. Open your GBP Project in an incognito window or a different browser. Clear cached data if the error persists in your usual browser, as stale cache can interfere with upload processing. 7. Re-upload with a single image first. If multi-image uploads continue to fail, test with one image only to isolate whether the issue is file-specific or affects all uploads in this project. ✅ How to Confirm It Worked After retrying the generation, you should see the cloud stack preview render successfully within the project view — the error banner will disappear and your uploaded image(s) will display in the posting queue or overview area. Navigate to Left sidebar → Local → Overview and confirm the post or image appears under the relevant tab. If the preview loads without any error message and the image is visible in the project, the cloud stack was generated 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.

🛠️ Troubleshooting Cloud Stack Generation Failed Errors

This article addresses the "Cloud stack generation failed. Please try generating again" error that can appear when uploading images within the platform. This error is typically triggered by image file issues, upload timing problems, or exceeding system constraints — even when you believe you are within the allowed limits. Follow the steps below to identify and fix the root cause. 🔍 Common Causes - Unsupported file format or corrupt image: The platform requires standard image formats (JPG, PNG, WebP). Corrupt files or uncommon formats can silently fail during cloud processing. - File size too large: Even if you have selected fewer than the maximum number of images, an individual file may exceed the per-image size limit. - Image dimensions out of range: Extremely large or unusually small pixel dimensions can cause the cloud stack to fail during generation. - Temporary upload or server timeout: A slow connection or a brief platform instability can interrupt the cloud processing step. - Metadata or EXIF data conflict: Some images carry embedded data that can interfere with cloud stack processing. 🛠️ Step-by-Step 1. Check your image file format. Confirm each image you are uploading is saved as JPG, PNG, or WebP. If your file is in HEIC, TIFF, BMP, or another format, convert it to JPG or PNG using any free image converter before re-uploading. 2. Check individual file size. Even if you selected fewer than 4 images, verify that each individual file is under 5 MB. Large files can exceed the cloud processing limit on their own. Compress or resize any oversized images before retrying. 3. Check image dimensions. Ensure your images are not excessively large (e.g., raw camera exports at 8000×6000 px or higher). Resize to a web-friendly resolution such as 1200×800 px and attempt the upload again. 4. Strip image metadata. Use a tool such as Squoosh (squoosh.app) or your operating system's export options to save a clean copy of the image without EXIF metadata, then try uploading the cleaned file. 5. Retry the generation. After addressing any file issues, dismiss the error message, re-select your images, and click the generate button again. Wait for the progress indicator to complete fully before navigating away. 6. Try a single image first. If the error persists with multiple images, isolate the problem by uploading one image at a time to identify which specific file is causing the failure. 7. Clear your browser cache and retry. A stale session can contribute to upload failures. Clear your browser cache, log back in, and attempt the upload in a fresh session or a different supported browser (Chrome or Edge recommended). ✅ How to Confirm It Worked After retrying, the cloud stack generation is successful when: - The progress indicator completes without displaying the "Cloud stack generation failed" message. - Your uploaded image or images appear as previews or thumbnails within the interface where you initiated the upload. - Any associated content or feature that depends on the image (such as a schema entry or GBP post) shows the image attached and ready to use. If the error reappears on a specific image even after following all steps above, save the file name, its format, and its size so our team can investigate a potential processing issue on that file type. 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. Additional Notes Confirm you are selecting fewer than 4 images — deselect all images and reselect them one at a time to rule out a selection state error in the UI. Also: try a different browser or clear your cache / open in incognito window, as stale cache can interfere with upload processing.

🖼️ Fix Cloud Stack Photo Count Errors in Brand Vault

🗺️ Where to Find Brand Vault Access your Brand Vault: top-right More Features menu (grid icon, next to your account menu) → Brand Vault, or the top-right More Features menu (grid icon) → Brand Vault. If you have already created one, it will appear there. ⚠️ Understanding the 'Too Many Photos in DKN' Error This error appears when the number of photos associated with your Brand Vault exceeds the allowed limit for a Cloud Stack. The limit applies to all photos stored within your Brand Vault's photo library — not only the photos you select at the moment of Cloud Stack creation. This means that even if you choose only four photos during the Cloud Stack setup, the error can still occur if your overall Brand Vault photo library already contains too many images. 📸 What Counts Toward the Photo Limit The photo count is based on the total images stored in your Brand Vault photo library. Important: The exact breakdown of which image types count toward the limit — such as logos, profile images, or images from connected sources — is not fully documented at this time. If you are seeing a count that does not match what you expect, do not remove photos based on assumptions about hidden fields. Instead, contact our team directly for verified guidance (see below). 🔧 Steps to Resolve the Error 1. Open your Brand Vault project using either method above. 2. Review the total number of photos currently stored in your Brand Vault — not just the ones you plan to use for the Cloud Stack. 3. If your total photo count is at or near the limit, remove photos you no longer need to bring the total below the allowed threshold. 4. Once the library count is within the limit, return to the Cloud Stack creation flow and try again. ❓ What to Do If the Error Persists If you have reduced your photo library count and the error still appears, or if the number shown in your library does not seem to explain the error, do not delete additional photos without guidance. There may be account-specific factors affecting your limit that require investigation by our team. When contacting support, please have the following ready: your Brand Vault project name, the exact error message you are seeing, and a timestamp of when the error occurred. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚠️ Cloud Stack Shows a Blank Preview After Generation Completes

If your Cloud Stack preview is blank even though the orchestrator has confirmed generation is complete, a known bug may have falsely reported success before your content finished building. Trigger a fresh regeneration using the steps below — your settings, keywords, and configuration are preserved. ⚠️ What Causes the Blank Preview The Cloud Stack orchestrator has a known issue where it reports "fully generated and ready for review" without first confirming that content is actually available. This false-success state most often occurs after multiple edit or regenerate cycles on the same stack. The preview page is blank because the underlying content did not finish building — the confirmation message is inaccurate. 🔍 How to Confirm This Is the Issue Look for all three of these signs before following the recovery steps: - The orchestrator or agent shows a "fully generated" or "ready for review" success message. - The Cloud Stack preview page loads completely blank — no sections, headings, or body content appear. - The blank preview occurred after at least one prior edit or regenerate cycle on the same stack. 🛠️ How to Recover a Blank Cloud Stack Preview Triggering a single fresh regeneration resolves the issue in most cases. 1. Go to Authority → Cloud Stacks. 2. Locate the affected stack in your project list. 3. Click Regenerate. Do not create a new stack — regenerating keeps all saved settings. 4. Stay on the page until generation fully completes. Do not navigate away or refresh mid-generation. 5. Open the Preview tab and confirm that sections and body content are visible before publishing or scheduling. The fix is successful when the Preview tab displays your stack's full content. ⚠️ What to Avoid During Recovery - Do not click Regenerate multiple times in quick succession — repeated triggers can reproduce the same false-success state. - Do not publish or schedule the stack until the Preview tab confirms visible content. - If the preview is still blank after regeneration completes, wait 2–3 minutes, refresh the page, then try once more. 🔑 When to Contact Support If the preview remains blank after two separate regeneration attempts, contact the Search Atlas support team. Include the following in your message: - The stack name and the project it belongs to. - A screenshot of the blank preview page. - A screenshot of the "fully generated" confirmation message from the orchestrator. The support team can inspect the stack's generation state and reset it directly. 🎯 You now know how to identify and recover from the Cloud Stack blank-preview bug — regenerate the affected stack and confirm visible content in the Preview tab before publishing. If two regeneration attempts fail, contact Search Atlas support with the details above.

Fix a Persistent Indeed Link in Cloud Stacks

🔍 What Is This Issue? Some users have reported that an Indeed URL — often linked to a company they do not own — keeps reappearing in their Cloud Stacks footers and Knowledge Graph even after they delete it. Because the stale value is retained at the database level, deleting it through the platform UI alone will not permanently remove it from previously created stacks. Resolving this issue requires escalation to a support engineer. ✅ Steps to Take Before Contacting Support 1. Check your Knowledge Graph settings: Navigate to your Knowledge Graph settings and look for any Indeed URL stored under your brand profile. If you see it, attempt to delete or clear it and save your changes. This ensures the UI-level value is removed, even though the underlying database-level value will still need to be cleared by an engineer. 2. Identify affected Cloud Stacks: Go to your Cloud Stacks section in the platform and review your existing stacks. Note which stacks are displaying the incorrect Indeed link in their footers. Record the names or IDs of these stacks so you can share them with the support team. 3. Confirm the Indeed URL is not intentional: Make sure the URL does not belong to a legitimate profile associated with your brand. If it is definitely not yours, proceed to contact support with that confirmation. 4. Gather key details to share with support: Before reaching out, have the following ready: the exact Indeed URL that keeps appearing and the names or IDs of the affected Cloud Stacks. 🧹 What the Support Engineer Will Do Once you contact support, a support engineer will review your account, identify the affected Cloud Stack records containing the stale Indeed URL, and manually remove the value at the database level. They will confirm once the removal is complete so you can verify the footers no longer display the incorrect link. To get this resolved, please contact the Search Atlas support team via live chat and share the details you gathered above. The support team will escalate to an engineer who can perform the database-level removal — this is the confirmed path to a permanent fix.

🛠️ Fix Cloud Stack Build Server Error 500

🔍 What This Article Covers Some customers have experienced Cloud Stack builds that fail with a Server Error 500 and remain stuck on the message 'Waiting for content generation to complete...'. This issue was caused by a platform-level bug that has since been resolved by our engineering team. This article explains what happened and what steps to take so your build completes successfully. ⚙️ What Caused the Error This error was traced to an internal platform issue affecting the Cloud Stack build process. The engineering team identified and resolved the bug, and the fix has been deployed across the platform. ✅ Steps to Resolve Because the underlying bug has been fixed, you do not need to change your build settings or recreate your project. Follow the steps below to successfully complete your Cloud Stack build: 1. Retry the build. Attempt to run the Cloud Stack build again. The error should no longer occur now that the platform fix is in place. 💡 Tips If the Build Still Fails - Make sure you are using the latest version of your browser and that no browser extensions are interfering with the platform. - Try a different browser entirely if the issue persists. - Wait a few minutes and attempt the build again, as occasional transient network issues can cause temporary failures. 🆘 Still Need Help? If your Cloud Stack build continues to fail after following the steps above, please gather the following details before reaching out so our team can investigate quickly: - Your domain or target keyword for the build - A screenshot or screen recording of the error If you need further assistance, please contact our support team so we can investigate further.

🖼️ Fix Image Padding Issues in Cloud Stacks

🔍 Overview Some customers noticed that padding around article images disappeared in their Cloud Stack projects, affecting the professional appearance of published content. This was caused by a CSS rendering defect in Cloud Stack templates — specifically in the Standard Authority and Agency templates — where image padding, alignment, and button display were not rendering correctly across different screen sizes. Search Atlas engineers have since resolved the underlying CSS issues through several targeted fixes, including corrections to image padding, content alignment, responsive layout behaviour across breakpoints, and the display of inline elements such as the Read more button. ✅ What Was Fixed - Missing or collapsed padding around images in Cloud Stack article templates - Broken image dimensions and missing padding in Agency template previews - Alignment issues with authority copy and local business layouts on smaller screens - Responsive layout defects affecting Cloud Stack base templates across different breakpoints - Excessive page scrolling caused by the Images section layout These fixes were deployed by the engineering team and apply automatically to your Cloud Stack projects — no manual action is required on your end to receive the updates. 🛠️ What To Do If You Still See Layout Issues If you are still experiencing image padding or layout problems in your Cloud Stack projects after the fixes were deployed, follow these steps: 1. Open your Cloud Stack projects in Search Atlas and navigate to the affected project. 2. Review how images and content are rendering in the current preview. 3. If the layout still appears broken — for example, images have no padding, content is misaligned, or the Read more button is missing — try refreshing the page and reviewing the template again, as cached versions of the page can sometimes display outdated rendering. 4. If the issue persists after refreshing, check whether the problem appears only in the preview or also in the published output, and note which template type you are using (for example, Standard Authority or Agency). 5. Gather a screenshot or brief description of what is broken, including the template name and the URL of the affected Cloud Stack, before contacting support. 💡 Tips for Maintaining a Professional Layout - Use the built-in template options available within Cloud Stacks rather than heavily customised templates, as standard templates receive ongoing compatibility updates. - After publishing or updating a Cloud Stack, check the live output on multiple screen sizes to confirm images and text are displaying correctly. - If you use a custom template, be aware that custom CSS may conflict with platform-level updates — review your cust

Fix Cloud Stack Showing Zero Deployed Providers

Overview Your Cloud Stack showing a deployed provider count of zero despite stacks being live requires the Search Atlas support team to investigate and resolve on your account. This article explains how to contact support effectively so your case can be resolved as quickly as possible. If you are unable to resolve an issue after following these steps, contact the Search Atlas support team via live chat in the dashboard. Issue 1: Cloud Stack Shows Zero Deployed Providers If your Cloud Stack report shows a deployed provider count of 0, this is a known display issue that the Search Atlas support team can correct on your account. There are no self-serve steps that reliably fix this — an agent must investigate your specific account configuration. To get this resolved as quickly as possible, contact the Search Atlas support team via live chat in the dashboard and provide the following information: - Your project name - Your Cloud Stack order number - A brief description that your deployed provider count is showing as zero The support team will review your account, correct the display count, and confirm when your Cloud Stack data is accurately reflected. Key Things to Remember - A zero provider count in Cloud Stack is a known display issue — it does not necessarily mean your stacks failed to deploy. - For both issues, contacting the Search Atlas support team via live chat in the dashboard with your order number is the fastest path to resolution.