Skip to content

thedaviddias/Front-End-Checklist / skills/physical-address

physical-address

Verified

Use when auditing local business websites, e-commerce sites, or any site where a physical presence affects trust or local search visibility.

FileKindSize
SKILL.mdskill md2.2 KB
references/rule.mdmarkdown3.7 KB

references/rule.md

View on GitHub
# Display a physical business address

> Checks for visible physical address information

**Priority:** medium · **Difficulty:** beginner · **Time:** 10 min

---
A physical address on your website serves multiple purposes: it establishes trust with users, satisfies legal disclosure requirements, and is a key signal for local SEO.

## Code Examples

```html
<!-- ✅ Good: Complete address in <address> element -->
<address>
  <strong>Acme Corporation</strong><br />
  123 Main Street, Suite 4<br />
  Springfield, IL 62701<br />
  United States<br />
  <a href="tel:+15551234567">(555) 123-4567</a><br />
  <a href="mailto:info@acme.com">info@acme.com</a>
</address>
```

```html
<!-- ❌ Bad: Address in generic div, no semantic markup -->
<div class="footer-contact">
  123 Main St. | Springfield | IL
</div>
```

## Why It Matters

A visible physical address builds user trust (especially for e-commerce and YMYL sites), supports local SEO rankings, and is a requirement for compliance in many jurisdictions.

## Where to Display the Address

| Location | Required? |
|----------|----------|
| Contact page | Yes |
| Footer (every page) | Strongly recommended |
| About page | Recommended |
| LocalBusiness schema | Yes (structured data) |

## With HTML Microdata

```html
<div itemscope itemtype="https://schema.org/LocalBusiness">
  <span itemprop="name">Acme Corporation</span>
  <address itemprop="address" itemscope itemtype="https://schema.org/PostalAddress">
    <span itemprop="streetAddress">123 Main Street, Suite 4</span><br />
    <span itemprop="addressLocality">Springfield</span>,
    <span itemprop="addressRegion">IL</span>
    <span itemprop="postalCode">62701</span><br />
    <span itemprop="addressCountry">US</span>
  </address>
  <a itemprop="telephone" href="tel:+15551234567">(555) 123-4567</a>
</div>
```

## JSON-LD (Preferred)

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Acme Corporation",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main Street, Suite 4",
    "addressLocality": "Springfield",
    "addressRegion": "IL",
    "postalCode": "62701",
    "addressCountry": "US"
  },
  "telephone": "+1-555-123-4567"
}
</script>
```

## Address Format Consistency

The address displayed on the page must exactly match:
1. Your Google Business Profile
2. Your LocalBusiness JSON-LD schema
3. Any other directory listings (Yelp, Yellow Pages, etc.)

Even minor differences like `St.` vs `Street` reduce local SEO confidence.

## Legal Requirements

Many jurisdictions require websites to display a business address:
- EU: Required under the e-Commerce Directive and various national laws
- UK: Required under The Electronic Commerce Regulations 2002
- US: Required for certain regulated industries and e-commerce

Always display the registered business address, not a PO Box for these purposes.

## Exceptions

- Local SEO guidance only applies when the business actually serves a geographic area or has public location information relevant to searchers.
- Service-area businesses may need service-area guidance instead of storefront-focused address markup or location-page patterns.
- Do not invent addresses, business categories, or geographic claims to satisfy local SEO recommendations; accuracy overrides completeness.

## Verification

### Automated Checks

- Inspect rendered HTML and HTTP headers to confirm the expected metadata or crawlability signal is present.
- Test the affected URL with Google Search Console or equivalent tooling where relevant.
- Re-crawl a representative page set after deployment.

### Manual Checks

- Confirm the change does not create conflicting canonical-url, robots, or structured-data signals.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall