One product in five categories — duplicate problem?

'Q: My product appears under multiple categories. Is that creating duplicate content issues?'

Short answer: Only if each category generates a different URL for the same product. One canonical URL fixes it.

The longer version: showing a product in five category listings is normal merchandising and totally fine. The problem appears when your platform mints a unique product URL per category — /sale/widget, /new/widget, /gifts/widget — all the same product. Now you have five competing URLs splitting signals.

Fix: every product resolves to one canonical URL regardless of which category the user clicked from. The product page's canonical tag points to that single address; the rest either don't exist or canonical to it.

For breadcrumbs and structure, assign one primary category as the canonical path even though the product appears in several listings. That keeps your hierarchy clean and your relevance focused.

Rule of thumb: a product can live in many lists but must have exactly one address.

Got a duplicate-content question? Drop it.

Which filter combinations should I let Google index?

'Q: I want some facet pages indexed but not all. How do I decide which?'

Short answer: Index a facet only when its combination has real search demand and unique inventory.

The longer version: don't decide by gut — decide by demand. A facet page earns indexing if it passes three tests:

— People search for it. 'Nike running shoes' has volume; 'Nike running shoes size 10.5 blue under $73' does not.
— It has enough products to be a satisfying page (a one-product facet is thin).
— It's not a near-duplicate of an existing category.

Generally: single-select on high-demand attributes (brand, type, primary color) — index. Multi-select stacks, price ranges, sort orders, in-stock toggles — never index.

Practical setup: maintain an allowlist of indexable facet patterns. Everything else gets nofollowed internal links plus a robots disallow on the param, so crawlers never even reach the combinatorial explosion.

Rule of thumb: if you'd write a meta title for it without cringing, it can be indexed.

Got a faceted-nav question? Drop it.

Can I canonical my product to Amazon's listing?

'Q: I sell the same product on my site and Amazon. Should my page canonical to the Amazon URL to avoid duplication?'

Short answer: No — never canonical your own pages to a marketplace. You'd hand them your rankings.

The longer version: a cross-domain canonical tells Google 'the version on that domain is the real one, index that instead.' Point it at Amazon and you're voluntarily de-indexing your own product page. People do this by accident through SEO plugins or feed tools — check yours.

Selling identical manufacturer-described products is fine; you're not 'duplicating' in a harmful way. To stand out:

— Rewrite the manufacturer's boilerplate description (everyone else uses the same feed text).
— Add your own photos, Q&A, and reviews.
— Build internal links and earn external ones to your URL specifically.

That's how a smaller store outranks a marketplace listing for long-tail product searches.

Rule of thumb: your canonical should point to a URL you own and want to rank. Full stop.

Got a canonical question? Drop it.

Q: 'We noindexed faceted pages but traffic didn't move. Did we waste our time?'

Short answer: Not if you watched the right metric — crawl budget, not rankings.

The longer version: A mid-size outdoor gear store had ~480k indexable URLs, mostly color/size/brand filter combinations. They added noindex,follow to any URL with 2+ active filters and blocked the worst parameter combos in robots.txt. Rankings on money pages were flat for the first 6 weeks — which scared them. But Googlebot requests to category templates jumped from 38% to 71% of total crawl, and new products started getting indexed in 2 days instead of 11. Three months later, category page sessions were up 34% because Google was finally re-crawling the pages that mattered.

Rule of thumb: Faceted cleanup is a crawl-efficiency play first, a ranking play second. Measure log files, not just positions, for the first two months.

Got an e-com SEO question? Drop it.

—
Кстати, по этой теме сейчас открыты позиции: @careers_radar

Faceted nav: block crawling or just noindex?

'Q: I added noindex to my filter pages but Google still wastes crawl budget on them. What gives?'

Short answer: noindex stops indexing, not crawling — those are two different problems.

The longer version: a noindex tag only works after Googlebot fetches the page and reads the tag, so every filtered URL still gets crawled. On a store with 40 filters across 200 categories, that's millions of low-value URLs eating your budget before anything gets de-indexed.

The fix is layered. Decide which facet combos have search demand (color, brand) and let those be real indexable pages. For the infinite junk (price sliders, multi-select stacks), block the parameter pattern in robots.txt so Google never fetches it. Use rel=nofollow on internal facet links so you stop feeding crawlers the path in the first place.

Rule of thumb: noindex for pages you want seen-but-not-ranked, robots block for pages you don't want crawled at all.

Got an e-com SEO question? Drop it.

What do I do with out-of-stock product pages?

'Q: A product is sold out. Do I 404 it, redirect it, or leave it up?'

Short answer: Depends on whether it's coming back — and here are the three branches.

The longer version: split by intent.

Temporarily out of stock (restocking soon): keep the URL live, keep it indexed, and add availability schema with OutOfStock. Surface a 'notify me' form and link to similar in-stock items. You keep the rankings warm for when inventory returns.

