Google Maps Scraper
Google Maps scraper for lead generation.
Install
npx skills add Mahanaicoach/google-maps-scraper-kit --skill google-maps-scraper -g -a claude-code -y- Repository
- Mahanaicoach/google-maps-scraper-kit2.1k
- Category
- DevOps
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Google Maps scraper for lead generation. Turns a business type and a place into a clean CSV of local businesses by driving the kit's own Google Maps engine, running locally (with Python and a headless Chrome, or in Docker) as a REST API on localhost:8080. Returns 8 lead fields by default (name, phone, email, website, category, address, rating and review count), plus social profiles by default (Instagram, Facebook, LinkedIn, TikTok, YouTube, X; `--no-socials` skips them), row filters such as businesses without a website, or all 36 raw fields. Use when the user wants a lead list, "a list of [businesses] in [place]", local business data, contact enrichment for places (emails, phones, socials), or a whole-city run past Google's ~120 results per search. Do not use for scraping Instagram, TikTok, YouTube, X or any other social media platform directly.
Google Maps Scraper
Turn a business type and a location into clean lead rows with the kit's own script,
scripts/scrape.py, which drives the local engine's job API for you.
Mental model
The kit's engine runs on this machine (python3 scripts/engine.py start, or a Docker container) with
a REST API at http://localhost:8080. It is bound to localhost and refuses requests from other
websites; it needs no key unless SCRAPER_API_KEY is set in the kit's .env. A scrape is an async
job: the script creates it, waits for it, collects its rows from the local engine, enriches them
(emails, socials) and writes one CSV. One job can run many keywords. Each result has up to 36 raw fields, plus
categories.
Port. The URLs in this file show port 8080. Use the port python3 scripts/engine.py status
printed, or SCRAPER_PORT from the kit's .env (default 8080), wherever a URL is needed.
The only commands this skill runs are the kit's own, from the kit folder: python3 scripts/engine.py status (then start, or docker compose up -d when the user runs Docker) and python3 scripts/scrape.py …
(py instead of python3 on Windows). No command is ever built from a scraped value, and nothing is
fetched from a URL found in the results.
