Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.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
53/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
Social share image
14/20og:image set; twitter:image missing
Meta completeness
14/20Organization schema
0/15Contact 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
- 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
https://cs.pikabu.ru/images/share_preview/main.pngThe 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
16 charsIdeal length is 25–60 characters for social sharing previews.
25–60 charsog:title very short — may render with awkward whitespace in social cards.
Source: Open Graph Protocol
53 charsIdeal length is 55–200 characters for social sharing previews.
55–200 charsog:description very short — provides little context in social cards.
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
pikabu.ru
Пикабу — Горячее
Самое уютное информационно-развлекательное сообщество
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — falling back from og:title
- twitter:description — falling back from og:description
- twitter:image — falling back from og:image
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
PIKABU.RU
Пикабу — Горячее
Самое уютное информационно-развлекательное сообщество
- og:title — Пикабу — Горячее
- og:description — Самое уютное информационно-развлекательное сообщество
- og:image — https://cs.pikabu.ru/images/share_preview/main.png
- og:type — website
- og:url — https://pikabu.ru/
- og:site_name — Пикабу
Пикабу — Горячее
pikabu.ru
- og:title — Пикабу — Горячее
- og:description — Самое уютное информационно-развлекательное сообщество
- og:image — https://cs.pikabu.ru/images/share_preview/main.png
pikabu.ru
Пикабу — Горячее
Самое уютное информационно-развлекательное сообщество
- og:title — Пикабу — Горячее
- og:description — Самое уютное информационно-развлекательное сообщество
- og:image — https://cs.pikabu.ru/images/share_preview/main.png
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
ALinks200 links checked, 198 healthy, 2 brokenPASS
Broken Links (2)
| Status | URL | Found in | Error |
|---|---|---|---|
| ERR | tg://resolve?domain=pikabu_access_code_bot&start= | <a> | Get "tg://resolve?domain=pikabu_access_c... |
| 400 | https://pikabu.ru/oauth.php?type=ya | <a> | Bad Request |
Redirects (4)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://vk.ru/js/api/openapi.js?169 | https://vk.ru/js/api/openapi.js?169 | <script> | 0 |
| https://ads.adfox.ru/260477/goLink?p1=cn... | https://ads.adfox.ru/260477/goLink?p1=cn... | <a> | 0 |
| https://pikabu.ru/story/vnimanie_vopros_... | https://pikabu.ru/story/vnimanie_vopros_... | <a> | 0 |
| https://pikabu.ru/story/mobilnaya_pwaver... | https://pikabu.ru/story/mobilnaya_pwaver... | <a> | 0 |