Content
· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FImage OptimizationAction4 issues found across 4 imagesFIX
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
36/100
Site name appears as
| Page title | Lioc | |
| og:site_name | Lioc | |
| twitter:site | — | |
| Organization.name | — |
Consistent
Brand assets
Favicon
8/15single size only
Social share image
0/20Meta completeness
8/20Organization schema
0/15Contact info discoverable
10/10contact page + tel link
Findings
- Missing brand name in: 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:image missing
- No Organization schema — Google can't render your logo in the knowledge panel
How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.
COpen GraphActionOpen Graph tags are partially configured — some improvements recommended.REVIEW
The og:description tag controls the description in social sharing previews.
No og:description means social cards either show no subtitle or scrape the first paragraph — usually unflattering.
Learn more ▾ ▴
Without og:description, social platforms either render no subtitle or pull whatever text appears first on the page. The first paragraph is rarely written for share-card context. A purpose-written 150-200 character og:description gives a polished card.
Source: Open Graph Protocol
The og:image tag provides a preview image for social sharing.
No og:image means social shares are imageless — measurably less engaging than image-cards across every major platform.
Learn more ▾ ▴
Twitter, Facebook, and LinkedIn all use og:image (or twitter:image as a fallback) for share-card thumbnails. Without one, the post renders as a text-only card. A 1200x630px image (Twitter's preferred size) covers all platforms.
Source: Open Graph Protocol
11 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
Preview
www.lioc.nl
Home - Lioc
No description
- twitter:card — summary_large_image
- twitter:title — falling back from og:title
- twitter:description — Add twitter:description to give the preview body text
- twitter:image — Add twitter:image — preview card without an image looks broken
No preview image for Twitter/X
→ Add og:image or twitter:image (≥300×157 for summary_large_image)
WWW.LIOC.NL
Home - Lioc
No description
- og:title — Home - Lioc
- og:description — Add og:description to give the preview body text
- og:image — Add og:image — preview card without an image looks broken
- og:type — website
- og:url — https://www.lioc.nl/en/
- og:site_name — Lioc
No preview image for Facebook
→ Add og:image (recommended 1200×630)
Home - Lioc
www.lioc.nl
- og:title — Home - Lioc
- og:description — Add og:description to give the preview body text
- og:image — Add og:image — preview card without an image looks broken
No preview image for LinkedIn
→ Add og:image (recommended 1200×627)
www.lioc.nl
Home - Lioc
No description
- og:title — Home - Lioc
- og:description — Add og:description to give the preview body text
- 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 | — | — | — |
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.lioc.nl/en/#website",
"url": "https://www.lioc.nl/en/",
"name": "Lioc",
"description": "Buitengewoon beschermd",
"potentialAction": [
{
"@type": "SearchAction",
"target": "https://www.lioc.nl/en/?s={search_term_string}",
"query-input": "required name=search_term_string"
}
],
"inLanguage": "en-US"
},
{
"@type": "WebPage",
"@id": "https://www.lioc.nl/en/#webpage",
"url": "https://www.lioc.nl/en/",
"name": "Home - Lioc",
"isPartOf": {
"@id": "https://www.lioc.nl/en/#website"
},
"datePublished": "2019-03-14T12:38:42+00:00",
"dateModified": "2021-05-26T16:17:34+00:00",
"breadcrumb": {
"@id": "https://www.lioc.nl/en/#breadcrumb"
},
"inLanguage": "en-US",
"potentialAction": [
{
"@type": "ReadAction",
"target": [
"https://www.lioc.nl/en/"
]
}
]
},
{
"@type": "BreadcrumbList",
"@id": "https://www.lioc.nl/en/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"item": {
"@type": "WebPage",
"@id": "https://www.lioc.nl/en/",
"url": "https://www.lioc.nl/en/",
"name": "Home"
}
}
]
}
]
}ALinks41 links checked, 40 healthy, 1 brokenPASS
Broken Links (1)
| Status | URL | Found in | Error |
|---|---|---|---|
| 429 | https://www.instagram.com/lioc_eindhoven/ | <a> | Too Many Requests |