Rank tracker that thinks in URLs, not keyword lists.
A flat list of keywords isn’t a data model. SERPVoyager organizes every keyword by the URL that targets it, by category, by page type. Every report already speaks the language of your site.
- Host(1)runninghub.com
- Page type(4)CategoryProductBrandGuide
- Primary category(12)Running ShoesBrandsApparelGuides
- Sub-category(84)RoadTrailTrackMarathon
- URL(132)/running-shoes/road//brands/nike//guides/best-running-shoes-2026/
- Keyword(487)road running shoesnike pegasus 41best trail running shoes
Built around the URL tree, not around tags.
Every other rank tracker we tried treats keywords as a flat list and asks you to tag them. At 100,000 keywords that’s not a feature, it’s a second job.
Your site already has the taxonomy baked into its URLs. /shoes/nike/running/ isn’t three random tokens; it’s a category, a brand, and an intent. SERPVoyager reads that structure and rolls every metric in the product up a five-tier hierarchy (host → page type → primary category → sub-category → URL → keyword) automatically.
The 10% your URLs don’t tell us, you fix with a rule, not a per-keyword tag.
- /running-shoes/31222.4%
- /running-shoes/road/8418.6%
- /running-shoes/road/cushioned/246.2%
- /running-shoes/road/lightweight/184.8%
- /running-shoes/trail/5610.2%
- /running-shoes/track/328.4%
- /brands/8618.4%
- /brands/nike/4816.8%
Drill from “all of site” → Shoes → Nike → Running → the individual PDP without touching a tag. Every keyword count is a live rollup.
Every feature flows from the same one decision.
None of the four below would work on a flat keyword list. They’re only possible because every keyword carries its URL, category, and page type around with it.
Cannibalization, structurally.
“Two URLs ranking for the same keyword” is impossible to define without the URL-keyword link. We treat it as a workflow: detect, assign, resolve, and re-open the moment it comes back.
Share of Voice by anything.
Compare your Shoes category’s SoV vs. a named competitor’s Shoes category. Or your Nike sub-category. Or your Nike Running deep sub-category. CTR-weighted, formula on the page.
Experiments with matched controls.
Test a new PDP template against a control of PDPs that match on page type, category, and starting position. The data model makes “matched” actually possible — not a wave of the hand.
Movers by URL pattern.
Filter today’s gainers and losers by URL pattern. Is /blog/* trending up? /shoes/* trending down? Answer in one filter — not three tools, not a CSV download.
The four questions we get every week.
Do I have to tag every keyword manually?
No. SERPVoyager infers page type and category from URL structure on first crawl. Manual overrides are supported per URL or per rule, but they’re the exception — not the workflow.
What if our URL structure is messy?
Most sites have 80–90% of their structure encoded in URLs and a long tail of weird patterns. Define a handful of rules (e.g. /p/[id] = PDP, /c/[slug] = PLP) once and the long tail gets classified on the next crawl. Custom overrides are available for the truly one-off cases.
Does it work for sites without category folders?
Yes. You can map any keyword to any URL manually, or classify URLs via title patterns, slug patterns, or canonical analysis. The URL tree is the default because it works for 90% of sites; for the rest, the same data model is built another way.
What about subdomains and international subfolders?
Subdomains are tracked as separate projects by default and can be rolled up. International subfolders (/en/, /fr/, /de/) are handled as a top-level facet so you can compare a single category across locales.
Your keywords, grouped by the URLs that actually rank them.
Plug in your keywords today. Tomorrow morning, they’re grouped by target URL and rolled up through your 4-level category tree, with avg position, traffic, and Share of Voice at every level.
14-day free trial. No credit card.