Conversion
Should I show pricing on my website
What 13x checks
This is rule conversion.pricing-visible in the public registry: Pricing is stated or reachable. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.
- Surface
- Conversion
- Score weight
- 4 of the readiness score
- Scope
- Reported as skipped when the page renders only with JavaScript
- Applies
- To every site
Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.
The fix
The same text the audit hands you when this check fails on your own site.
No price, pricing page or free-tier statement was found.
For a self-serve product this is usually the largest single conversion problem: a visitor who cannot tell whether it is affordable leaves rather than asking.
Options, in order of how well they usually work:
1. State the price, even provisionally. "From $29/month" is enough. 2. State the free tier. "Free for one project, no card required" answers the same question. 3. Say what it depends on if it genuinely varies. "From $500 per project" beats "Contact us".
Hiding price behind a sales conversation is a deliberate strategy for enterprise deals, and if that is the choice this finding does not apply.
Does your site have this problem?
13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.
No signup. Results in 30 seconds.
More conversion checks
- Why every launch page needs an email captureThere is a way to capture an email
- What size should an og:image beog:image is the right size
- Which analytics should I install before launchAnalytics is installed
- My page has no clear call to actionThere is a recognisable call to action
- Why I need error tracking before launchErrors are reported somewhere
- Why my site needs a contact routeThere is a way to make contact