Product Page SEO: Which of Your 400 Products Deserve Unique Copy

A store owner posted in r/ecommercemarketing in October 2025 that writing unique titles and descriptions for hundreds of new products "feels impossible". Every product page SEO guide on page one says to do it anyway. So the supplier text stays, and the store ranks for nothing.

The honest answer is that you don't write 400 descriptions. You find the 60 to 80 products that earn clicks and revenue, write those properly, template the next hundred or so, and stop the rest from competing with them. This guide is that method, with the data join that makes the tiers fall out on their own.

Why 400 unique product descriptions is the wrong goal

The thread is worth reading in full, because the OP had already run the experiment. "When I first started, I just copied the supplier descriptions, but those pages never ranked well. Then I tried rewriting a few manually and noticed those actually brought in some traffic."

Two replies, both from October 2025, gave the answer the guides skip. One: "the top 20% of products will drive 80% of the revenue, so make sure these are crawled, indexed and optimized", then "wait 30 days, come back and optimize each page individually based on google search consloe data". The other split the catalogue into three tiers:

• Tier 1: "Best-sellers, flagship items, high-margin products", which get "unique titles, rich descriptions, internal links, FAQs".
• Tier 2: "Category representatives, seasonal items, products with steady search volume", which get a "partial rewrite + templated structure".
• Tier 3: "Low-traffic variants, one-offs, long-tail SKUs", which get "light optimization or even canonicalized to parent category".

The thread stops there. It doesn't say how to pick the tiers without guessing, what "fully optimized" contains, or that canonicalising a product to a category is not what a canonical tag is for. The rest of this guide fills those three gaps.

Step 1: Tier the catalogue with Search Console clicks and GA4 revenue

Tiering by gut works for the ten products you already know sell. It fails for the long tail, where a product that quietly earns 40 clicks a month for a model-number query looks identical to one that earns nothing. The two numbers that separate them live in different tools, so you join them on the product URL.

The join, by hand

1. Export Search Console pages. Performance, Search results, last 3 months, filter Page contains your product path (/products/ on Shopify, /product/ on WooCommerce). Export clicks and impressions per URL.
2. Export GA4 revenue by landing page. Reports, Engagement, Landing page, same 3 months, with the Total revenue metric. Export it.
3. Normalise the URLs. Strip query strings and trailing slashes so a variant URL joins to its parent, and the two exports agree.
4. Join on URL in a sheet. Every product URL now has four columns: clicks, impressions, revenue, and blank where it earned none.
5. Sort by revenue, then by impressions. The tiers are the three bands of that sort.

We built CrawlRaven's ecommerce mode for exactly this join: it lists every product URL with its Search Console clicks, impressions and GA4 revenue in one table, so the tiers fall out of a sort. The same audit flags product pages with missing or broken Product markup and duplicate titles across the catalogue, which is where step 2 starts.

The free plan covers 1 site; the 3-site lifetime licence launched at $49. Lifetime pricing steps up as licenses sell, so check the pricing page for the current batch. Today's number is on the pricing page.

Where to draw the tier lines

Run the three questions in the flow above, in order, and stop at the first yes:

• Revenue in the last 90 days, or top 20% by units sold: tier 1. Revenue outranks everything. A product that sells from paid or email traffic and has no organic clicks still gets the full page, because the query exists and you are not on it yet.
• Impressions in Search Console but no revenue: tier 2. Google already shows the page for something. A template that names the attribute in the query is usually enough to earn the click.
• Neither: tier 3. Split it once more: a variant or near-duplicate of an indexed product canonicalises to it; a standalone one-off stays templated, with noindex only if crawl budget is a real constraint.

On a 400-product catalogue that usually lands around 80 products in tier 1, 150 in tier 2 and the rest in tier 3. Your numbers will differ. The order of work will not.

Step 2: Give tier 1 the full product page

"Unique copy" is the phrase everyone uses and the smallest part of the job. A tier-1 product page carries eight elements. I checked what three live stores ship before writing the list: Allbirds on Shopify, Barefoot Buttons on WooCommerce, and Zappos, all fetched in September 2026.

Title tag and meta description

The title tag names the product, the attribute the query uses, and the brand. Allbirds ships "Men's Cruiser | Everyday Comfort & Style | Allbirds"; Barefoot Buttons ships "Barefoot Buttons V1 Standard Clear Acrylic Footswitch Topper", which carries the model, the material and the product type a guitarist types.

The meta description is where templates show. Zappos runs one pattern: "Men's Kenneth Cole Charles by Kenneth Cole at Zappos.com. Read ... product reviews, or select the size, width, and color of your choice." Barefoot Buttons wrote theirs: "Turn tiny switches into solid targets... No wobble. No misses." Tier 1 gets the second kind.

