Part of the Rankar Suite — the demand layer

Rankar suite · Keyword intelligence

RankSearch Keyword Research
& Strategy Platform

RankSearch Keyword Research with volume, keyword difficulty, intent, CPC and Opportunity Score

RankSearch turns live DataForSEO demand data into the exact pages you should build — clustered, mapped, prioritised by traffic-per-effort, and shared across your team through one 30-day cache.

Built for in-house SEO teams, agencies and content leads who have to defend a publishing plan — not just hand over a keyword export.

  • Live DataForSEO data
  • 30-day workspace-shared cache
  • No per-seat data charges
  • CSV + JSON export on every table
30-day
shared data cache
200
keywords per bulk run
5
research modules
1
credit ledger for the whole team

What is RankSearch

A keyword research and strategy workspace, not a keyword database

RankSearch is the demand layer of the Rankar Suite. It pulls live DataForSEO metrics for a scope you set once, clusters that demand into topics, elects the page that should own each topic, and orders the work by traffic-per-effort — so research leaves the tool as a publishing plan rather than a spreadsheet.

The problem it solves

Generic suites stop at a filtered list. The translation from rows to pages happens in docs the tool can never see, which is where cannibalisation, duplicated provider spend and unowned work get introduced.

Who it is built for

In-house SEO teams, agencies and content leads who have to defend a publishing plan — plus analysts who need country, language and engine scope respected on every single request.

Why it lives in the Rankar Suite

Every other Rankar product needs to know what to build, track or audit. RankSearch is where that decision is made, and it hands clusters to RankWriter, keywords to RankTracker and new pages to RankAudit without re-entry.

How it differs from a dashboard

A dashboard reports. RankSearch decides: exclusive keyword-to-page assignment, pillar and supporting structure, effort in days, phased delivery order and explicit states for every provider failure mode.

  • Five research modules on one scope and one 30-day shared cache
  • Rankar Opportunity Score with editable weights
  • Gap analysis against up to four rivals
  • CSV and JSON portability on every table

The problem

Keyword research ends in a spreadsheet nobody ships

Every generic suite gives you the same thing: 4,000 rows, five filters and no answer to the only question that matters — which pages do we build, in what order, and who owns them?

Exports, not decisions

A CSV of volumes is raw material. Someone still has to turn it into pages, and that work happens in docs the tool never sees.

Accidental cannibalisation

Two writers pick the same term from the same list, and six months later your own pages compete for it.

Duplicate provider spend

Five analysts research one market and the workspace pays five times for identical lookups.

Blank screens on limits

When a provider rate-limits or hits a spend ceiling, most tools show nothing and the review meeting stalls.

Value

SEO intelligence, one workflow, decisions you can ship

Search visibility work fails on fragmentation: demand data in one tool, competitor analysis in another, the plan in a doc none of them can see. RankSearch keeps keyword research, competitor gap analysis and roadmap assembly on one dataset.

SEO intelligence in one environment

Search volume by country and globally, keyword difficulty with a plain-language read, intent classification, CPC, competitive density, traffic potential and 12-month trend — resolved for the same scope across every module, so two analysts never compare two different numbers.

  • Keyword overview, ideas and People-also-ask in one screen
  • SERP analysis enriched with page authority, referring domains and backlinks
  • Opportunity Score weighing demand, ranking potential, SERP weakness and value
  • Freshness stated on screen: live or cached, its age and expiry

One workspace instead of five tabs

Research, discovery, bulk qualification, competitor gaps and roadmap assembly are five views of one dataset. Scope is set once and inherited; the keyword drawer, compare tray and cache are shared, so work moves forward instead of restarting in the next tool.

  • Scope set once — every module inherits country, language and engine
  • Any keyword opens the same detail drawer from any table
  • Shared cache and in-flight deduplication across the whole team
  • Workspace export, import and reset as a single JSON file

Insights you can act on this sprint

Output is page-level, not row-level: which pages to build, in what order, at what effort, and which existing pages are at risk. Ranking opportunities, competitor gaps and quick wins arrive already prioritised by traffic-per-effort.

  • Quick-win flags and phased delivery order in the roadmap
  • Missing / weak / shared / strong gap buckets against four rivals
  • Cannibalisation prevented at assembly — one keyword, one page
  • Hand-off to RankWriter briefs and RankTracker tracking

Why RankSearch

Six reasons teams switch from generic keyword suites

Every one of these is implemented in the product today — not a roadmap promise.

A strategy engine, not a keyword exporter

Semrush and SE Ranking hand you a filtered list. RankSearch hands you page-level output: clusters, a chosen pillar, supporting pages, one keyword per page, effort estimates and a phased publishing order.

Cannibalisation prevented by construction

Every keyword is assigned to exactly one page during assembly, so two of your own pages can never be planned against the same term.

Team-shared 30-day cache

Requests are keyed on keyword + country + language + engine + device and hashed. Identical simultaneous calls are deduplicated in-process, so five analysts researching the same market cost one lookup.

Traffic-per-effort prioritisation

The roadmap ranks work by expected monthly traffic against estimated effort in days, with quick wins flagged — so the first sprint is the highest-return one.

Never a blank screen

A full error taxonomy (rate limited, provider spend limit, no data, no rankings, bad locale, auth, network) drives explicit UI states, and terminal provider failures degrade to deterministic demo data with a visible banner.

Built for the Rankar suite

One keyword drawer, one scope bar, one credit ledger, and direct hand-off into RankWriter content briefs and RankTracker rank tracking.

Product demo

See how a keyword becomes a publishing plan

The five steps behind every RankSearch project — keyword overview, Magic Tool discovery, bulk qualification, gap analysis and the Strategy Builder roadmap. The guided tour at the top of this page walks all of them.

app.rankar.ai / ranksearchScreen recording
  1. 01

    Set scope

    Pick country, language and engine once — every module inherits it.

  2. 02

    Research or expand

    Start from a keyword overview, or expand a seed in the Magic Tool and filter to winnable terms.

  3. 03

    Qualify at scale

    Push a list through Bulk Keywords and compare candidates side by side.

  4. 04

    Find the gaps

    Run Gap Analysis against up to four rivals to catch demand you're missing.

  5. 05

    Build the plan

    Cluster into pillar and supporting pages with one keyword per page.

  6. 06

    Ship it

    Export CSV/JSON, or hand off to RankWriter briefs and RankTracker tracking.

Product tour

Real screens, real metrics, production UI

Nothing below is a mockup. These are the shipped RankSearch screens, in the same operator theme you get on day one.

Keyword overview

One screen for demand, difficulty, intent and value — plus the Opportunity Score and a 12-month trend.

  • Volume by country and global split
  • Difficulty with plain-language read
  • Enriched SERP table
  • Ideas + questions, clickable

Magic Tool discovery

Expand a seed into a market, then filter down to the terms you can realistically win.

  • Volume, KD, intent, CPC and word-count filters
  • Related / broad / question / long-tail tabs
  • Difficulty backfilled in bulk
  • Multi-select and compare

Strategy Builder roadmap

Clusters become pillar and supporting pages, ordered by traffic-per-effort across phases.

  • Semantic clusters with themed labels
  • Pillar + supporting election
  • Effort in days, expected traffic
  • Phase-based CSV roadmap

Competitor gap

Four rivals, one matrix: the demand they hold and you don't, with volume and difficulty attached.

  • Missing / weak / shared / strong buckets
  • Position deltas per competitor
  • Send any gap into the roadmap
  • Full matrix export

Modules

Five modules, one scope, one cache

Set country, language and engine once. Every module inherits it, writes into the same 30-day cache, and shares the same keyword detail drawer — so research never restarts from zero.

Keyword Research

Core

Full keyword overview in one screen

Volume by country, global demand split, keyword difficulty with a plain-language read, intent classification, CPC, competitive density, traffic potential and a 12-month trend — plus the Rankar Opportunity Score that weighs demand, ranking potential, SERP weakness and business value.

  • Country / language / engine scope on every request
  • SERP analysis enriched with page authority, referring domains, backlinks and estimated traffic
  • Keyword ideas and People-also-ask questions that are clickable straight into a new overview
  • Keyword detail drawer shared by every module

Rankar Magic Tool

Discovery

Filter a whole market down to what you can win

One seed expands into the full keyword universe, then filters do the work: volume ranges, difficulty ceilings, intent, word count, CPC floors, include/exclude terms and SERP-feature presence. Sort by Opportunity Score to surface easy wins and high-value terms instantly.

  • Related, broad-match, question and long-tail tabs
  • Difficulty backfilled in bulk so no row shows a blank score
  • Multi-select then compare keywords side by side
  • Save filter sets and export the filtered view to CSV

Keyword Strategy Builder

Differentiator

From keyword set to publishing roadmap

