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
sussex.ac.uk
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)
SUSSEX.AC.UK
No title set
No description
Title will be truncated (63 chars / 60 max)
- 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
Title will be truncated on Facebook (63 chars, max 60)
→ Shorten og:title to ≤60 characters
No preview image for Facebook
→ Add og:image (recommended 1200×630)
No title set
sussex.ac.uk
- 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)
sussex.ac.uk
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 | University of Sussex - a leading, research-intensive university | |
| 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.
BMixed Content1 HTTP resource(s) loaded on HTTPS pageREVIEW
http://purl.org/dc/terms/Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.
https://purl.org/dc/terms/Mixed content — HTTP resource on HTTPS page. Browser may block silently or warn user.
Source: Google Chrome Security
ALinks146 links checked, 143 healthy, 1 brokenPASS
Broken Links (1)
| Status | URL | Found in | Error |
|---|---|---|---|
| 999 | https://www.linkedin.com/school/university-of-suss... | <a> | HTTP 999 |
Redirects (2)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://sussex.ac.uk/disclaimer | http://www.sussex.ac.uk/about/website/di... | <link> | 5 |
| http://purl.org/dc/terms/ | https://www.dublincore.org/specification... | <link> | 5 |
AStructured Data2 JSON-LD block(s) found — structured data is well configured.PASS
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
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
JSON-LD Blocks
{
"@context": "http://schema.org",
"@type": "CollegeOrUniversity",
"url": "https://www.sussex.ac.uk/",
"name": "University of Sussex",
"location": {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"streetAddress": "Sussex House",
"addressLocality": "Brighton",
"postalCode": "BN1 9RH",
"addressRegion": "United Kingdom"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "50.8643619",
"longitude": "-0.0869846"
}
},
"logo": "https://www.sussex.ac.uk/images/logo.png",
"telephone": "01273 606755",
"sameAs": [
"https://www.facebook.com/uniofsussex",
"https://www.instagram.com/sussexuni/"
]
}{
"@context": "http://schema.org",
"@type": "WebSite",
"url": "https://www.sussex.ac.uk/",
"potentialAction": [
{
"@type": "SearchAction",
"target": "https://www.sussex.ac.uk/search/results?q={search_term_string}",
"query-input": "required name=search_term_string"
}
]
}