Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DLinksAction99 links checked, 92 healthy, 6 brokenFIX
Broken Links (6)
| Status | URL | Found in | Error |
|---|---|---|---|
| 404 | https://suggest.sso.dzen.ru | <link> | Not Found |
| 404 | https://suggest.dzen.ru | <link> | Not Found |
| 403 | https://dzen.ru/ | <link> | Forbidden |
| 410 | https://avatars.mds.yandex.net | <link> | HTTP 410 |
| 404 | https://mc.yandex.ru | <link> | Not Found |
| 400 | https://ads.adfox.ru | <link> | Bad Request |
Redirects (1)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://sportsdzen.ru/topic/sport | https://sportsdzen.ru/api/sportsdzen-sso... | <a> | 5 |
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
47/100
Site name appears as
| Page title | главная новостная информационная платформа, которая помогает миллионам людей узнавать, что происходит в мире. | |
| og:site_name | Дзен | |
| twitter:site | — | |
| Organization.name | — |
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
8/20Organization schema
0/15Contact info discoverable
5/10tel 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
- twitter:card missing
- No Organization schema — Google can't render your logo in the knowledge panel
- 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.
BOpen GraphOpen Graph tags are partially configured — some improvements recommended.REVIEW
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
81 charsTitles over 60 characters may be truncated in social sharing previews.
25–60 charsog:title borderline-too-long — Facebook/LinkedIn may truncate. Aim for ~60-70 characters max.
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

dzen.ru
Статьи, новости и видео от популярных блогеров и СМИ | Будь в теме — будь в Дзене
Оставайтесь в курсе актуальных событий и следите за любимыми темами — от спорта до путешествий, от стиля до технологий. А умные алгоритмы порекомендуют контент с учётом ваших интересов
Title will be truncated (145 chars / 70 max)
Description will be truncated (340 chars / 200 max)
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — falling back from og:title
- twitter: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 (145 chars, max 70)
→ Shorten the title to ≤70 characters
Description will be truncated on Twitter/X (340 chars, max 200)
→ Tighten the description to ≤200 characters

DZEN.RU
Статьи, новости и видео от популярных блогеров и СМИ | Будь в теме — будь в Дзене
Оставайтесь в курсе актуальных событий и следите за любимыми темами — от спорта до путешествий, от стиля до технологий. А умные алгоритмы порекомендуют контент с учётом ваших интересов
Title will be truncated (145 chars / 60 max)
Description will be truncated (297 chars / 155 max)
- og:title — Статьи, новости и видео от популярных блогеров и СМИ | Будь в теме — будь в Дзене
- og:description — falling back from <meta name=description>
- og:image — https://s3.dzeninfra.ru/zen/opengraph/general.png
- og:type — website
- og:url — https://dzen.ru/
- og:site_name — Дзен
Title will be truncated on Facebook (145 chars, max 60)
→ Shorten og:title to ≤60 characters
Description will be truncated on Facebook (297 chars, max 155)
→ Tighten og:description to ≤155 characters

Статьи, новости и видео от популярных блогеров и СМИ | Будь в теме — будь в Дзене
dzen.ru
Title will be truncated (145 chars / 120 max)
Description will be truncated (297 chars / 150 max)
- og:title — Статьи, новости и видео от популярных блогеров и СМИ | Будь в теме — будь в Дзене
- og:description — falling back from <meta name=description>
- og:image — https://s3.dzeninfra.ru/zen/opengraph/general.png
Title will be truncated on LinkedIn (145 chars, max 120)
→ Shorten og:title to ≤120 characters
Description will be truncated on LinkedIn (297 chars, max 150)
→ Tighten og:description to ≤150 characters
dzen.ru
Статьи, новости и видео от популярных блогеров и СМИ | Будь в теме — будь в Дзене
Оставайтесь в курсе актуальных событий и следите за любимыми темами — от спорта до путешествий, от стиля до технологий. А умные алгоритмы порекомендуют контент с учётом ваших интересов

Description will be truncated (340 chars / 300 max)
- og:title — Статьи, новости и видео от популярных блогеров и СМИ | Будь в теме — будь в Дзене
- og:description — falling back from og:description
- og:image — https://s3.dzeninfra.ru/zen/opengraph/general.png
Long description may be shortened by Slack (340 chars, guideline ~300)
→ Consider tightening to ~300 chars for the cleanest unfurl
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 | ⚠ | — | — | — |
CStructured DataActionNo structured data (JSON-LD) found.REVIEW
Adding structured data helps search engines understand your content and can enable rich results.
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