Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DLinksAction200 links checked, 193 healthy, 7 brokenFIX
Broken Links (7)
| Status | URL | Found in | Error |
|---|---|---|---|
| 404 | https://www.apple.com/wss/fonts | <link> | Not Found |
| 404 | https://www.apple.com/wss/fonts?families=SF+Pro,v4... | <link> | Not Found |
| 429 | https://apps.apple.com/us/app/paramount/id53016816... | <a> | Too Many Requests |
| 429 | https://apps.apple.com/ml/iphone/today | <a> | Too Many Requests |
| 429 | https://apps.apple.com/mr/iphone/today | <a> | Too Many Requests |
| 429 | https://apps.apple.com/ma/iphone/today | <a> | Too Many Requests |
| 429 | https://apps.apple.com/np/iphone/today | <a> | Too Many Requests |
BOpen GraphOpen Graph tags are partially configured — some improvements recommended.REVIEW
https://apps.apple.com//assets/images/share/app-store.pngThe 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
The og:type tag helps social platforms categorize the content.
Default og:type is 'website' but the right value (article, product, profile) unlocks richer metadata fields and higher engagement.
Learn more ▾ ▴
og:type controls which other og: fields a platform respects. og:type=article enables og:article:published_time, author, and section — surfaced in news cards. og:type=product enables price/availability fields surfaced by Pinterest and shopping integrations. Default 'website' silently disables those.
Source: Open Graph Protocol
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.
Without twitter:card, Twitter renders posts as plain text — no preview image, no structured layout.
Learn more ▾ ▴
Twitter requires `<meta name="twitter:card" content="summary_large_image">` (or summary) to render share-cards at all. Without it, links appear as raw text and engagement plummets vs cards. Twitter also falls back to og:image if twitter:image isn't set, so configure both.
Source: Twitter Developer Platform
Preview
apps.apple.com
Today for iPhone - App Store
Find apps and games for iPhone, iPad, Mac, and more on the App Store.
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — Today for iPhone - App Store
- twitter:description — Find apps and games for iPhone, iPad, Mac, and more on the App Store.
- twitter:image — https://apps.apple.com//assets/images/share/app-store.png
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
APPS.APPLE.COM
Today for iPhone - App Store
Find apps and games for iPhone, iPad, Mac, and more on the App Store.
- og:title — Today for iPhone - App Store
- og:description — Find apps and games for iPhone, iPad, Mac, and more on the App Store.
- og:image — https://apps.apple.com//assets/images/share/app-store.png
- og:type — Add og:type — Recommended — tells Facebook the content category
- og:url — https://apps.apple.com/us/iphone/today
- og:site_name — App Store
Today for iPhone - App Store
apps.apple.com
- og:title — Today for iPhone - App Store
- og:description — Find apps and games for iPhone, iPad, Mac, and more on the App Store.
- og:image — https://apps.apple.com//assets/images/share/app-store.png
apps.apple.com
Today for iPhone - App Store
Find apps and games for iPhone, iPad, Mac, and more on the App Store.
- og:title — Today for iPhone - App Store
- og:description — Find apps and games for iPhone, iPad, Mac, and more on the App Store.
- og:image — https://apps.apple.com//assets/images/share/app-store.png
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 | — | — | — |
BBrand PresenceSite-name consistency, favicon, social image, meta tags, schema, and contact signalsREVIEW
Brand Presence
Partial brand coverage — a few channels are missing brand signals.
B
84/100
Site name appears as
| Page title | App Store | |
| og:site_name | App Store | |
| twitter:site | @AppStore | |
| Organization.name | App Store |
Consistent
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
20/20og:image + twitter:image set
Meta completeness
14/20Organization schema
15/15has name, logo + url
Contact info discoverable
0/10no contact info discoverable
Findings
- twitter:card missing
- Consider adding contactPoint — helps appear in "contact us" rich results
- No discoverable contact info — trust signal is weak, legal risk is higher in regulated regions
How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.
A+Mixed ContentNo mixed content detected — all resources use HTTPS.PASS
A+Structured Data1 JSON-LD block(s) found — structured data is well configured.PASS
JSON-LD Blocks
{
"@context": "https://schema.org",
"@id": "https://apps.apple.com/#organization",
"@type": "Organization",
"name": "App Store",
"url": "https://apps.apple.com",
"logo": "https://apps.apple.com/assets/app-store.png",
"sameAs": [
"https://www.wikidata.org/wiki/Q368215",
"https://twitter.com/AppStore",
"https://www.instagram.com/appstore/",
"https://www.facebook.com/appstore/"
],
"parentOrganization": {
"@type": "Organization",
"name": "Apple",
"@id": "https://www.apple.com/#organization",
"url": "https://www.apple.com/"
}
}