How to report a rank inaccuracy

Report suspected SEO or AI ranking inaccuracies from the rankings table More menu, after verifying SERP screenshots and confirming the rank date window.

Prerequisites

  • Project with rankings data and support.ticket.create (or org owner)

When a tracked keyword’s position looks wrong for a recent check date, you can raise a rank inaccuracy report from the Rankings dashboard. The report becomes a Support ticket for the data / rankings team, with enough context for engineering to investigate.

Before you start

  • Use a dashboard date range whose end date is within the last 7 days. Older end dates cannot be submitted.
  • If the end date is more than 2 days old, you will see a warning: live SERPs may have moved since we stored the rank. You can still continue; the ticket is handled at normal priority (about 5 working days). Fresher dates are high priority (about 2 working days).
  • Prefer verifying the SERP snapshot when one exists. Snapshots may be missing for some older checks — that is OK.

Steps

  1. Open Projects → your project → Rankings (SEO) for the correct search context.
  2. Select one or more keywords with the row checkboxes.
  3. Open the table More menu → Report inaccuracy.
  4. Review the age warning if shown, then confirm the selected keywords and ranks.
  5. Confirm you checked SERP screenshots (or that no snapshot was available). If you need help:
    • Open Table Settings and enable the SERP column.
    • Click the SERP / snapshot icon on the keyword row to open the stored HTML.
  6. Say whether the issue is only for the selected keywords or a repeated pattern across keywords.
  7. Enter the expected rank for each keyword and a short description of what looks wrong.
  8. If the expected rank is within ±5 of the shown rank, confirm you still want to report — small differences can be normal SERP volatility.
  9. Submit. You are taken to the new Support ticket thread.

Outcome

Support receives a Data / rankings ticket. Agents see a private internal note with project, context, rank job IDs, and screenshot paths so engineering can debug without asking you to re-send IDs.

Related