Audit a business website for inconsistent names, addresses, and phone numbers. Compare visible page content with structured data, then standardize spelling and formatting to support accurate business information in local search.
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.
nap-consistency compares the names, addresses, and phone numbers published on a business website and identifies differences. These three fields are collectively called NAP. It checks spelling, address abbreviations, phone number separators, and how suite or unit numbers are written. The review covers both visible page text and LocalBusiness structured data, which communicates business information to search engines.
Use it to review local SEO for a business with a physical location, or when contact details appear in different formats across pages. It helps bring information scattered across footers, contact pages, and about pages into one consistent format.
LocalBusiness JSON-LD match the visible text.”This skill is intended for websites belonging to businesses with physical addresses. The material also explains consistency with Google Business Profile and external directories, but its concrete checking and correction steps focus mainly on information within the website.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
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.
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.
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.
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.
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/rules/seo/nap-consistency
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.