Editorial standards
SitemapKit editorial policy
These standards apply to guides, glossary definitions, integrations, comparisons, use cases, and data-driven directory pages.
Serve the reader's task
A guide must help complete a sitemap or technical SEO workflow. We do not publish pages whose only difference is a substituted keyword, platform name, or domain.
Prefer primary evidence
Protocol claims link to standards, search engine documentation, product documentation, or reproducible test output. Secondary sources are used only when they add necessary context.
Separate facts from product positioning
Examples can demonstrate SitemapKit, but product calls to action do not change the technical conclusion. Comparisons describe methodology, verification dates, and limitations.
Use automation transparently
Automation can assist data collection, drafting, formatting, and validation. Published technical claims must remain traceable to code behavior, observed output, or a cited source, and automated pages must provide page-specific value.
Show freshness honestly
Pages show publication or update dates when those dates represent a substantive editorial or data change. A deployment alone does not reset content freshness.
Correct material errors
When a technical statement, example, or data interpretation is shown to be wrong, we correct it. Substantive changes update the page’s modification date; its original publication date stays unchanged.
Ownership
Clément Chaal is responsible for maintaining SitemapKit’s technical content and handling corrections. Guides identify this maintenance responsibility and link their primary references. The update notes record substantive guide changes. Author credits remain distinct from maintenance, and no independent reviewer is assigned to this guide update.