Skip to content
https://hackerone.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
81
GRADE
B
FIX
2
REVIEW
1
PASS
2
INFO
0
Checks
5
2 PASS 1 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 titleHackerOne
og:site_nameHackerOne
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

12/15

covers apple-touch-icon + SVG

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

8/20

Organization schema

4/15

Organization schema present but missing all recommended fields

Contact info discoverable

5/10

contact page

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
  • Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
  • twitter:card missing
  • Organization schema missing logo — add a logo property pointing to a square PNG
  • Organization schema missing url — point it at the canonical homepage
  • 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.

C
Open Graph
Action
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::
Missing og:type
The og:type tag helps social platforms categorize the content.
Info::
Missing twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

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

The og:type tag helps social platforms categorize the content.

Why this matters

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.

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

hackerone.com

Leader in Continuous Threat Exposure Management | HackerOne

No description

Preview quality · Twitter/X F · 40/100
  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from og:title
  • twitter:description — Add twitter:description to give the preview body text
  • twitter:image — falling back from og:image

  • twitter:card is missing

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

HACKERONE.COM

Leader in Continuous Threat Exposure Management | HackerOne

No description

Preview quality · Facebook C · 70/100
  • og:title — Leader in Continuous Threat Exposure Management | HackerOne
  • og:description — Add og:description to give the preview body text
  • og:image — https://www.hackerone.com/sites/default/files/2025-02/hackerone.png
  • og:type — Add og:type — Recommended — tells Facebook the content category
  • og:url — https://www.hackerone.com/new-home-page
  • og:site_name — HackerOne

Leader in Continuous Threat Exposure Management | HackerOne

hackerone.com

Preview quality · LinkedIn A · 85/100
  • og:title — Leader in Continuous Threat Exposure Management | HackerOne
  • og:description — Add og:description to give the preview body text
  • og:image — https://www.hackerone.com/sites/default/files/2025-02/hackerone.png

hackerone.com

Leader in Continuous Threat Exposure Management | HackerOne

No description

Preview quality · Slack A · 85/100
  • og:title — Leader in Continuous Threat Exposure Management | HackerOne
  • og:description — Add og:description to give the preview body text
  • og:image — https://www.hackerone.com/sites/default/files/2025-02/hackerone.png

Social preview quality

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

C · 70/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description———
twitter:image⚠———
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
A
Structured Data
1 JSON-LD block(s) found — structured data is well configured.
PASS
1 JSON-LD block(s) found — structured data is well configured.
Warning::
Missing required property "name" for Organization
The "name" property is required for the Organization schema type.
Info::
Missing recommended property "url" for Organization
Adding "url" can improve how search engines display your content.
Info::
Missing recommended property "logo" for Organization
Adding "logo" can improve how search engines display your content.
Info::
Missing recommended property "sameAs" for Organization
Adding "sameAs" can improve how search engines display your content.

The "name" property is required for the Organization schema type.

Why this matters

Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.

Learn more ▾

Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.

Source: Google Search Central / schema.org

Adding "url" 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

Adding "logo" 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

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
2 properties Valid
Missing required property: name
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://www.hackerone.com/#organization",
      "name": "HackerOne",
      "url": "https://www.hackerone.com/"
    },
    {
      "@type": "WebSite",
      "@id": "https://www.hackerone.com/#website",
      "name": "HackerOne",
      "url": "https://www.hackerone.com/",
      "publisher": {
        "@type": "Organization",
        "@id": "https://www.hackerone.com/#organization"
      },
      "inLanguage": "en"
    }
  ]
}
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback