About SearchWebCode

SearchWebCode builds a search engine for the stored homepage source of public websites. Its reports and guides are published by SearchWebCode, the same organization that develops and operates the service.

People and contact

For product questions, report methodology or a correction, contact admin@searchwebcode.com. Our bylines identify SearchWebCode as the publisher and link to these methods.

What the index measures

The public index stores one homepage per hostname, including subdomains, and follows a quarterly rebuild schedule. Its size counts indexed homepage documents, not unique registered domains. When several crawls contain the same hostname, the newest capture is retained. It records captured HTML and inline code; it does not continuously observe each site, confirm code execution or measure vendor customers.

How to read counts

Candidate upper bound: pages passing the index prefilter. Some can fail the exact source check.
Estimated matches: a projection from checked source samples, with sampling uncertainty.
Verified matches: an exact query count established by the engine, for the stated footprint and index.
Historical unclassified total: an archived number whose original verification type was not retained. It is not certified as an exact adoption count.

An individual returned source match establishes that the selected string occurs in stored source. Review its context before describing a running installation or drawing a security conclusion.

Datasets and reproducibility

Reports link to dated CSVs, exact footprints, denominators and measurement limits. A live query checks the current index; reproducing an old total requires the original index and query responses. Start with the August footprint snapshot, jQuery estimates or comparison workflow.

Corrections and comparisons

Editorial updates correct claims while retaining the source snapshot date. We link to primary vendor documentation for support and pricing facts. Provider-by-provider speed or coverage claims need dated query settings and result evidence. Our published comparison guide supplies a method rather than a measured cross-provider benchmark.

Include the page URL, the claim and supporting source when requesting a correction. Current pricing and allowances are generated from the billing catalog.