Skip to content

Conversion

Why my site needs a contact route

Someone who hits a bug, wants a feature, or is ready to pay for something bigger has no way to tell you. It is also required alongside the legal pages in most jurisdictions, and payment providers ask for it during onboarding.

What 13x checks

This is rule conversion.contact-route in the public registry: There is a way to make contact. 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.

Add a contact route. In order of effort:

html code
<a href="mailto:hello@example.com">hello@example.com</a>

A dedicated /contact page with a form is better if you expect volume, and a booking link (Cal.com, Calendly) is better if you want conversations.

This is not only conversion: a contact address is required alongside your legal pages in most jurisdictions, payment providers ask for it during onboarding, and someone ready to pay for something bigger currently has no way to tell you.

Make sure the address receives mail — see the MX finding if it does not.

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