🔍 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:
- Submit URLs to the URL Indexer: Use the URL Indexer tool inside Search Atlas to submit your cloud stack URLs and prompt faster crawling.
- 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.
- 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.
- 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.
- 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.