SEO for a marketplace: two sides, category pages, and the listings

Serve buyers first. Categories and locations capture the demand. Listings convert on the tail only when each solves a search on its own.

Sellers care about exposure, but flooding the index with thin listings buries the pages that can rank. A smaller, higher quality index wins more often.

• Category and location pages: own the main queries buyers use.
• Listing pages: rank only when rich, unique, and maintained.
• Facets and filters: useful for users, controlled for crawlers.
• Moderation and dedupe: stop spam, repeats and boilerplate from wasting crawl.

Start with buyer intent. Map the head terms by task and type, then by place where it fits. For services this is city or neighbourhood. For goods this is availability or delivery area.

1. 1

   List the demand terms

   Pull queries from Search Console and on-site search. Add auto-suggest terms. Example: "/bikes/mountain-bikes" and "/bikes/mountain-bikes/london".

2. 2

   Set the page families

   One URL pattern per family. Example: "/{category}", "/{category}/{subcat}", "/{category}/{city}". Keep it shallow. Use hyphens and readable slugs.

3. 3

   Set creation thresholds

   Only create a category or location page when you have supply and a minimum of real content. Empty pages waste crawl and harm trust.

4. 4

   Lock the template

   Decide which blocks every demand page must have: intro that names the query, listings module, filters, FAQs, images, internal links, and a clear CTA.

A fixed example: "/cleaners/london" with an H1 that says Cleaners in London, copy that names the areas covered, a live list of available cleaners, pricing guidance, reviews, and links to nearby areas.

• Title and H1: use the exact demand term within about 60 characters. Example title: Mountain bikes in London | YourMarketplace.
• Intro paragraph: a short answer in plain words. No fluff. Name the places, specs or job to be done.
• Listings module: inventory that matches the query by default, not empty or irrelevant.
• Filters for users: common options surfaced, but do not create indexable pages for every option.
• Static content: price ranges, delivery times, areas served, service scope, what is included and what is not.
• Trust: review counts, ratings, refund terms, IDs where regulated.
• Internal links: nearby locations, sibling categories, and a link up to the parent hub.
• FAQ: questions that arise on this page only, short and factual.

Write for the buyer. Example before: a page with only a heading and an empty grid. After: a page with copy that names London boroughs, shows in-stock models, price bands, and delivery times.

Listings are your long tail. They only earn clicks when each holds unique, specific content that answers a searcher without the category page. Set a clear bar and stick to it.

• Enforce minimum fields at listing creation. Make required: title, category, price, location, clear photos, and a description that passes length and duplication checks.
• Detect boilerplate. If most of the text matches another listing, fail moderation or force merge. Show variants as options, not separate URLs.
• Write helpful microcopy. On "/listings/bike-123", include assembly notes, compatible parts, delivery dates, and return rules. That is what wins the long tail.
• Expire responsibly. When a listing ends, keep the URL live with noindex and links to active substitutes. Do not blanket redirect to the category.

Mark up each indexable listing with JSON-LD. Use Product, Offer and aggregateRating where you have them. Keep it truthful and in sync with the visible page. Test it before you ship changes.

• Product: name, description, image, brand or make, model or sku where known.
• Offer: price, priceCurrency, itemCondition, availability, url, seller where applicable.
• aggregateRating: ratingValue and reviewCount only when you show both on the page.
• BreadcrumbList: reflect the category trail the user sees.
• Organisation and WebSite data belong on templates, not per listing.

For services, still use Product and Offer if it functions like a productised service. If it is a pure lead page with no concrete price or availability, skip Offer until you can state them.

• Place JSON-LD in the HTML, not only in client-side scripts. Assistants and crawlers read the HTML.
• Keep microdata and JSON-LD consistent if both exist, or choose one and remove the other.
• Validate with the rich results test and fix errors right away.

Filters serve users. Uncontrolled, they explode into millions of thin URLs. Decide which facets can create indexable pages and block the rest from the index.

1. 1

   List your facets

   Examples: price range, brand, size, colour, condition, delivery time, rating, sort.

2. 2

   Pick the few that deserve indexation

   Only standalone useful combinations. Example: "/bikes/mountain-bikes/london?brand=giant" stays noindex. Save index for "/bikes/mountain-bikes/london".

