Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FOpen 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
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
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

mikecrm.com
No title set
No description
Description will be truncated (229 chars / 200 max)
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — falling back from <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">
Description will be truncated on Twitter/X (229 chars, max 200)
→ Tighten the description to ≤200 characters

MIKECRM.COM
No title set
No description
Title will be truncated (70 chars / 60 max)
Description will be truncated (229 chars / 155 max)
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://cdnq4.de.mikecrm.com/images/logo/brand_300.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 — MikeCRM
Title will be truncated on Facebook (70 chars, max 60)
→ Shorten og:title to ≤60 characters
Description will be truncated on Facebook (229 chars, max 155)
→ Tighten og:description to ≤155 characters

No title set
mikecrm.com
Description will be truncated (229 chars / 150 max)
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://cdnq4.de.mikecrm.com/images/logo/brand_300.png
Description will be truncated on LinkedIn (229 chars, max 150)
→ Tighten og:description to ≤150 characters
mikecrm.com
No title set
No description

- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://cdnq4.de.mikecrm.com/images/logo/brand_300.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 | ⚠ | — | — | — |
CBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsREVIEW
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
C
62/100
Site name appears as
| Page title | MikeCRM - Ein führender Dienst für Datensammlung und Marktforschung. | |
| og:site_name | MikeCRM | |
| twitter:site | — | |
| Organization.name | MikeCRM |
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
8/20Organization schema
15/15has name, logo + url
Contact 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
- og:title missing
- twitter:card missing
- Consider adding contactPoint — helps appear in "contact us" rich results
- 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.
ALinks93 links checked, 85 healthy, 0 brokenPASS
Broken Links (1)
| Status | URL | Found in | Error |
|---|---|---|---|
| 403 | https://real.mikecrm.com | <link> | Forbidden |
Redirects (4)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://www.mikecrm.com/cn/ | https://www.mikecrm.com/cn/ | <link> | 0 |
| https://www.mikecrm.com/ja/ | https://www.mikecrm.com/ja/ | <link> | 0 |
| https://mikecrm.com/login.php | https://mikecrm.com/login.php?ma_tmnl_uu... | <a> | 5 |
| https://mikecrm.com/login.php?s=4 | https://mikecrm.com/login.php?s=4&ma_tmn... | <a> | 5 |
A+Mixed ContentNo mixed content detected — all resources use HTTPS.PASS
A+Structured Data1 JSON-LD block(s) found — structured data is well configured.PASS
JSON-LD Blocks
{
"@context": "http://schema.org",
"@type": "Organization",
"name": "MikeCRM",
"url": "https://www.mikecrm.com",
"image": "https://www.mikecrm.com/images/logo/brand_300.png",
"logo": "https://www.mikecrm.com/images/logo/brand_300.png",
"sameAs": [
"https://www.facebook.com/MikeCRMLtd/",
"https://twitter.com/MikeCRM_Service"
]
}