Skip to content
https://max.ru

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
81
GRADE
B
FIX
2
REVIEW
1
PASS
2
INFO
0
Checks
5
2 PASS 1 REVIEW 2 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.
Info::
og:title is long (75 characters)
Titles over 60 characters may be truncated in social sharing previews.
Got: 75 chars Expected: 25–60 chars
Info::
Missing og:url
The og:url tag specifies the canonical URL for the shared content.
Info::
Missing og:type
The og:type tag helps social platforms categorize the content.
Info::
Missing og:site_name
The og:site_name tag displays the website name in social previews.
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

URL: 75 chars

Titles over 60 characters may be truncated in social sharing previews.

Expected: 25–60 chars
Why this matters

og:title borderline-too-long — Facebook/LinkedIn may truncate. Aim for ~60-70 characters max.

Source: Open Graph Protocol

The og:url tag specifies the canonical URL for the shared content.

Why this matters

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.

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

The og:site_name tag displays the website name in social previews.

Why this matters

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

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

max.ru

MAX – быстрое и легкое приложение для общения и решения повседневных задач

No description

Preview quality · Twitter/X F · 40/100

Title will be truncated (136 chars / 70 max)

Description will be truncated (210 chars / 200 max)

  • 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 — falling back from og:image

  • twitter:card is missing

    → Add <meta name="twitter:card" content="summary_large_image">

  • Title will be truncated on Twitter/X (136 chars, max 70)

    → Shorten the title to ≤70 characters

  • Description will be truncated on Twitter/X (210 chars, max 200)

    → Tighten the description to ≤200 characters

MAX.RU

MAX – быстрое и легкое приложение для общения и решения повседневных задач

No description

Preview quality · Facebook F · 35/100

Title will be truncated (136 chars / 60 max)

Description will be truncated (210 chars / 155 max)

  • og:title — MAX – быстрое и легкое приложение для общения и решения повседневных задач
  • og:description — falling back from <meta name=description>
  • og:image — https://max.ru/s/img/og-logo.png
  • 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

  • Title will be truncated on Facebook (136 chars, max 60)

    → Shorten og:title to ≤60 characters

  • Description will be truncated on Facebook (210 chars, max 155)

    → Tighten og:description to ≤155 characters

  • og:image is too small for Facebook (50×50)

    → Upload an image at least 200×200 — recommended 1200×630 for large cards

MAX – быстрое и легкое приложение для общения и решения повседневных задач

max.ru

Preview quality · LinkedIn B · 80/100

Title will be truncated (136 chars / 120 max)

Description will be truncated (210 chars / 150 max)

  • og:title — MAX – быстрое и легкое приложение для общения и решения повседневных задач
  • og:description — falling back from <meta name=description>
  • og:image — https://max.ru/s/img/og-logo.png

  • Title will be truncated on LinkedIn (136 chars, max 120)

    → Shorten og:title to ≤120 characters

  • Description will be truncated on LinkedIn (210 chars, max 150)

    → Tighten og:description to ≤150 characters

  • og:image is too small for LinkedIn (50×50)

    → Upload an image at least 200×200

max.ru

MAX – быстрое и легкое приложение для общения и решения повседневных задач

No description

Preview quality · Slack A+ · 95/100
  • og:title — MAX – быстрое и легкое приложение для общения и решения повседневных задач
  • og:description — falling back from <meta name=description>
  • og:image — https://max.ru/s/img/og-logo.png

Social preview quality

Averaged across Twitter/X, Facebook, LinkedIn, and Slack.

D · 62/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

Partial brand coverage — a few channels are missing brand signals.

F

35/100

Site name appears as

Page titleбыстрое и легкое приложение для общения и решения повседневных задач
og:site_name—
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

8/15

single size only

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

8/20

Organization schema

0/15

Contact info discoverable

0/10

no contact info discoverable

Findings

  • Missing brand name in: og:site_name, twitter:site, Organization.name
  • 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
  • twitter:card 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.

C
Structured Data
Action
No structured data (JSON-LD) found.
REVIEW
No structured data (JSON-LD) found.
Info::
No structured data (JSON-LD) found
Adding structured data helps search engines understand your content and can enable rich results.

Adding structured data helps search engines understand your content and can enable rich results.

Why this matters

Without schema.org markup, your pages can't appear as rich results (stars, FAQs, recipes) in search.

Learn more ▾

Structured data is what unlocks rich snippets — review stars, FAQ accordions, recipe cards, breadcrumbs, etc. — that take up more SERP space and dramatically improve click-through. The schema.org vocabulary is well-documented and JSON-LD is the easiest format.

Source: Google Search Central / schema.org

No structured data found

Structured data (JSON-LD) helps search engines understand your content better. Adding it can improve your search result appearance.

Common types include:

  • WebSite — your site identity and search box
  • Organization — your company information
  • Article — blog posts and news articles
  • Product — e-commerce product pages
  • BreadcrumbList — navigation paths
Learn more at schema.org
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
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback