Home / Docs / Data and coverage
Data freshness and coverage
How old an answer can be and what a public crawl can't detect, so you know when a result needs a second look.
Where the data comes from
Every answer comes from a monthly snapshot of HTTP Archive's public crawl, which tests the homepage and one inner page of about 15 million sites that real Chrome users visit. Technologies are detected with HTTP Archive's fork of the Wappalyzer rules, and Core Web Vitals are Chrome UX Report field data from the newest month at or before the crawl.
How fresh it is
We load each crawl once HTTP Archive has finished publishing it, so a result can be up to about six weeks old. meta.crawl_date tells you which crawl you're looking at, and first_seen and last_seen on each technology are the first and latest crawls in which we saw it on that site. Our history starts with our first snapshot, so first_seen can be later than the day a site really added something.
What the crawl can't see
Sites with little Chrome traffic are often missing from the crawl, and a lookup on one says "not covered" and costs nothing. Detection only sees what loads on public pages, so tools that live behind a login, like a CRM's back office or payroll software, don't show up. A site that blocks the crawler or loads a tool only after some interaction may also look like it doesn't use it. The data has no company firmographics, contacts or emails.
Related reading
For how teams put this data to work, read the technographics guide, or see how WhichSitesUse compares with BuiltWith and Wappalyzer.
Start with 250 free credits
Sign up with your work email and pull a real list from your own market before you pay a cent.