Test ContactTap: postal address formats

ContactTap · The address gauntlet

What this page tests. Addresses are the hardest thing a contact scanner reads — there is no single format, and half the world writes them differently. Each section feeds the scanner one real-world layout. found rows should appear in the popup; known miss rows document real formats the current patterns don't cover yet — honestly, and used as the working list for improvements.

1 · Default-country pin (structured data)

This block pins the page's default phone region to US, exactly like the primary test page. Expected: one ordinary found card, with the address assembled from its parts.

2 · Semantic <address> elements

The HTML <address> tag is how well-built pages mark contact blocks. ContactTap trusts it when it looks postal (contains a digit); pure author-credit uses are ignored.

3 · Addresses inside map links (“Directions” buttons)

Many hotel and venue pages never print their address as text — it lives only inside a maps link. The page authored that link as deliberately as a tel: link, so ContactTap reads it.

4 · Postal addresses in plain text — the format gauntlet

This is the section the address scanner earns its keep on. US addresses anchored on street-suffix + city + state + ZIP and UK addresses anchored on the postcode are expected finds; the “known miss” rows document real formats the current patterns don't cover, so improvements can be checked against this same page.

← Back to the primary test page · Scam patterns test page →