> For the complete documentation index, see [llms.txt](https://docs.seoneo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seoneo.io/additional-information/glossary/cloud-staking.md).

# Cloud staking

Cloud Stacking SEO is a search engine optimization (SEO) technique that involves creating multiple cloud-based properties and interlinking them to boost the visibility of a target website in search engines.

SEO Neo offers the easiest, fastest and most versatile way to generate cloud-based properties within the software. You can create extremely complex and effective SEO campaigns by mixing cloud blogs with WEB 2.0 blogs and any other group type supported by SEO Neo.

{% hint style="info" %}
**Learn more**

* [Creating your own diagrams with diagram editor](/documentation/diagram-editor.md)
* [Link Group Types](/documentation/diagram-editor/link-group-types.md)
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.seoneo.io/additional-information/glossary/cloud-staking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.