Skip to content
https://tuv.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
68
GRADE
D
FIX
3
REVIEW
1
PASS
1
INFO
0
Checks
5
1 PASS 1 REVIEW 3 FIX
D
Open Graph
Action
Open Graph tags need attention — social sharing previews may be incomplete.
FIX
Open Graph tags need attention — social sharing previews may be incomplete.
Critical::
og:image is not reachable
The og:image URL could not be fetched. Social platforms won't be able to display it.
Got: https://www.tuv.com/system-media-files/img/logo_en_transparent_svg.svg
Warning::
Missing og:title
The og:title tag controls the title shown in social sharing previews.
Info::
og:description is short (13 characters)
Ideal length is 55–200 characters for social sharing previews.
Got: 13 chars Expected: 55–200 chars
Info::
Missing og:url
The og:url tag specifies the canonical URL for the shared content.
Info::
Missing og:site_name
The og:site_name tag displays the website name in social previews.
URL: https://www.tuv.com/system-media-files/img/logo_en_transparent_svg.svg

The og:image URL could not be fetched. Social platforms won't be able to display it.

Why this matters

An unreachable og:image URL (404, DNS fail, slow timeout) means social platforms cache the failure and serve no image for hours.

Learn more ▾

Social platforms (Facebook, Twitter) cache OG metadata aggressively — including failed image fetches. A momentarily-broken og:image can leave your shares imageless for hours. Test og:image URLs in Facebook's Sharing Debugger to force re-cache after fixing.

Source: Open Graph Protocol / Facebook Sharing Debugger

The og:title tag controls the title shown in social sharing previews.

Why this matters

Without og:title, social shares fall back to the <title> tag — usually awkwardly truncated or branded for SEO not social.

Learn more ▾

og:title controls what appears as the headline in social-share cards (Twitter, Facebook, LinkedIn, Slack, iMessage). When omitted, platforms fall back to <title>, which is usually optimized for SEO (longer, brand-suffixed) and reads badly in social context. A 50-60-character og:title gives a clean preview.

Source: Open Graph Protocol

URL: 13 chars

Ideal length is 55–200 characters for social sharing previews.

Expected: 55–200 chars
Why this matters

og:description very short — provides little context in social cards.

Source: Open Graph Protocol

The og:url tag specifies the canonical URL for the shared content.

Why this matters

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.

Why this matters

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

Preview

tuv.com

No title set

TÜV Rheinland

Preview quality · Twitter/X A+ · 95/100
  • twitter:card — summary
  • twitter:title — falling back from <title>
  • twitter:description — TÜV Rheinland
  • twitter:image — https://www.tuv.com/system-media-files/img/logo_en_transparent_svg.svg

TUV.COM

No title set

TÜV Rheinland

Preview quality · Facebook C · 65/100
  • og:title — falling back from <title>
  • og:description — TÜV Rheinland
  • og:image — https://www.tuv.com/system-media-files/img/logo_en_transparent_svg.svg
  • 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

No title set

tuv.com

Preview quality · LinkedIn A+ · 95/100
  • og:title — falling back from <title>
  • og:description — TÜV Rheinland
  • og:image — https://www.tuv.com/system-media-files/img/logo_en_transparent_svg.svg

tuv.com

No title set

TÜV Rheinland

Preview quality · Slack A+ · 95/100
  • og:title — falling back from <title>
  • og:description — TÜV Rheinland
  • og:image — https://www.tuv.com/system-media-files/img/logo_en_transparent_svg.svg

Social preview quality

Averaged across Twitter/X, Facebook, LinkedIn, and Slack.

A · 87/100
FieldTwitter/XFacebookLinkedInSlack
og:title⚠⚠⚠
og:description
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description———
twitter:image———
D
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
FIX

Brand Presence

Your brand name differs across channels — visitors see inconsistent identity.

D

52/100

Site name appears as

Page titlephone-no-padding
og:site_name—
twitter:site@tuvcom_presse
Organization.name—

Inconsistent — names differ across channels

Brand assets

Favicon

8/15

single size only

Social share image

20/20

og:image + twitter:image set

Meta completeness

14/20

Organization schema

0/15

Contact info discoverable

5/10

contact page

Findings

  • Brand name differs across channels — users see inconsistent identity
  • Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
  • og:title 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.

C
Structured Data
Action
No structured data (JSON-LD) found.
REVIEW
No structured data (JSON-LD) found.
Info::
No structured data (JSON-LD) found
Adding structured data helps search engines understand your content and can enable rich results.

Adding structured data helps search engines understand your content and can enable rich results.

Why this matters

Without schema.org markup, your pages can't appear as rich results (stars, FAQs, recipes) in search.

Learn more ▾

Structured data is what unlocks rich snippets — review stars, FAQ accordions, recipe cards, breadcrumbs, etc. — that take up more SERP space and dramatically improve click-through. The schema.org vocabulary is well-documented and JSON-LD is the easiest format.

Source: Google Search Central / schema.org

No structured data found

Structured data (JSON-LD) helps search engines understand your content better. Adding it can improve your search result appearance.

Common types include:

  • WebSite — your site identity and search box
  • Organization — your company information
  • Article — blog posts and news articles
  • Product — e-commerce product pages
  • BreadcrumbList — navigation paths
Learn more at schema.org
A+
Mixed Content
No mixed content detected — all resources use HTTPS.
PASS
No mixed content detected — all resources use HTTPS.
Info::
No mixed content detected — all resources use HTTPS
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback