Finding a business and judging its website are different questions, answered by different sources. Here’s what each source supplies, what it can’t tell you, and what you still check yourself.
Finding businesses
Overture Places, and OpenStreetMap when connected
A discovery scan reads business listings from Overture Places, or from OpenStreetMap once the operator connects a dedicated data service. Until then OpenStreetMap shows as unavailable; the service doesn’t lean on free community servers. Each source supplies its own names, contact routes and website fields. LeadLegWork filters and ranks them with a scoring method you can inspect, and every result names its source. Records from different providers stay separate: they aren’t merged, and one isn’t treated as confirming the other.
Source dates and, where supplied, Overture’s existence confidence help you judge a record. OpenStreetMap has no confidence score, and its snapshot date is when the data was fetched, not when the business was checked. None of these confirm a business’s current details. “No website listed” is a reason to look, not proof there isn’t one.
Google PageSpeed Insights, if the operator enables it
For a public website you choose, LeadLegWork can request a mobile or desktop Lighthouse report from Google PageSpeed Insights and show its performance, accessibility, best-practice and SEO scores, load metrics and suggested fixes.
Each report shows its test date and device. They’re lab measurements that vary between runs, not a promise about real visitors, search ranking or revenue.
Set up by the operator
This check measures a website; it doesn’t search Google Maps for businesses. The operator can add a server-side PageSpeed key. Customers don’t connect Google Cloud or supply Google Places keys in the current paid app. Without a dedicated key, checks can fail on shared quota, and a live check hasn’t yet been confirmed for this pilot. A failed request never turns into a score.
A check runs only when you choose “Run Google website check”, and it sends that page’s address to Google. Results for the same page are reused for 24 hours, with up to 20 new checks per workspace per UTC day.
Each prospect has links to search Google Maps or look for an official website. Confirm the right business, its contact details and whether there’s really an opportunity, with the business itself or its own site. Record where you confirmed each detail before it goes into a demo or a pitch.
Those research links simply open Google. They don’t call the Places API, import listing data or mark a lead as verified. No automated benchmark of contact accuracy has been run.
Questions about Google
Does the paid pilot use the Google Places API?
No. Discovery uses Overture or an operator-connected OpenStreetMap service. Customer-supplied Google Places keys aren’t supported. A specific Google workflow may be pursued after launch if Google permits it, but that isn’t announced or promised. PageSpeed checks are separate, and listings are never described as “Google-verified”.
Why is Google Places kept out?
Google Maps Platform restricts storing, exporting and reusing its content. A commercial Places workflow would need the right access and a design checked against those terms before launch. Google Maps Platform terms ↗
Are Google Cloud credits included?
No. LeadLegWork doesn’t provide Cloud credits or a monthly Google allowance, and the paid plan doesn’t include a customer Google Cloud connection. Any Google service the operator sets up has its own access and quota rules.
Are the leads more accurate than other tools’?
That hasn’t been measured. What the product offers today is evidence you can trace and one workflow from research to pitch. How it compares.