Rank Tracker API

Intro

Rank tracking becomes a very different problem when you are managing hundreds of websites, thousands of keywords, or SEO reporting that needs to update automatically.

Logging into a dashboard and exporting data manually might work for smaller projects. At scale, it quickly becomes a bottleneck.

That is why we built the Ranktracker API.

The Ranktracker API is now live and gives developers, SEO teams, agencies, SaaS companies, and data teams programmatic access to their Ranktracker data.

You can use the API to:

• Retrieve Top 100 keyword rankings
• Access SERP data
• Detect AI Overviews and other SERP features
• Create and manage tracked domains
• Add and manage keywords
• Track competitors
• Access ranking history
• Calculate Share of Voice
• Organise keywords using tags
• Monitor account usage and quota
• Build automated SEO reporting pipelines
• Connect ranking data to internal applications and dashboards

Instead of manually moving SEO data between platforms, the Ranktracker API allows your own software to work directly with the ranking infrastructure behind Ranktracker.

Create or manage your API key: https://app.ranktracker.com/account/api

Read the API documentation: https://developers.ranktracker.com/

What Is the Ranktracker API?

The Ranktracker API is a REST API that provides programmatic access to your Ranktracker account.

Rather than opening Ranktracker every time you need ranking information, your application can request the data automatically.

The API is structured around the same core resources used throughout Ranktracker:

• Accounts
• Domains
• Keywords
• Competitors
• Ranking history
• SERP data
• Share of Voice
• Tags
• Usage and quota

This gives developers the ability to both retrieve Ranktracker data and manage what Ranktracker tracks.

For example, an SEO agency could automatically create a Ranktracker project when a new client enters its CRM, add the client's keywords and competitors, and then feed their rankings into an internal reporting dashboard.

A SaaS platform could use the same API to surface ranking data directly inside its own product.

A data team could automatically send daily rankings into BigQuery, Snowflake, PostgreSQL, Google Sheets, or another data warehouse for further analysis.

For an overview of how the resources fit together, see the Ranktracker API Core Concepts guide.

Top 100 Rankings by Default

One of the biggest advantages of the Ranktracker API is the depth of the ranking data.

Every keyword check includes the Top 100 Google results by default.

That means you can analyse all 10 pages of search results instead of only seeing what currently ranks on page one.

This matters because SEO progress usually begins long before a keyword reaches the Top 10.

A keyword might move:

Position 91 → Position 63 → Position 37 → Position 18 → Position 9

That represents significant SEO progress.

If your ranking data stops at the first 10 results, almost the entire journey is invisible.

Top 100 tracking allows you to monitor:

• New rankings entering Google's Top 100
• Keywords moving towards page one
• Large ranking gains and losses
• Competitor movement
• Long-tail search visibility
• New content performance
• Programmatic SEO campaigns
• Large keyword portfolios

This makes the API useful for both high-level SEO reporting and detailed ranking analysis.

Learn more about the API:

https://developers.ranktracker.com/

Track Rankings Across 107,000+ Locations

Search results vary significantly depending on where a search is performed.

Ranktracker supports 107,000+ locations, giving teams the ability to track local, national, and international search visibility through the API.

Keyword tracking can be configured around factors including:

• Search engine
• Location
• Language
• Device

For example, the same keyword could be monitored separately for:

• United States — desktop
• United States — mobile
• United Kingdom — desktop
• Germany — mobile
• Poland — desktop

Each configuration can be treated as a separate tracked keyword.

This is particularly useful for:

• International SEO
• Multi-location businesses
• Local SEO agencies
• Ecommerce businesses
• Publishers operating across different markets
• SaaS companies targeting multiple countries
• Enterprise SEO teams

Rather than treating a keyword as having one universal ranking position, you can analyse how visibility changes across different markets and devices.

Desktop and Mobile Rank Tracking

Desktop and mobile search results can differ.

Ranktracker therefore allows keyword tracking to be segmented by device.

This means an integration can separately analyse:

• Desktop rankings
• Mobile rankings

For example, a page may rank highly on desktop but perform differently on mobile due to differences in SERP layout, local results, or other search features.

Keeping these datasets separate gives SEO teams a much clearer picture of how users actually encounter their websites in search.

The API also allows device segmentation when working with features such as Share of Voice.

SERP Features and AI Overview Detection

Modern Google results contain much more than traditional organic listings.

SERPs can include:

• AI Overviews
• Featured snippets
• Maps
• Local results
• Videos
• Shopping results
• People Also Ask
• Other search features

The Ranktracker API includes SERP feature information and AI Overview detection alongside keyword data.

That means your integration can analyse not only where a website ranks, but also what surrounds that ranking in Google.

For example, you could identify:

• Keywords that trigger an AI Overview
• SERPs containing featured snippets
• Search queries dominated by video results
• Keywords producing local or map results
• Changes in SERP composition over time

This is increasingly important because organic position alone does not always tell the whole story.

A page ranking third on a traditional SERP and a page ranking third underneath an AI Overview, map pack, videos, and People Also Ask can receive very different levels of visibility.

The API allows those differences to become part of your SEO analysis.

See the full API documentation:

https://developers.ranktracker.com/

Access Complete SERP Data

Ranktracker can provide much more than a single ranking number.

For tracked keywords, the API can expose the latest search results together with associated SERP information.

The API resource structure includes:

• Latest SERP data
• Ranking information
• SERP features
• Cached SERP HTML

This means developers can build workflows around the actual search results rather than simply storing something like:

Position: 12

For advanced SEO teams, this provides much more flexibility.

You could use SERP information to:

• Analyse competing URLs
• Investigate unexpected ranking changes
• Identify changes to result layouts
• Build internal SERP analysis tools
• Store historical SERP information
• Feed search-result information into other models or analytics systems

The complete endpoint reference can be found here:

https://developers.ranktracker.com/rest-api/

Manage Domains Through the API

Domains are one of the core Ranktracker API resources.

The REST API allows you to:

• Create domains
• Retrieve domains
• Update domains
• Delete domains

A domain represents a site being tracked inside Ranktracker.

Each domain can then contain its own:

• Keywords
• Competitors
• Ranking history
• Share of Voice data

This makes automated onboarding possible.

For example, an agency could create the following workflow:

New client signs up
        ↓
Create Ranktracker domain
        ↓
Add client keywords
        ↓
Add competitors
        ↓
Begin rank tracking
        ↓
Send data to reporting dashboard

There is no need for a team member to manually configure every new project.

A complete walkthrough is available in the Add a Domain and Track Keywords tutorial.

Add and Manage Keywords Programmatically

Once a domain exists, keywords can be managed through the API.

You can use the API to add tracked keywords while specifying the search configuration associated with them.

Tracked keyword data can include factors such as:

• Word
• Search engine
• Location
• Language
• Device
• Ranking results

You can also manage the tracking lifecycle of existing keywords.

This includes the ability to:

• Retrieve keywords
• Read their ranking information
• Pause tracking
• Resume tracking
• Stop tracking
• Access SERP information
• Assign tags

This makes it possible for your own application to control which keywords Ranktracker monitors.

Bulk Keyword Tracking

Large SEO accounts should not need to make one API request for every keyword.

Ranktracker supports bulk keyword operations.

The keyword creation endpoint accepts a words × search engines configuration, allowing many tracked keyword combinations to be created in one request.

For example, imagine you want to track:

• 100 keywords
• US desktop
• US mobile

Those configurations can produce 200 tracked keyword combinations without requiring 200 individual setup requests.

Bulk operations are particularly useful for:

• Agencies
• Enterprise SEO
• Large ecommerce stores
• Programmatic SEO
• SaaS SEO platforms
• Large content publishers

Ranktracker also supports bulk keyword tagging.

Read the complete bulk operations guide:

https://developers.ranktracker.com/guides/bulk-operations/

Track SEO Competitors

Rankings become much more useful when they include competitive context.

The Ranktracker API allows competitors to be managed against tracked domains.

This makes it possible to automatically analyse your search performance alongside competing websites.

You could use competitor data to monitor:

