Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
F
39/100
Site name appears as
| Page title | metacpan.org | |
| og:site_name | MetaCPAN | |
| twitter:site | @metacpan | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
12/15covers apple-touch-icon
Social share image
14/20og:image set; twitter:image missing
Meta completeness
8/20Organization schema
0/15Contact info discoverable
0/10no contact info discoverable
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
- Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
- og:title 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.
COpen GraphActionOpen Graph tags are partially configured — some improvements recommended.REVIEW
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
Preview

metacpan.org
No title set
No description
- twitter:card — summary
- twitter:title — falling back from <title>
- twitter:description — Add twitter:description to give the preview body text
- twitter:image — falling back from og:image

METACPAN.ORG
No title set
No description
- og:title — falling back from <title>
- og:description — Add og:description to give the preview body text
- og:image — https://metacpan.org/static/images/og.png
- og:type — article
- og:url — https://metacpan.org/
- og:site_name — MetaCPAN

No title set
metacpan.org
- og:title — falling back from <title>
- og:description — Add og:description to give the preview body text
- og:image — https://metacpan.org/static/images/og.png
metacpan.org
No title set
No description

- og:title — falling back from <title>
- og:description — Add og:description to give the preview body text
- og:image — https://metacpan.org/static/images/og.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 DataAction1 JSON-LD block(s) found — some improvements recommended.REVIEW
JSON parse error: Mismatch type map[string]interface {} with value array "at index 0: mismatched type with value\n\n\t[\n {\n \"@context\": \"https://s\n\t^...............................\n"
JSON-LD block fails to parse — Google ignores the entire block, so structured data effectively isn't there.
Learn more ▾ ▴
Common causes: trailing comma, single quotes instead of double, unescaped quote in a string value. Validate at https://validator.schema.org/ or Search Console's Rich Results Test.
Source: schema.org / Google Search Central
JSON-LD Blocks
[
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "MetaCPAN",
"url": "/",
"image": "/static/images/dots.svg",
"potentialAction": {
"@type": "SearchAction",
"target": "/search?q={query}",
"query-input": "required name=query",
"query": "required"
}
}
]