Check both with the meta checker; the Shopify meta description guide covers the theme field.

Copy that answers the buying question

A shopper on a product page has one question left: is this the right one for me? The copy answers it in three parts, and none of them is in the supplier's paragraph:

• Who it is for. The use, the skill level, the room, the pedal. Barefoot Buttons opens with LEDs staying visible and "common 3PDT switches 3/8" (10mm)", then answers "How big is a Standard Barefoot Button?" in a questions block.
• What it fits or works with. Compatibility, sizing, what else you need. This is where the model-number and "fits" queries land.
• What it is not. The honest line that cuts returns and reads as expertise: runs narrow, not for outdoor use, needs the larger bore.

Length follows the product. 120 to 300 words plus a specs table covers most of a catalogue. Keep the page to one product, because Google's merchant listing documentation says product rich results "only support pages that focus on a single product (or multiple variants of the same product)".

Specs table and Product structured data

Put the attributes in an HTML table, not a PDF or an image. It is the content the long-tail queries match, and the field list your tier-2 template draws from. Then add the structured data. Google's Product structured data intro splits the feature in two, and a store wants the second:

Two rules from the same documentation decide whether the markup does anything. Google "may attempt to verify merchant listing product data" against the page, so the price and availability in the markup must be the visible ones. And Google recommends the markup "in the initial HTML", because JavaScript-generated markup "can make Shopping crawls less frequent and less reliable".

The product schema generator writes a valid block for one product, and the schema validator shows what the theme actually emits. On Shopify the markup also has to agree with the Merchant Center feed.

Image file names, alt text and internal links

Image alt text is where the three stores split. Barefoot Buttons: "Barefoot Buttons V1 Standard Clear Acrylic guitar pedal footswitch topper top view for 3PDT switch 3/8 inch 10mm", on a file named barefoot-buttons-v1-standard-clear-footswitch-topper.png. Zappos: "Pair View", "Top View", "Bottom View", with 6 of 25 images carrying no alt at all.

Allbirds sits between: the alt reads "Men's Cruiser - Medium Grey (Blizzard Sole)", but the lead image file on the Medium Grey page is named for Dark Navy. Small, and exactly what a tier-1 pass catches. Run each tier-1 URL through the image alt checker; the image optimization entry has the file-name rules.

A product that only the category grid links to has one weak inbound link. Tier 1 gets four: a sentence in the category copy (the category page SEO guide covers writing it), a mention in the buying guide for the head term, and two related products. Tier 2 gets the grid and the related-products module.

Step 3: Template tier 2 with variables, not manufacturer text

Tier 2 has impressions and no revenue, which means Google already shows the page for a query and shoppers pass it by. A template with variable slots is unique per product as long as the slots are filled from real fields, and it is built once in a CSV, which is how both Shopify and WooCommerce bulk-edit products.

• Title: {Product} {Attribute} | {Category} | {Brand}, where Attribute is the field the query uses. Search Console's Queries tab, filtered to the URL, tells you which one.
• Meta description: one sentence with two slots, such as fit and material, never the first line of the description.
• Description: three template paragraphs (who it is for, what it fits, what is in the box) with a slot in each, followed by the generated specs table.
• Alt text: {Product} {Attribute} {angle} from the same fields.
• Never: the supplier's paragraph, not even as a base. It is on every reseller's page and it is the text the OP said "never ranked well".

The 30-day rule from the thread is the promotion rule. Recheck the join a month later: any tier-2 product that earned clicks or a sale moves to tier 1 and gets written by hand. That is how the tier-1 list grows from 80 toward the products that deserve it, instead of from a guess.

Step 4: Decide what tier 3 does: canonical, noindex or nothing

The Reddit advice to canonicalise low-value products to the category comes with a warning: "may need to noindex too since google ignores canons often". Google ignores them because that is not the tag's job. Its consolidate duplicate URLs doc describes rel="canonical" as a preference among "duplicate or very similar pages". A one-off product is neither.

So tier 3 splits by what the page actually is:

• A variant or near-duplicate of an indexed product (same item in another colour, a bundle, the same product reachable at a second URL): canonical to the parent product, out of the sitemap. This is the case the tag exists for, and the duplicate content it prevents is real.
• A standalone one-off with no demand: leave it templated and indexable. If crawl stats show Googlebot spending its budget on thousands of these, add noindex to the tail. Google's same doc warns that noindex "will completely block the page from Search", so only use it where you mean it.
• A product with a second URL through a category path (Shopify's /collections/x/products/y): canonical to /products/y, which the theme does by default. Verify it, because apps and theme edits break it.

The same documentation ranks the signals: a redirect is stronger than rel="canonical", which is stronger than a sitemap entry, and robots.txt is not a canonicalisation method at all. Do not block tier 3 in robots.txt; Google may still index the URL from links.

Variants and the canonical

Google's ecommerce URL guidance recommends giving each variant its own URL, either a path segment like /t-shirt/green or a parameter like /t-shirt?color=green, and says: "If you use optional query parameters to identify variants, use the URL with the query parameter omitted as the canonical URL."

The two stores handle it differently, and both are defensible:

• Allbirds puts the colour in the handle (/products/mens-cruiser-medium-grey), self-canonicalises each colour, and carries size as a parameter (?size=8). The JSON-LD is a ProductGroup with variesBy size and colour and 42 hasVariant entries, so Google sees one product with variants across several URLs.
• Zappos puts colour in the path (/product/10038622/color/72), canonicalises to the colour URL, and sets the Product's url to the parent product while the Offer's url is the colour page.

The tiering question is whether a variant deserves its own indexable page. The join answers it: a colour with its own impressions ("cruiser grey") earns a tier-2 page; a size never does. Google's product variant markup documentation covers both single-page and multi-page layouts.

Out-of-stock products: keep, redirect or 404

An out-of-stock product page with rankings is an asset; deleting it throws the rankings away. Google's launch guidance even describes shipping a whole site "with products marked as out of stock" before fulfilment is ready. The decision is about whether the product returns:

• It will be back: keep the page live, set availability to OutOfStock or BackOrder in the markup and on the page, add a back-in-stock form, and link two alternatives. Leave the price visible.
• It is discontinued and a successor exists: 301 to the successor product, because a redirect is Google's strongest canonical signal and the intent matches.
• It is discontinued and nothing replaces it: return 404 or 410. Google's URL guidance says the same for a category that has emptied and been removed from navigation: "consider returning a 404".
• Never redirect to the homepage. It is not the page the shopper or Google asked for, and it sends the ranking signals nowhere useful.

Zappos does it at scale: an out-of-stock product URL I fetched redirected to an internal search page for the product name, with ?oosRedirected=true appended. That keeps the shopper among near-matches. A smaller store should redirect to the successor product instead.

Measure the tiers, then promote and demote

The join that built the tiers is the report that maintains them. Rerun it every 30 days for the first quarter, then quarterly:

• Tier 1 clicks and revenue per URL. Rewritten pages should gain impressions within two to four weeks and clicks after. A tier-1 page losing clicks month on month is decay, and gets the first look.
• Tier 2 promotions. Any templated page with a sale or a run of clicks moves up and gets written.
• Tier 3 leakage. Variant URLs earning their own impressions in the Pages report mean the canonical is being ignored; check for one canonical and no conflicting sitemap entry.
• Markup health. Search Console's Merchant listings report lists pages with missing or invalid Product markup. Fix tier 1 first.

This is the ecommerce-specific half of an ecommerce SEO checklist. The other half, category pages and the plumbing that differs from a software site, is in SaaS SEO vs ecommerce SEO. If the catalogue is supplier stock you don't hold, does SEO work for dropshipping stores covers why tier 1 is even more selective.

Product page SEO FAQs

Tiering and prioritisation

The 80/20 rule, how to find the products that deserve unique copy, and whether every product needs a unique description. The FAQ block below answers each in the same terms as the steps.

What goes on the page

Description length, what the title tag carries, and what Product markup and AggregateRating do and do not do for ranking.

Variants, stock and platforms

Variant URLs and canonicals, out-of-stock pages, and where Shopify and WooCommerce differ.

What to do this week

• Run the join for the last 90 days and sort by revenue. Write the tier-1 list down; it is shorter than you think.
• Validate three tier-1 URLs in the schema validator: one Offer, visible price, availability, a rating only where reviews exist.
• Write the tier-2 template with three slots and bulk-apply it by CSV. Delete the supplier paragraph as you go.
• Rewrite the first ten tier-1 pages, highest revenue first, with the eight elements above.
• Set a 30-day reminder to rerun the join and promote.

Sources

• r/ecommercemarketing: How do you handle SEO when adding hundreds of new products at once? (October 2025)
• Google Search Central: Introduction to Product structured data
• Google Search Central: Merchant listing (Product, Offer) structured data
• Google Search Central: Product snippet structured data
• Google Search Central: Product variant structured data
• Google Search Central: How to specify a canonical URL
• Google Search Central: Designing a URL structure for ecommerce sites
• Google Search Central: How to launch a new ecommerce website
• Allbirds: Men's Cruiser product page (fetched September 2026)
• Barefoot Buttons: V1 Standard Clear Acrylic product page (fetched September 2026)
• Zappos: Men's Kenneth Cole Charles product page (fetched September 2026)
• Keyword data: DataForSEO Labs keyword overview and SERP API, United States, September 2026.