Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.BLinks200 links checked, 197 healthy, 3 brokenREVIEW
Broken Links (3)
| Status | URL | Found in | Error |
|---|---|---|---|
| ERR | https://usps.com/manage/informed-delivery.htm | <a> | Get "https://usps.com/manage/informed-de... |
| ERR | https://usps.com/assets/images/welcome/premium/id-... | <img> | Get "https://usps.com/assets/images/welc... |
| ERR | https://usps.com/assets/images/welcome/featured/25... | <img> | Get "https://usps.com/assets/images/welc... |
Redirects (1)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://verified.usps.com/login?goto=htt... | https://verified.usps.com/login?goto=htt... | <a> | 0 |
BOpen GraphOpen Graph tags are partially configured — some improvements recommended.REVIEW
https://www.usps.com/assets/images/welcome/usps-homepage.jpgThe og:image URL could not be fetched. Social platforms won't be able to display it.
An unreachable og:image URL (404, DNS fail, slow timeout) means social platforms cache the failure and serve no image for hours.
Learn more ▾ ▴
Social platforms (Facebook, Twitter) cache OG metadata aggressively — including failed image fetches. A momentarily-broken og:image can leave your shares imageless for hours. Test og:image URLs in Facebook's Sharing Debugger to force re-cache after fixing.
Source: Open Graph Protocol / Facebook Sharing Debugger
14 charsIdeal length is 25–60 characters for social sharing previews.
25–60 charsog:title very short — may render with awkward whitespace in social cards.
Source: Open Graph Protocol
222 charsDescriptions over 200 characters may be truncated in social sharing previews.
55–200 charsog:description borderline-too-long — social platforms truncate around ~200 chars.
Source: Open Graph Protocol
The og:site_name tag displays the website name in social previews.
Without og:site_name, social cards omit the brand attribution — users see the post but not who published it.
Learn more ▾ ▴
og:site_name appears in the social card chrome (above the title in Facebook/LinkedIn previews). Without it, posts read as anonymous URLs. Set it to your brand name to get free attribution on every share.
Source: Open Graph Protocol
Preview

usps.com
Welcome | USPS
Welcome to USPS.com. Track packages, pay and print postage with Click-N-Ship, schedule free package pickups, look up ZIP Codes, calculate postage prices, and find everything you need for sending mail and shipping packages.
Description will be truncated (222 chars / 200 max)
- twitter:card — summary
- twitter:title — Welcome | USPS
- twitter:description — Welcome to USPS.com. Track packages, pay and print postage with Click-N-Ship, schedule free package pickups, look up ...
- twitter:image — https://www.usps.com/assets/images/welcome/usps-homepage.jpg
Description will be truncated on Twitter/X (222 chars, max 200)
→ Tighten the description to ≤200 characters

USPS.COM
Welcome | USPS
Welcome to USPS.com. Track packages, pay and print postage with Click-N-Ship, schedule free package pickups, look up ZIP Codes, calculate postage prices, and find everything you need for sending mail and shipping packages.
Description will be truncated (222 chars / 155 max)
- og:title — Welcome | USPS
- og:description — Welcome to USPS.com. Track packages, pay and print postage with Click-N-Ship, schedule free package pickups, look up ...
- og:image — https://www.usps.com/assets/images/welcome/usps-homepage.jpg
- og:type — article
- og:url — https://www.usps.com/
- og:site_name — Add og:site_name — Recommended — site-level brand line in the preview
Description will be truncated on Facebook (222 chars, max 155)
→ Tighten og:description to ≤155 characters

Welcome | USPS
usps.com
Description will be truncated (222 chars / 150 max)
- og:title — Welcome | USPS
- og:description — Welcome to USPS.com. Track packages, pay and print postage with Click-N-Ship, schedule free package pickups, look up ...
- og:image — https://www.usps.com/assets/images/welcome/usps-homepage.jpg
Description will be truncated on LinkedIn (222 chars, max 150)
→ Tighten og:description to ≤150 characters
usps.com
Welcome | USPS
Welcome to USPS.com. Track packages, pay and print postage with Click-N-Ship, schedule free package pickups, look up ZIP Codes, calculate postage prices, and find everything you need for sending mail and shipping packages.

- og:title — Welcome | USPS
- og:description — Welcome to USPS.com. Track packages, pay and print postage with Click-N-Ship, schedule free package pickups, look up ...
- og:image — https://www.usps.com/assets/images/welcome/usps-homepage.jpg
Social preview quality
Averaged across Twitter/X, Facebook, LinkedIn, and Slack.
| Field | Twitter/X | Slack | ||
|---|---|---|---|---|
| og:title | ||||
| og:description | ||||
| og:image | ||||
| og:type | ||||
| og:url | ||||
| og:site_name | ||||
| twitter:card | — | — | — | |
| twitter:title | — | — | — | |
| twitter:description | — | — | — | |
| twitter:image | — | — | — |
CStructured DataAction1 JSON-LD block(s) found — some improvements recommended.REVIEW
JSON parse error: Mismatch type map[string]interface {} with value array "at index 0: mismatched type with value\n\n\t[{\"@context\":\"http://schema.org\"\n\t^...............................\n"
JSON-LD block fails to parse — Google ignores the entire block, so structured data effectively isn't there.
Learn more ▾ ▴
Common causes: trailing comma, single quotes instead of double, unescaped quote in a string value. Validate at https://validator.schema.org/ or Search Console's Rich Results Test.
Source: schema.org / Google Search Central
JSON-LD Blocks
[
{
"@context": "http://schema.org",
"@id": "https://www.usps.com/#organization",
"@type": "Organization",
"legalName": "United States Postal Service",
"alternateName": "USPS",
"url": "https://www.usps.com/",
"logo": "https://www.usps.com/global-elements/header/images/utility-header/logo-sb.svg",
"contactPoint": [
{
"@type": "ContactPoint",
"telephone": "+1-800-222-1811",
"contactType": "package tracking",
"availableLanguage": [
"EN",
"ES"
],
"contactOpintion": "TollFree",
"areaServed": "US"
},
{
"@type": "ContactPoint",
"telephone": "+1-800-275-8777",
"contactType": "customer service",
"contactOption": "TollFree",
"availableLanguage": [
"EN",
"ES"
],
"areaServed": "US"
},
{
"@type": "ContactPoint",
"telephone": "+1-800-877-8339",
"contactType": "customer service",
"contactOption": [
"HearingImpairedSupported",
"TollFree"
],
"availableLanguage": "EN",
"areaServed": "US"
},
{
"@type": "ContactPoint",
"telephone": "+1-800-344-7779",
"contactType": "technical support",
"areaServed": "US",
"availableLanguage": [
"EN",
"ES"
]
}
],
"sameAs": [
"https://www.facebook.com/USPS",
"https://twitter.com/usps",
"http://www.pinterest.com/uspsstamps/",
"https://www.youtube.com/usps"
]
},
{
"@context": "http://schema.org",
"@id": "https://www.usps.com/#webpage",
"@type": "WebPage",
"url": "https://www.usps.com/"
},
{
"@context": "http://schema.org",
"@id": "https://www.usps.com/#website",
"@type": "WebSite",
"url": "https://www.usps.com/",
"name": "USPS",
"potentialAction": {
"@type": "SearchAction",
"target": "https://www.usps.com/searchesults.htm?keyword={search_term_string}",
"query-input": "required name=search_term_string"
}
}
]CBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsREVIEW
Brand Presence
Partial brand coverage — a few channels are missing brand signals.
C
67/100
Site name appears as
| Page title | USPS | |
| og:site_name | — | |
| twitter:site | @USPS | |
| Organization.name | — |
Consistent
Brand assets
Favicon
8/15single size only
Social share image
20/20og:image + twitter:image set
Meta completeness
20/20Organization schema
4/15Organization schema present but missing all recommended fields
Contact info discoverable
5/10contact page
Findings
- Missing brand name in: og:site_name, Organization.name
- Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
- Organization schema missing logo — add a logo property pointing to a square PNG
- Organization schema missing url — point it at the canonical homepage
- Consider adding contactPoint — helps appear in "contact us" rich results
- Only partial contact info discoverable — consider adding a dedicated contact page or mailto/tel link
How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.