I do local SEO and automation work for clients, mostly US service businesses like roofers, restoration companies and realtors. Two jobs kept eating my time:
- Auditing Google Business Profiles. Is the listing claimed? Does it have a website, HTTPS, hours, enough reviews? Is the business name stuffed with keywords?
- Building prospect lists from Google Maps by copying names, phones and websites into a spreadsheet one at a time.
So I turned both into a Chrome extension: LocalPulse.
What it does
- Listing audit: open any Google Business Profile on Maps, click the "LP" button, and get a score out of 100 across 11 checks (claimed status, website, HTTPS, phone, hours, rating, review count, keyword-stuffed names).
- One-click CID copy: the Google CID, without digging through the page source.
- Prospect lists: run a Maps search and collect public listing details (name, category, rating, reviews, phone, website, address), then export to CSV.
The stack
- Extension: Manifest V3, vanilla JS. Content scripts read the Maps page directly. Extra listing data (photo counts, post recency, secondary categories) comes from Maps' own embedded place data, so no extra permissions are needed.
- License server: FastAPI on Render. It validates Dodo Payments license keys server-side and gives the extension a token that expires after 6 hours.
- Pro features run on the server: fix steps, competitor benchmark, reports and the email finder. A cracked copy of the extension unlocks nothing useful.
If Pro were just a flag stored inside the extension, anyone could bypass it in about five minutes. Moving the valuable logic server-side was the single best decision in this build.
The best feature came from a Reddit comment
After launch, someone pointed out that an audit tool shouldn't treat "probably wrong" the same as "definitely wrong". Every check is now either confirmed (full deduction) or verify (half deduction), and each one shows the evidence behind it. Scores feel much fairer, and clients trust the report more.
Bugs I only found by testing on live Maps
- Non-US Google domains (google.co.uk, google.ca) didn't match my URL patterns
- European number formats broke review-count parsing
- Google appends "ยท Visited link" to names you've clicked, which broke name matching
- Ads duplicated organic listings in lead exports
- Google Sheets read phone numbers starting with "+" as formulas
Unit tests didn't catch any of these. Test against the real page.
What went wrong outside the code
- Payment provider rejection. My first application was rejected because they classed the product as "services". What fixed it was a proper product page plus privacy, terms and refund policy pages. If you sell software, build those pages before you apply.
- Lead scraping triggers policy reviews. Expect questions from payment providers about any feature that collects data, even public listing data. Be ready to explain exactly what you collect and why.
- The Chrome Web Store has limits. My developer account caps me at 2 published extensions, so plan your product line around that.
- Store review takes time. Submit early and keep your permissions minimal. Every permission you request is one more thing a reviewer can question.
Free vs Pro
The free tier is useful on its own: the full audit score, all 11 checks, CID copy, 20 leads per search and CSV export.
Pro adds fix steps for failed checks, a top-10 competitor benchmark, a lead Opportunity Score (0-100) with bulk deep scan, branded PDF audit reports, auto-written pitch emails, unlimited leads, an email and social profile finder, Google Sheets export, and filters such as "no website" and "low reviews".
Pricing is $12/month or $99/year, plus a $59 lifetime launch deal. The lifetime deal exists to get early users and feedback rather than to maximize revenue.
Try it
๐ LocalPulse on the Chrome Web Store
More details: nnaveenkumar.com/localpulse
If you work in local SEO or build Chrome extensions, I'd love feedback, especially on which audit checks you'd add. Ask me anything about the build in the comments.
Top comments (0)