Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FOpen GraphActionNo Open Graph tags found — social sharing previews will be generic.FIX
Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.
Without Open Graph tags, social shares show a broken or empty preview card.
Learn more ▾ ▴
When someone shares your URL on Facebook, LinkedIn, Slack, iMessage, or any modern chat app, the preview comes from <meta property="og:*"> tags. Without them you get either no card or whatever fragment the social platform guesses — usually unflattering. The four core og: tags (title, description, image, url) cover what every major platform actually reads.
Source: Open Graph Protocol
Preview
wikihow.com
wikiHow
wikiHow - How to do anything
- twitter:card — summary_large_image
- twitter:title — wikiHow
- twitter:description — wikiHow - How to do anything
- twitter:image — Add twitter:image — preview card without an image looks broken
No preview image for Twitter/X
→ Add og:image or twitter:image (≥300×157 for summary_large_image)
WIKIHOW.COM
wikiHow
wikiHow - How to do anything
Description will be truncated (164 chars / 155 max)
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — Add og:image — preview card without an image looks broken
- 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 — Add og:site_name — Recommended — site-level brand line in the preview
Description will be truncated on Facebook (164 chars, max 155)
→ Tighten og:description to ≤155 characters
No preview image for Facebook
→ Add og:image (recommended 1200×630)
wikiHow
wikihow.com
Description will be truncated (164 chars / 150 max)
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — Add og:image — preview card without an image looks broken
Description will be truncated on LinkedIn (164 chars, max 150)
→ Tighten og:description to ≤150 characters
No preview image for LinkedIn
→ Add og:image (recommended 1200×627)
wikihow.com
wikiHow
wikiHow - How to do anything
- og:title — falling back from og:title
- og:description — falling back from og:description
- 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 | — | — | — |
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
30/100
Site name appears as
| Page title | wikiHow: How-to instructions you can trust. | |
| og:site_name | — | |
| twitter:site | @wikihow | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
12/15covers 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
- Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
- og:title missing
- og:image 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.
A+Links200 links checked, 200 healthy, 0 brokenPASS
Redirects (1)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://sb.scorecardresearch.com/cs/8003... | https://sb.scorecardresearch.com/cs/8003... | <script> | 0 |
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
Adding "description" can improve how search engines display your content.
Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.
Learn more ▾ ▴
Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.
Source: Google Search Central / schema.org
JSON-LD Blocks
{
"@context": "http:\/\/schema.org",
"@type": "WebSite",
"name": "wikiHow",
"url": "https:\/\/www.wikihow.com",
"logo": {
"@type": "ImageObject",
"url": "https:\/\/www.wikihow.com\/skins\/owl\/images\/wikihow_logo_nobg_60.png",
"width": 326,
"height": 60
},
"alternateName": "wikiHow: How-to instructions you can trust.",
"potentialAction": {
"@type": "SearchAction",
"target": {
"@type": "EntryPoint",
"urlTemplate": "https:\/\/www.wikihow.com\/wikiHowTo?search={search}"
},
"query-input": "required name=search"
},
"sameAs": [
"https:\/\/www.facebook.com\/wikiHow\/",
"https:\/\/twitter.com\/wikiHow",
"https:\/\/www.instagram.com\/wikihow\/",
"https:\/\/www.linkedin.com\/company\/wikihow\/",
"https:\/\/www.youtube.com\/user\/WikiHow"
]
}