Skip to content
https://iihs.org

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
3
PASS
1
INFO
0
Checks
5
1 PASS 3 REVIEW 1 FIX
B
Open Graph
Open Graph tags are partially configured — some improvements recommended.
REVIEW
Open Graph tags are partially configured — some improvements recommended.
Warning::
Missing og:description
The og:description tag controls the description in social sharing previews.
Info::
og:title is short (9 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 9 chars Expected: 25–60 chars

The og:description tag controls the description in social sharing previews.

Why this matters

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

URL: 9 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

Preview

iihs.org

IIHS-HLDI

No description

Preview quality · Twitter/X B · 80/100

Description will be truncated (311 chars / 200 max)

  • twitter:card — 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

  • Description will be truncated on Twitter/X (311 chars, max 200)

    → Tighten the description to ≤200 characters

IIHS.ORG

IIHS-HLDI

No description

Preview quality · Facebook A · 90/100

Description will be truncated (311 chars / 155 max)

  • og:title — IIHS-HLDI
  • og:description — falling back from <meta name=description>
  • og:image — https://www.iihs.org/frontend/images/IIHS-HLDI-avatar-1200x1200.jpg
  • og:type — website
  • og:url — https://www.iihs.org/
  • og:site_name — IIHS-HLDI crash testing and highway safety

  • Description will be truncated on Facebook (311 chars, max 155)

    → Tighten og:description to ≤155 characters

IIHS-HLDI

iihs.org

Preview quality · LinkedIn A · 90/100

Description will be truncated (311 chars / 150 max)

  • og:title — IIHS-HLDI
  • og:description — falling back from <meta name=description>
  • og:image — https://www.iihs.org/frontend/images/IIHS-HLDI-avatar-1200x1200.jpg

  • Description will be truncated on LinkedIn (311 chars, max 150)

    → Tighten og:description to ≤150 characters

iihs.org

IIHS-HLDI

No description

Preview quality · Slack A+ · 95/100

Description will be truncated (311 chars / 300 max)

  • og:title — IIHS-HLDI
  • og:description — falling back from <meta name=description>
  • og:image — https://www.iihs.org/frontend/images/IIHS-HLDI-avatar-1200x1200.jpg

  • Long description may be shortened by Slack (311 chars, guideline ~300)

    → Consider tightening to ~300 chars for the cleanest unfurl

Social preview quality

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

A · 88/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description⚠⚠⚠
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description⚠———
twitter:image⚠———
B
Structured Data
1 JSON-LD block(s) found — some improvements recommended.
REVIEW
1 JSON-LD block(s) found — some improvements recommended.
Warning::
Missing or invalid @context in block #1
The @context should be "https://schema.org" for search engines to recognize the data.
Got: http://schema.org/ Expected: https://schema.org
Info::
Missing recommended property "sameAs" for Organization
Adding "sameAs" can improve how search engines display your content.
URL: http://schema.org/

The @context should be "https://schema.org" for search engines to recognize the data.

Expected: https://schema.org
Why this matters

JSON-LD without @context is invalid structured data — Google ignores the entire block.

Learn more ▾

@context must be 'https://schema.org' (or the schema-specific URL). Without it, the block isn't parseable as schema.org JSON-LD and Google skips it. Most schema generators handle this; manual edits sometimes drop the field.

Source: JSON-LD spec / schema.org

Adding "sameAs" can improve how search engines display your content.

Why this matters

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

Block 1 : Organization
10 properties Valid
Missing or invalid @context
{
  "@context": "http://schema.org/",
  "@type": "Organization",
  "url": "https://www.iihs.org",
  "name": "IIHS-HLDI",
  "logo": "https://www.iihs.org/frontend/images/logo-no-lettering.svg",
  "nonprofitStatus": "Nonprofit501c3",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://www.iihs.org/search?query={search_term_string}",
    "query-input": "required name=search_term_string"
  },
  "foundingDate": 1959,
  "legalName": "Insurance Institute for Highway Safety (IIHS) and the Highway Loss Data Institute (HLDI)",
  "address": {
    "@type": "PostalAddress",
    "addressLocality": "Arlington",
    "addressRegion": "VA",
    "postalCode": "22203",
    "streetAddress": "4121 Wilson Boulevard, 6th floor"
  }
}
C
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
REVIEW

Brand Presence

Your brand name differs across channels — visitors see inconsistent identity.

C

65/100

Site name appears as

Page titleIIHS-HLDI
og:site_nameIIHS-HLDI crash testing and highway safety
twitter:site@IIHS_autosafety
Organization.nameIIHS-HLDI

Inconsistent — names differ across channels

Brand assets

Favicon

12/15

covers apple-touch-icon

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

14/20

Organization schema

15/15

has name, logo + url

Contact info discoverable

5/10

contact page

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)
  • Consider adding contactPoint — helps appear in "contact us" rich results
  • 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+
Mixed Content
No mixed content detected — all resources use HTTPS.
PASS
No mixed content detected — all resources use HTTPS.
Info::
No mixed content detected — all resources use HTTPS
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback