Skip to content
https://app.vip100x.com

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Checks
9
5 PASS 4 REVIEW
C
Open Graph
Action
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: http://localhost:3000/brand/100x-og-image.png
Info::
og:title is short (13 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 13 chars Expected: 25–60 chars
Info::
og:description is short (42 characters)
Ideal length is 55–200 characters for social sharing previews.
Got: 42 chars Expected: 55–200 chars
Info::
Missing og:url
The og:url tag specifies the canonical URL for the shared content.
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.
URL: http://localhost:3000/brand/100x-og-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

URL: 13 chars

Ideal length is 25–60 characters for social sharing previews.

Expected: 25–60 chars
Why this matters

og:title very short — may render with awkward whitespace in social cards.

Source: Open Graph Protocol

URL: 42 chars

Ideal length is 55–200 characters for social sharing previews.

Expected: 55–200 chars
Why this matters

og:description very short — provides little context in social cards.

Source: Open Graph Protocol

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

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

Preview

app.vip100x.com

100X Platform

100X enterprise gaming operations platform

Preview quality · Twitter/X A+ · 100/100
  • twitter:card — summary_large_image
  • twitter:title — 100X Platform
  • twitter:description — 100X enterprise gaming operations platform
  • twitter:image — http://localhost:3000/brand/100x-og-image.png

APP.VIP100X.COM

100X Platform

100X enterprise gaming operations platform

Preview quality · Facebook D · 55/100
  • og:title — 100X Platform
  • og:description — 100X enterprise gaming operations platform
  • og:image — http://localhost:3000/brand/100x-og-image.png
  • 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

100X Platform

app.vip100x.com

Preview quality · LinkedIn A+ · 100/100
  • og:title — 100X Platform
  • og:description — 100X enterprise gaming operations platform
  • og:image — http://localhost:3000/brand/100x-og-image.png

app.vip100x.com

100X Platform

100X enterprise gaming operations platform

Preview quality · Slack A+ · 100/100
  • og:title — 100X Platform
  • og:description — 100X enterprise gaming operations platform
  • og:image — http://localhost:3000/brand/100x-og-image.png

Social preview quality

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

A · 88/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
No structured data (JSON-LD) found.
REVIEW
No structured data (JSON-LD) found.
Info::
No structured data (JSON-LD) found
Adding structured data helps search engines understand your content and can enable rich results.

Adding structured data helps search engines understand your content and can enable rich results.

Why this matters

Without schema.org markup, your pages can't appear as rich results (stars, FAQs, recipes) in search.

Learn more ▾

Structured data is what unlocks rich snippets — review stars, FAQ accordions, recipe cards, breadcrumbs, etc. — that take up more SERP space and dramatically improve click-through. The schema.org vocabulary is well-documented and JSON-LD is the easiest format.

Source: Google Search Central / schema.org

No structured data found

Structured data (JSON-LD) helps search engines understand your content better. Adding it can improve your search result appearance.

Common types include:

  • WebSite — your site identity and search box
  • Organization — your company information
  • Article — blog posts and news articles
  • Product — e-commerce product pages
  • BreadcrumbList — navigation paths
Learn more at schema.org
C
Rich Results Eligibility
Action
No JSON-LD found -- no rich-result eligibility
REVIEW
No JSON-LD found -- no rich-result eligibility
Info::
No JSON-LD structured data on the page
No `<script type="application/ld+json">` blocks found. Without structured data, search engines fall back to inferring page meaning from raw HTML -- which works but doesn't unlock SERP features (rich snippets, knowledge panel, FAQ accordion, breadcrumb trail). Adding even basic JSON-LD (Organization for the site identity, BreadcrumbList for navigation context) is a low-effort SEO win.
C
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
REVIEW

Brand Presence

Partial brand coverage — a few channels are missing brand signals.

C

60/100

Site name appears as

Page title100X Platform
og:site_name—
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

15/15

covers multiple sizes, apple-touch-icon + SVG

Social share image

20/20

og:image + twitter:image set

Meta completeness

20/20

Organization schema

0/15

Contact info discoverable

0/10

no contact info discoverable

Findings

  • Missing brand name in: og:site_name, twitter:site, Organization.name
  • No Organization schema — Google can't render your logo in the knowledge panel
  • 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.

A
Mixed Content
1 HTTP resource(s) loaded on HTTPS page
PASS
1 HTTP resource(s) loaded on HTTPS page
Warning::
HTTP meta loaded on HTTPS page
Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.
Got: http://localhost:3000/brand/100x-og-image.png Expected: https://localhost:3000/brand/100x-og-image.png
URL: http://localhost:3000/brand/100x-og-image.png

Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.

Expected: https://localhost:3000/brand/100x-og-image.png
Why this matters

Mixed content — HTTP resource on HTTPS page. Browser may block silently or warn user.

Source: Google Chrome Security

A+
Open Graph / Twitter Card Depth
OG image dimensions and Twitter card configuration look healthy
PASS
OG image dimensions and Twitter card configuration look healthy
Info::
OG/Twitter Card depth is clean -- dimensions, card type, and inheritance all valid
A+
Image Optimization
No images to analyze
PASS
No images to analyze
A+
Autoplay Media
No autoplay media on the page
PASS
No autoplay media on the page
Info::
No autoplay media on the page
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback