Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DOpen GraphActionOpen Graph tags need attention — social sharing previews may be incomplete.FIX
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
10 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
The og:site_name tag displays the website name in social previews.
Without og:site_name, social cards omit the brand attribution — users see the post but not who published it.
Learn more ▾ ▴
og:site_name appears in the social card chrome (above the title in Facebook/LinkedIn previews). Without it, posts read as anonymous URLs. Set it to your brand name to get free attribution on every share.
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
sika.com
Sika Group
No description
- twitter:card — Add <meta name="twitter:card" content="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
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)
SIKA.COM
Sika Group
No description
- og:title — Sika Group
- 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.sika.com
- 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)
Sika Group
sika.com
- og:title — Sika Group
- 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)
sika.com
Sika Group
No description
- og:title — Sika Group
- 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
https://schema.org/The @context should be "https://schema.org" for search engines to recognize the data.
https://schema.orgJSON-LD without @context is invalid structured data — Google ignores the entire block.
Learn more ▾ ▴
@context must be 'https://schema.org' (or the schema-specific URL). Without it, the block isn't parseable as schema.org JSON-LD and Google skips it. Most schema generators handle this; manual edits sometimes drop the field.
Source: JSON-LD spec / schema.org
Adding "sameAs" 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
{
"@type": "Organization",
"@context": "https://schema.org/",
"url": "https://www.sika.com",
"name": "Sika Group",
"telephone": "+41 58 436 6800",
"logo": "/content/dam/media/sika-global/logo/Sika_NoClaim_pos_rgb_mobile.png",
"address": {
"@type": "PostalAddress",
"streetAddress": "Zugerstrasse 50",
"addressLocality": "Baar (ZG)",
"addressRegion": "Switzerland",
"postalCode": " CH-6340",
"addressCountry": "corp"
}
}CBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsREVIEW
Brand Presence
Partial brand coverage — a few channels are missing brand signals.
C
58/100
Site name appears as
| Page title | Sika Group | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | Sika Group |
Consistent
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
0/20Meta completeness
8/20Organization schema
15/15has name, logo + url
Contact info discoverable
10/10contact page + tel link
Findings
- Missing brand name in: og:site_name, twitter:site
- No social share image — shared links render as bare URLs
- og:image missing
- twitter:card missing
- Consider adding contactPoint — helps appear in "contact us" rich results
How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.