Editorial and tool review policy

Public pages are selected, not generated in bulk

The internal registry contains more converter definitions than the public website. Registry membership alone does not create an indexable page.

A public tool must have a working conversion function, representative examples, tool-specific questions and answers, practical use cases, result checks and clear limitations in both English and Hebrew.

Functional review

Automated tests cover converter behavior, metadata, links, static output and representative browser flows. The production checks also verify that public routes return the expected status, that unpublished routes remain unavailable, and that converter input is not included in analytics events.

Automated checks support editorial review; they do not replace a human check of whether the page explains a real task clearly.

Content review

Each public page must explain when the tool is useful, what input it expects, what the output means, which mistakes are common and what should be checked before the result is reused.

Generic word count is not treated as proof of value. Pages that rely only on shared template text stay outside the public sitemap and do not load advertising.

Advertising boundary

Advertising is limited to reviewed tool pages. Home, category, policy, contact, analytics, error and other navigation-oriented pages do not load Google AdSense.

A tool page uses two separated placements after substantial tool and guidance content. Advertising must not cover controls, sit next to conversion actions, or become the only way to leave a screen.

Corrections

Reported defects are checked against a reproducible, non-sensitive example. A page can be removed from indexing and advertising if its function or guidance no longer passes review.