Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.BLinks110 links checked, 107 healthy, 3 brokenREVIEW
Broken Links (3)
| Status | URL | Found in | Error |
|---|---|---|---|
| 404 | https://www.googletagmanager.com/gtag/js?id=G-W21F... | <script> | Not Found |
| 403 | https://fpf.org/xmlrpc.php?rsd | <link> | Forbidden |
| 429 | https://www.instagram.com/futureofprivacy/ | <a> | Too Many Requests |
Redirects (6)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://ajax.googleapis.com | https://ajax.googleapis.com | <link> | 0 |
| https://fpf.org/fpf-training-program-202... | https://fpf.org/fpf-training-program-202... | <a> | 0 |
| https://fpf.org/issue/ai-ml/ | https://fpf.org/issue/ai-ml/ | <a> | 0 |
| https://fpf.org/about/eu/ | https://fpf.org/about/eu/ | <a> | 0 |
| https://fpf.org/issue/global/ | https://fpf.org/issue/global/ | <a> | 0 |
| https://fpf.org/issue/heath-data/ | https://fpf.org/issue/heath-data/ | <a> | 0 |
BBrand PresenceSite-name consistency, favicon, social image, meta tags, schema, and contact signalsREVIEW
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
B
74/100
Site name appears as
| Page title | The Future of Privacy Forum | |
| og:site_name | Future of Privacy Forum | |
| twitter:site | @futureofprivacy | |
| Organization.name | Future of Privacy Forum |
Inconsistent — names differ across channels
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
14/20og:image set; twitter:image missing
Meta completeness
20/20Organization schema
15/15has name, logo + url
Contact info discoverable
5/10contact page
Findings
- Brand name differs across channels — users see inconsistent identity
- Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
- 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.
A+Mixed ContentNo mixed content detected — all resources use HTTPS.PASS
A+Open GraphOpen Graph tags are well configured for social sharing.PASS
237 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
Preview
fpf.org
The Future of Privacy Forum
Future of Privacy Forum and the FPF Education and Innovation Foundation are non-profit organizations that serve as catalysts for privacy leadership and scholarship, advancing principled data practices in support of emerging technologies.
Description will be truncated (237 chars / 200 max)
- twitter:card — summary_large_image
- twitter:title — The Future of Privacy Forum
- twitter:description — Future of Privacy Forum and the FPF Education and Innovation Foundation are non-profit organizations that serve as ca...
- twitter:image — falling back from og:image
Description will be truncated on Twitter/X (237 chars, max 200)
→ Tighten the description to ≤200 characters
FPF.ORG
The Future of Privacy Forum
Future of Privacy Forum and the FPF Education and Innovation Foundation are non-profit organizations that serve as catalysts for privacy leadership and scholarship, advancing principled data practices in support of emerging technologies.
Description will be truncated (237 chars / 155 max)
- og:title — The Future of Privacy Forum
- og:description — Future of Privacy Forum and the FPF Education and Innovation Foundation are non-profit organizations that serve as ca...
- og:image — https://fpf.org/wp-content/uploads/2020/09/favicon.ico
- og:type — website
- og:url — https://fpf.org/
- og:site_name — Future of Privacy Forum
Description will be truncated on Facebook (237 chars, max 155)
→ Tighten og:description to ≤155 characters
og:image is too small for Facebook (16×16)
→ Upload an image at least 200×200 — recommended 1200×630 for large cards
The Future of Privacy Forum
fpf.org
Description will be truncated (237 chars / 150 max)
- og:title — The Future of Privacy Forum
- og:description — Future of Privacy Forum and the FPF Education and Innovation Foundation are non-profit organizations that serve as ca...
- og:image — https://fpf.org/wp-content/uploads/2020/09/favicon.ico
Description will be truncated on LinkedIn (237 chars, max 150)
→ Tighten og:description to ≤150 characters
og:image is too small for LinkedIn (16×16)
→ Upload an image at least 200×200
fpf.org
The Future of Privacy Forum
Future of Privacy Forum and the FPF Education and Innovation Foundation are non-profit organizations that serve as catalysts for privacy leadership and scholarship, advancing principled data practices in support of emerging technologies.
- og:title — The Future of Privacy Forum
- og:description — Future of Privacy Forum and the FPF Education and Innovation Foundation are non-profit organizations that serve as ca...
- og:image — https://fpf.org/wp-content/uploads/2020/09/favicon.ico
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 | ⚠ | — | — | — |
A+Structured Data2 JSON-LD block(s) found — structured data is well configured.PASS
Adding "potentialAction" can improve how search engines display your content.
Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.
Learn more ▾ ▴
Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.
Source: Google Search Central / schema.org
JSON-LD Blocks
{
"@context": "https:\/\/schema.org",
"@type": "WebSite",
"name": "Future of Privacy Forum",
"alternateName": "Future of Privacy Forum",
"description": "",
"url": "https:\/\/fpf.org"
}{
"@context": "https:\/\/schema.org",
"@type": "Organization",
"name": "Future of Privacy Forum",
"url": "https:\/\/fpf.org",
"alternateName": "Future of Privacy Forum",
"description": "Future of Privacy Forum",
"logo": "https:\/\/fpf.org\/wp-content\/uploads\/2023\/06\/Future-of-Privacy-Forum.jpg",
"sameAs": [
"https:\/\/www.facebook.com\/FutureofPrivacy",
"https:\/\/x.com\/@futureofprivacy",
"https:\/\/www.instagram.com\/futureofprivacy",
"https:\/\/youtube.com\/@FutureofPrivacy",
"https:\/\/www.linkedin.com\/company\/the-future-of-privacy-forum\/"
],
"contactPoint": [
{
"@type": "ContactPoint",
"contactType": "customer support"
}
]
}