Bulk Keyword Rank Checker: Check Hundreds of Rankings Without a Per-Keyword Bill
A bulk keyword rank checker can mean two different things: reading positions Google already measured, or scraping results for a keyword list. Here is when to use each.

On this page
- Two kinds of bulk rank checker
- Method 1: pull every ranking from the Search Console API
- Reading the numbers
- Method 2: a SERP-scraping bulk checker for the keywords Search Console cannot see
- What to compare when choosing a bulk rank checker
- Method 3: skip the list and let the data build it
- Where SEOAgent fits
- Which approach to pick
- FAQ
- How do I check multiple keyword rankings at once for free?
- Why does my keyword show no position in Search Console?
- Why do a bulk checker and Search Console disagree?
- What is the difference between a bulk keyword rank checker and a rank tracker?
- How many keywords can I check in bulk?
- References
TL;DR — "Bulk keyword rank checker" covers two different jobs. If you want positions for queries your site already appears for, pull them from the Google Search Console API: one request returns up to 25,000 query and page rows, with no per-keyword fee. If you need a position for a keyword Google has never shown your site for, or for a specific city or device, you need a SERP-scraping rank checker. Most sites need the first one daily and the second one rarely.
A common starting point: you have a spreadsheet of 300 target keywords and want to know where each one ranks today. Pasting them into a web form one at a time does not scale, and many bulk checkers charge by tracked keyword. The right approach depends on which keywords are on the list.
The same job goes by several names: bulk rank checker, multiple keyword rank checker, multi keyword position checker, bulk rank tracker, bulk keyword ranking checker. A "checker" is usually a one-off lookup of a list, and a "tracker" is the same lookup repeated on a schedule so you can see movement. Everything below applies to both. The only difference is whether you keep the snapshots.
Two kinds of bulk rank checker
| Search Console data | SERP-scraping checker | |
|---|---|---|
| Where positions come from | Google's own measurement of your real impressions | A query run against Google from a chosen location and device |
| Which keywords it covers | Every query Google has shown your site for | Only the list you enter |
| Keyword you do not rank for yet | No row at all | Shows "not in top 100" |
| Position meaning | Impression-weighted average over the date range | One reading at one moment |
| Location and device | Filterable by country and device, not by city | Whatever you configure |
| Cost shape | Free API | Usually metered per keyword or per check |
Neither is "more accurate" in the abstract. They answer different questions. Search Console tells you how you are doing across the searches that actually happened. A scraper tells you what one searcher in one place would have seen for a keyword you picked.
Method 1: pull every ranking from the Search Console API
The Search Console Search Analytics API returns clicks, impressions, CTR and average position grouped by dimensions you choose. A request grouped by query and page looks like this:
{
"startDate": "2026-09-27",
"endDate": "2026-10-24",
"dimensions": ["query", "page"],
"rowLimit": 25000,
"startRow": 0
}
Each row has keys (the query and the URL), clicks, impressions, ctr and position. rowLimit tops out at 25,000 per request, so page through with startRow until a response comes back short. The Search Console web UI, by comparison, only exports up to 1,000 rows, which is the usual reason people reach for the API.
A minimal script that pages through the API and writes rows.json, using an OAuth access token with the webmasters.readonly scope in GSC_TOKEN and your property in GSC_SITE (for example sc-domain:example.com):
import { writeFileSync } from 'node:fs';
const site = encodeURIComponent(process.env.GSC_SITE!);
const url = `https://www.googleapis.com/webmasters/v3/sites/${site}/searchAnalytics/query`;
const rows: unknown[] = [];
for (let startRow = 0; ; startRow += 25000) {
const res = await fetch(url, {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.GSC_TOKEN}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
startDate: '2026-09-27',
endDate: '2026-10-24',
dimensions: ['query', 'page'],
rowLimit: 25000,
startRow,
}),
});
if (!res.ok) throw new Error(`Search Console API ${res.status}: ${await res.text()}`);
const page = (await res.json()).rows ?? [];
rows.push(...page);
if (page.length < 25000) break;
}
writeFileSync('rows.json', JSON.stringify({ rows }));
To check a specific list, save the keywords one per line in keywords.txt, save the API response as rows.json, and filter:
import { readFileSync } from 'node:fs';
const wanted = new Set(
readFileSync('keywords.txt', 'utf8').split('\n').map((k) => k.trim().toLowerCase()).filter(Boolean)
);
const { rows } = JSON.parse(readFileSync('rows.json', 'utf8'));
const hits = rows.filter((r: { keys: string[] }) => wanted.has(r.keys[0].toLowerCase()));
for (const r of hits.sort((a: any, b: any) => a.position - b.position)) {
console.log(r.position.toFixed(1), r.impressions, r.keys[0], r.keys[1]);
}
const found = new Set(hits.map((r: { keys: string[] }) => r.keys[0].toLowerCase()));
console.log('No Search Console data for:', [...wanted].filter((k) => !found.has(k)));
The last line matters. Keywords with no row are the ones Google has not shown your site for in that range, which is useful information, but it is not the same as "ranks #101".
Reading the numbers
- Position is an average. It is weighted across impressions, so a query with three impressions at positions 4, 9 and 30 reports a blended number. Treat a one or two place move on a low-impression query as noise.
- Compare equal windows. Pull the last 28 days and the 28 days before, so a seasonal change does not look like a ranking change.
- Group by page too. If two of your URLs trade places on one query, a keyword-only report hides it.
- Mind the lag and the retention. Search Console data arrives a couple of days late and goes back about 16 months, so start storing your own snapshots early.
Method 2: a SERP-scraping bulk checker for the keywords Search Console cannot see
Use a scraper-based checker when:
- you are deciding whether to write a page, and want to know where you sit for a keyword before you have any impressions;
- you need a position in one city or on one device type;
- you want to monitor a competitor's URL for the same keyword list.
Limits to expect from any tool in this category: it checks only the keywords you add, each position is a single sample, results vary by location and personalization, and pricing usually scales with the number of keywords and the refresh frequency. Check the provider's terms too, since automated queries against Google results are against Google's terms and tools differ in how they source data.
What to compare when choosing a bulk rank checker
Whichever tool you evaluate, these are the questions that separate them. Check each against the provider's own documentation, since limits change.
| Question | Why it matters |
|---|---|
| How is the keyword limit counted? | Some tools cap tracked keywords per plan, some meter each check. A daily check of 300 keywords is 300 checks a day, so the two models can cost very differently. |
| How often can positions refresh? | Daily is common; on-demand re-checks are often metered separately. |
| Can you set country, city and device? | A local keyword checked from the wrong location gives a misleading position. |
| How deep does it look? | A checker that stops at the top 20 or top 50 reports "not found" for a page sitting at 60. |
| Does it show which URL ranks? | Needed to catch two of your pages competing, or the wrong page ranking. |
| Can you export history as CSV or via API? | Without your own snapshots you cannot compare periods or leave the tool. |
| Does it track competitors on the same list? | Useful for competitor gap checks, usually priced per domain. |
| Where does the data come from? | Scraped results, a SERP data API, or Search Console. This decides the accuracy caveats above. |
Method 3: skip the list and let the data build it
If your real goal is "tell me when something moves", a keyword list is the wrong starting point, because you can only monitor what you remembered to type in. Starting from Search Console means the list builds itself from queries you already appear for, including ones you never targeted. Those are often the quickest wins: a query at position 11 to 20 with solid impressions is a page one edit away.
Where SEOAgent fits
SEOAgent is a Skill and CLI that runs inside your own coding agent (Claude Code, Cursor, Codex) on your own model, and edits files in your repo. You review every diff. It is not a standalone bulk rank checker, and it does not scrape search results.
What it does for rankings:
- With the optional paid cloud tier and a Search Console connection (
seoagent gsc connect), it syncs clicks, impressions and positions into a dashboard daily. There is no tracked-keyword cap on the position data, because it covers every query Google reports for your site. - It enriches your keyword inventory with search volume and difficulty and labels each keyword: easy win, striking distance, competitor gap. Rank tracking from Search Console and keyword monitoring cover that in detail.
- When a keyword is in striking distance or a page drops, the autopilot queues an action.
seoagent syncpulls it into.seoagent/inbox/, your agent makes the edit in the repo, andseoagent ackcloses it out. seoagent citationstracks whether AI answer engines cite you, which a classic position checker cannot show. See how to check your AI search visibility.

