Skip to content
https://jugem.jp

Content

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

41/100

Site name appears as

Page title自分だけのこだわりブログをはじめよう
og:site_nameJUGEMブログ | 自分だけのこだわりブログをはじめよう
twitter:site—
Organization.name—

Inconsistent — names differ across channels

Brand assets

Favicon

8/15

single size only

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

14/20

Organization schema

0/15

Contact info discoverable

0/10

no contact info discoverable

Findings

  • Brand name differs across channels — users see inconsistent identity
  • Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
  • Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
  • twitter:card missing
  • 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.

B
Open Graph
Open Graph tags are partially configured — some improvements recommended.
REVIEW
Open Graph tags are partially configured — some improvements recommended.
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 twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

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

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

jugem.jp

JUGEMブログ | 自分だけのこだわりブログをはじめよう

PC・スマホ広告の非表示に完全対応。趣味や日記など自分だけのこだわりブログをJUGEMではじめてみませんか？無料でもはじめられます。

Preview quality · Twitter/X F · 45/100

Title will be truncated (71 chars / 70 max)

  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from og:title
  • twitter:description — falling back from og:description
  • twitter:image — falling back from og:image

  • twitter:card is missing

    → Add <meta name="twitter:card" content="summary_large_image">

  • Title will be truncated on Twitter/X (71 chars, max 70)

    → Shorten the title to ≤70 characters

JUGEM.JP

JUGEMブログ | 自分だけのこだわりブログをはじめよう

PC・スマホ広告の非表示に完全対応。趣味や日記など自分だけのこだわりブログをJUGEMではじめてみませんか？無料でもはじめられます。

Preview quality · Facebook D · 60/100

Title will be truncated (71 chars / 60 max)

Description will be truncated (184 chars / 155 max)

  • og:title — JUGEMブログ | 自分だけのこだわりブログをはじめよう
  • og:description — PC・スマホ広告の非表示に完全対応。趣味や日記など自分だけのこだわりブログをJUGEMではじめてみませんか？無料でもはじめられます。
  • og:image — https://imaging.jugem.jp/images/portal/common/ogimage.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 — JUGEMブログ | 自分だけのこだわりブログをはじめよう

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

    → Shorten og:title to ≤60 characters

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

    → Tighten og:description to ≤155 characters

JUGEMブログ | 自分だけのこだわりブログをはじめよう

jugem.jp

Preview quality · LinkedIn A+ · 95/100

Description will be truncated (184 chars / 150 max)

  • og:title — JUGEMブログ | 自分だけのこだわりブログをはじめよう
  • og:description — PC・スマホ広告の非表示に完全対応。趣味や日記など自分だけのこだわりブログをJUGEMではじめてみませんか？無料でもはじめられます。
  • og:image — https://imaging.jugem.jp/images/portal/common/ogimage.png

  • Description will be truncated on LinkedIn (184 chars, max 150)

    → Tighten og:description to ≤150 characters

jugem.jp

JUGEMブログ | 自分だけのこだわりブログをはじめよう

PC・スマホ広告の非表示に完全対応。趣味や日記など自分だけのこだわりブログをJUGEMではじめてみませんか？無料でもはじめられます。

Preview quality · Slack A+ · 100/100
  • og:title — JUGEMブログ | 自分だけのこだわりブログをはじめよう
  • og:description — PC・スマホ広告の非表示に完全対応。趣味や日記など自分だけのこだわりブログをJUGEMではじめてみませんか？無料でもはじめられます。
  • og:image — https://imaging.jugem.jp/images/portal/common/ogimage.png

Social preview quality

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

B · 75/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
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