Discussion
  • Indexing
  • Technical SEO

Classifieds with the same item posted by several sellers: canonicalise, merge into one page, or let Google choose?

Published 1 reply

Discussion starter: a programmatic SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    It depends on whether the listings are really the same item. If several sellers are offering an identical new product, such as the same phone model or the same book edition, the listings are near-duplicates and the best structure is one indexable product page that aggregates the offers, with individual listings either not indexable or canonicalised to it. If the “same item” is a unique used item cross-posted or reposted, the fix is de-duplication at the point of posting, not canonical tags. Letting Google choose is the weakest option in both cases: it spends crawl on many near-identical pages and picks a canonical you may not want, often a listing that expires next week.

    Three different situations

    Situation Example Best structure
    Identical new products from several sellers The same model of power drill sold by five shops One product page listing all offers; seller listings not separately indexed
    One seller reposting the same item A used sofa posted three times to stay near the top De-duplicate at posting; enforce posting rules; keep one listing
    Unique items of the same model Several used cars of the same make, model and year Each listing is genuinely different; index model and category pages, and index listings selectively

    Aggregating identical products

    For identical new items, a product page that lists every seller’s offer is better for users, who can compare price, condition and delivery in one place, and better for search, because one strong page replaces many weak ones. This is how most marketplaces handle identical products. Individual seller listings can still exist as URLs for checkout and sharing, with a canonical pointing to the product page or a noindex, and the product page carries the structured data for the product with its offers.

    To do this you need a way to match listings to a product: a GTIN or model number, or a matching process that uses title, brand and attributes. Where matching is uncertain, keep listings separate rather than merging items that differ.

    De-duplicating reposts

    Reposting is a platform policy problem. Detect duplicates at posting time using the seller account, images and text similarity, and either block the repost or replace the older listing. Offer a paid “bump” feature if sellers want visibility, rather than letting them create duplicates. Canonical tags between reposted listings are a poor substitute, because the listings expire and change, and Google has to crawl every copy to find the tag.

    Unique items: index the stable layer

    Where each listing is a unique item, such as used cars or property, the listings are not duplicates, but they are short-lived. The pages that hold rankings best are usually the stable ones: make and model pages, category and location pages, which always have current inventory. Individual listings can be indexable while live, but plan for their expiry: return a 404 or 410 when they are removed, or redirect to the relevant model or category page when there is a close match. Leaving expired listings live as “sold” pages with no content creates soft 404s at scale.

    Watch for this:

    Canonicalising listings to other listings is fragile on a classifieds site, because the target may expire before the canonical is processed. Point canonicals only at stable URLs, such as product or model pages, never at another listing.

    What happens if you let Google choose

    Google clusters near-duplicate pages and picks one as canonical, but it does so on its own schedule and with its own criteria. On a classifieds site that often means crawling many copies, choosing a listing that expires shortly after, and reporting large numbers of pages as “Duplicate, Google chose different canonical than user” or “Duplicate without user-selected canonical” in the Page indexing report. The crawl spent on duplicates is crawl not spent on new listings, which is costly for a site whose inventory changes daily.

    Hypothetical example:

    A general classifieds site has thousands of listings for new, boxed consumer electronics, with the same model often listed by dozens of small retailers. Google indexes a random selection and many near-identical listings sit in “Crawled - currently not indexed”. The site introduces product pages matched by model number, each showing all current offers sorted by price, and sets seller listings for matched products to point their canonical to the product page. Used and unique items keep their own listing pages. Within a few months the product pages rank for model queries that the scattered listings never won, and Googlebot’s crawl shifts towards new listings.

    Structured data for aggregated offers

    A product page that lists offers from several sellers can describe them with Product markup containing an AggregateOffer, giving the lowest and highest price and the number of offers, rather than a single Offer. That accurately represents a page where the platform is not the only seller. Check Google’s current product structured data documentation for which search features support aggregate offers and which require a single merchant’s offer, because the rules differ between product snippets and merchant listings. Keep the markup generated from the live offer data, so the price range and offer count update when sellers join, leave or change prices; stale aggregate prices are as misleading as stale single prices.

    What to monitor

    • The Page indexing report’s duplicate categories, before and after changes.
    • Crawl share going to listings versus product and category pages in logs.
    • Impressions and clicks for model and product queries.
    • Expired listing handling: status codes returned for removed listings and soft 404 counts.

    Aggregate identical products onto one page with all offers, prevent reposts at the source, index the stable model and category layer for unique items, and never leave the canonical decision to Google on a site where listings change every day.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.