Content
· 9 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
https://s7g10.scene7.com/is/image/eni/Opengraph-homepage-enicom-1:horizontal-16-9?&wid=1200&hei=630&fit=crop,1&bfc=onThe 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: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
The og:type tag helps social platforms categorize the content.
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
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
Preview
eni.com
Eni, an integrated energy company
No description
- twitter:card — summary_large_image
- twitter:title — falling back from og:title
- twitter:description — Add twitter:description to give the preview body text
- twitter:image — falling back from og:image
ENI.COM
Eni, an integrated energy company
No description
- og:title — Eni, an integrated energy company
- og:description — Add og:description to give the preview body text
- og:image — https://s7g10.scene7.com/is/image/eni/Opengraph-homepage-enicom-1:horizontal-16-9?&wid=1200&hei=630&fit=crop,1&bfc=on
- og:type — Add og:type — Recommended — tells Facebook the content category
- 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
Eni, an integrated energy company
eni.com
- og:title — Eni, an integrated energy company
- og:description — Add og:description to give the preview body text
- og:image — https://s7g10.scene7.com/is/image/eni/Opengraph-homepage-enicom-1:horizontal-16-9?&wid=1200&hei=630&fit=crop,1&bfc=on
eni.com
Eni, an integrated energy company
No description
- og:title — Eni, an integrated energy company
- og:description — Add og:description to give the preview body text
- og:image — https://s7g10.scene7.com/is/image/eni/Opengraph-homepage-enicom-1:horizontal-16-9?&wid=1200&hei=630&fit=crop,1&bfc=on
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 | ⚠ | — | — | — |
FImage OptimizationAction7 issues found across 77 imagesFIX
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
68/100
Site name appears as
| Page title | Filter Button | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | ENI |
Inconsistent — names differ across channels
Brand assets
Favicon
15/15covers multiple sizes, apple-touch-icon + SVG
Social share image
14/20og:image set; twitter:image missing
Meta completeness
14/20Organization schema
15/15has name, logo + url
Contact info discoverable
5/10contact page
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
- 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+Links200 links checked, 200 healthy, 0 brokenPASS
Redirects (1)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://yellow.eni.com | https://yellow.eni.com | <a> | 0 |
A+Mixed ContentNo mixed content detected — all resources use HTTPS.PASS
A+Open Graph / Twitter Card DepthOG image dimensions and Twitter card configuration look healthyPASS
A+Structured Data1 JSON-LD block(s) found — structured data is well configured.PASS
JSON-LD Blocks
{
"@context": "https://schema.org",
"@type": "Corporation",
"name": "ENI",
"alternateName": "Six-Legged Dog",
"url": "https://www.eni.com/",
"logo": "https://www.eni.com/content/dam/enicom/images/loghi/logoEni.svg"
}