Physical address: PostalAddress and LocalBusiness schema
A real address is a trust signal a visitor can verify. squirrel looks for address structured data across the crawl.
What the address signal is
A publicly listed address tells a visitor there is a place and an entity behind the site. For a business with premises it is also what feeds local search results and map listings, where the address is the thing being matched.
Structured data is what makes it machine-readable. PostalAddress describes the address itself, and it is normally attached to a LocalBusiness or Organization node that says whose address it is.
What squirrel checks
The rule is site-wide. It walks the crawled pages looking for two things in the list of schema types the parser collected: PostalAddress, and any of LocalBusiness, Organization, Restaurant or Store. That list covers top-level and @graph nodes, so a PostalAddress nested as an address property does not satisfy the first test on its own. It emits a single check named physical-address:
- Skipped when no pages were crawled. Message:
No pages available for analysis. - Pass when either was found. Message:
Address schema markup found, withLocalBusiness/OrganizationorPostalAddressas the value. - Info when neither was. Message:
No address schema markup detected, withAdd PostalAddress schema if applicableas the value.
The check reads structured data only. An address printed in the footer as plain text is not detected, and an Organization node with no address at all passes, since the type alone satisfies the second test. Severity info, weight 3.
The rule only runs when the audit classified the site as a local business. A classification below medium confidence, or an audit with no site metadata at all, runs it anyway.
How to fix it
{"@context":"https://schema.org","@type":"LocalBusiness","name":"Acme","address":{"@type":"PostalAddress","streetAddress":"12 Example St","addressLocality":"Sydney","addressRegion":"NSW","postalCode":"2000","addressCountry":"AU"}}Publish the address in the footer or on the contact page and mark it up as a PostalAddress on the node that owns it. Keep the name, address and phone identical to what your directory and map listings say.
An online-only business can list a registered office. The point is that something is verifiable.
| Rule ID | eeat/physical-address |
| Category | E-E-A-T |
| Scope | Site-wide |
| Severity | info |
| Weight | 3/10 |
Enable / disable
Disable this rule
[rules]
disable = ["eeat/physical-address"]Disable all E-E-A-T rules
[rules]
disable = ["eeat/*"]Enable only this rule
[rules]
enable = ["eeat/physical-address"]enable replaces the default ["*"], so this is the only rule selected. Leave disable out: a rule that matches any disable pattern is skipped even when enable names it. Only an enabled setting under a rule’s own [rule_options] table overrides both lists.
Related rules
- schema/local-business: the full local business markup this address belongs to.
- local/nap-consistency: whether the same details appear consistently across the site.
- eeat/contact-page: the page the address usually sits on.
- links/tel-mailto: the phone number that goes with it.
E-E-A-T findings ship in every audit next to the SEO, performance and agent experience rules. See Fix SEO issues with AI for how an agent works through a report.
References
Check your site
Run squirrel audit https://example.com and open the E-E-A-T section of the report. The site is reported with the address schema types found. Signed-out local audits need no account and cost nothing. Signed-in audits spend credits.