3. 3

   Set canonical rules

   All filtered and sorted URLs canonical to the clean category or location. Pagination can self-canonical or point to the view-all page if you have one.

4. 4

   Apply meta robots and robots.txt carefully

   Use meta robots noindex, follow on URLs you want crawled for discovery but not indexed. Avoid blocking in robots.txt unless you must hide them entirely.

5. 5

   Keep parameters stable

   Name parameters consistently. Declare them in analytics and watch their crawl in Search Console and log files.

A fixed page after control: "/sofas/chesterfield/manchester" indexes. "/sofas/chesterfield/manchester?sort=price_asc&inStock=true&colour=red" remains noindex with a canonical to the clean URL. Users still get the filter state.

• Homepage to top categories and top cities. Limit to what you can keep stocked.
• Category to subcategories and nearby areas. Use a list of links, not only cards hidden behind JS.
• Listings link up to their category trail and to relevant sibling listings, not random ones.
• Breadcrumbs across all levels. Keep names consistent across pages and schema.
• Editorial pages link into categories where they help, not as a token.

Example: "/bikes" links to "/bikes/mountain-bikes" and to "/bikes/road-bikes". "/bikes/mountain-bikes/london" links to "/bikes/mountain-bikes/cambridge" and its parent. "/listings/bike-123" links back to both and to two related in-stock models.

Index bloat kills marketplaces. Your sitemap should list only pages you want indexed today. Demand pages and indexable listings only. No filters, no expired items, no test URLs.

• Split sitemaps by type: categories and locations in one, listings in another. This makes errors easier to spot.
• Remove URLs from sitemaps the day they go noindex or expire for good.
• Use the Search Console Coverage and Performance reports to find pages shown but never clicked, thin pages, and duplicates.
• Set a monthly pruning cadence. Review low-impression listings. Improve the ones with potential. Noindex or delete the rest.
• Soft 404s waste crawl. If a page has almost no content or only says Sold out, fix it or noindex it. Do not serve a thin page with a 200 code.

1. 1

   Find bloat

   Export all indexable URLs. Compare to sitemap and to URLs with impressions in 28 days. Anything indexable with zero impressions is a suspect.

2. 2

   Decide keep, fix, or cut

   If a page could rank with a small edit, fix. If not, noindex. If it should never exist, 410.

3. 3

   Redirect only where helpful

   Merge true duplicates and redirect to the best version. Do not redirect every dead listing to the top category.

User content builds the marketplace and can sink it. Moderate for spam, duplicates, illegal items, and low effort listings. Do this at creation and in batch jobs.

• Block copy-paste farms. Compare titles and descriptions with fuzzy matching. Reject near-duplicates or force a merge into variants.
• Watermark and normalise images. Enforce minimum resolution. Auto-detect stock photos and ask for real pictures.
• Template prompts for sellers. Give fields and examples so their copy answers the buyer’s questions instead of filler.
• Flag low-engagement pages. Listings with zero views in 28 days and thin content should be improved or noindexed.
• Keep a changelog per listing. Show last updated with a date when you make material edits buyers care about.

You will generate many category and location pages. Programmatic SEO only works when each page has data and utility of its own. Avoid scaled content abuse. Tie every page to live inventory and facts you can show.

• Guardrails: only publish combinations with stock, reviews, and clear copy blocks. Queue the rest as drafts.
• De-dup at generation. If "/plumbers/london" and "/plumbers/greater-london" are the same, pick one. Point internal links to it and keep the other out of the index.
• Enrichment: pull price bands, delivery times, and top brands per page from your data warehouse nightly.
• Human passes: set a weekly review of new high-impact pages. Edit titles and intros by hand for the top pages.

Search-backed assistants cite clear, factual pages. Your category and location pages should read like concise answers. Stable names, lists, figures buyers can quote, and HTML that renders without scripts are the traits assistants pick up as of 2026.

• Allow Googlebot and Bingbot. Allow the answering crawlers you want to be visible to. Blocking them makes you invisible to assistants.
• Write an explainer for your model. A short block on each demand page that says what you include and exclude, with limits and prices where possible.
• Get on third-party lists. Directories and comparison pages rank and are cited. For example, a roundup of "best wedding photographers in Bristol" that includes your hub page.