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
Partial brand coverage — a few channels are missing brand signals.
D
53/100
Site name appears as
| Page title | Mapy.com | |
| og:site_name | Mapy.com | |
| twitter:site | — | |
| 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
14/20Organization schema
0/15Contact info discoverable
0/10no contact info discoverable
Findings
- Missing brand name in: twitter:site, Organization.name
- Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
- 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.
COpen GraphActionOpen 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
photoValid values are: summary, summary_large_image, app, player.
Invalid twitter:card value means Twitter renders no card at all — your shares appear as plain-text URLs.
Learn more ▾ ▴
twitter:card accepts only 'summary', 'summary_large_image', 'app', or 'player'. Anything else (typos, made-up values) means Twitter falls back to no-card rendering. Use 'summary_large_image' for most blog/article content; 'summary' for compact previews.
Source: Twitter Developer Platform
8 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
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
Preview
mapy.cz
Mapy.com
No description
- twitter:card — photo
- twitter:title — falling back from og:title
- twitter:description — Add twitter:description to give the preview body text
- twitter:image — falling back from og:image
MAPY.CZ
Mapy.com
No description
- og:title — Mapy.com
- og:description — Add og:description to give the preview body text
- og:image — https://mapy.com/screenshoter?url=https%3A%2F%2Fmapy.com%2Fen%2F%26p%3D3%26l%3D0&width=1200&height=630
- og:type — Add og:type — Recommended — tells Facebook the content category
- og:url — https://mapy.com/en/
- og:site_name — Mapy.com
Mapy.com
mapy.cz
- og:title — Mapy.com
- og:description — Add og:description to give the preview body text
- og:image — https://mapy.com/screenshoter?url=https%3A%2F%2Fmapy.com%2Fen%2F%26p%3D3%26l%3D0&width=1200&height=630
mapy.cz
Mapy.com
No description
- og:title — Mapy.com
- og:description — Add og:description to give the preview body text
- og:image — https://mapy.com/screenshoter?url=https%3A%2F%2Fmapy.com%2Fen%2F%26p%3D3%26l%3D0&width=1200&height=630
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