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
33/100
Site name appears as
| Page title | Technology insight for the enterprise | |
| og:site_name | InfoWorld | |
| twitter:site | — | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
0/20Meta completeness
8/20Organization schema
0/15Contact info discoverable
5/10contact page
Findings
- Brand name differs across channels — users see inconsistent identity
- No social share image — shared links render as bare URLs
- og:image missing
- 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:image tag provides a preview image for social sharing.
No og:image means social shares are imageless — measurably less engaging than image-cards across every major platform.
Learn more ▾ ▴
Twitter, Facebook, and LinkedIn all use og:image (or twitter:image as a fallback) for share-card thumbnails. Without one, the post renders as a text-only card. A 1200x630px image (Twitter's preferred size) covers all platforms.
Source: Open Graph Protocol
9 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
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
infoworld.com
InfoWorld
Business technology, IT news, product reviews and enterprise IT strategies.
- 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 — Add twitter:image — preview card without an image looks broken
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
No preview image for Twitter/X
→ Add og:image or twitter:image (≥300×157 for summary_large_image)
INFOWORLD.COM
InfoWorld
Business technology, IT news, product reviews and enterprise IT strategies.
- og:title — InfoWorld
- og:description — Business technology, IT news, product reviews and enterprise IT strategies.
- og:image — Add og:image — preview card without an image looks broken
- og:type — website
- og:url — https://www.infoworld.com/
- og:site_name — InfoWorld
No preview image for Facebook
→ Add og:image (recommended 1200×630)
InfoWorld
infoworld.com
- og:title — InfoWorld
- og:description — Business technology, IT news, product reviews and enterprise IT strategies.
- og:image — Add og:image — preview card without an image looks broken
No preview image for LinkedIn
→ Add og:image (recommended 1200×627)
infoworld.com
InfoWorld
Business technology, IT news, product reviews and enterprise IT strategies.
- og:title — InfoWorld
- og:description — Business technology, IT news, product reviews and enterprise IT strategies.
- og:image — Add og:image — preview card without an image looks broken
No preview image — Slack unfurl will be text-only
→ Add og:image or twitter:image
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[{\"@context\":\"https:\\/\\/schema.o\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": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https:\/\/www.infoworld.com\/"
},
{
"@type": "ListItem",
"position": 2,
"name": "InfoWorld",
"item": ""
}
]
},
{
"@context": "https:\/\/schema.org",
"@type": "Organization",
"name": "InfoWorld",
"url": "https:\/\/www.infoworld.com",
"description": "Business technology, IT news, product reviews and enterprise IT strategies.",
"memberOf": {
"@type": "Organization",
"name": "Foundry",
"url": "https:\/\/www.foundryco.com"
},
"logo": {
"@type": "ImageObject"
},
"mainEntityOfPage": {
"@type": "CollectionPage",
"name": "InfoWorld Homepage",
"url": "https:\/\/www.infoworld.com",
"description": "Business technology, IT news, product reviews and enterprise IT strategies."
}
}
]