What it is
The Google SERP Tracking API allows you to access your ranking data via API instead of the web interface.
You can:
Retrieve keyword rankings
Access historical ranking data
Pull movement metrics
Access keyword metrics (search volume, intent, CPC, etc.)
Retrieve Share of Voice data
Trigger keyword updates
This enables automation, dashboard integrations, internal tooling, and large-scale reporting.
Why it matters
The API is ideal if you:
Build custom dashboards
Manage large keyword sets
Operate at agency or enterprise scale
Integrate SEO data into BI systems
Automate reporting pipelines
Feed ranking data into client portals
Instead of manually exporting CSVs, the API allows you to build a fully automated SERP reporting stack.
What you can access
The Google SERP Tracking API provides access to:
Ranking data
Current rank
Best rank
Ranking URL
Ranking position changes
Movement metrics (1d, 7d, 30d, lifetime)
Last updated timestamp
Keyword metadata
Search volume
Search intent
SERP features
Competition
CPC
Search results count
Tags
Date added
Tracking location
Device (desktop, mobile, maps)
Historical data
Historical ranking positions
Movement over time
Visibility score
Estimated traffic
Share of Voice
SOV %
Competitor visibility
7-day trends
What is NOT available via API
The following are not available via the standard API:
Spyglass HTML snapshot data
β
How to get your API key
Log into Keyword.com
Go to Settings β Account
Copy your API Key
Keep your API key secure. It provides access to your account data.
API documentation
Full API documentation, including:
Endpoints
Authentication methods
Request/response structure
Examples
Rate limits
Field definitions
is available at:
Authentication
All API requests require:
Your API key
Proper request headers
Authentication details are provided inside the API documentation.
Updating keywords via API
You can:
Add keywords
Update keywords
Trigger keyword refreshes
Move keywords between projects
There is no strict limit on how many keywords can be updated in a single call, but:
Large updates are queued internally
Smaller batches (under 50) are recommended for efficiency
Rate limits
API requests are subject to rate limits.
For full details on:
Requests per hour
Request throttling
Best practices
Refer to the API documentation at docs.keyword.com.
Common use cases
1. Internal dashboards
Pull ranking + movement data into internal reporting systems.
2. Client portals
Display live ranking data inside your own SaaS or agency portal.
3. Automated reporting
Combine SERP tracking data with traffic and revenue metrics.
4. Data warehouse integration
Push ranking data into BI tools (BigQuery, Snowflake, etc.).
Best practices
Keep API calls efficient and batched
Store ranking snapshots for long-term analytics
Combine API ranking data with GSC + GA4 for full performance visibility
Use tags and groups to structure large API queries
