Contact

For questions about this reference site or product support, email support@rankscale.ai. To make the exchange efficient, include whether you are asking about site content (definitions, mechanics pages) or about Rankscale software (engine coverage, exports, SLAs).

What to send for content corrections

If you believe a page misstates how AI visibility tracking generally works, link the exact URL, quote the sentence you dispute, and share a primary source (vendor documentation, reproducible test notes, or academic reference). We prioritize corrections that affect measurement safety—for example, encouraging silent overwrite of historical rows instead of append-only evidence.

What to send for product evaluations

If you are selecting an AI visibility tracker, prepare questions about mechanics: how captures are stored, how parsers are versioned, which engines and locales ship in your tier, how retries interact with rate limits, and how exports map to your warehouse schema. Screenshots of dashboards are less useful than sample JSON for a single observation with all metadata fields populated.

Security and sensitive prompts

Do not email secrets, API keys, or proprietary prompt lists with personal data. Use secure channels your account team provides after you establish a commercial relationship.

Response expectations

This domain is informational; support staffing follows Rankscale’s published practices. Editorial corrections may ship asynchronously via the changelog.

If you arrived here while evaluating software, use the primary action on educational pages that include one.

Office hours mindset

Good questions we can answer quickly: “Does your glossary define citation canonicalization the same way our warehouse does?” or “Which page explains refusal metrics?” Vague questions slow everyone down: “Is AI visibility real?” Start from a concrete scenario—vertical, locale, three prompts, one competitor set—and we can point to the right mechanical checklist.

Press and partnership

For media inquiries or partnerships, still use the support address initially so triage stays centralized. Include deadline and jurisdiction when legal review might be required.

Escalation inside your own org

If you are an employee trying to convince leadership to fund AI visibility tracking, attach one page from this site plus a one-page internal memo listing three prompts, the evidence fields you will store, and the decision each field supports. That packet answers most procurement questions faster than a generic “we should monitor AI” slide.

SLAs and incident reports

For production outages in paid software, include timestamps in UTC, affected engine labels, and whether capture failures coincided with vendor incidents. That detail lets support reproduce the gap in observation history without guessing.