If every query is sent only to the PDP, one page has to serve both purchase intent and deeper research. But mass-generating additional URLs is risky too: having content does not automatically mean there is independent search demand.
Production · implemented and validated at scale
Product reviews: a dedicated landing page for pre-purchase intent
Some shoppers search not simply for a product but for “model + reviews” while they are still deciding. We created standalone indexable /reviews pages for products with 3+ reviews, gave them their own title/H1/meta and kept a direct path back to purchase. At the scale of tens of thousands of products, rankings for these queries improved noticeably.
Case at a glanceIdentified the demand, designed the page-type concept, SEO requirements, indexation and metadata rules, PDP connections, UAT and post-launch analysis.
Review pages remained a production page type and are still in use. In parallel, we tested dedicated /characteristics pages for products with 10+ properties: rankings for those queries also improved, but scale exposed an important limitation — a content threshold alone does not prove demand. The characteristics model was reworked, while reviews remained.
01Query: model + reviews→02/reviews landing→03Explore feedback→04Product page→05Purchase
The dedicated landing page serves pre-purchase research intent without breaking the commercial journey: the product page and purchase remain one step away.
This is a growth case: SEO created a new acquisition surface
Reviews were searched as a distinct decision-stage task, so we did not force one PDP to serve every intent equally well. The new /reviews page type gained its own search role while staying in a short commercial journey. The /characteristics branch exposed the scaling limit: enough content without distinct demand does not justify another indexable URL.
Why a new page type made sense
The query “product + reviews” belongs to the decision stage: the shopper is still comparing options and trying to reduce purchase risk. A PDP already contains reviews, but its primary job is to present the product and drive purchase. We separated the research intent into a dedicated landing page without breaking the connection to the PDP.
What the dedicated reviews page added
This was not simply a copied PDP tab but a search landing tailored to a specific user task.
Standalone URL
The /reviews page is indexable as its own search entity.
Own title / H1 / meta
Metadata and heading are adapted to the “product + reviews” intent.
Better review exploration
Navigation and filtering support the shopper who is still evaluating the product.
Direct PDP connection
Review research did not become a dead end: purchase stayed one simple step away.
One PDP, two different jobs
The solution separated user intent while keeping both pages in the same commercial journey.
PDP
The core product page: product details, price, availability, choice and purchase.
Reviews landing
A specialized page for a shopper who wants to study real customer experience before buying.
What the outcome showed
After launch, rankings for review- and characteristics-related queries improved noticeably. Exact historical ranking values are not used in this public case, so the result is not turned into a fabricated KPI. The important point is that the page-type hypothesis survived production use at large-catalog scale.
Characteristics produced a second important lesson
Dedicated /characteristics pages also had their own title/H1/meta and were created when a product had 10+ properties. Production use exposed a limitation in that first rule.
Initial hypothesis
Enough product properties should provide enough content for a useful standalone page.
What scale revealed
A page can have enough content while independent search demand is weak. Mass generation started to create unnecessary search inventory.
How the rule evolved after production use
The case produced not only a new page type but a more mature rule for scaling SEO inventory.
Find a distinct intent
Confirm that the shopper is solving a separate pre-purchase task.
Check content sufficiency
Reviews or properties must genuinely fill the page.
Check search demand
The existence of content alone should not automatically justify an indexable URL.
Keep the strong part, rework the weak part
Reviews remained; the characteristics model was reworked after real production evidence.
My role
SEO was not an audit after development; it was the source of the product hypothesis and requirements.
Demand research
Identified the distinct “product + reviews / characteristics” query clusters.
Page-type concept
Defined why the standalone page was needed and when it was allowed to exist.
SEO architecture
URL, indexability, canonical, title/H1/meta, PDP links and creation rules.
UAT and analysis
Validated implementation, reviewed rankings and adjusted the weaker branch after production use.
Context & measurement
- Context
- Large e-commerce business · product pages
- Scale / period
- tens of thousands of products · reviews from 3+ reviews · characteristics from 10+ properties
Key lesson
SEO scaling is not about maximizing the number of indexable pages. A new URL earns its place when distinct intent, sufficient content and a short path to commercial action exist at the same time.
Product SEO / search landing pages
Facing a similar challenge?
Tell me where SEO is blocked by product, engineering or data.