Feed it a domain or seed keywords and RankSearch clusters semantically, elects pillar and supporting pages, maps every keyword to exactly one page to prevent cannibalisation, then ranks the whole plan by traffic-per-effort across delivery phases.

  • Real semantic clustering on shared phrases — not one cluster per keyword
  • Pillar / supporting hierarchy with related keywords listed per cluster
  • Effort in days, expected monthly traffic and quick-win flags per page
  • Phase-based roadmap, CSV export, hand-off to RankWriter and RankTracker

Bulk Keywords

Scale

Qualify 200 keywords in one pass

Paste a list, get volume, difficulty, intent, CPC and Opportunity Score for every term in a single virtualised table. Ideal for validating a content backlog, a paid keyword dump or a migration inventory.

  • Virtualised rows with density toggle for large sets
  • Sort and filter without re-querying the provider
  • Whole run served from — and written into — the shared cache
  • UTF-8 BOM CSV export that opens clean in Excel

Gap Analysis

Competitive

The keywords four rivals rank for and you don't

Compare your domain against up to four competitors and split the result into missing, weak, shared and strong buckets — with volume and difficulty attached so the gap turns straight into a roadmap.

  • Missing / weak / shared / strong classification
  • Position deltas per competitor
  • Send any gap keyword into the Strategy Builder
  • Export the full gap matrix

The differentiator

Not another keyword list — an actual site plan

The Strategy Builder is where RankSearch stops looking like a keyword tool. It clusters demand semantically, elects the pillar page, attaches supporting pages, assigns each keyword to exactly one URL, then orders the whole thing by traffic-per-effort so your first sprint is your highest-return sprint.

Semantic clusters

Keywords group on shared phrases (bigrams preferred); singleton buckets merge into their nearest cluster and each cluster is labelled by its shared theme.

Pillar + supporting map

Every cluster elects a pillar page and its supporting pages, with the related keywords listed per row.

One keyword, one page

Assignment is exclusive during assembly, so cannibalisation can't be planned into the roadmap.

Traffic-per-effort phases

Effort in days, expected monthly traffic and quick-win flags drive a phased delivery order — exportable to CSV.

See the roadmap your own keywords produce.

Open a live keyword overview, or feed a domain into the Strategy Builder and watch clusters, pillar pages and phases assemble.

From data to action

Discover, analyse, prioritise, act, measure

The same dataset moves through all five stages inside RankSearch. Nothing is re-typed, re-exported or re-billed between them.

01

Discover

Keyword overview, Magic Tool expansion, questions and related terms under one country, language and engine scope.

Live DataForSEO

02

Analyse

Difficulty, intent, CPC, competitive density, 12-month trend and SERP weakness enriched with page authority and referring domains.

9 metrics per keyword

03

Identify opportunities

Opportunity Score ranks demand against ranking potential and business value; gap analysis surfaces missing and weak buckets.

Editable weights

04

Take action

Strategy Builder clusters demand, elects pillar and supporting pages and assigns one keyword to one page, phased by traffic-per-effort.

Effort in days

05

Track results

Promote keywords into RankTracker, push clusters to RankWriter briefs, or export the roadmap as CSV and the workspace as JSON.

Suite hand-off

Rankar Suite

RankSearch is the demand layer of the Rankar Suite

The suite shares one scope bar, one keyword drawer and one credit ledger. RankSearch decides what to build; the other products build, audit, ship and measure it. Nothing you research here has to be re-entered anywhere else.

Centre of the suite

RankSearch

Keyword research & strategy

Demand data in, publishing plan out. Everything downstream inherits its clusters, keywords and scope.

Shared across the suite

  • Country, language and engine scope
  • Keyword detail drawer
  • 30-day provider cache + usage ledger
  • Workspace export / import as JSON

RankWriter

Receives clusters

Turns a cluster into a content brief with primary and supporting keywords mapped.

RankTracker

Receives keywords

Tracks promoted keywords under the same country, language and engine scope.

RankAudit

Audits new pages

Technical audit of the pages your roadmap creates, so new pillars ship crawlable.

RankSpy

Extends gap data

Deeper competitor intelligence behind the gap buckets RankSearch surfaces.

RankOps

Executes phases

Turns roadmap phases into assigned, tracked delivery work.

RankLinks

Builds authority

Link acquisition against the pillar pages the roadmap prioritises.

RankAIO

Measures AI visibility

Checks whether the pages you planned are cited in AI search answers.

Use cases

Who runs RankSearch, and for what

In-house SEO teams

Turn quarterly demand research into a phased publishing roadmap the content team can execute without a translation layer.

Agencies

Run identical scoped research per client, share one cache across the team, and export a roadmap that doubles as the deliverable.