What it will not do:
- Report a position for a keyword where Google has never shown your site.
- Simulate rankings for a specific city or device.
- Work as a dashboard-only tool: it needs a coding agent and a repo.
- Replace a scraper if that is what you need. Use one alongside it.
Which approach to pick
- You want to know where you rank across everything, cheaply: Search Console API (Method 1).
- You have a target list of keywords you do not rank for yet: a scraper for those, then move to Search Console once impressions appear.
- You want rankings to turn into edits: read positions, find pages in striking distance, and have your coding agent revise the title, headings and internal links for those pages. SEO analytics and reporting shows how to structure that weekly pass.
No rank checker can promise a ranking or a timeline. It tells you where you stand, and what you do with that is the work. To try SEOAgent on a repo, start with the free Skill and CLI: SEOAgent for Claude Code.
FAQ
How do I check multiple keyword rankings at once for free?
Use the Search Console API as in Method 1. It returns average position for every query your site has appeared for, with no per-keyword cost. Free scraper-based checkers exist, but they typically limit how many keywords you can check per day or per session.
Why does my keyword show no position in Search Console?
Search Console only reports queries that produced at least one impression in the date range, and it omits some rare queries for privacy. No row means Google has not shown your site for that exact query lately. It does not mean you rank 101. Widen the date range, or use a scraper for that keyword.
Why do a bulk checker and Search Console disagree?
A scraper records one result, from one location and device, at one moment. Search Console averages the positions across every impression that actually occurred, so personalization, location and SERP features all feed into it. Expect differences of a few places, and larger ones on local or heavily personalized queries.
What is the difference between a bulk keyword rank checker and a rank tracker?
A checker answers "where do these keywords rank right now". A tracker stores the answer on a schedule so you can chart movement. If your tool does not keep history, save the output yourself (the Method 1 script writes a file you can commit or store with a date in the name).
How many keywords can I check in bulk?
For Search Console, as many queries as Google has data for: up to 25,000 rows per request, paged with startRow. For scraping tools, the limit is set by your plan.
References
SEOAgent for GitHub
Your first SEO pull request in about 5 minutes.
Connect the repo your site lives in. SEOAgent finds what holds the site back in search and fixes it in pull requests. You review and merge every change.
- ✓14 days free
- ✓No card
- ✓$79/site/month after
- ✓What SEOAgent found, and the plan for your site
- ✓Meta descriptions for 14 pages
- ✓Sitemap and robots.txt
- ✓Organization schema
- 370+sites
- 1,100+articles written
- 3,500+SEO changes made