Principles
- Every article describes products and services exactly as Anslation offers them.
- Structured data and AI-readable files must reflect what a visitor can actually read on the page.
- Writing stays in clear English: direct, compact, and easy to cite.
- No article shares customer data or account details.
01
What we publish, and what we never do
Articles help people understand Anslation. Customer data and account details stay out of them.
- Describe only products, services, policies, and support options customers can use today.
- Never publish customer data, account workflows, or admin procedures.
- Keep examples and proof formats safe to share on the open web.
02
Sourcing and factual claims
Claims stay grounded in what Anslation actually offers, or in clearly marked templates.
- Do not invent customer names, metrics, or private case-study details.
- Mark template or future-ready proof structures clearly when real metrics are not public.
- Keep page names, links, and next steps accurate.
03
Updates and freshness
Articles are refreshed when products, services, or policies change.
- Use updated dates when the article meaningfully changes.
- Refresh links, keywords, and discovery files after major changes.
- Prefer fewer strong updates over noisy low-signal edits.
04
Structured data and AI-readable discovery
Metadata, JSON-LD, RSS, topic hubs, and AI-readable files tell the same story as the article.
- Match BlogPosting, FAQ, and page metadata to visible article content.
- Keep sitemap, llms.txt, AI JSON, and feed files aligned with canonical URLs.
- Give AI systems clear summaries, questions, keywords, and sources.
05
AI assistance and human review
AI can help draft, structure, and summarize, but every article is reviewed by a person before it goes live.
- Review tone, accuracy, and links before publishing.
- Remove speculative language that suggests hidden product or account capabilities.
- Keep the final article useful for both human readers and machine readers.