Gone for the season but returns yearly: same — never throw away a URL that earns links and traffic every Q4.

Discontinued forever: 301 redirect to the closest equivalent product or the parent category. Only 404 if there's genuinely no relevant replacement, because a 301 to an irrelevant page is a soft-404 trap.

Rule of thumb: redirect to relevance, not to the homepage — homepage redirects get treated as soft 404s.

Got an out-of-stock edge case? Drop it.

Why did my product rich results disappear?

'Q: My star ratings showed up for months, then vanished. I didn't change anything.'

Short answer: Google probably tightened how it trusts your review markup, not your code.

The longer version: rich result eligibility isn't just 'valid schema' — it's 'valid schema Google believes.' Common silent killers:

— aggregateRating with zero visible reviews on the page. The markup must reflect content a user can actually see.
— Reviews pulled from a third-party widget that loads in an iframe Google can't tie back to the product.
— A reviewCount that doesn't match what's rendered.

Google also rotates which sites get the visual treatment in competitive categories, so two valid pages can get different treatment.

Fix: make every rated review visible in the HTML (not lazy-loaded behind a tab that needs a click), keep counts honest, and validate in the Rich Results Test. Then request indexing and wait a crawl cycle.

Rule of thumb: schema describes the page; it can't invent content that isn't there.

Got a schema question? Drop it.

If you're into what we post, @StackAndCompare is the natural next follow — they work the SEO tools reviews beat hard. Honest, hands-on SEO tool comparisons — Ahrefs vs Semrush vs the cheap alternative,…

Should I still use rel=next/prev for pagination?

'Q: I read Google dropped rel=next/prev. So how do I handle paginated category pages now?'

Short answer: Correct — Google ignores rel=next/prev. Treat each paginated page as a standalone URL.

The longer version: Google confirmed years ago it stopped using those tags. Modern approach:

— Let page 2, 3, etc. be crawlable and self-canonical (page 2 canonicals to page 2, NOT page 1). Canonicalizing everything to page 1 hides those products from discovery.
— Make sure deep products are reachable. Crawlers don't click 'load more' or scroll infinitely, so JS-only pagination can orphan page-30 products.
— Keep clean ?page=2 URLs with real anchor links Googlebot can follow.

For index bloat worries, you can noindex thin paginated pages — but only if products on them are linked elsewhere (sitemap, related blocks), or you'll bury them.

Rule of thumb: pagination exists to help crawlers reach products, not to rank. Optimize for discovery, not for the listing page itself.

Got a pagination question? Drop it.

Should internal search result pages be indexed?

'Q: My site search creates URLs like /search?q=red+shoes. Google indexed thousands of them. Bad?'

Short answer: Almost always bad — block them. They're a classic index-bloat and crawl-trap.

The longer version: internal search pages are infinite (every query a user types makes one), usually thin, and overlap with your real category pages. Google has called out 'search-within-search' results as a poor experience for years.

Fix: disallow /search (or your param) in robots.txt and add noindex as a backstop on any already-indexed ones. Submit a temporary removal for the worst offenders if it's severe.

The nuance worth knowing: a handful of search queries may represent real demand you don't have a landing page for. Don't index the search page — instead, build a proper category or collection page for that term. That's the difference between bloat and opportunity.

Rule of thumb: if a search query has real demand, it deserves a real page — not an indexed search URL.

Got a crawl-budget question? Drop it.

Each color variant has its own URL — duplicate content?

'Q: My red, blue, and green versions of one shirt are 3 separate URLs with near-identical text. Will Google penalize me?'

Short answer: No penalty — but you're splitting ranking signals and confusing Google about which to show.

The longer version: there's no 'duplicate content penalty.' The real cost is dilution: links and relevance spread across three thin pages instead of one strong one.

Two valid models:

— One canonical product page with a color selector (variants swap via JS, single URL). Simplest, consolidates everything. Best when color isn't a search term.
— Separate variant URLs, each self-canonical, IF people actually search 'blue running shirt.' Then give each genuinely distinct content: unique title, variant-specific images, color in the copy.

What you should NOT do: three URLs with identical text and no canonical strategy. Pick consolidation or differentiation — don't sit in the middle.

Rule of thumb: separate URLs only when the variant has its own search demand. Otherwise, one URL with a swatch picker.

Got a variant question? Drop it.

Category page or blog post for 'best X' keywords?

'Q: Should 'best wireless headphones' target my category page or a blog buying guide?'

Short answer: Check the live SERP first — Google tells you which format it wants.

The longer version: for many 'best [product]' queries, Google ranks editorial guides and comparison articles, not raw category grids — because the intent is research, not 'show me everything.' For others ('cheap white sneakers'), it ranks category pages because intent is transactional.

So: search the term, see what's ranking on page one. If it's mostly listicles and reviews, you need a guide. If it's mostly store category pages, optimize the category.

