Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FOpen GraphActionOpen Graph tags need attention — social sharing previews may be incomplete.FIX
https://opentext.com/assets/images/OT_ShareImage_Facebook.pngThe og:image URL could not be fetched. Social platforms won't be able to display it.
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.
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
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: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
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
opentext.com
OpenText | Secure Information Management for AI
No description
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — OpenText | Secure Information Management for AI
- 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">
OPENTEXT.COM
OpenText | Secure Information Management for AI
No description
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://opentext.com/assets/images/OT_ShareImage_Facebook.png
- og:type — article
- og:url — Add og:url — Recommended — canonical URL for the share
- og:site_name — OpenText
OpenText | Secure Information Management for AI
opentext.com
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://opentext.com/assets/images/OT_ShareImage_Facebook.png
opentext.com
OpenText | Secure Information Management for AI
No description
- og:title — falling back from og:title
- og:description — falling back from <meta name=description>
- og:image — https://opentext.com/assets/images/OT_ShareImage_Facebook.png
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 Data2 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
JSON-LD Blocks
{
"@context": "https://schema.org/",
"@type": "Corporation",
"name": "OpenText",
"url": "https://www.opentext.com/",
"logo": "https://www.opentext.com/assets/images/opentext-logo-datatype.png",
"contactPoint": {
"@type": "ContactPoint",
"telephone": "1-800-540-7292",
"contactType": "customer service",
"contactOption": "TollFree"
},
"sameAs": [
"https://twitter.com/OpenText",
"https://www.youtube.com/user/opentextcorp",
"https://www.linkedin.com/company/opentext"
]
}{
"@context": "http://schema.org",
"@type": "Organization",
"name": "OpenText",
"legalName": "OpenText Corporation",
"url": "https://www.opentext.com/",
"logo": "https://www.opentext.com/assets/images/opentext-logo-datatype.png",
"description": "OpenText offers cloud-native solutions in an integrated and flexible Information Management platform to enable intelligent, connected and secure organizations.",
"foundingDate": "1991",
"address": {
"@type": "PostalAddress",
"streetAddress": "275 Frank Tompa Drive",
"addressLocality": "Waterloo",
"addressRegion": "ON",
"postalCode": "N2L 0A1",
"addressCountry": "CA"
},
"contactPoint": {
"@type": "ContactPoint",
"contactType": "customer service",
"telephone": "1-800-540-7292",
"contactOption": "TollFree"
},
"sameAs": [
"https://x.com/OpenText",
"https://www.youtube.com/user/opentextcorp",
"https://www.linkedin.com/company/opentext",
"https://www.instagram.com/_opentext/",
"https://www.bloomberg.com/profile/company/0366447Z:US",
"https://www.crunchbase.com/organization/opentext",
"https://en.wikipedia.org/wiki/OpenText"
],
"award": [
"Waterloo Area's Top Employers - 2025",
"Canada's Top Employers for Young People - 2025",
"World’s Top Companies for Women - 2024",
"Canada's Greenest Employers - 2024",
"Canada's Best Diversity Employers - 2024",
"Canada's Top 100 Employers - 2024",
"The World's Best Employers - 2024",
"World's Best Companies - 2024",
"Canada's Most Admired Corporate Cultures by Waterstone - 2021-2023"
]
}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
60/100
Site name appears as
| Page title | Secure Information Management for AI | |
| og:site_name | OpenText | |
| twitter:site | — | |
| Organization.name | OpenText |
Inconsistent — names differ across channels
Brand assets
Favicon
8/15single size only
Social share image
14/20og:image set; twitter:image missing
Meta completeness
8/20Organization schema
15/15has name, logo + url
Contact info discoverable
10/10contact page + tel 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
- Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
- og:title missing
- twitter:card missing
How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.