🔍 Overview
If you are experiencing issues with PR Distribution or CloudStacks in Search Atlas, this guide walks you through the most common problems and how to resolve them quickly. Follow the steps below before reaching out to support.
⚙️ Common PR Distribution Issues and Fixes
PR Distribution allows you to publish and syndicate press releases across a network of sites. If something is not working as expected, try the following steps:
- Check your submission status. Navigate to your PR Distribution dashboard and confirm whether your press release shows a status of Pending, Processing, or Failed. A Pending status means it is queued and will process shortly.
- Review your content for compliance. Press releases that contain prohibited content, broken links, or formatting errors may be rejected. Re-read the content guidelines and ensure your release meets all requirements before resubmitting.
- Verify your account credits or plan limits. Press release distribution draws from your shared Hyperdrive Credits (HDC) balance — if that balance is exhausted, new submissions will be blocked. Go to the account menu (person icon, top-right) → Billing → Plans & Top-ups to check your current Hyperdrive Credits usage and balance.
- Clear your browser cache and retry. Occasionally, stale cache data can cause submission forms to behave unexpectedly. Clear your cache, refresh the page, and attempt your submission again.
- Check for platform status updates. If multiple submissions are failing at the same time, there may be a temporary service disruption. Check the Search Atlas status page or the in-app notification banner for updates.
☁️ Common CloudStacks Issues and Fixes
CloudStacks is a powerful link-building feature that creates a network of cloud-based properties pointing to your target URLs. Here are the most common issues and how to address them:
- Stack not building or stuck in progress. If your CloudStack has been stuck in the Building state for more than 24 hours, first check whether your target URL is accessible and returns a 200 status code. Broken or redirected URLs can stall the build process.
- Properties not indexed. Newly created cloud properties can take several days to be indexed by search engines. This is normal behaviour. Allow 5–10 business days before expecting indexation results.
- Incorrect target URL submitted. If you submitted the wrong URL for a CloudStack, contact support immediately. Depending on the build stage, the team may be able to update the target URL before the stack is fully deployed.
- Stack shows as complete but links are not visible. Confirm you are viewing the correct project in your dashboard. Use the filter or search function to locate the specific stack by name or date created. If the stack report appears blank, try refreshing the page or switching browsers.
- Duplicate stack submission. Submitting the same URL multiple times does not always improve results and may affect your link profile. Review your active stacks before creating a new one for the same target URL.
🔗 Issues Affecting Both PR Distribution and CloudStacks
If you are experiencing problems with both features at the same time, the issue is likely related to one of the following:
- Account or billing issue. A lapsed subscription or failed payment can restrict access to multiple features simultaneously. Go to the account menu (person icon, top-right) → Billing to verify your subscription status and update your payment method if needed.
- Browser or device compatibility. Both features require a modern browser. Ensure you are using the latest version of Chrome, Firefox, Edge, or Safari. Disable browser extensions that may interfere with the platform, such as ad blockers or script blockers.
- Session or login issue. Log out of your Search Atlas account, clear your cookies, and log back in. This resolves many unexpected UI or submission errors.
- API or integration conflict. If you are using the Search Atlas API or a third-party integration, verify that your API key is valid and that your requests are formatted correctly according to the latest API documentation.
📋 Before You Contact Support
To help our team resolve your issue as quickly as possible, gather the following information before starting a chat:
- The name or ID of the affected PR submission or CloudStack
- The target URL associated with the issue
- A description of what you expected to happen versus what actually happened
- Any error messages you saw on screen
- The date and time you first noticed the issue
💬 Still Need Help?
If the steps above did not resolve your issue, our support team is ready to assist. 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.