Skip to content
https://builtin.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
64
GRADE
D
FIX
3
REVIEW
1
PASS
1
INFO
0
Checks
5
1 PASS 1 REVIEW 3 FIX
F
Open Graph
Action
No Open Graph tags found — social sharing previews will be generic.
FIX
No Open Graph tags found — social sharing previews will be generic.
Warning::
No Open Graph meta tags found
Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.

Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.

Why this matters

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

No image set

builtin.com

No title set

No description

Preview quality · Twitter/X F · 15/100

Description will be truncated (223 chars / 200 max)

  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from <title>
  • twitter:description — falling back from <meta name=description>
  • twitter:image — Add twitter:image — preview card without an image looks broken

  • twitter:card is missing

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

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

    → Tighten the description to ≤200 characters

  • No preview image for Twitter/X

    → Add og:image or twitter:image (≥300×157 for summary_large_image)

No image set

BUILTIN.COM

No title set

No description

Preview quality · Facebook F · 5/100

Description will be truncated (223 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 (223 chars, max 155)

    → Tighten og:description to ≤155 characters

  • No preview image for Facebook

    → Add og:image (recommended 1200×630)

No image set

No title set

builtin.com

Preview quality · LinkedIn D · 50/100

Description will be truncated (223 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 (223 chars, max 150)

    → Tighten og:description to ≤150 characters

  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

builtin.com

No title set

No description

Preview quality · Slack C · 70/100
  • 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

  • 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.

F · 35/100
FieldTwitter/XFacebookLinkedInSlack
og:title⚠⚠⚠
og:description⚠⚠⚠
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description⚠———
twitter:image———
F
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.

F

22/100

Site name appears as

Page title<!---->Close Cookie Preferences<!---->
og:site_name—
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

8/15

single size only

Social share image

0/20

Meta completeness

4/20

Organization schema

0/15

Contact info discoverable

5/10

contact page

Findings

  • Missing brand name in: og:site_name, twitter:site, Organization.name
  • No social share image — shared links render as bare URLs
  • Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
  • og:title missing
  • og:image missing
  • twitter:card 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.

B
Structured Data
1 JSON-LD block(s) found — some improvements recommended.
REVIEW
1 JSON-LD block(s) found — some improvements recommended.
Warning::
Missing required property "name" for WebSite
The "name" property is required for the WebSite schema type.
Warning::
Missing required property "url" for WebSite
The "url" property is required for the WebSite schema type.
Info::
Missing recommended property "description" for WebSite
Adding "description" can improve how search engines display your content.
Info::
Missing recommended property "potentialAction" for WebSite
Adding "potentialAction" can improve how search engines display your content.

The "name" property is required for the WebSite 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

The "url" property is required for the WebSite 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 "description" 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 "potentialAction" 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 : WebSite
2 properties Valid
Missing required property: name
Missing required property: url
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebSite",
      "@id": "https://builtin.com/#website",
      "url": "https://builtin.com/",
      "name": "Built In",
      "publisher": {
        "@id": "https://builtin.com/#organization"
      }
    },
    {
      "@context": "https://schema.org",
      "@type": "Organization",
      "@id": "https://builtin.com/#organization",
      "name": "Built In",
      "url": "https://builtin.com",
      "logo": "https://static.builtin.com/dist/images/built-logo.png",
      "sameAs": [
        "https://www.linkedin.com/company/built-in",
        "https://www.instagram.com/builtin/",
        "https://www.facebook.com/BuiltInHQ/",
        "https://twitter.com/builtin"
      ],
      "description": "Built In is a top destination for tech professionals around the world. Our platform features real-time job listings, deep company profiles and content-rich communities in key innovation markets across the U.S. and globally.",
      "foundingDate": "2011",
      "founders": [
        {
          "@type": "Person",
          "name": "Maria Christopoulos Katris"
        },
        {
          "@type": "Person",
          "name": "Adam Calica"
        }
      ],
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "222 N LaSalle St, Suite 1550",
        "addressLocality": "Chicago",
        "addressRegion": "IL",
        "postalCode": "60601",
        "addressCountry": {
          "@type": "Country",
          "name": "US"
        }
      }
    }
  ]
}
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