Find issues that hurt Google Maps and Google Business Profile visibility: NAP consistency, LocalBusiness schema, and local SEO signals. Add your listing details for a NAP comparison.
Heuristic checks — not the Google Business API · Optional GBP NAP comparison · No login required
Usually your homepage or contact / location page.
Most local pack issues involve name, address, or phone drift — paste what the public sees on Google to compare with your page.
Paste a full maps.google.com/…/place/… link to pre-fill the business name. Short goo.gl links and address/phone still need manual paste — we never call the Google API.
8 free checks left today
Free checks used for today. The limit resets at midnight in this website’s timezone.
View premium access optionsAnalysing…
Local SEO Score
NAP consistency, LocalBusiness schema, and on-page local signals from this URL.
Checks that moved your score up or down.
NAP, schema, and local on-page signals from this scan.
Premium
Have an access code? Export this result as a branded PDF (1 credit when a PDF renderer is configured; printable HTML is free), or start weekly email re-checks of this URL until the code expires. Premium does not change the scoring algorithm — same NAP checks as free.
Services
Structured data audits, NAP consistency, and rollout planning—beyond what a free checker can validate.
Simple process
Your homepage or a location/contact page usually carries the clearest NAP and LocalBusiness signals. No account or install required.
Paste a full Google Maps place URL to pre-fill the business name, then add the public address and phone. Short maps.app.goo.gl links cannot be expanded here — open them and copy the full place URL, or paste NAP text by hand. Without GBP fields, the tool cannot verify NAP against the local-pack listing.
A server-side, SSRF-safe fetch (the same infrastructure the AEO Readiness Checker uses) pulls the live HTML, then extracts LocalBusiness/Organization JSON-LD, microdata, tel: links, hreflang alternates, and plain-text phone numbers and address-like blocks from footer and contact regions, even when they carry no markup at all.
Each check lists a severity, what was found, and why it matters. If no GBP details were provided, the score is explicitly capped and labelled unverified rather than presenting a misleadingly high number.
NAP consistency is an important local trust and entity-resolution signal that businesses can verify directly.
NAP consistency means a business name, address, and phone number remain consistent across its public website, Google Business Profile, and structured data such as LocalBusiness JSON-LD. Consistent details help search and AI systems associate a page with the correct real-world entity, while also reducing customer confusion; they do not guarantee local rankings.
Drift happens quietly. A business moves office and updates the GBP listing, but a footer template still shows the old suite number. A phone number gets ported to a new provider and the JSON-LD is never touched. A regional franchise page inherits the parent company's address by copy-paste. None of these show up as a broken link or a 404 — they only show up as inconsistency between two sources that both look correct in isolation.
That inconsistency has two costs. First, ranking: Google's local algorithm treats consistent NAP across the web as a trust signal, and a mismatch between your own site and your own listing is the easiest inconsistency to fix — and the easiest one to be penalized for ignoring. Second, conversion: a visitor who calls the number in your footer and reaches a disconnected line, or drives to the address in your JSON-LD and finds a different suite, does not come back.
This free checker catches the technical half of that problem in seconds. For the ongoing half — rollout across multiple locations, structured-data audits, and monitoring after every template change — see our technical SEO and local schema work.
A rules-based 0–100 summary of measurable page, schema, language, and submitted NAP-alignment signals—not a Google ranking or local-pack forecast.
The score rewards complete LocalBusiness data, visible contact details, consistent submitted Google Business Profile information, and usable language signals. If you skip all GBP fields, the default score ceiling is 84 because listing alignment was not verified; the remaining technical findings are still valid.
Four signal groups, from raw markup to a real GBP comparison — and an honest list of what it deliberately does not claim to do.
Eyeballing two browser tabs misses the sources that do not render visually — JSON-LD, microdata, and hreflang.
Most teams "check" NAP consistency by opening the website and the Google Business Profile side by side and reading them. That catches obvious visible typos, but it cannot see what a browser does not render: a stale phone number inside LocalBusiness JSON-LD, a missing hreflang tag on the German version of the page, or an address baked into structured data that no longer matches the footer text next to it. This tool reads exactly what search engines and AI crawlers read.
| Checking by eye | Local SEO Checker | |
|---|---|---|
| What you compare | Your memory of what the listing says | The exact GBP text you paste, matched against your live page |
| What it reads on your site | Whatever is visible in your browser | JSON-LD, microdata, tel: links, and plain-text footer/contact copy |
| Multilingual sites | Easy to miss a missing hreflang tag on one locale | Flags html[lang] and hreflang presence directly |
| Speed | Several minutes per page, per locale | Seconds, repeatable after every edit |
Local SEO gets harder, not easier, once a second language or region enters the picture — each locale needs its own consistent NAP story, and mixed signals across locales confuse both classic local packs and AI answer engines about which entity (and which physical location) you mean.
Official and independent documentation (not endorsements of this tool):
Same SSRF-safe fetch infrastructure as the AEO checker, built for production sites, not a generic template.
The Local SEO Checker is built and maintained by Maksut — the same WordPress engineering and technical AEO practice behind the AEO Readiness Checker. Every check reflects a real signal we have seen affect local-pack visibility on production client sites: schema gaps, hreflang omissions, and NAP drift that only became obvious once someone compared the listing to the live page.
This is not the official Google Business Profile API and does not read data from your GBP dashboard — you decide what to paste, and nothing you paste is stored (see this site's privacy policy). Do not paste secrets or personal data you would not want logged. Results are heuristic checks, not a substitute for Search Console or a guarantee of ranking position.