Audit LocalBusiness markup
Inspect raw HTML for LocalBusiness types and the key properties supplied for a location or service-area business.
Local SEO Checker
Free, no signup. Check raw LocalBusiness markup and visible NAP/service-area clues on one public page. The report keeps this page audit separate from profile and directory consistency.
Checks run from our server; we fetch the URL you enter and don't keep the results. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
Sample report Deterministic detector example
Raw HTML containing LocalBusiness JSON-LD, “123 Main Street,” “+1 555 111 2222,” and “Serving Boston” returns:
Local schema: LocalBusiness-style schema found.
Visible NAP: Visible phone and address signals found.
Service area: Visible service-area signal found.
How to use it
- Enter the public location or contact page that should carry the business details.
- Select Audit and review all three independent findings.
- Confirm warnings in the page source and rendered page before changing markup.
- Audit Google Business Profile and third-party directory consistency separately.
+ saves the current site or page. Use ☆ beside any saved site, page, or list to favorite it. Recent check history appears below.
Create a named list
Target filled from your local choices.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Rate this tool
What the results mean
- Local schema — checks for three supported business-type strings in raw HTML.
- Visible NAP — passes when both phone-like and street-address-like text are present.
- Service area — passes on visible “service area” or “serving” wording; absence is informational.
- Not evaluated — required document evidence was unavailable, never a negative verdict.
How it works
The protected fetch endpoint retrieves public HTML, which is parsed into a document context. Three deterministic detectors inspect the serialized markup and normalized body text. No model, map result, profile API, or directory database contributes to the findings.
Features
- One-page raw-HTML audit.
- Separate schema, NAP, and service-area findings.
- Visible summaries instead of a composite local score.
- No login or business-profile authorization.
Limitations
The schema check recognizes only LocalBusiness, Restaurant, and Store strings. Phone and address recognition is intentionally simple and does not compare normalized business identities. The tool does not validate JSON-LD syntax, rendered content, opening hours, map rankings, reviews, proximity, directory citations, or profile ownership.
Frequently asked questions
What local SEO signals does this checker inspect?
It checks for LocalBusinessLocalBusiness schema (schema.org/LocalBusiness) is structured data — usually JSON-LD — that describes a physical business to search engines: its name, address, phone, hours, geo-coordinates, and price range. Google requires only name and address, consumes about a dozen recommended properties, and treats it as a corroborating signal, not a substitute for a Google Business Profile.-, Restaurant-, or Store-style schema, a visible phone-and-address combination, and wording such as service area or serving in the raw HTML.
Does it audit my Google Business Profile?
No. It does not connect to Google Business Profile, Maps, reviews, categories, hours, photos, or verification state.
What does incomplete NAP mean?
The raw page text did not contain both a phone-like number and a simple street-address pattern. That is a review prompt, not proof that the business data is missing or incorrect.
Can it compare citations across directories?
No. The checker fetches one page only and does not compare names, addresses, or phone numbers with directories or other sites.
Why might a JavaScript site get a warning?
The audit uses fetched raw HTML. Business details inserted only after JavaScript runs may not appear, so verify rendered output separately.
Feature requests for Local Seo Checker
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Where this tool helps
Common use cases
Compare visible NAP details
Review whether the visible name, address, and phone information agrees with the structured data.
Check service-area signals
Find missing or conflicting locality and service-area details that need human confirmation.
Preflight a location-page template
Test a representative page before rolling a schema or NAP change across many locations.
Watch the full workflow
Local SEO Checker walkthrough
Read the transcript
Local SEO Checker
A location page should present consistent business identity signals to people and crawlers. This checker looks for supported local-business schema strings, visible phone and street-address clues, and service-area wording in raw H-T-M-L. I’ll show the three findings, practical use cases, evidence limits, and the profile and citation checks to do next.
Step 1
Use this checker for a storefront, office, restaurant, or service-area landing page before launch, after template changes, or while investigating inconsistent business details across public surfaces.
Step 2
Choose the page that should carry the business details for the relevant location. The audit reads public raw H-T-M-L, so script-injected contact information or schema may need separate rendered inspection.
Step 3
This walkthrough enters a fictional business dot example location U-R-L and does not make a live fetch. In normal use, select Audit and interpret each finding independently rather than treating one passing row as an overall verdict.
Step 4
This clearly labeled fictional report shows three independent observations. The patterns are intentionally simple; confirm the exact business identity and visible customer-facing details before changing production data.
Step 5
The schema row recognizes LocalBusiness, Restaurant, and Store type strings in raw H-T-M-L. It does not validate J-S-O-N-L-D syntax, properties, identifiers, or whether the entity matches the real business.
Step 6
Visible N-A-P passes when phone-like and street-address-like text are both present. The detector does not normalize formats or compare a canonical business identity across pages and directories.
Step 7
The service-area row looks for visible phrases such as service area or serving. Absence is informational because not every business needs a service-area statement on every page.
Step 8
Separate schema, visible contact details, and service-area findings help narrow investigation while avoiding a single composite score that could hide missing evidence.
Step 9
Deterministic detectors inspect the fetched raw document for a bounded set of business-type, phone, address, and service-area patterns. They do not call maps, profiles, or directory providers.
Step 10
When a fetch is truncated or required document evidence is unavailable, observed positives may remain useful, but absence and clean-page claims are not evaluated. Inspect the raw source and rendered page directly.
Step 11
Schema recognition covers only three supported type strings, and phone and address detection is intentionally simple. The tool does not validate rendered content, opening hours, identity consistency, reviews, citations, ownership, proximity, maps, or local rankings.
Step 12
Confirm the rendered page and full schema, then reconcile name, address, phone, hours, categories, and service areas with the owned business profile and authoritative directories. Test calls, directions, and the location-page experience, then monitor actual local results.
Use the page audit as one part of local consistency.
Correct confirmed page-level gaps, then compare the exact name, address, phone, hours, categories, and service areas with Google Business Profile and authoritative directories. Validate complete schema and the rendered page, confirm ownership and landing-page behavior, and monitor real local visibility. This tool does not measure rankings, reviews, or proximity.
Common issues & how to fix them
- Warning LocalBusiness schema is missing Fix: Add valid LocalBusiness JSON-LD with the specific subtype, name, address, telephone, URL, and applicable opening hours.
- Warning Visible name, address, or phone signals are incomplete Fix: Display a consistent business name, postal address, and local phone number in crawlable page content and structured data.
- Information Visible service-area signal is missing Fix: State the cities or regions served in visible copy and represent the service area accurately in LocalBusiness markup where applicable.