Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
D
51/100
Site name appears as
| Page title | エキサイトブログ|使いやすい無料ブログ | |
| og:site_name | エキサイトブログ | |
| twitter:site | @excite_blog | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
12/15covers apple-touch-icon
Social share image
14/20og:image set; twitter:image missing
Meta completeness
20/20Organization schema
0/15Contact info discoverable
0/10no 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
- Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
- 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.
BOpen GraphOpen Graph tags are partially configured — some improvements recommended.REVIEW
https://md.exblog.jp/img/top/layout/image-ogp_exblog_logo.gifThe og:image URL could not be fetched. Social platforms won't be able to display it.
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
19 charsIdeal length is 25–60 characters for social sharing previews.
25–60 charsog:title very short — may render with awkward whitespace in social cards.
Source: Open Graph Protocol
The og:url tag specifies the canonical URL for the shared content.
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
Preview

exblog.jp
エキサイトブログ|使いやすい無料ブログ
写真家やプロカメラマンも愛用する画像にこだわる無料ブログサービス。洗練されたデザインで、料理、暮らし、アートなど、あらゆるテーマを自由に表現できます。アクセス解析、アフィリエイト、リッチリンクなどの機能も充実。
Description will be truncated (315 chars / 200 max)
- twitter:card — summary
- twitter:title — falling back from og:title
- twitter:description — falling back from og:description
- twitter:image — falling back from og:image
Description will be truncated on Twitter/X (315 chars, max 200)
→ Tighten the description to ≤200 characters

EXBLOG.JP
エキサイトブログ|使いやすい無料ブログ
写真家やプロカメラマンも愛用する画像にこだわる無料ブログサービス。洗練されたデザインで、料理、暮らし、アートなど、あらゆるテーマを自由に表現できます。アクセス解析、アフィリエイト、リッチリンクなどの機能も充実。
Description will be truncated (315 chars / 155 max)
- og:title — エキサイトブログ|使いやすい無料ブログ
- og:description — 写真家やプロカメラマンも愛用する画像にこだわる無料ブログサービス。洗練されたデザインで、料理、暮らし、アートなど、あらゆるテーマを自由に表現できます。アクセス解析、アフィリエイト、リッチリンクなどの機能も充実。
- og:image — https://md.exblog.jp/img/top/layout/image-ogp_exblog_logo.gif
- og:type — website
- og:url — Add og:url — Recommended — canonical URL for the share
- og:site_name — エキサイトブログ
Description will be truncated on Facebook (315 chars, max 155)
→ Tighten og:description to ≤155 characters

エキサイトブログ|使いやすい無料ブログ
exblog.jp
Description will be truncated (315 chars / 150 max)
- og:title — エキサイトブログ|使いやすい無料ブログ
- og:description — 写真家やプロカメラマンも愛用する画像にこだわる無料ブログサービス。洗練されたデザインで、料理、暮らし、アートなど、あらゆるテーマを自由に表現できます。アクセス解析、アフィリエイト、リッチリンクなどの機能も充実。
- og:image — https://md.exblog.jp/img/top/layout/image-ogp_exblog_logo.gif
Description will be truncated on LinkedIn (315 chars, max 150)
→ Tighten og:description to ≤150 characters
exblog.jp
エキサイトブログ|使いやすい無料ブログ
写真家やプロカメラマンも愛用する画像にこだわる無料ブログサービス。洗練されたデザインで、料理、暮らし、アートなど、あらゆるテーマを自由に表現できます。アクセス解析、アフィリエイト、リッチリンクなどの機能も充実。

Description will be truncated (315 chars / 300 max)
- og:title — エキサイトブログ|使いやすい無料ブログ
- og:description — 写真家やプロカメラマンも愛用する画像にこだわる無料ブログサービス。洗練されたデザインで、料理、暮らし、アートなど、あらゆるテーマを自由に表現できます。アクセス解析、アフィリエイト、リッチリンクなどの機能も充実。
- og:image — https://md.exblog.jp/img/top/layout/image-ogp_exblog_logo.gif
Long description may be shortened by Slack (315 chars, guideline ~300)
→ Consider tightening to ~300 chars for the cleanest unfurl
Social preview quality
Averaged across Twitter/X, Facebook, LinkedIn, and Slack.
| Field | Twitter/X | Slack | ||
|---|---|---|---|---|
| og:title | ||||
| og:description | ||||
| og:image | ||||
| og:type | ||||
| og:url | ||||
| og:site_name | ||||
| twitter:card | — | — | — | |
| twitter:title | ⚠ | — | — | — |
| twitter:description | ⚠ | — | — | — |
| twitter:image | ⚠ | — | — | — |
CStructured DataActionNo structured data (JSON-LD) found.REVIEW
Adding structured data helps search engines understand your content and can enable rich results.
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
A+Links200 links checked, 200 healthy, 0 brokenPASS
Broken Links (2)
| Status | URL | Found in | Error |
|---|---|---|---|
| 403 | https://ssl2.excite.co.jp/idc/login/?si=blog&ru=ht... | <a> | Forbidden |
| 403 | https://ssl2.excite.co.jp/idc/new/?si=blog&ru=http... | <a> | Forbidden |