• Which competitors are gaining visibility
• Which sites are overtaking your domain
• Changes across shared keyword groups
• Competitive ranking trends
• Relative search visibility
• Share of Voice changes

For agencies, this can become part of an automated client reporting system.

Instead of manually comparing a client with competitors every month, the relevant data can be integrated directly into the reporting pipeline.

Access Historical Ranking Data

Current rankings only show what is happening now.

Historical ranking data shows the direction in which SEO performance is moving.

Ranktracker provides domain ranking history through the API, allowing developers to analyse visibility over time.

Historical data can help identify:

• Ranking gains
• Ranking losses
• Visibility trends
• Keyword movement
• Changes after SEO campaigns
• Google update impact
• Long-term campaign performance

You can also use ranking history to create custom charts and dashboards.

For example:

Ranktracker API
       ↓
Daily ranking extraction
       ↓
Data warehouse
       ↓
Historical SEO dataset
       ↓
Dashboard / Alerts / Analysis

Ranktracker provides a dedicated tutorial showing how to pull daily rankings into a data warehouse:

https://developers.ranktracker.com/guides/tutorials/pull-rankings-to-a-warehouse/

Send Ranktracker Data to a Data Warehouse

One of the most useful API workflows is automatically storing Ranktracker data in your own database or warehouse.

For example, ranking data could be sent into:

• BigQuery
• Snowflake
• PostgreSQL
• MySQL
• Google Sheets
• Internal analytics databases

That information can then be combined with other business data.

For example:

Ranktracker
     ↓
Ranktracker API
     ↓
Data Warehouse
     ↓
Google Search Console
Analytics
Conversions
Revenue
CRM Data
     ↓
Business Intelligence Dashboard

This creates a much richer picture of SEO performance.

Instead of simply knowing that a keyword moved from position 8 to position 3, you could analyse whether the change also resulted in:

• More organic clicks
• More leads
• Higher conversion rates
• Increased revenue

The Rankings to Warehouse tutorial provides an example of building this type of pipeline.

Build Share of Voice Reports

The Ranktracker API also exposes Share of Voice data.

Share of Voice provides a broader measurement of how visible a domain is across a tracked keyword set.

Instead of asking:

Where do we rank for this keyword?

you can ask:

How visible are we across this entire search market?

This becomes especially powerful when competitor data is included.

The Share of Voice API can be used to analyse:

• Your overall visibility
• Competitor visibility
• Visibility changes over time
• Relative market position
• Desktop visibility
• Mobile visibility

The endpoint supports date ranges and device segmentation, allowing Share of Voice to be incorporated into custom SEO reports.

A complete implementation example is available here:

https://developers.ranktracker.com/guides/tutorials/share-of-voice-report/

Organise Keywords With Tags

Large keyword portfolios become difficult to manage without organisation.

Ranktracker provides account-level tags that can be attached to tracked keywords.

You could create tags for:

• Product categories
• Search intent
• Locations
• Content types
• Campaigns
• Clients
• Funnel stages
• Business units
• SEO teams

For example:

"buy running shoes" → Commercial
"best running shoes" → Comparison
"how to clean running shoes" → Informational

The same tags can be reused across different domains and keyword groups.

Ranktracker also provides bulk tagging so large groups of keywords can be organised without requiring individual requests.

A dedicated tutorial is available here:

https://developers.ranktracker.com/guides/tutorials/bulk-tag-keywords/

Monitor Account Usage and Quota

Automated systems also need to understand the account resources available to them.

The Ranktracker API provides:

GET /v1/account/usage

This endpoint reports account usage and limits.

Current usage information can include:

• API access status
• Keywords
• Data rows
• On-demand usage
• SERP Analyser usage

Each quota can provide values such as:

• Usage
• Limit
• Remaining

This allows an application to check available capacity before starting a large operation.

For example, before importing thousands of keywords, your system can query account usage and determine how much capacity remains.

Read the complete guide:

https://developers.ranktracker.com/guides/usage-and-quota/

How Ranktracker API Authentication Works

Ranktracker REST API requests are authenticated using an API key.

