Skip to content
https://ovh.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
80
GRADE
B
FIX
3
REVIEW
0
PASS
2
INFO
0
Checks
5
2 PASS 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.
Warning::
Missing og:description
The og:description tag controls the description in social sharing previews.
Warning::
Missing og:image
The og:image tag provides a preview image for social sharing.
Info::
og:title is short (8 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 8 chars Expected: 25–60 chars
Info::
Missing og:type
The og:type tag helps social platforms categorize the content.
Info::
Missing twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

The og:description tag controls the description in social sharing previews.

Why this matters

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.

Why this matters

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

URL: 8 chars

Ideal length is 25–60 characters for social sharing previews.

Expected: 25–60 chars
Why this matters

og:title very short — may render with awkward whitespace in social cards.

Source: Open Graph Protocol

The og:type tag helps social platforms categorize the content.

Why this matters

Default og:type is 'website' but the right value (article, product, profile) unlocks richer metadata fields and higher engagement.

Learn more

og:type controls which other og: fields a platform respects. og:type=article enables og:article:published_time, author, and section — surfaced in news cards. og:type=product enables price/availability fields surfaced by Pinterest and shopping integrations. Default 'website' silently disables those.

Source: Open Graph Protocol

Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

Why this matters

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

No image set

ovh.com

OVHcloud

No description

Preview quality · Twitter/X F · 20/100
  • 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 — 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)

No image set

OVH.COM

OVHcloud

No description

Preview quality · Facebook F · 45/100
  • og:title — OVHcloud
  • 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 — https://www.ovhcloud.com/fr/
  • og:site_name — OVHcloud
  • No preview image for Facebook

    → Add og:image (recommended 1200×630)

No image set

OVHcloud

ovh.com

Preview quality · LinkedIn D · 55/100

Description will be truncated (155 chars / 150 max)

  • og:title — OVHcloud
  • og:description — falling back from <meta name=description>
  • og:image — Add og:image — preview card without an image looks broken
  • Description will be truncated on LinkedIn (155 chars, max 150)

    → Tighten og:description to ≤150 characters

  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

ovh.com

OVHcloud

No description

Preview quality · Slack B · 75/100
  • og:title — OVHcloud
  • 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.

F · 48/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card
twitter:title
twitter:description
twitter:image
F
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.

F

34/100

Site name appears as

Page titleOVHcloud France
og:site_nameOVHcloud
twitter:site@OVHcloud_fr
Organization.name

Inconsistent — names differ across channels

Brand assets

Favicon

12/15

covers apple-touch-icon + SVG

Social share image

0/20

Meta completeness

8/20

Organization schema

4/15

Organization schema present but missing all recommended fields

Contact info discoverable

5/10

contact page

Findings

  • Brand name differs across channels — users see inconsistent identity
  • No social share image — shared links render as bare URLs
  • Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
  • og:image missing
  • twitter:card missing
  • Organization schema missing logo — add a logo property pointing to a square PNG
  • Organization schema missing url — point it at the canonical homepage
  • 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+
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
A+
Structured Data
1 JSON-LD block(s) found — structured data is well configured.
PASS
1 JSON-LD block(s) found — structured data is well configured.
Info::
Custom type "Corporation" — unable to validate specific properties

JSON-LD Blocks

Block 1 : Corporation
2 properties Valid
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Corporation",
      "name": "OVHcloud France",
      "sameAs": [
        "https://twitter.com/ovhcloud",
        "https://www.linkedin.com/company/ovh",
        "https://en.wikipedia.org/wiki/OVH",
        "https://www.wikidata.org/wiki/Q568183",
        "https://github.com/ovh"
      ],
      "url": "https://www.ovhcloud.com/fr/",
      "logo": {
        "@type": "ImageObject",
        "url": "https://www.ovhcloud.com/themes/contrib/ovh_theme_patternlab/images/logos/OVHcloud_logo.svg"
      }
    },
    {
      "@type": "WebSite",
      "name": "OVHcloud France",
      "url": "https://www.ovhcloud.com/fr/",
      "potentialAction": {
        "@type": "SearchAction",
        "query-input": "required name=query_string",
        "target": {
          "@type": "EntryPoint",
          "urlTemplate": "https://www.ovhcloud.com/fr/search-result/{query_string}",
          "inLanguage": "fr"
        }
      }
    }
  ]
}
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback