Editorial policy

This site publishes informational pages about AI visibility tracking. The goal is stable definitions, clear limits, and practical reading order grounded in how measurement pipelines actually work—capture, normalization, labeling, aggregation—rather than hype about replacing traditional SEO overnight.

Corrections

If you believe a statement is factually wrong, email the address on the contact page. We fix clear errors and note material changes in the changelog when it helps readers. Mechanical guidance (for example, “store append-only observations”) is intentionally conservative; if vendors ship better patterns, we update pages after verifying them against public docs or reproducible tests.

Independence of voice

Body copy does not promote a vendor. When you need software, use the primary action on pages that include one. Educational pages should read the same whether or not Rankscale existed, aside from legally required disclosure on the imprint.

How we treat product examples

Engine pages describe typical capture and citation behaviors at a high level. They do not claim insider knowledge of undisclosed ranking systems. When we discuss mechanics like variance, refusals, or tool-use flows, we describe classes of behavior practitioners observe across programs, not proprietary telemetry.

Conflict handling

If a page disagrees with a vendor blog, we prefer language that explains the measurement trade-off (“two runs may diverge because of sampling”) instead of picking winners. Readers should reconcile details with the vendor’s own specifications.

Operator

Responsible party and disclosure live on the imprint.

Style and neutrality

We prefer precise verbs (“store,” “parse,” “aggregate”) over vague superlatives (“revolutionary”). When two measurement approaches conflict, we describe trade-offs instead of declaring a winner. That editorial stance keeps the site useful when vendors ship overlapping features and marketing language diverges.

Contributions

This site is maintained by the operator, not an open wiki. External contributors cannot directly edit pages; send proposals via email with citations. Accepted suggestions are implemented by maintainers so HTML, accessibility, and internal link integrity stay consistent.

Retention of correspondence

Emails about corrections may be retained long enough to implement fixes and audit decisions. Do not include confidential third-party data unless you have a non-disclosure framework in place with Rankscale.

Link rot and external citations

When pages link to third-party documentation, we periodically verify that URLs still resolve. The web moves faster than print; if you spot a broken outbound link, tell us so we can point to archives or updated anchors without changing the underlying mechanical guidance.

Language

Primary language is English. Translations, if added later, will be labeled with revision dates because measurement vocabulary does not always map cleanly across locales.