Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DOpen GraphActionOpen Graph tags need attention — social sharing previews may be incomplete.FIX
https://guide-images.cdn.ifixit.com/igi/YlogWMLVAtHbPF5J.fullThe og:image URL could not be fetched. Social platforms won't be able to display it.
An unreachable og:image URL (404, DNS fail, slow timeout) means social platforms cache the failure and serve no image for hours.
Learn more ▾ ▴
Social platforms (Facebook, Twitter) cache OG metadata aggressively — including failed image fetches. A momentarily-broken og:image can leave your shares imageless for hours. Test og:image URLs in Facebook's Sharing Debugger to force re-cache after fixing.
Source: Open Graph Protocol / Facebook Sharing Debugger
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: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
ifixit.com
iFixit: The Free Repair Manual
No description
Description will be truncated (328 chars / 200 max)
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — falling back from og: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 (328 chars, max 200)
→ Tighten the description to ≤200 characters
IFIXIT.COM
iFixit: The Free Repair Manual
No description
Description will be truncated (328 chars / 155 max)
- og:title — iFixit: The Free Repair Manual
- og:description — falling back from <meta name=description>
- og:image — https://guide-images.cdn.ifixit.com/igi/YlogWMLVAtHbPF5J.full
- og:type — Add og:type — Recommended — tells Facebook the content category
- og:url — https://www.ifixit.com/
- og:site_name — iFixit
Description will be truncated on Facebook (328 chars, max 155)
→ Tighten og:description to ≤155 characters
iFixit: The Free Repair Manual
ifixit.com
Description will be truncated (328 chars / 150 max)
- og:title — iFixit: The Free Repair Manual
- og:description — falling back from <meta name=description>
- og:image — https://guide-images.cdn.ifixit.com/igi/YlogWMLVAtHbPF5J.full
Description will be truncated on LinkedIn (328 chars, max 150)
→ Tighten og:description to ≤150 characters
ifixit.com
iFixit: The Free Repair Manual
No description
Description will be truncated (328 chars / 300 max)
- og:title — iFixit: The Free Repair Manual
- og:description — falling back from <meta name=description>
- og:image — https://guide-images.cdn.ifixit.com/igi/YlogWMLVAtHbPF5J.full
Long description may be shortened by Slack (328 chars, guideline ~300)
→ Consider tightening to ~300 chars for the cleanest unfurl
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 | ⚠ | — | — | — |
DBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
D
42/100
Site name appears as
| Page title | iFixit: The Free Repair Manual | |
| og:site_name | iFixit | |
| twitter:site | — | |
| Organization.name | — |
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
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
- twitter:card 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.
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
ALinks200 links checked, 199 healthy, 1 brokenPASS
Broken Links (4)
| Status | URL | Found in | Error |
|---|---|---|---|
| 404 | https://api.config-security.com/ | <link> | Not Found |
| 403 | https://cart-products.cdn.ifixit.com | <link> | Forbidden |
| 403 | https://assets.cdn.ifixit.com | <link> | Forbidden |
| 403 | https://guide-images.cdn.ifixit.com | <link> | Forbidden |