Skip to content
https://stores.jp

SEO

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

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

Checks
7
5 PASS 1 FIX
F
Content Depth
Action
289 words, Standard
FIX
289 words, Standard
Warning::
Page has 289 words — thin content
Most well-ranking pages have 300+ words of substantive content.
Info::
Text-to-HTML ratio is 4%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Standard (grade 16)
Warning::
Thin content — only 289 words
Got: 289 words
289 words

Thin content

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 16

Text-to-HTML Ratio

4% text 96% HTML

10 KB / 214 KB

Most well-ranking pages have 300+ words of substantive content.

Why this matters

Thin content (<300 words) rarely ranks — Google quality guidelines explicitly call out thin pages.

Source: Google Search Quality Guidelines

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://stores.fun
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target reachable (self-referencing)
Info::
Canonical points to a different domain
Canonical URL Problem
Page URL https://stores.jp Canonical https://stores.fun Match Self-referencing (correct)
A
Meta Tags
Title: 87 chars
PASS
Title: 87 chars
Info::
Page title is set
Got: STORES（ストアーズ） | 店舗の売上をあげる総合プラットフォーム
Warning::
Title is 87 characters — will be truncated in search results
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"STORES（ストアーズ） | 店舗の売上をあげる総合プラットフォーム"

87 characters Will truncate
Title: STORES（ストアーズ） | 店舗の売上をあげる総合プラットフォーム
H1: レジ・決済・予約・ECをひとつで管理できる店舗システム
Match: Very different
Robots: Indexable (no restrictions)

Alignment helps users confirm they've reached the right page.

Why this matters

Title and H1 disagree significantly — Google may treat one as the canonical topic and the other as off-topic, weakening ranking.

Learn more ▾

Title is the SERP headline; H1 is the on-page headline. They should describe the same page. Large divergence (different topics, different keywords) signals confusion and Google may rewrite the title in SERP. Align both to the same primary topic.

Source: Google Search Central / on-page SEO

A+
Image SEO
61 images, 57 descriptive filenames
PASS
61 images, 57 descriptive filenames
Info::
4 image(s) have hash/generic filenames
Info::
4 image(s) missing alt text — see Accessibility tab
57 descriptive
0 hash-based
4 generic
61 total
FilenameQualityAltIssues
0generic✓1
Current: 0
Suggested: action.jpg
0generic✓1
Current: 0
Suggested: action.jpg
0generic✓1
Current: 0
Suggested: action.jpg
0generic✓1
Current: 0
Suggested: action.jpg
adsctdescriptive✗1
adsctdescriptive✗1
adsctdescriptive✗1
adsctdescriptive✗1

See Accessibility tab for detailed alt text quality analysis.

A+
Schema Markup Audit
4 schema types detected
PASS

Rich result eligibility

Organization Eligible

Organization knowledge panel

WebSite Eligible

Sitelinks search box

FAQPage Eligible

FAQ rich results

Organization Eligible

Organization knowledge panel

Detected schema types

Organization json-ld → Organization knowledge panel
2/2 required · 4/4 recommended
Required fields (Google)
  • name — Required for the knowledge panel
  • url — Required for entity matching
Recommended fields
  • logo — Strongly recommended — appears in the knowledge panel header
  • sameAs — Connects the entity across the web
  • contactPoint — Enables direct contact from the knowledge panel
  • description — Used as the panel summary
Google's spec for this type
WebSite json-ld → Sitelinks search box
2/2 required · 0/1 recommended
Required fields (Google)
  • name — Required for the sitelinks search box
  • url — Required to anchor the search box to your domain
Recommended fields
  • potentialAction — Add a SearchAction with target and query-input Enables the in-SERP search box
Google's spec for this type
FAQPage json-ld → FAQ rich results
1/1 required
Required fields (Google)
  • mainEntity — Required — without this the FAQ schema is invalid
Google's spec for this type
Organization json-ld → Organization knowledge panel
2/2 required · 3/4 recommended
Required fields (Google)
  • name — Required for the knowledge panel
  • url — Required for entity matching
Recommended fields
  • logo — Strongly recommended — appears in the knowledge panel header
  • sameAs — Connects the entity across the web
  • contactPoint — Add ContactPoint with telephone and contactType Enables direct contact from the knowledge panel
  • description — Used as the panel summary
Google's spec for this type

Adding these recommended fields improves chances of getting Sitelinks search box in search results.

Why this matters

Schema entity has required fields but could add recommended ones for richer SERP layouts (star ratings, prices, etc.).

Source: Google Search Central

Adding these recommended fields improves chances of getting Organization knowledge panel in search results.

Why this matters

Schema entity has required fields but could add recommended ones for richer SERP layouts (star ratings, prices, etc.).

Source: Google Search Central

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