Smart move: do both and interlink. The buying guide captures research intent and links down to the category and top products; the category captures transactional intent. The guide also earns the links your category page can't.

Rule of thumb: match the format Google is already rewarding for that exact query — don't fight the SERP.

Got a keyword-mapping question? Drop it.

Is manufacturer description text hurting my SEO?

'Q: I use the supplier's product descriptions like everyone else. Is that duplicate content?'

Short answer: It won't penalize you, but it gives Google zero reason to pick you over 50 identical stores.

The longer version: when 50 retailers run the same feed text, Google filters down to a few — usually the biggest brands. You're invisible by default. This is opportunity cost, not a penalty.

What moves the needle on a product page:

— A rewritten description with details the spec sheet skips: who it's for, real-world fit, common complaints.
— A short 'why we recommend it' note in your own voice.
— Real reviews and a Q&A section (user-generated content is unique by definition and adds long-tail keyword surface).
— Specs in a structured table Google can parse.

You don't need to rewrite all 5,000 SKUs. Start with your top 50 revenue products — the 80/20 there is huge.

Rule of thumb: unique content is most valuable on the products that already make you money.

Got a product-page question? Drop it.

My seasonal category is empty — what status code?

'Q: My 'Christmas decorations' category has zero products in July. Should it 404?'

Short answer: No — keep it 200 with helpful content, never 404 a page that ranks half the year.

The longer version: 404-ing a temporarily empty category throws away the authority and links it built last season. But leaving a bare 'no products found' page risks a soft-404 flag from Google, which de-indexes it anyway.

The move is to keep the page meaningful year-round:

— Show 'coming back this season' messaging with the expected date.
— Surface related evergreen products or adjacent categories.
— Keep your buying-guide content and internal links intact.
— Optionally, a sitewide search and email-capture for restock alerts.

Now the page has real content (not 'zero results'), stays indexed, and is ready the moment you reload inventory.

Rule of thumb: empty ≠ gone. Make a seasonal page useful in the off-season instead of deleting it.

Got a category-lifecycle question? Drop it.

Do breadcrumbs actually help SEO, or just look nice?

'Q: Are breadcrumbs worth implementing for e-commerce SEO or are they cosmetic?'

Short answer: They do three real SEO jobs — they're not cosmetic.

The longer version:

— Internal linking: breadcrumbs push authority back up to category and parent pages and clarify your site hierarchy to crawlers. On a deep store, that flow matters.
— SERP appearance: with BreadcrumbList schema, Google shows your category path instead of an ugly URL string in results, which can lift click-through.
— Context: they tell Google how a product relates to its category, reinforcing topical relevance.

Two gotchas: make the breadcrumb reflect the page's primary category (a product in 3 categories should have one canonical breadcrumb path), and make sure the visible breadcrumb matches your schema — mismatches get ignored or flagged.

Rule of thumb: breadcrumbs are free internal links plus a SERP upgrade. Implement them with schema, and keep the path canonical.

Got a schema or linking question? Drop it.

Does infinite scroll hurt my product discovery?

'Q: My category pages use infinite scroll instead of pagination. Are products getting missed?'

Short answer: Often yes — Googlebot doesn't scroll, so anything past the first load can go undiscovered.

The longer version: infinite scroll loads more items as a user scrolls, but crawlers don't simulate that gesture. If the only way to reach product #200 is by scrolling, Google may never see it through that page.

The fix is paginate-behind-the-scroll: keep infinite scroll for users, but back it with real, crawlable paginated URLs (?page=2) that load the same items, linked with actual anchor tags. Frameworks like this give humans the smooth scroll and bots a clickable path.

Belt and suspenders: make sure every product is also reachable from your XML sitemap and from related-product / cross-sell modules, so discovery never depends on one navigation method.

Rule of thumb: if a crawler can't click to it, assume it won't find it. Always provide a link-based path to deep products.

Got a crawlability question? Drop it.

What's the best title tag formula for product pages?

'Q: I have 8,000 products. What title template ranks best without writing each one by hand?'

Short answer: Lead with the searchable product name, then the differentiator, then brand — and keep it under ~60 characters where it counts.

The longer version: a strong programmatic template, in priority order:

{Product Name} {Key Attribute} | {Brand}

Example: 'Merino Wool Base Layer, Men's | Northpeak'. The most-searched words sit at the front where they carry weight and survive truncation.

Things that quietly help:

— Drop boilerplate prefixes like 'Buy' or 'Shop' eating front-of-title space.
— Inject a high-intent modifier only when it's true and searched ('Waterproof', 'Organic').
— Put your store name at the end, not the start — nobody searches your brand to find a generic SKU.

Then override the template manually for your top 50-100 revenue products, where a tailored title beats any formula.

Rule of thumb: template the long tail, hand-craft the head. Front-load the words people actually type.

Got a title-tag question? Drop it.