1. Introduction
2. What you get
3. Requirements (non-negotiable)
4. Why we are so strict: Google and our reputation
5. How to submit your post
6. What happens after you submit

Introduction

Do you use cloudHQ and want to write about it? We are happy to thank you with about one year of the cloudHQ Premium plan for all cloudHQ apps, for personal use. This note explains exactly what we expect. Please read it before you write, not after we send the polite rejection.

What you get

If your post is approved, we apply about one year of the Premium plan for all cloudHQ apps to one cloudHQ account that you name. The Premium plan is for personal use. This applies once per person or company. It is a thank-you for a useful, honest post; it is not payment for praise.

Requirements (non-negotiable)

1. You are a real cloudHQ user. You have your own cloudHQ account and you really used the app you write about. We do not accept posts about features you only read about.
2. Written by you, not by AI. The text must be written by a human who actually used cloudHQ. AI tools may be used only to check spelling and grammar, and you must say so in the post. A post that was generated by AI is rejected.
3. Your real workflow, step by step. Explain the workflow you actually used. Tell us who you are, what you wanted to achieve and which cloudHQ app you used. Then describe every step in order: what you clicked, what you typed, what you saw on the screen and what the result was. Someone who reads your post should be able to repeat your steps. "cloudHQ is great" is not a workflow.
4. Screenshots from your own cloudHQ account. Show the important steps with screenshots taken in your own cloudHQ account. Pictures copied from our website or from this support site do not count. Give each image a short description (alt text).
5. At least 300 words of original content, with a clear title, headings and short paragraphs that are easy to read.
6. Unique content. The text must not be copied from anywhere, including our own articles, and must not be a duplicate of another page.
7. SEO basics. A page title and meta description, one main heading (H1), a target keyword used naturally (not stuffed), and links to the cloudHQ app you describe using the full address, for example https://www.cloudhq.net.
8. The name is written cloudHQ, with a lowercase "c" at the beginning. Not CloudHQ, not Cloudhq.
9. Published and indexable. The post is live on a public page that Google can find, on your own website or blog (an article on a large publishing platform is accepted if it is public and indexable). The site has been online for at least one year. Drafts that are not public cannot be approved.
10. The public link. You send us the public link of your blog post, which is the address of the page. Do not send the text or a file.
11. Honest. We do not ask for a positive review, we ask for a truthful one. Do not describe features that cloudHQ does not have.

If a post does not meet these requirements, it cannot be approved for the free year.

Why we are so strict: Google and our reputation

This is not bureaucracy for its own sake. A blog post that links to cloudHQ becomes part of how Google sees cloudHQ and your own website. If a post is thin, copied, generated by AI, stuffed with keywords or poorly structured, Google can lower the ranking of the page or penalize it. That hurts you, because your page loses visibility, and it hurts cloudHQ, because low-quality pages that mention us damage our reputation and our own search ranking. That is a technical and a reputational harm that we cannot accept, so we only approve posts that follow the basic SEO rules: unique content, appropriate use of the keyword, meta tags, readability, and no duplicate content.
Also, a small warning from experience: writing a good blog post is not a simple task. If it were easy, everyone would already have written one and we would not need this page. Please plan a few hours, not ten minutes.

How to submit your post

1. Publish your post.
2. Email the public link (the address of the page, not the pasted text) to support@cloudhq.net from the email address of your cloudHQ account, and tell us which cloudHQ account should receive the free year.
3. If you want feedback before you publish, you can send a link to a draft in Google Docs. We give feedback on the structure and on these requirements, but we can only approve a published post.

What happens after you submit

• We answer within 10 business days. If you have not heard from us after 10 business days, reply to your email.
• If something is missing, we tell you exactly what to change. You can fix the post and send the link again.
• If the post is approved, we apply about one year of the Premium plan to your account and confirm by email.
• The post must stay public for at least 12 months after approval. If it is removed or changed so that it no longer meets the requirements, we may end the free year.