SEO
· 14 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.Cross-tab audit — SEO, performance, crawlability, mobile, structured data
DContent DepthAction51 words, Fairly EasyFIX
Thin content
Reading level
Grade 8
Text-to-HTML Ratio
1 KB / 6 KB
Most well-ranking pages have 300+ words of substantive content.
Thin content (<300 words) rarely ranks — Google quality guidelines explicitly call out thin pages.
Source: Google Search Quality Guidelines
BCanonical URLMinor issuesREVIEW
Search engines will determine the canonical URL themselves, which may cause duplicate content issues.
Without a canonical, Google may treat each URL variant (with/without slash, with tracking params, http/https) as duplicate content and split ranking.
Learn more ▾ ▴
A canonical link tells Google which URL is the 'real' one when multiple URLs serve identical content. Without it, link equity gets split across variants and none of them rank as well as a single canonical version would. One <link rel="canonical"> tag in <head> covers it.
Source: Google Search Central
CSitemap FreshnessActionSitemap exists but no <lastmod> entriesREVIEW
BSitemap Hygiene1 hygiene issue(s) on a 0-URL sitemapREVIEW
AMeta TagsTitle optimizedPASS
"o-sumo | 大相撲 番付・星取表"
Without a meta description, Google auto-generates a snippet from page content -- usually less click-attractive than a hand-written summary. Add `<meta name="description" content="...">` with a 70-160 char summary.
No meta description -- Google auto-generates a SERP snippet from page content, usually less click-attractive than a hand-written summary.
Learn more ▾ ▴
Meta description is shown as the snippet under the title in search results. A well-written description significantly improves click-through rate. Add `<meta name="description" content="...">` with a 70-160 character summary.
Source: Google Search Central
Consider differentiating — the title is for search results, the H1 is for the page.
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
ATitle Style Depth1 title-style issue(s) detectedPASS
A+Internal Links24 internal, 2 externalPASS
Link Distribution
Anchor Text Quality
Most Linked Internal Pages
| # | URL | Links |
|---|---|---|
| 1 | / | 2 |
| 2 | /20260309-torikumi/ | 1 |
| 3 | /20260321-torikumi/ | 1 |
| 4 | /20260315-torikumi/ | 1 |
| 5 | /20260319-torikumi/ | 1 |
| 6 | /20260320-torikumi/ | 1 |
| 7 | /20260322-torikumi/ | 1 |
| 8 | /20260310-torikumi/ | 1 |
| 9 | /202603-yotei/ | 1 |
| 10 | /20260308-torikumi/ | 1 |
Top External Domains
| Domain | Links |
|---|---|
| x.com | 1 |
| github.com | 1 |
A+Image SEONo imagesPASS
A+Hreflang URL QualityNo hreflang tags on the pagePASS
A+Hreflang CompletenessNo hreflang tags on this page -- check is N/A (single-language site or unannotated)PASS
A+Sitemap × Robots ConsistencyNo sitemap-vs-robots conflicts detectedPASS
A+Markup QualityNo markup-quality issues detectedPASS
A+Schema Markup AuditPer-type completeness vs Schema.org requirements + rich-result eligibilityPASS
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.
Hreflang0 hreflang tagsINFO
No hreflang tags detected.
Hreflang tags are only needed for multilingual or multi-regional sites.