Tool standards

Tool methodology.

How the free website tools are designed, tested, reviewed and limited before publication.

What a tool must do

A published tool must perform the task described on the page. Inputs, outputs and limitations are stated in plain language. Tools are not published only to create a search landing page, and a tool that cannot produce a meaningful result should not be presented as working.

Browser-based tools keep calculations and text transformations on the visitor’s device unless a page clearly states that a server request is required. Live website checks are separated from local utilities because they have different privacy, reliability and network constraints.

Calculation sources and formulas

Straightforward calculators use visible formulas or standardized ratios. Unit converters expose the relationship between the source and destination units on the page. Business calculators state the variables being combined and should be treated as planning aids rather than accounting, tax, investment or legal advice.

When a result depends on a third-party system, live network condition or proprietary dataset, the page must identify that dependency instead of presenting an invented metric.

Testing before indexing

Core interface behavior is checked for valid input, decimal values, empty states, copy or download controls where applicable, responsive layout and basic keyboard use. Programmatically generated converter pages are available to users but are kept out of search indexing by default. A smaller reviewed set can be indexed after the page, formula, metadata and internal links are checked.

Accuracy and rounding

Most browser calculations use JavaScript floating-point numbers. Extremely large or small results may appear in scientific notation, and the last displayed digits can be affected by floating-point rounding. Where a professional standard specifies a conversion convention or rounding rule, that standard takes precedence over a general-purpose web calculator.

Corrections and maintenance

Broken tools, incorrect formulas and misleading descriptions should be corrected rather than preserved for traffic. Tool logic and publishing rules may be updated as browser behavior, web standards or search requirements change. The visible page should continue to describe what the current tool actually does.