🔍 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:
- 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.
- 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.
- 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.