--- title: "Fix your product page template so each product ranks for its buying searches" description: "Audit one ecommerce product template: title pattern, original copy, variant URLs, Product markup, images, reviews, speed, and stock states." canonical: "https://scalewithsearch.com/articles/ecommerce-seo-product-page-optimization" date: "2026-03-20" modified: "2026-09-25" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Real estate - Real estate - [Real estate](https://scalewithsearch.com/for/real-estate) - Work - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief) - Build - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work) - For your business - Trades and home services - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops) - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair) - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors) - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors) - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning) - [Locksmiths](https://scalewithsearch.com/for/locksmiths) - [Moving companies](https://scalewithsearch.com/for/moving-companies) - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies) - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors) - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage) - [Roofing companies](https://scalewithsearch.com/for/roofing-companies) - [Towing companies](https://scalewithsearch.com/for/towing-companies) - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping) - [Solar installers](https://scalewithsearch.com/for/solar-installation) - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction) - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving) - Practices and professional services - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices) - [Dental practices](https://scalewithsearch.com/for/dental-practices) - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms) - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics) - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms) - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics) - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness) - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health) - [Medical billing companies](https://scalewithsearch.com/for/medical-billing) - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies) - [Financial advisors](https://scalewithsearch.com/for/financial-advisors) - [Property management companies](https://scalewithsearch.com/for/property-management) - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing) - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers) - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain) - Agencies, MSPs, and manufacturing - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers) - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing) - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers) - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants) - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators) - Restaurants, shops, studios, and nonprofits - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality) - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce) - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers) - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits) - [All industries](https://scalewithsearch.com/for/) - Learn - For your office - [Office job guides](https://scalewithsearch.com/guides/) - [Browser calculators](https://scalewithsearch.com/tools/) - Start here - [How it works](https://scalewithsearch.com/how-it-works) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip) - Guides - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles by cluster - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - For machines - [llms.txt](https://scalewithsearch.com/llms.txt) - [llms-full.txt](https://scalewithsearch.com/llms-full.txt) - [Machine view](https://scalewithsearch.com/?view=machine) - Company - Evidence - [Proof](https://scalewithsearch.com/proof) - Company - [About](https://scalewithsearch.com/about) # Fix your product page template so each product ranks for its buying searches. A store with a few hundred products usually has one product template. Every page on that template carries the same title pattern, the same markup, the same image code, and the same stock logic. When the template is wrong, it is wrong on every product at once. A fix works the same way. You fix a template once, and the fix reaches the whole catalog. This article gives you a pass through one product template, element by element, and a worked example at the end. It does not cover category pages or filtered navigation; those are separate jobs. ## Split template work from product work Before you change anything, sort the page into two lists. Template elements come from code. The title tag pattern, the structured data, the breadcrumb, the image markup, the variant logic, and the stock-status behavior are template elements. A developer changes them once. Product elements come from the catalog or from a writer. The description, the specification values, the reviews, and the product questions are product elements. Someone edits them one product at a time. This split tells you who does what. It also tells you where to start. Template fixes reach every page, so do them first. Product copy is slow, so do it in priority order. ## Decide which search each product page answers A product page answers specific searches. A category page answers broad ones. "Cast iron skillet" is a category search. "Lodge 10.25 inch cast iron skillet" and "enamel cast iron skillet red 10 inch" are product searches. When a product page and a category page both target the broad term, they compete. Give the broad term to the category page. Give the product page the brand, model, size, material, and other attributes that a shopper types close to a purchase. The companion guide on [category page SEO](/articles/ecommerce-category-page-seo) covers the broad side of that split. To find the attributes, read three sources: - the Search Console queries that already show the product page; - the search box log from your own site, if your platform records it; - the questions your customer service team answers about the product. ## Write the title and H1 from those attributes A usable title pattern for most catalogs is this: ```text {Brand} {Product name} {Key attribute} | {Store name} ``` Put the attribute that separates this product from its neighbors near the front. For a skillet, that attribute is size or finish. For a boot, it is width or waterproofing. Keep the store name at the end, or drop it when the title runs long. Google builds the title link in results from several sources, including the `` element and the main heading on the page. When the title and the H1 agree with each other and with the page content, Google has less reason to rewrite the title. Google does not use the meta description as a ranking signal. The description can appear under the title and affect clicks. Write it from facts the shopper checks: material, size range, what comes in the box, and the delivery or return rule. ## Replace the manufacturer description Many stores publish the description the manufacturer supplies. Every other reseller publishes the same text. When Google finds the same text on many sites, it usually shows one version and filters the rest. Your page then competes on authority alone. An original description is the main product element you control. Write it in this order: 1. What the product is, in one plain sentence. 2. Who it suits, and who it does not suit. 3. The attributes that decide the purchase, with the values. 4. How to use it, fit it, or care for it. 5. What comes in the box. Put the specification values in a table, not in a paragraph. Shoppers scan them, and a table keeps the values consistent across products. You cannot rewrite a large catalog in one week. Sort products by one of two measures. The first is pages with many impressions and few clicks in Search Console. The second is products with the most revenue. Rewrite from the top of that list. ## Handle variants on purpose A product with colors or sizes has two URL choices. The first choice is one URL with a selector. The variants share the page, and any parameter URLs such as `?color=red` carry a canonical tag that points to the main URL. Use this when shoppers do not search for the variant by name. The second choice is one URL per variant. Each variant page gets a self-referencing canonical, its own title, and copy that names the variant. Use this only when a variant has its own search demand, such as a wide-fit shoe or a large-format print. Do not mix the two. A variant URL that is indexable, that duplicates the parent, and that has no canonical splits the signals between pages. The guide to [canonical tags](/articles/canonical-tags-developers) covers the tag itself. In February 2024, Google documented structured data for product variants. A `ProductGroup` item lists the variants with `hasVariant`, names the varying attributes with `variesBy`, and groups them with `productGroupID`. Add it when your variants live on separate URLs or on one page with a selector. ## Add Product markup that matches the page Product structured data lets Google show price, availability, and review stars in results. Google documents two result types: product snippets, for pages that review or describe a product, and merchant listings, for pages where a shopper can buy. Each type has its own required properties. Check the current list in Google's product structured data documentation before you ship. Render the markup from the same catalog fields that fill the visible page. A template version looks like this: ```json { "@context": "https://schema.org", "@type": "Product", "name": "{{ product.name }}", "image": ["{{ product.image_1 }}", "{{ product.image_2 }}"], "description": "{{ product.summary }}", "sku": "{{ product.sku }}", "gtin13": "{{ product.gtin }}", "brand": { "@type": "Brand", "name": "{{ product.brand }}" }, "offers": { "@type": "Offer", "url": "{{ product.url }}", "priceCurrency": "{{ store.currency }}", "price": "{{ product.price }}", "availability": "https://schema.org/{{ product.stock_state }}" } } ``` Add `aggregateRating` only when the page shows the reviews that produce it. Markup that states a price, a rating, or a stock state the shopper cannot see on the page breaks Google's structured data guidelines. The [ecommerce schema guide](/articles/ecommerce-schema-markup) covers the other types a store uses. Test one page in Google's Rich Results Test. Then watch the product reports in Search Console after the template ships. A template error shows up on every product. ## Make the images carry search value Product images appear in Google Images and in shopping results. Give each image a descriptive file name, such as `enamel-skillet-10-inch-red.jpg`, and alt text that describes what the image shows. Alt text is a description, not a keyword list. Show several angles and one image in use. Serve a modern format such as WebP or AVIF. Set `width` and `height` on every image so the layout does not move while images load. Do not lazy-load the main product image. It is usually the largest element in the first screen, and a lazy-loaded main image delays Largest Contentful Paint (LCP). Lazy-load the gallery images below it. ## Show reviews and answers in the HTML Reviews add original text to the page and answer objections that your copy does not. They help only when Google can read them. Some review widgets load inside an iframe or only after a click. Check the rendered HTML with the URL Inspection tool in Search Console. If the review text is not there, ask the review vendor for a server-rendered or crawlable option. Add a short product questions block from real customer service questions: sizing, compatibility, care, and returns. Answer each in two or three sentences on the page. ## Keep the page fast and stable Three Core Web Vitals apply to a product page: - LCP, which the main product image usually decides; - Cumulative Layout Shift (CLS), which late banners, review widgets, and images without dimensions cause; - Interaction to Next Paint (INP), which variant selectors and add-to-cart handlers affect. INP replaced First Input Delay as a Core Web Vital in March 2024. On product pages, third-party scripts for reviews, chat, and personalization are frequent INP causes. The [Core Web Vitals developer guide](/articles/core-web-vitals-developer-guide) covers diagnosis. ## Plan for stock changes A product that is out of stock for a short time keeps its page. Return status 200, set the availability in the markup to `OutOfStock`, and show a restock date or close alternatives. A product that is discontinued needs a decision. If a direct replacement exists, redirect with a 301 to the replacement. If no replacement exists, return 404 or 410. A redirect to the home page confuses shoppers, and Google can treat it as a soft 404. ## Link each product into the catalog Give every product page a breadcrumb that follows the category path, with `BreadcrumbList` markup. Link to the product from its category pages with normal `<a href>` links. Add related products and accessories as crawlable links, not only as script-rendered carousels. ## Worked example: one template pass A store sells cast-iron cookware. One product is a 10-inch enamel skillet in three colors. The audit of its template finds these conditions. | Element | Before | After | How to check | |---|---|---|---| | Title | `Skillet - Store Name` | `Brand Enamel Cast Iron Skillet 10 Inch, Red, Blue, Green \| Store Name` | View source | | Description | Manufacturer text | Original copy in the five-part order | Search a sentence in quotes | | Variant URLs | `?color=` URLs, each indexable, no canonical | One URL, parameters canonical to it, `ProductGroup` markup | URL Inspection on a variant URL | | Product markup | None | Template JSON-LD from catalog fields | Rich Results Test | | Main image | Lazy-loaded | Loaded at once, with dimensions | PageSpeed Insights LCP element | | Reviews | Iframe widget | Server-rendered review text | Rendered HTML in URL Inspection | | Stock logic | Page removed when stock hits zero | Page stays, markup says `OutOfStock` | Test with one zero-stock product | The developer changes the title pattern, the canonical logic, the markup, the image loading, and the stock logic in the template. Those five changes reach every product. The writer then rewrites descriptions for the top of the priority list, one product at a time. ## Measure the change In Search Console, filter the Performance report to pages that contain your product path, such as `/products/`. Compare clicks, impressions, and click-through rate for 28 days after the template release with the 28 days before it. Compare the same weeks one year earlier if your sales are seasonal. This comparison shows a change. It does not prove the cause. A Google update, a promotion, or a stock change in the same window can move the same numbers. Record the release date and the other events in that window next to the result. ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```