Skip to content
https://ana.co.jp

Content

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

ana.co.jp

No title set

No description

Preview quality · Twitter/X F · 15/100

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

ANA.CO.JP

No title set

No description

Preview quality · Facebook F · 0/100

Title will be truncated (68 chars / 60 max)

Description will be truncated (339 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 (68 chars, max 60)

    → Shorten og:title to ≤60 characters

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

ana.co.jp

Preview quality · LinkedIn D · 50/100

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

    → Tighten og:description to ≤150 characters

  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

ana.co.jp

No title set

No description

Preview quality · Slack C · 70/100

Description will be truncated (339 chars / 300 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

  • Long description may be shortened by Slack (339 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 · 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———
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 titleANAの航空券・飛行機 予約、空席照会、運賃案内|ANA
og:site_name—
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

12/15

covers apple-touch-icon

Social share image

0/20

Meta completeness

4/20

Organization schema

0/15

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
  • Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
  • og:title missing
  • og:image missing
  • twitter:card missing
  • No Organization schema — Google can't render your logo in the knowledge panel
  • 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.
Info::
Missing recommended property "description" for WebSite
Adding "description" can improve how search engines display your content.
Info::
Missing recommended property "potentialAction" for WebSite
Adding "potentialAction" can improve how search engines display your content.

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 "potentialAction" 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
4 properties Valid
{
  "@context": "http://schema.org",
  "@type": "WebSite",
  "name": "ANA",
  "url": "https://www.ana.co.jp"
}
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback