Is Purchase Page is a yes/no read on whether a page appears built to support a purchase or subscription action. RankGear returns 1 when the rendered HTML carries transactional language or Product schema, and 0 otherwise — but a signal in the markup is not proof that checkout actually works.
| Factor ID | RG-STR-006 |
|---|---|
| Family | Page structure |
| Measurement | Boolean classification (0 / 1) |
| Measured zone | Complete rendered HTML |
What it measures
This factor estimates whether the page supports a purchase or subscription action. It classifies the page as transactional or not, giving you a quick read on whether the page presents itself as a place to buy, order, or subscribe rather than to inform.
How RankGear measures it
RankGear returns 1 when the rendered HTML contains phrases such as “add to cart,” “buy now,” “purchase,” “order now,” “pay now,” or “subscribe,” or when its Schema Product counter is above zero. Matching is case-insensitive. If none of those signals are present, the factor returns 0.
What RankGear looks for
case-insensitive phrase match in rendered HTML:
"add to cart" | "buy now" | "purchase"
"order now" | "pay now" | "subscribe"
OR
Schema Product counter > 0 (e.g. <script type="application/ld+json"> { "@type": "Product" } </script>)| Value | Meaning |
|---|---|
| 1 | A purchase/subscription phrase was found, or Product schema is present — the page reads as transactional. |
| 0 | No transactional phrase and no Product schema — the page reads as non-transactional. |
How to optimize it
Treat this as an observation about how the page presents itself, not a target to chase. For genuinely transactional pages, make offers, pricing, availability, purchase controls, policies, and next steps clear and trustworthy so the page earns the classification honestly. Informational pages should not add purchase language merely to flip the classification — match the page to real search intent instead.
Important considerations
- Marketing prose can create false positives — a word like “purchase” in body copy can trip the match on a page that sells nothing.
- Presence of the signal does not prove checkout functionality; it only reflects the language and markup in the HTML.
- Product schema alone can trigger the factor, even without any visible buy controls.
- Match page design to genuine search intent rather than forcing transactional signals onto informational pages.
- This is a descriptive signal that correlates with transactional pages in a measured result set. It does not make a page rank and it does not guarantee any position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.