Rank Tracker API and Pulling Rankings Into Your Own Stack
A rank tracker API is an interface that lets your own code request keyword rankings from a rank tracking service and receive them as structured data, usually JSON over HTTPS. Instead of logging into a dashboard and exporting CSV files, you pull positions, ranking URLs, SERP features and history straight into a spreadsheet, a BI dashboard, a data warehouse or an AI agent.
How a rank tracker API works
The API sits between the tracking engine and whatever you want to build. A tracking service checks Google for your keywords from set locations and devices on a schedule and stores the results. The API exposes that store through endpoints you can call with an API key.
There are two broad types, and they suit different teams:
| Type | What you send | What you get back | Who it suits |
|---|---|---|---|
| Rank tracker API | A project, keyword set or date range | Stored positions, history and changes for keywords that the service tracks on a schedule | Agencies and in-house teams that want reporting and alerts |
| Raw SERP API | One query, location, device and language | The parsed results page for that single search | Developers building their own tracker or research tool |
With a raw SERP API, scheduling, storage, history and deduplication are your job. Since Google stopped supporting 100 results per page in September 2025, checking the top 100 for one keyword takes ten requests instead of one, which made building your own tracker on raw results noticeably more expensive. A tracking service’s API hands you the finished time series.
What a keyword ranking API returns
Field names vary by service, but a typical keyword ranking API response for one keyword check looks like this illustrative example:

