Quality and evidence, control 13 of 15
Q-13 Provide real calculators and decision tools
A calculator must calculate and a selector must meaningfully help selection. Do not promise a result and substitute a sales form or unrelated redirect.
- Priority
- High priority.
- Hard gate
- No
- Change class
- AUTO_WITH_TEST: A candidate requiring relevant tests.
- Quality bucket
- Original, non-commodity value
Why it matters
A calculator that only collects contact details frustrates users who came for an answer. Google's guidance on helpful, people-first content favours pages that genuinely help, and a tool that hides its result does not. Wrong maths is worse, because users may act on it.
Evidence to review
- Unit tests, manual examples and complete user-flow checks.
How to implement
- Define inputs, assumptions, formulas and limitations.
- Test boundary cases, impossible values and rounding.
- Offer a meaningful result before an optional lead capture where feasible.
- Keep generated result URL indexing deliberate.
How UltimateSEO checks this
Needs your evidence. No automated check covers this control, so it stays UNKNOWN until evidence is supplied.
Evidence needed: the inputs, formula, assumptions and limitations of each calculator or selector and whether the result is shown without a lead wall.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Sources
Part of The UltimateSEO Framework v4.3, catalogue dated 2026-10-14. Evidence states, control states and the publish gate are explained on the hub.