You can create and manage your keys directly inside Ranktracker:

https://app.ranktracker.com/account/api

Your API key should always be treated like a password.

The production API base URL is:

https://api.ranktracker.com

API resources sit underneath the /v1 path.

For example:

https://api.ranktracker.com/v1/domains

The API key is sent directly in the Authorization header.

There is no Bearer prefix for standard REST API requests.

Example:

curl https://api.ranktracker.com/v1/domains 
  -H "Authorization: tkn_usr_your_api_key_here"

A Ranktracker API key should be kept server-side and should never be exposed through:

• Browser JavaScript
• Front-end source code
• Public repositories
• Mobile application code
• Public configuration files

For more information, read:

Quickstart: https://developers.ranktracker.com/guides/quickstart/

Authentication: https://developers.ranktracker.com/guides/authentication/

Create/manage API keys: https://app.ranktracker.com/account/api

API Resource Structure

Ranktracker uses UUIDs to identify resources.

That includes resources such as:

• Domains
• Keywords
• Competitors
• Tags

A simplified representation looks like this:

Account
│
├── Usage
├── Tags
│
└── Domains
    │
    ├── Ranking history
    ├── Share of Voice
    ├── Competitors
    │
    └── Keywords
        │
        ├── SERP
        ├── Cached SERP HTML
        └── Tags

This makes the API structure predictable.

A domain has keywords and competitors.

A keyword belongs to a tracked domain and has associated SERP and ranking information.

Tags exist at account level and can be attached to keywords.

Read more:

https://developers.ranktracker.com/guides/concepts/

JSON API Responses

Ranktracker responses use a consistent JSON:API-style envelope.

The resource is returned under data, while its fields are stored under attributes.

For example:

{
  "data": {
    "id": "DOMAIN_UUID",
    "type": "domain",
    "attributes": {
      "host": "www.example.com",
      "projectName": "Example",
      "matchType": "any"
    }
  }
}

Developers should also be aware of an important naming convention:

• API responses use camelCase
• Write request bodies use snake_case

For example, a response might include:

projectName

while a write request uses:

project_name

This convention applies throughout the API.

See:

https://developers.ranktracker.com/guides/concepts/

Pagination

List endpoints are paginated so applications can work efficiently with large Ranktracker accounts.

Pagination applies to resources including:

• Domains
• Keywords
• Competitors
• Tags

The two main parameters are:

• page
• per_page

per_page supports up to 1,000 records per page.

Pagination information is returned through response headers including:

• X-Total-Count
• X-Total-Pages
• X-Per-Page
• X-Current-Page

For large exports, applications can therefore continue requesting pages until the complete dataset has been retrieved.

Read the pagination guide:

https://developers.ranktracker.com/guides/pagination/

Error Handling and Rate Limits

The Ranktracker API uses standard HTTP status codes to make failures easier to handle programmatically.

Common responses include:

Status	Meaning	Example
400	Bad request	A required parameter is missing or malformed
402	Quota exceeded	The requested operation would exceed an account allowance
403	Forbidden	The request is not authorised or API access is unavailable
404	Not found	The resource does not exist within the account
422	Validation error	The request is valid JSON but contains invalid data
429	Too many requests	The integration has been rate-limited

When a 429 response occurs, integrations should respect the returned Retry-After information before trying again.

This allows production applications to handle temporary throttling without simply failing.

The complete error and rate-limit documentation is available here:

https://developers.ranktracker.com/guides/errors-and-rate-limits/

Ranktracker REST API vs MCP

The REST API is not the only way to connect external software to Ranktracker.

Ranktracker also provides a hosted MCP Server.

MCP stands for Model Context Protocol and allows compatible AI applications and agents to work directly with Ranktracker data.

This includes compatible clients such as:

• ChatGPT
• Claude
• Cursor
• Other MCP-compatible AI applications

REST and MCP interact with the same underlying Ranktracker data, but they are designed for different workflows.

	Ranktracker REST API	Ranktracker MCP