{"keyword": "payroll software", "location": "Chicago, Illinois, US", "device": "mobile", "language": "en", "checked_at": "2026-11-02T06:00:00Z", "position": 4, "absolute_position": 7, "previous_position": 6, "url": "https://example.com/payroll/", "serp_features": ["ai_overview", "people_also_ask", "video"], "in_ai_overview": true, "competitors": [{"domain": "competitor.com", "position": 2}]}
Each field answers a specific question:
| Field | Meaning | Why it matters |
|---|---|---|
keyword |
The tracked query | Join key for every report |
location, device, language |
The conditions of the check | A position is meaningless without them |
checked_at |
Timestamp of the check, ideally in UTC | Builds the time series and aligns with your events |
position |
Organic rank, counting only classic results | The headline number |
absolute_position |
Rank counting every element on the page | Shows how far down the screen you really are |
previous_position |
The last stored result | Lets you compute change without a second call |
url |
The page from your site that ranks | Flags cannibalization when it changes |
serp_features |
Features present on the page | Explains changes in absolute rank and click-through |
in_ai_overview |
Whether your site was cited in the AI Overview | Separates AI citation from organic rank |
competitors |
Positions of tracked rival domains | Share-of-search and gap reports |
Two details catch people out. First, check how the API represents a keyword that is not found in the checked depth: some return null, others return a number such as 101. A null is safer, because a placeholder number silently distorts averages. Second, confirm whether position means organic or absolute rank; the difference is explained in the guide to tracking keyword rankings accurately.
How it differs from the Search Console API
Google’s own Search Analytics API reference returns rows with keys, clicks, impressions, ctr and position, grouped by dimensions such as query, page, country and device, with up to 25,000 rows per request. That position is an average across real impressions, not a fixed-condition check, and it has no competitor data. Many teams pull both: Search Console for real demand and clicks, a google rank tracker API for controlled positions. The article on checking keyword rankings in Google explains why the two numbers differ.
Common use cases for a rank tracker API
Dashboards and BI tools
The most common use is a reporting dashboard that combines rankings with traffic and revenue. A nightly job calls the API, writes rows into a warehouse table keyed by keyword, location, device and date, and joins them with analytics data. Teams then chart position buckets (1 to 3, 4 to 10, 11 to 20) by keyword cluster rather than one blended average.
Looker Studio reports
Looker Studio reads outside data through connectors. Google’s connector documentation describes Community Connectors as connections from Looker Studio to any internet-accessible data source, built in Apps Script. A ready-made connector for your rank tracker skips the warehouse step: you pick the connector, authorize it, and drag fields such as keyword, position and date into charts next to Search Console and GA4 data.
Spreadsheets and alerts
Smaller teams often call the API from a spreadsheet script or an automation tool. A simple pattern is a daily check that posts to a chat channel when a money keyword drops more than three positions or when the ranking URL changes.
AI agents through an MCP server
The Model Context Protocol (MCP), introduced by Anthropic in November 2024 and since adopted by other major AI companies, is an open standard for connecting AI assistants to external tools and data. A rank tracking service with an MCP server lets an assistant such as Claude or ChatGPT query your ranking data directly. Instead of building a dashboard, you can ask “which keywords lost more than five positions on mobile this week, and which URLs rank for them?” and get an answer from live data.
Asheard, for example, offers a REST API, an MCP server and a Looker Studio connector for its Google rank tracking data, alongside its AI visibility metrics.
How to evaluate a google rank tracker API
| Question | Why it matters |
|---|---|
| Does it cover the locations and devices you need, down to city or postal code? | Local and mobile data are where rankings differ most |
| Does it return both organic and absolute positions? | You can switch reporting views without re-collecting data |
| Are SERP features and AI Overview citations included? | Explains ranking changes that look like losses |
| How much history can you query, and at what granularity? | Year-over-year comparisons need stored daily or weekly data |
| What are the rate limits and pagination rules? | Large keyword sets need predictable bulk export |
| How is authentication handled? | Per-project keys that can be revoked are safer for client work |
| Are timestamps in UTC and fields documented? | Prevents off-by-one-day errors in reports |
| Is there a Looker Studio connector or MCP server? | Avoids building and maintaining your own integration |
A simple pipeline you can build in an afternoon
- Define the keyword set. Tag each keyword with cluster, intent, target URL, location and device.
- Schedule the pull. Call the API once a day after the tracker’s daily check finishes.
- Store raw rows. Keep one row per keyword, location, device and date; never overwrite history.
- Add Search Console data. Pull query and page metrics for the same dates and join on keyword and URL.
- Build views. Position buckets by cluster, winners and losers, URL changes, and SERP feature presence.
- Set alerts. Notify on large drops, lost AI Overview citations and changed ranking URLs.
- Annotate events. Releases, migrations, Google updates and the September 2025 Search Console shift.
Rankings plus AI visibility in one dataset
Google rankings now explain only part of search visibility. A page can rank first and be absent from the AI Overview above it, or be cited in AI answers for prompts it does not rank for. If you are building a stack anyway, plan a second table for AI visibility metrics (mentions, citations, share of voice by engine) next to the ranking table, joined by topic or keyword cluster. The guide to AI visibility metrics that matter covers which fields to store.

Frequently asked questions
What is a rank tracker API?
It is an interface that lets your own software request keyword ranking data from a rank tracking service and receive it as structured data, usually JSON. You can pull positions, ranking URLs, SERP features and history into dashboards, spreadsheets, data warehouses or AI agents without exporting files by hand from the tool’s interface.
Is there a free Google rank tracker API?
Google does not offer an API that returns live rankings for any keyword. The free Search Console API returns average position, clicks and impressions for queries where your own site already earned impressions. For fixed-location checks, competitor positions and SERP features, you need a rank tracking service or a SERP data API, and most of those are paid.
What is the difference between a SERP API and a rank tracker API?
A SERP API returns the parsed results page for one search at a time, so you handle scheduling, storage and history yourself. The rank tracking kind returns stored ranking data for keywords that a service already checks on a schedule, including history and changes. Developers building tools tend to use SERP APIs; reporting teams prefer rank tracker APIs.
Can I connect rank tracking data to Looker Studio?
Yes. Looker Studio reads external data through connectors, so you can use a rank tracker’s own Looker Studio connector if it offers one, or load the API data into Google Sheets or BigQuery and connect that. A direct connector is simpler because it handles authentication and field mapping for you.
