Skip to content
https://joelonsoftware.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
69
GRADE
D
FIX
2
REVIEW
3
PASS
0
INFO
0
Checks
5
3 REVIEW 2 FIX
D
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
FIX

Brand Presence

Partial brand coverage — a few channels are missing brand signals.

D

53/100

Site name appears as

Page titleJoel on Software
og:site_nameJoel on Software
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

15/15

covers multiple sizes + apple-touch-icon

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

14/20

Organization schema

0/15

Contact info discoverable

0/10

no contact info discoverable

Findings

  • Missing brand name in: twitter:site, Organization.name
  • 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.

B
Mixed Content
1 HTTP resource(s) loaded on HTTPS page
REVIEW
1 HTTP resource(s) loaded on HTTPS page
Critical::
HTTP link loaded on HTTPS page
Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.
Got: http://gmpg.org/xfn/11 Expected: https://gmpg.org/xfn/11
URL: http://gmpg.org/xfn/11

Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.

Expected: https://gmpg.org/xfn/11
Why this matters

Mixed content — HTTP resource on HTTPS page. Browser may block silently or warn user.

Source: Google Chrome Security

B
Open Graph
Open Graph tags are partially configured — some improvements recommended.
REVIEW
Open Graph tags are partially configured — some improvements recommended.
Critical::
og:image is not reachable
The og:image URL could not be fetched. Social platforms won't be able to display it.
Got: https://i0.wp.com/www.joelonsoftware.com/wp-content/uploads/2016/12/11969842.jpg?fit=400%2C400&ssl=1
Info::
og:title is short (16 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 16 chars Expected: 25–60 chars
Info::
Missing twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.
URL: https://i0.wp.com/www.joelonsoftware.com/wp-content/uploads/2016/12/11969842.jpg?fit=400%2C400&ssl=1

The og:image URL could not be fetched. Social platforms won't be able to display it.

Why this matters

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

URL: 16 chars

Ideal length is 25–60 characters for social sharing previews.

Expected: 25–60 chars
Why this matters

og: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.

Why this matters

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

joelonsoftware.com

Joel on Software

A weblog by Joel Spolsky, a programmer working in New York City, about software and software companies.

Preview quality · Twitter/X D · 50/100
  • 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 — falling back from og:image

  • twitter:card is missing

    → Add <meta name="twitter:card" content="summary_large_image">

JOELONSOFTWARE.COM

Joel on Software

A weblog by Joel Spolsky, a programmer working in New York City, about software and software companies.

Preview quality · Facebook A+ · 100/100
  • og:title — Joel on Software
  • og:description — A weblog by Joel Spolsky, a programmer working in New York City, about software and software companies.
  • og:image — https://i0.wp.com/www.joelonsoftware.com/wp-content/uploads/2016/12/11969842.jpg?fit=400%2C400&ssl=1
  • og:type — website
  • og:url — https://www.joelonsoftware.com/
  • og:site_name — Joel on Software

  • og:image is below recommended size (400×400)

    → Upload an image ≥1200×630 for the large preview card

Joel on Software

joelonsoftware.com

Preview quality · LinkedIn A+ · 100/100
  • og:title — Joel on Software
  • og:description — A weblog by Joel Spolsky, a programmer working in New York City, about software and software companies.
  • og:image — https://i0.wp.com/www.joelonsoftware.com/wp-content/uploads/2016/12/11969842.jpg?fit=400%2C400&ssl=1

joelonsoftware.com

Joel on Software

A weblog by Joel Spolsky, a programmer working in New York City, about software and software companies.

Preview quality · Slack A+ · 100/100
  • og:title — Joel on Software
  • og:description — A weblog by Joel Spolsky, a programmer working in New York City, about software and software companies.
  • og:image — https://i0.wp.com/www.joelonsoftware.com/wp-content/uploads/2016/12/11969842.jpg?fit=400%2C400&ssl=1

Social preview quality

Averaged across Twitter/X, Facebook, LinkedIn, and Slack.

A · 87/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description⚠———
twitter:image⚠———
C
Structured Data
Action
No structured data (JSON-LD) found.
REVIEW
No structured data (JSON-LD) found.
Info::
No structured data (JSON-LD) found
Adding structured data helps search engines understand your content and can enable rich results.

Adding structured data helps search engines understand your content and can enable rich results.

Why this matters

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
Learn more at schema.org
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback