Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.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
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:url tag specifies the canonical URL for the shared content.
Without og:url, social platforms infer the canonical URL — often picking a tracking-param variant that pollutes share counts.
Learn more ▾ ▴
og:url tells the social platform which URL to count this share against. Without it, platforms use the literal URL the user pasted (which may include utm_* parameters, ref codes, etc.). Setting og:url to the canonical form keeps share-count attribution clean.
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
rki.de
Startseite
No description
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — falling back from og:title
- twitter:description — falling back from <meta name=description>
- twitter:image — falling back from og:image
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
RKI.DE
Startseite
No description
- og:title — Startseite
- og:description — falling back from <meta name=description>
- og:image — https://www.rki.de/SiteGlobals/Frontend/Images/logo.svg?__blob=normal&v=2
- og:type — website
- 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
Startseite
rki.de
- og:title — Startseite
- og:description — falling back from <meta name=description>
- og:image — https://www.rki.de/SiteGlobals/Frontend/Images/logo.svg?__blob=normal&v=2
rki.de
Startseite
No description
- og:title — Startseite
- og:description — falling back from <meta name=description>
- og:image — https://www.rki.de/SiteGlobals/Frontend/Images/logo.svg?__blob=normal&v=2
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 | ⚠ | — | — | — |
CBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsREVIEW
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
C
62/100
Site name appears as
| Page title | Startseite | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | Robert Koch-Institut |
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
8/20Organization schema
15/15has name, logo + url
Contact info discoverable
5/10mailto link
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
- twitter:card missing
- Consider adding contactPoint — helps appear in "contact us" rich results
- 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+Links182 links checked, 181 healthy, 0 brokenPASS
A+Mixed ContentNo mixed content detected — all resources use HTTPS.PASS
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 "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
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
{
"@type": "Organization",
"image": "https://www.rki.de/SiteGlobals/Frontend/Images/logo.svg?__blob=normal",
"description": "Weitere Informationen zum RKI",
"name": "Robert Koch-Institut",
"address": {
"@type": "PostalAddress",
"streetAddress": "Nordufer 20",
"addressLocality": "Berlin",
"postalCode": "13353",
"addressCountry": "DE",
"@context": "https://schema.org"
},
"telephone": "+49 30 18754 0",
"url": "https://www.rki.de",
"vatId": "DE 165 893 430",
"email": "webmaster@rki.de",
"logo": "https://www.rki.de/SiteGlobals/Frontend/Images/logo.svg?__blob=normal",
"@context": "https://schema.org"
}{
"@type": "WebSite",
"url": "https://www.rki.de",
"potentialAction": {
"@type": "SearchAction",
"target": {
"@type": "EntryPoint",
"urlTemplate": "https://www.rki.de/SiteGlobals/Forms/Suche/Expertensuche/Expertensuche_Formular.html?templateQueryString={search_term_string}",
"@context": "https://schema.org"
},
"query-input": "required name=search_term_string",
"@context": "https://schema.org"
},
"@context": "https://schema.org"
}