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://index.hu/assets/images/facebook_logo.png?v5The 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
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

index.hu
No title set
No description
- twitter:card — summary_large_image
- twitter:title — falling back from <title>
- twitter:description — falling back from <meta name=description>
- twitter:image — falling back from og:image

INDEX.HU
No title set
No description
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://index.hu/assets/images/facebook_logo.png?v5
- 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

No title set
index.hu
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://index.hu/assets/images/facebook_logo.png?v5
index.hu
No title set
No description

- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://index.hu/assets/images/facebook_logo.png?v5
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 | ⚠ | — | — | — |
DBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
D
42/100
Site name appears as
| Page title | friss hírek, események, tények | |
| og:site_name | — | |
| twitter:site | @indexhu | |
| Organization.name | — |
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
0/15Contact info discoverable
0/10no contact info discoverable
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
- og:title missing
- No Organization schema — Google can't render your logo in the knowledge panel
- No discoverable contact info — trust signal is weak, legal risk is higher in regulated regions
How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.
ALinks200 links checked, 198 healthy, 2 brokenPASS
Broken Links (2)
| Status | URL | Found in | Error |
|---|---|---|---|
| ERR | about:blank | <iframe> | Get "about:blank": unsupported protocol ... |
| 404 | https://indapass.hu/providerlogin/?url=https%3A%2F... | <a> | Not Found |
Redirects (3)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://dex.hu/x.php?id=fxdfejlec&url=ht... | https://dex.hu/x.php?id=fxdfejlec&url=ht... | <a> | 0 |
| https://indaplay.hu | https://indaplay.hu | <a> | 0 |
| https://dex.hu/x.php?id=inxindaplay&url=... | https://dex.hu/x.php?id=inxindaplay&url=... | <a> | 0 |
A+Mixed ContentNo mixed content detected — all resources use HTTPS.PASS
A+Structured Data1 JSON-LD block(s) found — structured data is well configured.PASS
JSON-LD Blocks
{
"@context": "http://schema.org",
"@type": "WebPage",
"name": "Index",
"url": "http://index.hu/",
"potentialAction": {
"@type": "SearchAction",
"target": "http://index.hu/24ora?s={search_term_string}",
"query-input": "required name=search_term_string"
}
}