thedaviddias/front-end-checklist

nap-consistency

Use when auditing a local business website for local SEO. Applies to any business that has a physical address and wants to appear in local search results or Google Maps.

First seen Aug 9, 2026

Installation

$ npx skills add thedaviddias/front-end-checklist --skill nap-consistency

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from thedaviddias/front-end-checklist · top by installs.

npx skills add thedaviddias/front-end-checklist

Browse all from thedaviddias/front-end-checklist

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 74.1K
License MIT
Default branch main
Open issues 5
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
category
seo
priority
medium
difficulty
intermediate
estimatedTime
15
source
frontendchecklist.io
url
https://frontendchecklist.io/en/rules/seo/nap-consistency

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,458 B
  • docs SUMMARY.md 192 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 8 installs

SKILL.md

Keep NAP details consistent

Inconsistent NAP information across a website signals to search engines that the business details are unreliable, which can suppress local rankings and prevent the Knowledge Panel from showing accurate information.

Quick Reference

  • NAP = Name, Address, Phone — must be identical everywhere they appear on the site
  • Inconsistencies confuse search engines and hurt local ranking
  • Use identical formatting: same abbreviations, same phone format, same suite notation
  • Reinforce NAP consistency in LocalBusiness schema markup

Check

Search the site for all instances of the business name, street address, and phone number. Compare each occurrence for exact consistency in spelling, formatting, and abbreviation (e.g., 'St.' vs 'Street', '555-1234' vs '(555) 123-4567'). Also check JSON-LD LocalBusiness schema against the visible text.

Fix

Standardise all NAP occurrences to a single canonical-url format. Choose one format for each field: full street name vs abbreviation, phone number formatting, suite/unit notation. Update all pages, footer, contact page, about page, and structured data to match exactly.

Explain

NAP consistency is a local SEO ranking factor. Google cross-references a business's Name, Address, and Phone across the site and external citations (Google Business Profile, directories). When these differ even slightly, Google's confidence in the data decreases, which can lower local rankings and show incorrect information in search results.

Code Review

Extract all instances of the business name, street address, and phone number from the site. Compare each instance for exact formatting consistency: same abbreviations (St. vs Street), same phone format, same suite notation. Extract the address from any LocalBusiness JSON-LD and compare against visible HTML text. Report any differences.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/seo/nap-consistency