Content leads

Pick the next ten briefs by traffic-per-effort instead of gut feel, with one keyword locked to one page.

Migrations & consolidations

Push a whole URL inventory through Bulk Keywords to see which terms justify keeping, merging or killing a page.

New market entry

Switch country, language and engine once and re-run the same strategy pipeline against a market you have no data on.

Competitive recovery

Diff your domain against four rivals, take the missing and weak buckets, and route them straight into the roadmap.

Who it's for

Built for everyone who has to defend a search plan

The same five modules serve very different teams. Each of these is a workflow the product supports today, not a planned tier.

SEO agencies

Run identically scoped research per client, share one cache across the team, and export a roadmap that doubles as the client deliverable.

Freelancers

Get enterprise-grade demand data and a defensible page plan without buying a per-seat suite you only use part-time.

SEO specialists

Work at metric level: difficulty, SERP weakness, competitive density and trend, with editable Opportunity Score weights.

Affiliate marketers

Qualify up to 200 keywords per bulk run, spot low-difficulty demand fast, and build content order by traffic-per-effort.

E-commerce teams

Push a URL inventory through Bulk Keywords to see which category and product terms justify keeping, merging or retiring a page.

In-house SEO teams

Keep demand data, competitor gaps and the publishing roadmap in one workspace the content team can execute from directly.

One suite, one workflow

Replace a stack of disconnected tools with one chain of custody

Most SEO teams run research in one tool, competitor work in another and the actual plan in a document. Every hand-off loses context. The Rankar Suite keeps the chain intact from demand to published page.

A fragmented stack

  1. 01Multiple disconnected tools
  2. 02Separate dashboards and logins
  3. 03Scattered exports and spreadsheets
  4. 04Manual translation into a plan
  5. 05No shared scope or cache

Rankar Suite

  1. 01Rankar Suite
  2. 02RankSearch — the demand layer
  3. 03Connected products: Writer, Tracker, Audit, Spy, Ops, Links, AIO
  4. 04One scope, one cache, one credit ledger
  5. 05One unified SEO workflow

Data economics

One lookup, thirty days, the whole workspace

RankSearch treats provider data as a shared asset. Requests are keyed on keyword, country, language, engine and device, hashed, deduplicated in flight and reused for 30 days — with freshness always visible on screen.

Shared cache, one cost

A keyword fetched by anyone in the workspace serves everyone for 30 days.

Request deduplication

Identical simultaneous lookups collapse into a single provider call.

Raw payloads retained

Normalised JSONB plus the raw provider response, so metrics can be recomputed without re-billing.

Visible freshness

Every screen states whether data is live, cached, its age and its expiry date, with a one-click refresh.

Usage ledger

Provider usage is recorded per request so spend is attributable.

Graceful ceilings

When the daily provider ceiling is hit, the app degrades to demo data instead of failing.

Proof

Verified numbers, once they're yours

We don't publish borrowed logos or invented counts. These slots fill from your own workspace telemetry — websites tracked, keywords monitored, roadmaps shipped — as soon as real data exists.

Your data stays attributable

Every provider request is written to a usage ledger, so spend and freshness are auditable per keyword.

No lock-in on output

Export the whole workspace as JSON and every table as Excel-safe UTF-8 CSV, any time.

Tested where it counts

Unit coverage over scoring, roadmap assembly and the error taxonomy, with typecheck and an import guard in CI.

Comparison

RankSearch vs a generic keyword suite

Same input. Very different output.

DimensionGeneric suiteRankSearch
Primary outputFiltered keyword listPage-level publishing plan
ClusteringKeyword groups by string matchSemantic clusters on shared phrases, themed labels
Site structureNot modelledPillar + supporting pages elected per cluster
CannibalisationDetected after publishingPrevented at assembly — one keyword, one page
PrioritisationSort by volume or KDTraffic-per-effort with quick-win flags and phases
Data costPer-seat, per-lookupOne shared 30-day cache with in-flight deduplication
Provider limitsError or empty stateDeterministic demo fallback with a visible banner
Hand-offCSV downloadCSV, JSON workspace, RankWriter briefs, RankTracker tracking

Under the hood

Enterprise plumbing, operator-grade UI

Data provider

Live DataForSEO: keyword overview, keyword ideas, questions, bulk difficulty, SERP, ranked keywords, page metrics and traffic estimation.

Cache layer

Postgres tables for normalised cache, raw payloads and provider usage, with SHA-256 request hashing and 30-day expiry.

