Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DLinksAction200 links checked, 193 healthy, 7 brokenFIX
Broken Links (8)
| Status | URL | Found in | Error |
|---|---|---|---|
| ERR | https://www.rakuten.co.jp/ | <a> | Get "https://www.rakuten.co.jp/": contex... |
| ERR | https://books.rakuten.co.jp/ | <a> | Get "https://books.rakuten.co.jp/": cont... |
| ERR | https://books.rakuten.co.jp/e-book/ | <a> | Get "https://books.rakuten.co.jp/e-book/... |
| ERR | https://brandavenue.rakuten.co.jp/ | <a> | Get "https://brandavenue.rakuten.co.jp/"... |
| ERR | https://www.rakuten-bank.co.jp/ | <a> | Get "https://www.rakuten-bank.co.jp/": c... |
| ERR | https://www.linkshare.ne.jp/bestshare/ | <a> | Get "https://www.linkshare.ne.jp/bestsha... |
| ERR | https://www.rakuten.co.jp/sitemap/ | <a> | Get "https://www.rakuten.co.jp/sitemap/"... |
| 403 | https://yads.c.yimg.jp/js/yads-async.js | <script> | Forbidden |
Redirects (2)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://gum.criteo.com/sync?c=72&r=2&j=T... | https://gum.criteo.com/sync?c=72&r=2&j=T... | <script> | 0 |
| https://www.infoseek.co.jp/mission/list/ | https://www.infoseek.co.jp/mission/list/ | <a> | 0 |
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
41/100
Site name appears as
| Page title | Infoseek[インフォシーク] - 楽天が運営するニュースサイト | |
| og:site_name | Infoseek | |
| twitter:site | — | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
8/15single size only
Social share image
14/20og:image set; twitter:image missing
Meta completeness
14/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
- 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.
BOpen GraphOpen Graph tags are partially configured — some improvements recommended.REVIEW
https://media.image.infoseek.co.jp/shared/news/og/infoseeklogo.pngThe 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
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.
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

infoseek.co.jp
Infoseek[インフォシーク] - 楽天が運営するニュースサイト
Infoseek(インフォシーク)は、社会、経済、国際、芸能、スポーツ、IT、天気等の最新ニュースを配信しています。楽天ポイントが獲得出来るお小遣いコンテンツ(ポイ活)やお得な情報も充実しています。
Title will be truncated (76 chars / 70 max)
Description will be truncated (277 chars / 200 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 (76 chars, max 70)
→ Shorten the title to ≤70 characters
Description will be truncated on Twitter/X (277 chars, max 200)
→ Tighten the description to ≤200 characters

INFOSEEK.CO.JP
Infoseek[インフォシーク] - 楽天が運営するニュースサイト
Infoseek(インフォシーク)は、社会、経済、国際、芸能、スポーツ、IT、天気等の最新ニュースを配信しています。楽天ポイントが獲得出来るお小遣いコンテンツ(ポイ活)やお得な情報も充実しています。
Title will be truncated (76 chars / 60 max)
Description will be truncated (277 chars / 155 max)
- og:title — Infoseek[インフォシーク] - 楽天が運営するニュースサイト
- og:description — Infoseek(インフォシーク)は、社会、経済、国際、芸能、スポーツ、IT、天気等の最新ニュースを配信しています。楽天ポイントが獲得出来るお小遣いコンテンツ(ポイ活)やお得な情報も充実しています。
- og:image — https://media.image.infoseek.co.jp/shared/news/og/infoseeklogo.png
- og:type — article
- og:url — https://www.infoseek.co.jp
- og:site_name — Infoseek
Title will be truncated on Facebook (76 chars, max 60)
→ Shorten og:title to ≤60 characters
Description will be truncated on Facebook (277 chars, max 155)
→ Tighten og:description to ≤155 characters

Infoseek[インフォシーク] - 楽天が運営するニュースサイト
infoseek.co.jp
Description will be truncated (277 chars / 150 max)
- og:title — Infoseek[インフォシーク] - 楽天が運営するニュースサイト
- og:description — Infoseek(インフォシーク)は、社会、経済、国際、芸能、スポーツ、IT、天気等の最新ニュースを配信しています。楽天ポイントが獲得出来るお小遣いコンテンツ(ポイ活)やお得な情報も充実しています。
- og:image — https://media.image.infoseek.co.jp/shared/news/og/infoseeklogo.png
Description will be truncated on LinkedIn (277 chars, max 150)
→ Tighten og:description to ≤150 characters
infoseek.co.jp
Infoseek[インフォシーク] - 楽天が運営するニュースサイト
Infoseek(インフォシーク)は、社会、経済、国際、芸能、スポーツ、IT、天気等の最新ニュースを配信しています。楽天ポイントが獲得出来るお小遣いコンテンツ(ポイ活)やお得な情報も充実しています。

- og:title — Infoseek[インフォシーク] - 楽天が運営するニュースサイト
- og:description — Infoseek(インフォシーク)は、社会、経済、国際、芸能、スポーツ、IT、天気等の最新ニュースを配信しています。楽天ポイントが獲得出来るお小遣いコンテンツ(ポイ活)やお得な情報も充実しています。
- og:image — https://media.image.infoseek.co.jp/shared/news/og/infoseeklogo.png
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