MapLeads

Frequently looked up

Q1Why not use the Google Places API instead?

The Google Places API licenses data for display only, not for keeping. Google's terms allow storing place IDs indefinitely but restrict caching of other content like latitude and longitude to 30 consecutive calendar days, after which deletion is required. MapLeads maintains its own dataset, so exports remain yours to keep, re-filter, and re-download permanently.

Q2Where do the email addresses come from?

MapLeads does not extract emails from the maps themselves; no maps source displays email addresses. Instead, MapLeads visits each business's own website to collect emails published there, verifies each address before delivery, and labels them as deliverable, role-based, catch-all, or dead. No addresses are dropped, including generic inboxes like info@, which often serve as the only contact for small local businesses.

Q3Can one search cover a whole country?

Yes. There is no cap on the number of results a search may return. A country-wide search takes longer than a single neighborhood but produces the same file format and runs on MapLeads' infrastructure rather than your machine. You can start the search and close the tab; a webhook fires when it completes.

Q4Is there a free trial?

No free trial is offered. Plans are billed when you subscribe and can be cancelled at any time. However, browsing the business database costs nothing before subscribing, allowing you to filter and preview results without charge.

Q5Is it legal to scrape Google Maps?

MapLeads collects business listing information that is already published in public — company name, category, address, phone, website, rating and review count — plus the contact details a business publishes on its own site. What you may then do with that list is a separate question, and it depends on where you and the recipient sit: the EU's GDPR treats a named person at a company as personal data, and commercial email in the US has to meet the CAN-SPAM Act's rules on identification and opt-out. Data being public does not waive either one.