Skip to content
https://fliphtml5.com

Content

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

fliphtml5.com

No title set

No description

Preview quality · Twitter/X F · 20/100
  • 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">

  • No preview image for Twitter/X

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

No image set

FLIPHTML5.COM

No title set

No description

Preview quality · Facebook F · 5/100

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

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

fliphtml5.com

Preview quality · LinkedIn D · 50/100

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

    → Tighten og:description to ≤150 characters

  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

fliphtml5.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 · 36/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
Structured Data
Action
2 JSON-LD block(s) found — issues found that may affect search visibility.
FIX
2 JSON-LD block(s) found — issues found that may affect search visibility.
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 \"@context\": \"https://sc\n\t^...............................\n"
Warning::
Missing required property "name" for WebSite
The "name" property is required for the WebSite schema type.
Info::
Missing recommended property "description" for WebSite
Adding "description" can improve how search engines display your content.
Info::
2 JSON-LD blocks found

JSON parse error: Mismatch type map[string]interface {} with value array "at index 0: mismatched type with value\n\n\t[{\n \"@context\": \"https://sc\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

The "name" property is required for the WebSite 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 "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

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 \"@context\": \"https://sc\n\t^...............................\n"
[
  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "name": "FlipHTML5",
    "url": "https://fliphtml5.com/",
    "logo": "https://fliphtml5.com/images/logo_white.png",
    "description": "FlipHTML5 - online flipbook maker & digital publishing platform.",
    "contactPoint": [
      {
        "@type": "ContactPoint",
        "email": "support@fliphtml5.com",
        "contactType": "customer support"
      }
    ],
    "sameAs": [
      "https://www.facebook.com/FlipHTML5",
      "https://twitter.com/fliphtml5"
    ]
  },
  {
    "@context": "https://schema.org/",
    "@type": "HowTo",
    "name": "How to make a flipbook online?",
    "step": [
      {
        "@type": "HowToStep",
        "text": "Upload your PDF to FlipHTML5 and convert the static PDF to an interactive flipbook in minutes. Customize the layouts with pre-designed resources.",
        "name": "1. Upload Your PDF."
      },
      {
        "@type": "HowToStep",
        "text": "Level up your content by adding links, videos, images, buttons, and other rich assets to attract the most attention and gain more influence.",
        "name": "2. Enrich the Flipbook with Multimedia."
      },
      {
        "@type": "HowToStep",
        "text": "Share your book on social media or via email to get the most impact. Use the metric tool to analyze the performance.",
        "name": "3. Grab the Link and Share."
      }
    ]
  }
]
Block 2 : WebSite
4 properties Valid
Missing required property: name
{
  "@context": "https:\/\/schema.org",
  "@type": "WebSite",
  "url": "https:\/\/fliphtml5.com\/",
  "potentialAction": {
    "@type": "SearchAction",
    "target": {
      "@type": "EntryPoint",
      "urlTemplate": "https:\/\/fliphtml5.com\/exploring\/?q={search_term_string}"
    },
    "query-input": {
      "@type": "PropertyValueSpecification",
      "valueRequired": "TRUE",
      "valueName": "search_term_string"
    }
  }
}
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

26/100

Site name appears as

Page titleNew-Feature
og:site_name—
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

8/15

single size only

Social share image

0/20

Meta completeness

4/20

Organization schema

4/15

Organization schema present but missing all recommended fields

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
  • Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
  • og:title missing
  • 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
  • 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