Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FOpen GraphActionNo Open Graph tags found — social sharing previews will be generic.FIX
Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.
Without Open Graph tags, social shares show a broken or empty preview card.
Learn more ▾ ▴
When someone shares your URL on Facebook, LinkedIn, Slack, iMessage, or any modern chat app, the preview comes from <meta property="og:*"> tags. Without them you get either no card or whatever fragment the social platform guesses — usually unflattering. The four core og: tags (title, description, image, url) cover what every major platform actually reads.
Source: Open Graph Protocol
Preview
wri.org
No title set
No description
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — falling back from <title>
- twitter:description — falling back from <meta name=description>
- twitter:image — Add twitter:image — preview card without an image looks broken
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
No preview image for Twitter/X
→ Add og:image or twitter:image (≥300×157 for summary_large_image)
WRI.ORG
No title set
No description
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — Add og:image — preview card without an image looks broken
- og:type — Add og:type — Recommended — tells Facebook the content category
- og:url — Add og:url — Recommended — canonical URL for the share
- og:site_name — Add og:site_name — Recommended — site-level brand line in the preview
No preview image for Facebook
→ Add og:image (recommended 1200×630)
No title set
wri.org
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — Add og:image — preview card without an image looks broken
No preview image for LinkedIn
→ Add og:image (recommended 1200×627)
wri.org
No title set
No description
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — Add og:image — preview card without an image looks broken
No preview image — Slack unfurl will be text-only
→ Add og:image or twitter:image
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 | — | — | — |
FBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Partial brand coverage — a few channels are missing brand signals.
F
22/100
Site name appears as
| Page title | Click to see more | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | — |
Consistent
Brand assets
Favicon
8/15single size only
Social share image
0/20Meta completeness
4/20Organization schema
0/15Contact info discoverable
5/10contact page
Findings
- Missing brand name in: og:site_name, twitter:site, Organization.name
- No social share image — shared links render as bare URLs
- Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
- og:title missing
- og:image missing
- twitter:card missing
- No Organization schema — Google can't render your logo in the knowledge panel
- 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.
BStructured Data1 JSON-LD block(s) found — some improvements recommended.REVIEW
The "name" property is required for the WebSite schema type.
Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.
Learn more ▾ ▴
Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.
Source: Google Search Central / schema.org
The "url" property is required for the WebSite schema type.
Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.
Learn more ▾ ▴
Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.
Source: Google Search Central / schema.org
Adding "description" 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
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",
"@graph": [
{
"@type": "WebSite",
"@id": "https://www.wri.org/",
"name": "World Resources Institute",
"url": "https://www.wri.org/",
"publisher": {
"@type": "Organization",
"@id": "https://www.wri.org/",
"name": "World Resource Institute",
"url": "https://www.wri.org/",
"sameAs": [
"http://www.facebook.com/pages/World-Resources-Institute/61863318139",
"http://twitter.comworldresources",
"http://www.youtube.com/WorldResourcesInst",
"https://www.linkedin.com/company/world-resources-institute/"
],
"logo": {
"@type": "ImageObject",
"representativeOfPage": "True",
"url": "https://www.wri.org/profiles/contrib/wri_sites/themes/custom/ts_wrin/logo.png",
"width": "150",
"height": "53"
}
}
}
]
}ALinks153 links checked, 151 healthy, 2 brokenPASS
Broken Links (2)
| Status | URL | Found in | Error |
|---|---|---|---|
| 403 | https://wri.org/resources/type/initiatives-30003 | <a> | Forbidden |
| 403 | https://wri.org/resources/type/insights-50 | <a> | Forbidden |
Redirects (3)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://wri.org/forests | https://wri.org/forests | <a> | 0 |
| https://wri.org/economics | https://wri.org/economics | <a> | 0 |
| https://wri.org/business | https://wri.org/business | <a> | 0 |