Setting up keyword tracking
Create a Track project with the right keyword, domain, platforms, locations, and scan settings.
Create a Track project with the right keyword, domain, platforms, locations, and scan settings.
Before starting, confirm the client domain and brand, the exact query, target market, and which search surfaces answer the business question. You need access to the client and enough organization credits for the displayed scan estimate. Tracking is a recurring measurement commitment, so avoid enabling platforms or locations you will not use.
Create a tracking project
Select a client and open Track.
Create a project or start from the available benchmark workflow.
Enter the keyword and confirm the domain and brand.
Select the platforms that matter for this query.
Add locations when local or location-biased results matter.
Review the per-scan credit estimate.
Run the first scan or enable the available recurring schedule.
The estimate should update from the configured platforms, keywords, locations, and Local Pack grid where applicable. Review it before the first scan and again after changing settings. A completed setup without a completed scan does not yet contain visibility evidence.
Choose platforms deliberately
Traditional, AI, local, and video platforms measure different kinds of visibility and have different costs. Location-aware AI platforms can multiply work across additional locations. Enable only the surfaces you intend to monitor.
Organize tracking
Use topic groups and bulk settings where available to keep related keywords consistent. Turning auto-tracking off stops new scheduled scans for that keyword; you can still run a manual scan.
Use one persisted keyword record for each intended query/client scope. If you import or create in bulk, verify row-level language and location settings before starting scans. Similar keyword text can legitimately exist in different projects or markets, but accidental duplicates waste credits and fragment history.
Track a running scan
After you start a scan, Rankability returns you to the keyword list and shows the run's state on the project's row. A scan in progress shows Processing, and the list refreshes on its own while any run is still working — you do not need to keep a report page open.
A run that does not finish shows Stuck or Failed, with the recorded reason available on the row. When the run can be retried, select Retry on that row; the project returns to Processing and stays in the list.
Read the first result
After a completed scan, review SPI and its category breakdown, then open the detailed traditional, AI answer, citation, local, or video results that apply to the project.
Common issues
The run cost is too high — Reduce unnecessary platforms, locations, or grid points before approval. See Supported tracking platforms.
No scan data appears — Check that a run completed and that the selected platform, date, and location match it.
A platform says not tracked — Enable it in the keyword settings and run a new scan; historical runs cannot contain a platform that was not selected.
The keyword already exists — Open the existing tracked keyword and preserve its history instead of creating a duplicate.
Scheduled scans stopped — Check auto-tracking, project state, credits, and any visible error before starting a manual replacement.
The result differs from a manual search — Location, device, personalization, time, and provider context can differ. Compare the persisted scan with matching settings.
Related articles
Last updated
Was this helpful?