Skip to content
https://newrelic.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
3
PASS
2
INFO
0
Checks
5
2 PASS 3 REVIEW
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://newrelic.com/themes/custom/erno/assets/images/metadata/NROG_Image.png
Info::
Missing og:url
The og:url tag specifies the canonical URL for the shared content.
URL: https://newrelic.com/themes/custom/erno/assets/images/metadata/NROG_Image.png

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

The og:url tag specifies the canonical URL for the shared content.

Why this matters

Without og:url, social platforms infer the canonical URL — often picking a tracking-param variant that pollutes share counts.

Learn more

og:url tells the social platform which URL to count this share against. Without it, platforms use the literal URL the user pasted (which may include utm_* parameters, ref codes, etc.). Setting og:url to the canonical form keeps share-count attribution clean.

Source: Open Graph Protocol

Preview

newrelic.com

Observability built to understand AI

New Relic is an AI-powered observability platform that correlates your telemetry across your entire stack, so you can isolate the root cause and reduce MTTR.

Preview quality · Twitter/X A · 85/100
  • twitter:card — summary_large_image
  • twitter:title — falling back from og:title
  • twitter:description — falling back from og:description
  • twitter:image — falling back from og:image

NEWRELIC.COM

Observability built to understand AI

New Relic is an AI-powered observability platform that correlates your telemetry across your entire stack, so you can isolate the root cause and reduce MTTR.

Preview quality · Facebook B · 80/100

Description will be truncated (157 chars / 155 max)

  • og:title — Observability built to understand AI
  • og:description — New Relic is an AI-powered observability platform that correlates your telemetry across your entire stack, so you can...
  • og:image — https://newrelic.com/themes/custom/erno/assets/images/metadata/NROG_Image.png
  • og:type — website
  • og:url — Add og:url — Recommended — canonical URL for the share
  • og:site_name — New Relic
  • Description will be truncated on Facebook (157 chars, max 155)

    → Tighten og:description to ≤155 characters

Observability built to understand AI

newrelic.com

Preview quality · LinkedIn A+ · 95/100

Description will be truncated (157 chars / 150 max)

  • og:title — Observability built to understand AI
  • og:description — New Relic is an AI-powered observability platform that correlates your telemetry across your entire stack, so you can...
  • og:image — https://newrelic.com/themes/custom/erno/assets/images/metadata/NROG_Image.png
  • Description will be truncated on LinkedIn (157 chars, max 150)

    → Tighten og:description to ≤150 characters

newrelic.com

Observability built to understand AI

New Relic is an AI-powered observability platform that correlates your telemetry across your entire stack, so you can isolate the root cause and reduce MTTR.

Preview quality · Slack A+ · 100/100
  • og:title — Observability built to understand AI
  • og:description — New Relic is an AI-powered observability platform that correlates your telemetry across your entire stack, so you can...
  • og:image — https://newrelic.com/themes/custom/erno/assets/images/metadata/NROG_Image.png

Social preview quality

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

A · 90/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
2 JSON-LD block(s) found — some improvements recommended.
REVIEW
2 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
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.
Info::
Custom type "VideoObject" — unable to validate specific properties
Info::
2 JSON-LD blocks found
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

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 : VideoObject
10 properties Valid
Missing or invalid @context
{
  "@context": "http://schema.org/",
  "@id": "https://fast.wistia.net/embed/iframe/1enxzilg1j",
  "@type": "VideoObject",
  "duration": "PT11S",
  "name": "o11y_toolkit_apm",
  "thumbnailUrl": "https://embed-ssl.wistia.com/deliveries/3e50769ec691c6d2a3d03116bf31b88b95747bbe.jpg?image_crop_resized=960x720",
  "embedUrl": "https://fast.wistia.net/embed/iframe/1enxzilg1j",
  "uploadDate": "2026-03-04T18:02:14.000Z",
  "description": "a Website Homepage Videos video",
  "contentUrl": "https://embed-ssl.wistia.com/deliveries/4f33a4993386fb7e02677c1b59a5784b74f17cc0.m3u8"
}
Block 2 : Organization
2 properties Valid
Missing required property: name
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "url": "https://newrelic.com/",
      "sameAs": [
        "http://www.facebook.com/NewRelic",
        "https://twitter.com/newrelic",
        "https://www.instagram.com/newrelic/",
        "https://www.youtube.com/user/NewRelicInc/featured",
        "https://www.linkedin.com/company/new-relic-inc-"
      ],
      "name": "New Relic, Inc.",
      "contactPoint": {
        "@type": "ContactPoint",
        "telephone": "+1-888-643-8776",
        "contactType": "sales"
      },
      "logo": {
        "@type": "ImageObject",
        "url": "https://newrelic.com/themes/custom/erno/logo.svg",
        "width": "738px",
        "height": "132px"
      }
    },
    {
      "@type": "WebSite",
      "name": "New Relic",
      "url": "https://newrelic.com/",
      "potentialAction": {
        "@type": "SearchAction",
        "target": {
          "@type": "EntryPoint",
          "urlTemplate": "https://newrelic.com/search#stq={search_term}"
        },
        "query": "https://newrelic.com/search#stq={search_term}",
        "query-input": "required name=search_term"
      }
    }
  ]
}
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

63/100

Site name appears as

Page title<!---->Close Cookie Preferences<!---->
og:site_nameNew Relic
twitter:site@newrelic
Organization.name

Inconsistent — names differ across channels

Brand assets

Favicon

15/15

covers multiple sizes + apple-touch-icon

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

20/20

Organization schema

4/15

Organization schema present but missing all recommended fields

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

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