Content
· 5 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
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
Preview

viber.com
No title set
No description
- twitter:card — summary_large_image
- twitter:title — falling back from <title>
- twitter:description — Add twitter:description to give the preview body text
- twitter:image — falling back from og:image

VIBER.COM
No title set
No description
- og:title — falling back from <title>
- og:description — Add og:description to give the preview body text
- og:image — https://www.viber.com/app/uploads/geneic_2021_ogggeneric_logo.jpg
- og:type — website
- og:url — Add og:url — Recommended — canonical URL for the share
- og:site_name — Viber
og:image is below recommended size (600×600)
→ Upload an image ≥1200×630 for the large preview card

No title set
viber.com
- og:title — falling back from <title>
- og:description — Add og:description to give the preview body text
- og:image — https://www.viber.com/app/uploads/geneic_2021_ogggeneric_logo.jpg
viber.com
No title set
No description

- og:title — falling back from <title>
- og:description — Add og:description to give the preview body text
- og:image — https://www.viber.com/app/uploads/geneic_2021_ogggeneric_logo.jpg
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
Partial brand coverage — a few channels are missing brand signals.
D
52/100
Site name appears as
| Page title | Viber | |
| og:site_name | Viber | |
| twitter:site | @viber | |
| Organization.name | — |
Consistent
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
- Missing brand name in: Organization.name
- 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.
BLinks145 links checked, 142 healthy, 2 brokenREVIEW
Broken Links (2)
| Status | URL | Found in | Error |
|---|---|---|---|
| 404 | https://fonts.googleapis.com | <link> | Not Found |
| ERR | https://travel.rakuten.com/ | <a> | Get "https://travel.rakuten.com/": conte... |
Redirects (4)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://www.viber.com/en/business/ | https://www.viber.com/en/business/ | <a> | 0 |
| https://www.viber.com/en/business | https://www.viber.com/en/business | <a> | 0 |
| https://www.viber.com/gr/ | https://www.viber.com/gr/ | <a> | 0 |
| https://www.viber.com/cy/ | https://www.viber.com/cy/ | <a> | 0 |
BStructured Data1 JSON-LD block(s) found — some improvements recommended.REVIEW
The "name" property is required for the WebSite schema type.
Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.
Learn more ▾ ▴
Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.
Source: Google Search Central / schema.org
The "url" property is required for the WebSite schema type.
Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.
Learn more ▾ ▴
Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.
Source: Google Search Central / schema.org
Adding "description" can improve how search engines display your content.
Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.
Learn more ▾ ▴
Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.
Source: Google Search Central / schema.org
Adding "potentialAction" can improve how search engines display your content.
Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.
Learn more ▾ ▴
Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.
Source: Google Search Central / schema.org
JSON-LD Blocks
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "WebSite",
"@id": "https://www.viber.com/en/#website",
"url": "https://www.viber.com/en/",
"name": "Viber",
"description": "Free calls, text and picture sharing with anyone, anywhere!",
"potentialAction": [
{
"@type": "SearchAction",
"target": "https://www.viber.com/en/?s={search_term_string}",
"query-input": "required name=search_term_string"
}
],
"inLanguage": "en-US"
},
{
"@type": [
"WebPage",
null
],
"@id": "#webpage",
"url": "",
"name": "",
"isPartOf": {
"@id": "https://www.viber.com/en/#website"
},
"inLanguage": "en-US",
"potentialAction": [
{
"@type": "ReadAction",
"target": [
""
]
}
]
}
]
}