القائمة
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.
| name | nap-consistency |
| description | 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. |
| metadata | {"category":"seo","priority":"medium","difficulty":"intermediate","estimatedTime":"15","source":"frontendchecklist.io","url":"https://frontendchecklist.io/en/rules/seo/nap-consistency"} |
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/en/rules/seo/nap-consistency
Use when reviewing templates, rendered HTML, or shared components related to Implement accessible breadcrumb navigation. Validate the final browser-facing markup, not just the source framework abstraction.
Use when auditing metadata, crawlability, structured data, or indexability related to Implement valid BreadcrumbList schema. Verify the rendered HTML and HTTP response rather than relying only on source files.
Use when reviewing templates, rendered HTML, or shared components related to Declare UTF-8 character encoding. Validate the final browser-facing markup, not just the source framework abstraction.
Use when reviewing templates, rendered HTML, or shared components related to Set text direction for RTL languages. Validate the final browser-facing markup, not just the source framework abstraction.
Use when auditing a site's meta tag uniqueness, generating page-specific meta descriptions, or reviewing CMS templates that inject the same description globally.
Use when you need to find the 2-3 most popular and well-maintained npm packages relevant to a frontend checklist rule, validate they meet quality thresholds, and add them to the rule's frontmatter.
