Skip to content
https://fortunebusinessinsights.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
74
GRADE
C
FIX
2
REVIEW
2
PASS
1
INFO
0
Checks
5
1 PASS 2 REVIEW 2 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

fortunebusinessinsights.com

No title set

No description

Preview quality · Twitter/X F · 15/100

Description will be truncated (231 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 (231 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

FORTUNEBUSINESSINSIGHTS.COM

No title set

No description

Preview quality · Facebook F · 0/100

Title will be truncated (65 chars / 60 max)

Description will be truncated (231 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

  • Title will be truncated on Facebook (65 chars, max 60)

    → Shorten og:title to ≤60 characters

  • Description will be truncated on Facebook (231 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

fortunebusinessinsights.com

Preview quality · LinkedIn D · 50/100

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

    → Tighten og:description to ≤150 characters

  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

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

D

42/100

Site name appears as

Page titleFortune Business Insights
og:site_name—
twitter:site—
Organization.nameFortune Business Insights™

Inconsistent — names differ across channels

Brand assets

Favicon

8/15

single size only

Social share image

0/20

Meta completeness

4/20

Organization schema

15/15

has name, logo + url

Contact info discoverable

10/10

contact page, mailto link + tel link

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:title missing
  • og:image missing
  • twitter:card missing
  • Consider adding contactPoint — helps appear in "contact us" rich results

How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.

B
Structured Data
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: https://schema.org/ Expected: https://schema.org
Info::
Missing recommended property "description" for WebSite
Adding "description" 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::
2 JSON-LD blocks found
URL: https://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 "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 "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 : WebSite
5 properties Valid
Missing or invalid @context
{
  "@context": "https://schema.org/",
  "@type": "WebSite",
  "name": "Fortune Business Insights™",
  "url": "https://www.fortunebusinessinsights.com/",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://www.fortunebusinessinsights.com/search/?search={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
Block 2 : Organization
5 properties Valid
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Fortune Business Insights™",
  "url": "https://www.fortunebusinessinsights.com/",
  "logo": "https://www.fortunebusinessinsights.com/accets/frontend/img/logo.svg"
}
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