Front end

TanStack Start with server functions, TanStack Query, virtualised tables, keyboard-accessible drawers and density controls.

Portability

Workspace export / import / reset as JSON, plus UTF-8 BOM CSV on every table.

Quality gates

TypeScript typecheck in CI, an import-shadowing guard and unit tests over scoring, roadmap and error handling.

Design system

Geist and Geist Mono, indigo-on-near-black operator theme with a full light variant, recharts visualisations.

Pricing logic

You pay for data once, not per seat looking at it

RankSearch bills the workspace for provider lookups, and the 30-day shared cache means the same keyword never costs twice. Add analysts without multiplying data spend.

Team

Included

For a single in-house team on one primary market.

  • All five research modules
  • Shared 30-day cache and request deduplication
  • CSV + JSON workspace export
  • Unlimited viewers on cached data

Agency

Most used

Suite plan

For teams running many domains and markets in parallel.

  • Everything in Team
  • Multi-market scope switching
  • Gap Analysis against four rivals per run
  • Hand-off into RankWriter and RankTracker

Enterprise

Talk to us

For orgs that need attribution and governance on data spend.

  • Per-request usage ledger
  • Raw provider payload retention
  • Custom Opportunity Score weights
  • Suite-wide credit ceilings

FAQ

Questions buyers actually ask

What is RankSearch?

RankSearch is the keyword research and strategy workspace of the Rankar Suite. It pulls live demand data for a country, language and engine you set once, clusters that demand into topics, elects the pillar and supporting pages that should own each topic, and orders the work by traffic-per-effort — so the output is a publishing plan rather than a keyword export.

Who can use RankSearch?

In-house SEO teams, agencies, freelancers, SEO specialists, affiliate marketers, e-commerce teams and content leads. The five modules are the same for everyone; what differs is the entry point — a seed keyword, a bulk list, a domain, or a competitor set.

What SEO workflows can I run in it?

Keyword overview and metric analysis, seed expansion with questions and related terms, bulk qualification of up to 200 keywords per run, competitor gap analysis against up to four rivals, and roadmap assembly with pillar and supporting page mapping.

Where does the data come from?

Live DataForSEO endpoints for volume, difficulty, ideas, questions, SERP results and page-level metrics. Results are normalised into the shared cache so the same lookup is never billed twice inside 30 days.

How is this different from Semrush or SE Ranking?

Those tools stop at a keyword list. RankSearch continues into strategy: semantic clusters, elected pillar and supporting pages, one keyword per page to prevent cannibalisation, and a roadmap ordered by traffic-per-effort.

What does the 30-day cache actually change?

Cost and speed. Requests are keyed on keyword + country + language + engine + device, deduplicated in-process, and reused workspace-wide for 30 days — so a whole team researching one market pays for one lookup.

Can I still force fresh data?

Yes. Every screen shows whether the data is live or cached, how old it is and when it expires, with a Refresh data action that bypasses the cache for that request.

What happens when the provider limit is reached?

Instead of a blank screen you get deterministic demo data plus a visible banner explaining the state, so the workflow and the UI stay reviewable.

How does RankSearch fit into the Rankar Suite?

RankSearch is the demand layer. It decides what to build, then hands clusters to RankWriter as briefs, keywords to RankTracker for rank tracking, new pages to RankAudit for technical checks, and roadmap phases to RankOps. Scope, the keyword drawer, the cache and the credit ledger are shared across the suite, so nothing is re-entered.

Can agencies run multiple domains and markets?

Yes. Scope (country, language, engine) switches in one place and every module inherits it, Gap Analysis compares your domain against up to four rivals per run, and the shared cache means several analysts researching one market cost a single lookup.

Do I need to connect a website to start?

No. You can start from a seed keyword in Keyword Research or the Magic Tool. Adding a domain unlocks the domain-driven Strategy Builder input and Gap Analysis competitor comparison.

How does RankSearch help with SEO decision-making?

It converts demand into page-level decisions: semantic clusters, an elected pillar page with supporting pages, one keyword per page, effort in days against expected monthly traffic, quick-win flags and a phased order — so the argument for the next sprint is on screen, not in a spreadsheet.

How do I get the plan out of the tool?

CSV export on every table (UTF-8 BOM, Excel-safe), full workspace export/import as JSON, and direct hand-off into RankWriter content briefs and RankTracker rank tracking.

Start now

Run your next keyword project as a plan, not a spreadsheet.

Open Keyword Research with a live example already loaded, or jump straight into the Strategy Builder with your own domain.