Local SEO Software/Live

Website Audit

Audit any landing page on your site against the on-page signals that matter for local search. Every audit cross-references the page content against your Google Business Profile NAP — so the name, phone, and address customers see online actually match the listing Google ranks. Most audit tools score a page in isolation. We score it against the listing it's meant to support.

See pricing
82/100
On-Page Basics
95
Local Relevance
75
Schema
65
Technical
90
Business name
Phone (matches GBP)
Postcode

Why it's different

Built for the way local SEO actually works

NAP cross-referenced with your GBP

We compare the business name, phone, address, and postcode on the page against the canonical NAP on your Google Business Profile. Mismatches are flagged as critical — they're the single biggest local-SEO own-goal.

Local relevance, not generic SEO

Checks whether the city, service, and primary keyword appear in the title, H1, and meta description. Generic site auditors miss these because they don't know the location — we do.

Core Web Vitals + Lighthouse

Optional Lighthouse audit adds Performance, Accessibility, Best Practices, and SEO scores plus LCP, CLS, and INP. Toggle it on per audit — you only pay when you need it.

Action plan ranked by severity

Every failing check is grouped into an action plan and ordered by severity — critical, warning, info. Plus an AI-written summary calling out the highest-impact fixes first.

The differentiator

Cross-references your page against your Google Business Profile

Inconsistent NAP is the most common reason local pages underperform. Customers see one phone number on the page, Google sees another on the GBP listing, and the algorithm treats them as separate entities. Every other site auditor scores the page in isolation — we score it against the listing.

  • Business name fuzzy-matched against the page text and the H1
  • Phone matched on the last 9–10 digits, so '+44 20 7946 0000' and '020 7946 0000' both pass
  • Postcode normalised then substring-matched (UK and US patterns supported)
  • Street address verified by street-number + first-token presence
  • Critical-severity issue raised when phone or name is missing or different from the GBP record
82/100
On-Page Basics
95
Local Relevance
75
Schema
65
Technical
90
Business name
Phone (matches GBP)
Postcode

How it's scored

Five categories, weighted to local-search reality

Each audit returns a 0–100 score made up of five category scores. The categories are weighted by what actually moves local rankings, not what looks good on a generic SEO checklist.

  • On-Page Basics — title length, meta description, single H1, canonical, language attribute
  • Local Relevance — city in title and H1, NAP consistency, primary service in title
  • Schema — LocalBusiness JSON-LD detected, Open Graph tags present
  • Technical — HTTPS, no 4xx/5xx, no redirect chains, image alt coverage, page weight under 3 MB, no render-blocking resources
  • Performance (Lighthouse-only) — Performance score ≥ 70, LCP < 2.5s, CLS < 0.1, SEO and Accessibility scores
82/100
On-Page Basics
95
Local Relevance
75
Schema
65
Technical
90
Business name
Phone (matches GBP)
Postcode

Single-URL by design

One page, scored properly. Not 800 pages, scored shallowly.

Most local businesses have under 50 pages, and the pages that matter for local search are a small subset — the homepage and the city/service landing pages. Site-wide crawls take hours, drown you in low-priority issues, and miss the local-specific signals that actually rank. We chose depth over breadth.

  • Homepage, city pages, service pages, location pages — audit each one with the location it's meant to support
  • Re-audit after each round of fixes to verify the score moved — results land in under a minute
  • No async polling, no crawl queues, no 'come back tomorrow' — single live API call
82/100
On-Page Basics
95
Local Relevance
75
Schema
65
Technical
90
Business name
Phone (matches GBP)
Postcode

How it works

Three steps from signup to insight

1

Pick a location

Select any location in your workspace. The audit will use that location's GBP NAP as the canonical reference.

2

Choose a URL

Defaults to the website on the GBP record, but you can audit any page — a service page, a city page, an offer page. Toggle Lighthouse on if you want performance scoring.

3

Work the action plan

Score lands with categorised issues, an AI summary, and a NAP-vs-GBP card. Fix the critical items first. Re-run to verify the lift.

Credits

Audit cost

Pay for what you run. The base audit is 5 credits; adding Lighthouse is +5. Most plans cover hundreds of audits per month — effectively unlimited for the typical agency.

  • 5 credits per audit (Instant Pages only)
  • 10 credits per audit (with Lighthouse)
  • Starter plan: up to 1,000 audits per month at the base tier
See pricing

FAQ

Website Audit. Questions we get

Around 25 individual checks across five categories: On-Page Basics (title, meta description, H1, canonical), Local Relevance (city and service keywords in critical fields, NAP consistency vs your GBP), Schema (LocalBusiness JSON-LD, Open Graph), Technical (HTTPS, broken pages, redirects, image alt coverage, page weight, render-blocking resources), and Performance (only when Lighthouse is enabled). Each check has a documented point value and severity.

NAP stands for Name, Address, Phone — the three identity fields that prove to Google that the website and the Google Business Profile refer to the same entity. When they don't match, Google has reduced confidence in the listing and ranks it lower. We compare the page text against the canonical NAP on your GBP record, with fuzzy matching that tolerates phone formatting differences. Mismatched phone or business name is flagged critical because it's the single most common reason local pages underperform.

Lighthouse adds Performance, Accessibility, Best Practices, and SEO scores plus Core Web Vitals (LCP, CLS, INP). Add it when you suspect a page is slow, when the GBP audit shows healthy ranking signals but conversions are still poor, or when you're auditing a high-value landing page where mobile performance directly affects bookings. For routine on-page checks, the base audit is enough.

Yes — the audit accepts any URL. The NAP cross-reference will compare the competitor page against your GBP NAP though, which won't make sense, so treat that section as informational when auditing third-party pages. The on-page, schema, and technical scoring still applies.

Most local businesses have under 50 pages, and the pages that move local rankings are a small subset — the homepage and the city/service landing pages. Full-site crawls take hours, drown you in low-priority issues, and rarely change the action list. We chose depth over breadth: pick the page that matters and audit it properly. Site-wide crawl is a candidate for a future paid add-on, not the default tool.

On-page metrics come from DataForSEO's On-Page API (the Instant Pages endpoint, with optional Lighthouse). Page text for NAP matching is fetched directly so we have the full body to grep against — DataForSEO's response doesn't include raw HTML by default. Canonical NAP comes from the location record in your workspace, which you set when you connect your Google Business Profile. The AI summary is generated by Anthropic Claude (Haiku 4.5).

Run an audit on every page change, on a monthly cadence to catch silent regressions (third-party plugins, theme updates, accidental NAP changes), and immediately after any GBP NAP change so the page can be brought back into alignment. Track the score over time the same way you'd track a GBP score — it should trend up as you work the fix list.

Start tracking your real rankings today

See where you actually rank on Google Maps, not where Google tells you. Get started free with 250 credits.