A reason for every page
A page should answer a distinct question or support a real decision. We group related searches by intent rather than creating a near-identical page for every phrase. Useful content takes precedence over publishing volume.
The Ciny editorial policy keeps every page useful, specific and open to scrutiny.
These are the standards we use to guide Ciny's content. They apply to the substance of the work, not just how human a sentence sounds.
Facts before phrasing
Material claims need an identifiable source and appropriate context. Figures must retain their units, periods, baselines and limitations. When evidence is missing, the claim should be removed, qualified or held for verification.
AI assistance and human responsibility
AI can help organise research, develop outlines and draft content. People remain responsible for factual checks, editorial decisions and approval. Simulated audience feedback is not a substitute for research with real customers.
Honest product availability
Live, Available, In build and Planned describe different operating states. Live means a capability has run for a client with a dated result. Available means built and tested, with the first live run at onboarding. In build names what works and what is missing. Planned means it is on the roadmap. A planned integration or workflow must not be presented as a live feature. Account-specific setup and approval requirements should be explained near the capability.
Evidence with its limits
Work on our own system is identified as first-party evidence. Externally reported customer results remain attributed to their publisher. Observed outcomes are not a guarantee, and a correlation does not establish what caused a change.
Structure that helps the reader
Use clear headings, useful links and readable HTML. Structured data must match visible content and the actual page type. Neither markup nor an automated content score certifies Google compliance or guarantees a ranking or AI citation.
Sources and meaningful updates
Use primary sources where possible for technical claims. Distinguish official search guidance from industry observations and internal preferences. A material change merits review. A routine build is not a new publication date.
Corrections
Found a factual problem or an unclear claim? Send the page URL, the passage and the supporting source to hello@ciny.ai. A correction request should be reviewed against the original evidence before the wording is changed.
Reference guidance: Google on generative AI content and Google Search spam policies. These sources are not endorsements of Ciny.
See the standard
applied to real work.
Each case study keeps its evidence label, source and limits visible beside the result.