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.