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

SEO

· 7 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
1
PASS
5
INFO
1

Cross-tab audit — SEO, performance, crawlability, mobile, structured data

Checks
7
5 PASS 1 REVIEW
C
Content Depth
Action
930 words, Difficult
REVIEW
930 words, Difficult
Info::
Page has 930 words of content
Info::
Text-to-HTML ratio is 5%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Difficult (grade 21)
930 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 21

Text-to-HTML Ratio

5% text 95% HTML

25 KB / 518 KB

Very low ratio suggests heavy framework overhead or boilerplate.

Why this matters

Informational: ratio of visible text bytes to total HTML bytes. Very low ratios suggest excessive markup overhead.

A+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://www.infoseek.co.jp
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target returns 200
Info::
Canonical points to a different domain
Canonical URL Configured
Page URL https://infoseek.co.jp Canonical https://www.infoseek.co.jp Match Self-referencing (correct) Target 200 ✓
A
Meta Tags
Title: 76 chars
PASS
Title: 76 chars
Info::
Page title is set
Got: Infoseek[インフォシーク] - 楽天が運営するニュースサイト
Warning::
Title is 76 characters — will be truncated in search results
Info::
Title and H1 are identical
Consider differentiating — the title is for search results, the H1 is for the page.
Title

"Infoseek[インフォシーク] - 楽天が運営するニュースサイト"

76 characters Will truncate
Title: Infoseek[インフォシーク] - 楽天が運営するニュースサイト
H1: 楽天Infoseek
Match: Similar ✓
Robots: Indexable (no restrictions)

Consider differentiating — the title is for search results, the H1 is for the page.

Why this matters

Title and H1 match exactly — internally consistent but misses an opportunity to optimize each for its audience (Title for SERP CTR, H1 for on-page).

Learn more ▾

Title and H1 don't have to be identical — and often shouldn't be. The Title competes for SERP click-through (lead with keyword + value prop), while the H1 confirms to the visitor they're on the right page (more conversational is fine). Differentiating gains both surfaces.

Source: Google Search Central / on-page SEO

A+
Image SEO
20 images, 13 descriptive filenames
PASS
20 images, 13 descriptive filenames
Info::
7 image(s) have hash/generic filenames
13 descriptive
0 hash-based
7 generic
20 total
FilenameQualityAltIssues
.generic✓1
.generic✓1
.generic✓1
.generic✓1
.generic✓1
.generic✓1
.generic✓1

See Accessibility tab for detailed alt text quality analysis.

A+
Schema Markup Audit
Per-type completeness vs Schema.org requirements + rich-result eligibility
PASS

No structured data detected

Without JSON-LD or microdata, this page can't qualify for any of Google's rich result formats. Even basic Organization or WebSite schema is a quick win.

Hreflang
0 hreflang tags
INFO
0 hreflang tags

No hreflang tags detected.

Hreflang tags are only needed for multilingual or multi-regional sites.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback