Skip to content
https://whmcs.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
88
GRADE
B
FIX
2
REVIEW
0
PASS
3
INFO
0
Checks
5
3 PASS 2 FIX
F
Open Graph
Action
Open Graph tags need attention — social sharing previews may be incomplete.
FIX
Open Graph tags need attention — social sharing previews may be incomplete.
Warning::
Missing og:description
The og:description tag controls the description in social sharing previews.
Warning::
Missing og:image
The og:image tag provides a preview image for social sharing.
Info::
Missing og:type
The og:type tag helps social platforms categorize the content.
Info::
Missing og:site_name
The og:site_name tag displays the website name in social previews.
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: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

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

The og:site_name tag displays the website name in social previews.

Why this matters

Without og:site_name, social cards omit the brand attribution — users see the post but not who published it.

Learn more ▾

og:site_name appears in the social card chrome (above the title in Facebook/LinkedIn previews). Without it, posts read as anonymous URLs. Set it to your brand name to get free attribution on every share.

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

whmcs.com

WHMCS | Web Hosting Automation Made Easy

No description

Preview quality · Twitter/X F · 15/100

Description will be truncated (301 chars / 200 max)

  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from og: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 (301 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

WHMCS.COM

WHMCS | Web Hosting Automation Made Easy

No description

Preview quality · Facebook F · 25/100

Description will be truncated (301 chars / 155 max)

  • og:title — WHMCS | Web Hosting Automation Made Easy
  • 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 — https://www.whmcs.com
  • og:site_name — Add og:site_name — Recommended — site-level brand line in the preview

  • Description will be truncated on Facebook (301 chars, max 155)

    → Tighten og:description to ≤155 characters

  • No preview image for Facebook

    → Add og:image (recommended 1200×630)

No image set

WHMCS | Web Hosting Automation Made Easy

whmcs.com

Preview quality · LinkedIn D · 55/100

Description will be truncated (301 chars / 150 max)

  • og:title — WHMCS | Web Hosting Automation Made Easy
  • 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 (301 chars, max 150)

    → Tighten og:description to ≤150 characters

  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

whmcs.com

WHMCS | Web Hosting Automation Made Easy

No description

Preview quality · Slack B · 75/100

Description will be truncated (301 chars / 300 max)

  • og:title — WHMCS | Web Hosting Automation Made Easy
  • og:description — falling back from <meta name=description>
  • og:image — Add og:image — preview card without an image looks broken

  • Long description may be shortened by Slack (301 chars, guideline ~300)

    → Consider tightening to ~300 chars for the cleanest unfurl

  • 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 · 42/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

37/100

Site name appears as

Page titleWeb Hosting Billing & Automation Platform
og:site_name—
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

15/15

covers multiple sizes + apple-touch-icon

Social share image

0/20

Meta completeness

8/20

Organization schema

4/15

has logo + url

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
  • og:image missing
  • twitter:card missing
  • 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
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.

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

JSON-LD Blocks

Block 1 : Organization
7 properties Valid
Missing required property: name
{
  "@context": "http://schema.org",
  "@type": "Organization",
  "url": "https://www.whmcs.com",
  "logo": "https://www.whmcs.com/images/logo.png",
  "email": "sales@whmcs.com",
  "address": "2550 North Loop West, Houston, TX 77092",
  "sameAs": [
    "https://www.facebook.com/whmcsfans",
    "https://twitter.com/whmcs",
    "https://instagram.com/whmcsofficial",
    "https://www.linkedin.com/company/whmcs-ltd",
    "https://plus.google.com/+whmcs"
  ]
}
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback