Has Form is a boolean signal that returns 1 when RankGear detects a form element with attributes in the rendered page body, and 0 when it does not. It confirms markup presence only — not that the form is visible, accessible, secure, or actually works.
| Factor ID | RG-TEC-008 |
|---|---|
| Family | Tech & platform |
| Measurement | Boolean (0 / 1) |
| Measured zone | Rendered page body |
What it measures
Has Form reports whether RankGear detects a form element with attributes in the rendered page body. A positive result can indicate that the page includes an interactive form for a user task such as contact, search, signup, checkout, filtering, or login. The factor measures markup presence only — it does not determine the form’s purpose, visibility, accessibility, security, usability, or whether submission actually works.
How RankGear measures it
RankGear lowercases the rendered body HTML and checks for an opening form tag immediately followed by a space. A matching form element returns 1; otherwise the value is 0. This compatibility rule detects typical forms that carry attributes. A bare form tag with no attributes may not match, and interfaces built without a standard form element may also return 0.
What RankGear looks for
<form action="/contact" method="post">
<input name="email">
<button>Send</button>
</form>The detector matches the lowercased substring <form (an opening form tag followed by a space, i.e. a form element carrying attributes).
| Value | Meaning |
|---|---|
| 1 | A form element with attributes was found in the rendered body markup. |
| 0 | No qualifying form element was detected — the page may have no form, a bare <form> tag with no attributes, or a JavaScript interface built without a standard form element. |
How to optimize it
Treat this value as an observation about the page, not a target to hit. Add a form when it genuinely supports the page’s purpose and reduces friction for the visitor: keep fields limited to necessary information, label them clearly, provide useful validation and error messages, and confirm that keyboard and assistive-technology users can complete the task. Protect submitted information, explain how it will be used, prevent spam responsibly, and test the complete submission and confirmation flow. Do not add a nonfunctional form merely to change this factor.
Important considerations
- A value of 1 does not prove the form works — it confirms markup presence only.
- A bare form tag with no attributes can be missed by the detector.
- JavaScript interfaces that do not use a standard form element may not qualify.
- Forms can improve conversion or create unnecessary friction depending on intent.
- Evaluate performance, privacy, accessibility, and task completion separately.
- This is a prioritization signal that relates to position within a measured result set — it is correlational and does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.