Best for	Applications, dashboards, warehouses and scheduled jobs	AI assistants and agents
Caller	Your backend or HTTP client	ChatGPT, Claude, Cursor or another MCP client
Interface	REST endpoints	MCP tools
REST path	/v1/...	/mcp
Typical use	Moving and managing SEO data automatically	Exploring SEO data conversationally

For example, REST is a better choice if you want to:

• Export rankings every night
• Update a BI dashboard
• Automatically create SEO projects
• Add keywords from your application
• Synchronise ranking data with a database

MCP is better suited to questions such as:

Which of my tracked keywords dropped the most this week?

or:

Which competitors have gained the most visibility?

An AI client can select the appropriate Ranktracker tool and query the relevant data.

Many advanced SEO teams can use both.

REST handles infrastructure and automation. MCP makes Ranktracker data available to AI agents.

Learn more:

MCP overview: https://developers.ranktracker.com/mcp/

Connect an MCP client: https://developers.ranktracker.com/mcp/connect/

MCP tool reference: https://developers.ranktracker.com/mcp/tools/

What Can You Build With the Ranktracker API?

The Ranktracker API can be used for much more than displaying a keyword position.

Here are some of the most useful applications.

Automated SEO Reporting

An agency can automatically pull ranking information into its own reporting platform.

Instead of:

Open Ranktracker
↓
Export CSV
↓
Edit spreadsheet
↓
Upload report
↓
Send to client

you can build:

Ranktracker API
↓
Reporting platform
↓
Automatically updated client report

This is particularly valuable for agencies managing large numbers of clients.

Custom SEO Dashboards

Your company may already use an internal reporting or business intelligence platform.

The API allows Ranktracker data to become another data source inside that environment.

You could build dashboards displaying:

• Keyword rankings
• Ranking changes
• Top 3 keywords
• Top 10 keywords
• Top 100 keywords
• Share of Voice
• Competitor visibility
• SERP features
• AI Overview appearances

The resulting dashboard can be tailored specifically to your company's reporting needs.

Automated Client Onboarding

SEO agencies can connect Ranktracker to their client onboarding process.

For example:

Customer buys SEO package
↓
CRM creates client
↓
Ranktracker API creates domain
↓
Keywords are added
↓
Competitors are added
↓
Tracking begins

This removes repetitive manual project setup.

SEO Data Warehouses

Rankings become more valuable when they are connected with other marketing and business data.

Ranktracker information can be combined with:

• Google Search Console
• Analytics
• CRM data
• Conversion data
• Ecommerce revenue
• Lead data
• Content performance

This can help answer much more important questions than simply checking a ranking.

For example:

Which ranking improvements generated the most revenue?

or:

Which keyword groups are increasing visibility but not generating conversions?

Ranking Alerts

Historical ranking data can also power custom alerting systems.

An integration could automatically detect when:

• A keyword drops out of the Top 3
• A page enters the Top 10
• A keyword enters the Top 100
• A major keyword disappears from the Top 100
• A competitor overtakes your website
• Search visibility drops sharply

Alerts could then be sent into your own email, Slack, internal dashboard, or monitoring system.

Competitive Intelligence

Combining:

• Rankings
• Competitor tracking
• Ranking history
• Share of Voice

creates the foundation for an automated competitive SEO monitoring system.

Instead of evaluating competitors once every few months, their search visibility can become a continuously monitored metric.

Programmatic SEO Monitoring

Programmatic SEO can produce thousands or hundreds of thousands of landing pages.

Monitoring those projects manually is unrealistic.

The Ranktracker API allows developers to build ranking workflows capable of handling large keyword datasets and automatically pushing the resulting information into internal analytics systems.

AI-Powered SEO Analysis

Ranktracker's REST API and MCP Server can also become part of AI-driven SEO workflows.

For example, AI systems could help:

• Identify ranking losses
• Summarise ranking changes
• Find rapidly improving keywords
• Compare competitor visibility
• Analyse SERP changes
• Prioritise SEO opportunities
• Generate internal reports
• Investigate unusual ranking movements

The API provides the structured data, while AI can help interpret it.

Who Is the Ranktracker API For?

The Ranktracker API is particularly useful for:

• SEO agencies
• Enterprise SEO teams
• SaaS businesses
• SEO software companies
• Developers
• Data engineers
• BI teams
• Ecommerce businesses
• Affiliate marketers
• Publishers
• Multi-location businesses
• Programmatic SEO teams
• AI automation teams

If ranking data needs to be retrieved, moved, analysed, or managed automatically, an API is usually a much more scalable solution than manual exports.

Why Use Ranktracker Instead of Building Your Own Rank Tracking Infrastructure?

Collecting search rankings at scale involves much more than making a Google search.

A production rank-tracking system needs to account for:

• Locations
• Languages
• Devices
• Top 100 result collection
• SERP features
• AI Overviews
• Keyword configuration
• Historical ranking data
• Competitors
• Scheduling
• Search-result changes
• Data storage
• Reporting

Building and maintaining all of that infrastructure internally can take significant development resources.

Ranktracker handles the rank-tracking infrastructure and exposes the resulting data through a structured API.

Your developers can therefore focus on building the application, dashboard, workflow, or analysis your business actually needs.

How to Get Started With the Ranktracker API

Getting started only requires a few steps.

1. Open Your API Settings

Go directly to:

https://app.ranktracker.com/account/api

Create an API key and store it securely.

2. Read the Quickstart

Follow the official quickstart:

https://developers.ranktracker.com/guides/quickstart/

3. Make Your First Request

For example:

curl https://api.ranktracker.com/v1/domains 
  -H "Authorization: tkn_usr_your_api_key_here"

4. Explore the API Reference

The complete REST API reference is available here:

https://developers.ranktracker.com/rest-api/

5. Start Building

From there you can begin connecting Ranktracker to:

• Your application
• Your reporting stack
• Your data warehouse
• Your CRM
• Your internal tools
• Your AI workflows

Ranktracker API Documentation

The complete developer documentation can be found at:

Developer documentation: https://developers.ranktracker.com/

Create and manage API keys: https://app.ranktracker.com/account/api

Quickstart: https://developers.ranktracker.com/guides/quickstart/

Authentication: https://developers.ranktracker.com/guides/authentication/

Core concepts: https://developers.ranktracker.com/guides/concepts/

Pagination: https://developers.ranktracker.com/guides/pagination/

Errors and rate limits: https://developers.ranktracker.com/guides/errors-and-rate-limits/

Usage and quota: https://developers.ranktracker.com/guides/usage-and-quota/

Bulk operations: https://developers.ranktracker.com/guides/bulk-operations/

Track a domain tutorial: https://developers.ranktracker.com/guides/tutorials/track-a-domain/

Rankings to warehouse tutorial: https://developers.ranktracker.com/guides/tutorials/pull-rankings-to-a-warehouse/

Share of Voice tutorial: https://developers.ranktracker.com/guides/tutorials/share-of-voice-report/

Bulk tagging tutorial: https://developers.ranktracker.com/guides/tutorials/bulk-tag-keywords/

REST API reference: https://developers.ranktracker.com/rest-api/

MCP Server: https://developers.ranktracker.com/mcp/

Connect an MCP client: https://developers.ranktracker.com/mcp/connect/

MCP tool reference: https://developers.ranktracker.com/mcp/tools/

Start Building With the Ranktracker API

The Ranktracker API turns Ranktracker from an SEO dashboard into infrastructure that can sit directly inside your technology stack.

You can use it to manage domains and keywords, track competitors, retrieve Top 100 rankings, analyse SERPs, detect AI Overviews, monitor Share of Voice, access historical ranking data, organise keywords, build reporting pipelines, and integrate SEO information with the rest of your business.

For developers, it removes the need to manually export and move ranking data.

For agencies, it makes large-scale client automation possible.

For enterprise SEO teams, it allows ranking information to become part of internal analytics and data infrastructure.

And with Ranktracker's MCP Server, the same underlying SEO data can also be made accessible to AI assistants and agents.

Create your Ranktracker API key: https://app.ranktracker.com/account/api

Read the documentation: https://developers.ranktracker.com/

View the REST API reference: https://developers.ranktracker.com/rest-api/