Keyword Mapping Is a Routing Table: Assigning Search Intent to Marketplace Pages

If you've ever built a web app, you already understand keyword mapping. You just know it by another name: routing.

A router takes an incoming request and sends it to exactly one handler. If two handlers claim the same path, you get a conflict. If a path has no handler, you get a 404. If you shove every route into one giant controller, it works for a while and then becomes impossible to maintain.

Search works the same way. A query comes in, Google decides which of your URLs should handle it, and if you haven't been explicit, it guesses. On a marketplace, with hundreds or thousands of category, seller and listing pages, it guesses badly.

This post treats keyword mapping as a routing table for search intent, based on Journeyhorizon's guide to keyword mapping for marketplaces.

What keyword mapping actually is

Keyword mapping is the process of assigning target search terms to specific pages, so each page has a clear job. The workflow has three steps:

1. Research the keywords your buyers and sellers actually use.
2. Group them into clusters by topic and search intent.
3. Assign each cluster to the one page that should rank for it.

On a blog or a SaaS site, the "pages" are mostly articles and a few service pages. On a marketplace, the route table is far richer: category pages, filtered listing pages, seller profiles, seller onboarding, content hubs and comparison pages all compete for attention.

The route table for a marketplace

Here is the mapping the source recommends, rewritten as a routing config. Treat it as pseudocode for your SEO plan, not as something a framework will execute.

routes:
  - handler: category_page          # main pillar pages
    intent: high-volume, high-intent buyer
    example: "best project management tools"

  - handler: filtered_listing_page  # refined category views
    intent: long-tail, specific buyer
    examples:
      - "affordable project management tools under $50"
      - "best free project management software for small teams"

  - handler: seller_guide           # supply-side education
    intent: informational, seller
    examples:
      - "how to optimize your seller profile"
      - "pricing strategies for service providers"
      - "how to get more reviews as a seller"

  - handler: blog_or_industry_guide # authority content
    intent: research
    example: "the state of the freelance economy"

  - handler: comparison_page        # evaluation stage
    intent: high-intent, comparing platforms
    example: "<your platform> vs <competitor>"

  - handler: homepage
    intent: brand

Two rules make this table work:

• One primary handler per cluster. A keyword cluster maps to one primary page. Supporting pages link to it; they don't compete with it.
• Handler type must match intent. "Freelance writers" is a category-page query, not a blog-post query. Someone typing it wants to browse writers, not read an essay.

The source's own example of intent routing is a nice sanity check: a buyer searching "best handmade leather bags" should land on a category page, a prospective seller looking to list should land on onboarding, and an investor researching trends should land on the blog.

How many keywords per page?

The guide's rule of thumb: one primary keyword plus 3–5 closely related secondary keywords per page. Think of it like a route with a few aliases. More than that and the page usually stops having a clear purpose.

And on the homepage vs category debate: category pages usually win. Keep the homepage focused on the brand and let category pages capture high-intent buyer and seller queries.

Five bugs that break the routing

The source lists five mapping mistakes. Here they are as bug reports.

Bug 1: Ambiguous routes

Symptom: a category page and a blog post both target "how to buy handmade jewellery." Neither ranks well.
Fix: pick one primary page per keyword. The other page links to the owner instead of competing with it.

Bug 2: Wrong handler type

Symptom: commercial queries are routed to blog posts, so searchers bounce.
Fix: match page type to intent using the table above.

Bug 3: Static config

Symptom: the map was built at launch and never touched again, while new categories and segments shipped.
Fix: review and refresh the map quarterly.

Bug 4: Content not wired to the router

Symptom: blog posts get published because a topic "seemed interesting," and categories launch with no keyword research behind them.
Fix: content strategy flows from the map. If a piece of content doesn't own or support a mapped cluster, question why it exists.

Bug 5: Only one side of the market is routed

Symptom: every mapped keyword is a buyer query. Supply growth relies entirely on outbound sales.
Fix: map seller queries too, like "how to become a seller" or "selling on our platform." Marketplaces live or die on supply.

Treat the map like code: review it on a schedule

The guide's maintenance advice translates neatly into a recurring job. Once a quarter, run through this checklist:

• [ ] Which mapped keywords are actually driving organic traffic?
• [ ] Which pages are ranking for keywords you didn't plan? (Often a hint of a new opportunity.)
• [ ] Which clusters have no page at all? (Your 404s.)
• [ ] Where do multiple pages rank for the same keyword? Pick one owner and adjust internal links to support it.
• [ ] Are there new search trends in fast-moving categories?
• [ ] Are any mapped clusters still unoptimized?

Store the map somewhere versioned, even if it's just a spreadsheet with a change log. When categories or features ship, updating the map should be part of the definition of done, the same way updating routes and tests is.

A minimal schema for the map

You don't need a dedicated tool to get started. A table with these columns covers most of what the guide describes:

Column	Purpose
cluster	The primary keyword plus its 3–5 secondary keywords
intent	buyer, seller, research or comparison
owner_url	The single page that should rank
supporting_urls	Pages that link to the owner instead of competing with it
last_reviewed	Date of the last quarterly check
status	mapped, page missing, needs optimization

Filter by status = page missing and you have a content backlog. Filter by duplicate cluster values across different owners and you have your cannibalization bugs. It's a small amount of structure that makes the whole process reviewable.

Starting without data

A common objection: "We're pre-launch, we have no ranking data." The guide's answer is pragmatic. Start with your core categories and the main buyer and seller journeys, then refine as ranking and traffic data accumulates over several months. That's exactly how you'd ship an MVP router: cover the critical paths first, add routes as usage reveals them.

Benefits beyond organic search

Keyword mapping mainly pays off in organic traffic, but the source notes an indirect effect too. Cleaner site structure, better content and stronger internal linking build authority that also helps paid, referral and word-of-mouth channels. A well-organized site is easier for everyone to navigate, not just crawlers.

Takeaway

Keyword mapping won't produce overnight wins. It's foundational work, and the guide frames it as what separates marketplaces that grow through organic search from those that stay dependent on paid ads.

If you'd like a team to build or audit that routing table with you, Journeyhorizon works specifically with marketplaces, and its SEO services for marketplaces cover keyword strategy alongside technical SEO. Either way, start today: open a spreadsheet, list your page types, and give every important query exactly one home.