Skip to content
https://lexisnexis.com

Content

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

Brand Presence

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

F

25/100

Site name appears as

Page titleChoose Your Path
og:site_nameLexisNexis
twitter:site@LexisNexis
Organization.name—

Inconsistent — names differ across channels

Brand assets

Favicon

8/15

single size only

Social share image

0/20

Meta completeness

8/20

Organization schema

4/15

Organization schema present but missing all recommended fields

Contact info discoverable

0/10

no contact info discoverable

Findings

  • Brand name differs across channels — users see inconsistent identity
  • 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:image missing
  • 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
  • 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
Open Graph
Open Graph tags are partially configured — some improvements recommended.
REVIEW
Open Graph tags are partially configured — some improvements recommended.
Warning::
Missing og:image
The og:image tag provides a preview image for social sharing.
Info::
Missing twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

The og:image tag provides a preview image for social sharing.

Why this matters

No og:image means social shares are imageless — measurably less engaging than image-cards across every major platform.

Learn more ▾

Twitter, Facebook, and LinkedIn all use og:image (or twitter:image as a fallback) for share-card thumbnails. Without one, the post renders as a text-only card. A 1200x630px image (Twitter's preferred size) covers all platforms.

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

No image set

lexisnexis.com

Welcome to LexisNexis - Choose Your Path

Provider of legal, government, business and high-tech information sources. Learn more or login to your product now.

Preview quality · Twitter/X F · 30/100
  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — Welcome to LexisNexis - Choose Your Path
  • twitter:description — Provider of legal, government, business and high-tech information sources. Learn more or login to your product now.
  • 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">

  • No preview image for Twitter/X

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

No image set

LEXISNEXIS.COM

Welcome to LexisNexis - Choose Your Path

Provider of legal, government, business and high-tech information sources. Learn more or login to your product now.

Preview quality · Facebook C · 65/100
  • og:title — Welcome to LexisNexis - Choose Your Path
  • og:description — Provider of legal, government, business and high-tech information sources. Learn more or login to your product now.
  • og:image — Add og:image — preview card without an image looks broken
  • og:type — website
  • og:url — https://www.lexisnexis.com/en-us/gateway.page
  • og:site_name — LexisNexis

  • No preview image for Facebook

    → Add og:image (recommended 1200×630)

No image set

Welcome to LexisNexis - Choose Your Path

lexisnexis.com

Preview quality · LinkedIn C · 65/100
  • og:title — Welcome to LexisNexis - Choose Your Path
  • og:description — Provider of legal, government, business and high-tech information sources. Learn more or login to your product now.
  • og:image — Add og:image — preview card without an image looks broken

  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

lexisnexis.com

Welcome to LexisNexis - Choose Your Path

Provider of legal, government, business and high-tech information sources. Learn more or login to your product now.

Preview quality · Slack B · 80/100
  • og:title — Welcome to LexisNexis - Choose Your Path
  • og:description — Provider of legal, government, business and high-tech information sources. Learn more or login to your product now.
  • 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.

D · 60/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
1 JSON-LD block(s) found — some improvements recommended.
REVIEW
1 JSON-LD block(s) found — some improvements recommended.
Critical::
Malformed JSON-LD block #1
JSON parse error: Mismatch type map[string]interface {} with value array "at index 0: mismatched type with value\n\n\t[{\n\t\t\"@context\": \"https://schema\n\t^...............................\n"

JSON parse error: Mismatch type map[string]interface {} with value array "at index 0: mismatched type with value\n\n\t[{\n\t\t\"@context\": \"https://schema\n\t^...............................\n"

Why this matters

JSON-LD block fails to parse — Google ignores the entire block, so structured data effectively isn't there.

Learn more ▾

Common causes: trailing comma, single quotes instead of double, unescaped quote in a string value. Validate at https://validator.schema.org/ or Search Console's Rich Results Test.

Source: schema.org / Google Search Central

JSON-LD Blocks

Block 1 : Organization
0 properties Invalid
Invalid JSON: Mismatch type map[string]interface {} with value array "at index 0: mismatched type with value\n\n\t[{\n\t\t\"@context\": \"https://schema\n\t^...............................\n"
[
  {
    "@context": "https://schema.org/",
    "@type": "Organization",
    "@id": "https://www.lexisnexis.com/#organization",
    "name": "LexisNexis",
    "url": "https://www.lexisnexis.com/",
    "logo": "https://www.lexisnexis.com/images/common/svg/ln-logo.svg",
    "description": "Our teams combine unparalleled legal and business information with analytics and technology to advance what's possible.",
    "sameAs": [
      "https://www.linkedin.com/company/lexisnexis/"
    ],
    "telephone": "+1-888-285-3947",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "230 Park Ave Suite 7",
      "addressLocality": "New York City",
      "addressRegion": "NY",
      "postalCode": "10169",
      "addressCountry": "US"
    }
  },
  {
    "@context": "https://schema.org/",
    "@type": "WebSite",
    "@id": "https://www.lexisnexis.com/en-us/#website",
    "url": "https://www.lexisnexis.com/en-us",
    "name": "LexisNexis (United States)",
    "inLanguage": "en-US",
    "publisher": {
      "@id": "https://www.lexisnexis.com/#organization"
    },
    "potentialAction": {
      "@type": "SearchAction",
      "target": "https://www.lexisnexis.com/en-us/search?q={search_term_string}",
      "query-input": "required name=search_term_string"
    },
    "sameAs": [
      "https://x.com/lexisnexis_us",
      "https://www.facebook.com/lexisnexisus/",
      "https://www.youtube.com/user/LexisNexisLegal"
    ]
  }
]
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