This page explains how the content on orgo.space is made: who writes it, how facts are checked, how competitors are described, where AI tools are used, and what happens when something is wrong. It covers the blog, the guides, the alternatives and comparison pages, the feature pages and the trust documentation. Contracts and policies such as the Terms of Service and the Privacy Policy are legal documents and follow their own process.
Every page carries the name of the person responsible for it. Today most of the content is written by Orgo's three co-founders, whose profiles are on the About page:
Authorship will widen. Other members of the Orgo team sign pages as they take them on, and we may invite specialists from outside the company, such as a governance, membership or data-protection practitioner, to write or review a page in their field. Whoever signs a page is named with their role, an outside contributor is identified as one, and the same sourcing and review rules apply to everyone.
The trust and security documentation is reviewed quarterly and carries its own review date. Where it and a contractual document differ, the contract governs, and the page says so.
Nothing is published under a brand byline. A company cannot be asked whether it checked a number; a person can.
Every blog post starts with a research phase before a word is written. The target is at least ten statistics from primary sources: government bodies, academic and peer-reviewed work, and industry associations that publish their methodology and sample size. A statistic found in another blog post, with no original source behind it, is not used. Sources older than five years are replaced when a newer one exists.
Statistics are cited inline, with the source named and linked where it first appears. We do not use footnote numbers. Each source is linked once per article so the citation cannot be mistaken for link-building.
Guides are a different kind of document. A guide is written only for a question that has reached support more than once, and it is read end to end by someone who has used the feature before it is published. Each guide states what the platform does not do, not only what it does.
Alternatives and comparison pages are the content most likely to be doubted, so they follow the strictest rules on the site.
Claims about Orgo are limited to what the product does today, verified against the platform and its documentation. We do not publish invented performance figures, user counts or results. Orgo's own prices are drawn from one source and checked at build time, so a comparison page cannot quote a retired plan.
Where Orgo has a limitation, the page says so. The trust page states which certifications Orgo does not hold, and the alternatives pages state when another platform is the better choice. Honest scope is part of the product description, not a disclaimer.
We use AI assistants in research, drafting, editing and checking, and we say so. They search for sources, draft sections against our templates, check pages against the publishing checklists, and flag claims that cannot be traced. They do not decide what is true about Orgo or about a competitor.
Before a page goes live, the person whose name is on it reads it in full. Statistics are checked at the source, not in the draft. A guide must receive at least one correction from someone who has used the feature before it ships, which is a check an assistant cannot pass on its own.
The reverse also applies. Orgo's documentation is published for retrieval by AI systems and search engines, and the site's llms.txt gives them a verified summary of the company and the product. Our robots directives permit search and retrieval-time use and withhold training rights.
A page shows one date, "Last updated", and it means a substantive change: a new or changed fact, a
rewritten section, a changed comparison row. It is set by hand. Typo fixes, formatting changes and link
swaps do not move it, and nothing derives it from a file timestamp or a build. The same date feeds the
dateModified field in the page's structured data, so what a search engine reads matches what
a reader sees.
The original publication date of a blog post never changes, so an updated post is not presented as new.
A page's URL does not change once it is indexed. If a page has to move, the old address redirects to the new one.
If you find an error, write to contact@orgo.space with the page address and the claim in question. A confirmed factual error is corrected on the page, and the correction moves the "Last updated" date.
This page describes our editorial practice and is provided for information. It is not a contractual commitment and does not vary the Terms of Service, the Data Processing Agreement or the Privacy Policy. Security and compliance statements are governed by the trust page and the contractual documents it references.