Skip to main content

Business address is displayed in the UI

ab-001772 · marketing-local-seo.nap-business-info.address-displayed
Severity: highactive

Why it matters

An address present only in JSON-LD schema-org PostalAddress but absent from rendered HTML provides zero value to users and is less trusted by Google as a local relevance signal than visible, crawlable address text. Customers on a contact page who cannot find a physical address are more likely to bounce to a competitor with a clear location. For service businesses, a visible address also satisfies the trust threshold that converts first-time visitors — omitting it measurably degrades conversion on local landing pages.

Severity rationale

High because the absence of a visible address removes a primary user trust signal on contact and landing pages, directly hurting conversion for location-dependent businesses.

Remediation

Add the address to your src/components/footer.tsx using the HTML <address> element, which carries semantic meaning for user agents and screen readers.

// src/components/footer.tsx
import { BUSINESS } from "@/lib/business-info";

<address className="not-italic">
  {BUSINESS.address.street}<br />
  {BUSINESS.address.city}, {BUSINESS.address.state} {BUSINESS.address.zip}
</address>

The address should also appear on app/contact/page.tsx. Do not satisfy this check with address text inside an SVG or inside a display: none element.

Detection

  • ID: marketing-local-seo.nap-business-info.address-displayed

  • Severity: high

  • What to look for: Search for address data rendered in UI components. Check footer, contact page, and about page. The address should include street address, city, and state at minimum. Distinguish between an address truly displayed to users (in visible UI) versus only in JSON-LD (which is invisible to users but seen by crawlers).

  • Pass criteria: Count all visible address instances in the rendered UI. The full business address (at minimum 3 components: street, city, and state) is visible in at least 1 rendered UI location -- typically in the footer or on a contact/about page. The address being only in JSON-LD structured data does not satisfy this check.

  • Fail criteria: No address text found in any UI component, or address is present only in the JSON-LD schema but not in any user-visible HTML element.

  • Skip (N/A) when: Whole-audit N/A rule applies.

  • Detail on fail: "Business address not found in any rendered UI component (footer, contact page, etc.). Address may exist in JSON-LD only." or "Contact page exists but displays only a form — no address text rendered for users"

  • Remediation: Add the address to your src/components/footer.tsx using the semantic <address> element:

    <address>123 Main St, Springfield, OH 45501</address>
    

External references

Taxons

History