Skip to main content

Platform

AEO Website Research-grade Content Content Factory About Audits Rankings Pricing

Resources

Knowledge Base Research FAQ
Audit
OverviewHow to ImproveScore BreakdownSite PagesGuides
yoii.jp

yoii.jp

Weak AI visibility with 17 of 48 criteria passing. Biggest gap: llms.txt file.

41/100
1 since v1
F
Citation Avg
Answer Readiness
~40% weight
5/10
Content Structure
~25% weight
4/10
Trust & Authority
~15% weight
2/10
Technical Foundation
~10% weight
4/10
AI Discovery
~10% weight
3/10

Verdict

Critical AEO gaps at 41/100 - yoii.jp is largely invisible to AI engines. Key strengths include Table & List Extractability, Content Cannibalization, and Duplicate Content Blocks. Priority gaps: llms.txt File, Schema.org Structured Data, and Q&A Content Format.

#10085of 13363
View full rankings →
View improvement plan

How to Improve

Current
41/100
Projected
76/100
41Total Fixes
8Quick Wins
~102hEst. Effort
Quick Wins
Create /llms.txt fileConfigure robots.txt for AI crawlersBuild FAQ sections with schemaAdd ai.txt and content licensingFix canonical URL strategyImprove query-answer alignmentAdd visible date signalsReduce document weight
Create /llms.txt file
critical|low
Add llms-full.txt with extended content
medium|low
Create complete sitemap.xml
critical|medium
Fix HTML structure and meta tags
medium|low
Configure robots.txt for AI crawlers
critical|low
Reduce document weight
high|low
Fix canonical URL strategy
critical|low
Add internationalization signals
critical|medium
Improve server response efficiency
medium|low
Reduce render-blocking resources
low|low

Top Opportunities10

Publish original research, statistics, case studies, or proprietary data that AI engines can cite. Unique data points make your content a primary source rather than a derivative one.

Expand articles to 1000+ words with structured H2/H3 sections, comparison tables, and expert analysis. Thin content (under 300 words) is rarely cited by AI engines. Deep, well-structured articles demonstrate expertise.

Write concise, standalone answer paragraphs (2-3 sentences) immediately after question headings. These "snippet-ready" paragraphs are ideal for AI engine citations.

Add question-based headings (H2/H3) throughout your content. Use "What is...", "How does...", "Why should..." patterns that match how users query AI assistants.

Include "our analysis", "our data", "our testing" phrases backed by original research or proprietary data. 52.2% of AI-cited posts contain owned data signals.

Write 20-25 word self-contained answer sentences immediately after each H2 heading. 72.4% of AI-cited posts use this pattern - it gives engines a ready-made snippet to quote.

Define the primary entity in the first 500 characters, use consistent terminology (same term 70%+), and add "unlike X" signals to help AI engines distinguish your topics.

Write self-contained definition sentences and single-claim statements that AI engines can quote directly. Avoid pronouns like "this" or "that" at the start of answer paragraphs.

Include dateModified schema, visible last-updated dates, and time elements on content pages. Fresh content signals help AI engines prioritize your pages over stale alternatives.

Add inline citations to external sources, "According to [Source]..." attribution phrases, and a Sources section at the end of key articles.

Fix It With AI44

Your competitors are already optimizing for AI

Every day without action is traffic your site loses to AI-ready competitors. We fix that.

Fix My Score

Site Pages

Changes since v1Last audited 52 days ago
40
41
+1
View full comparison →
Add Original Data & Case StudiesIncrease Content DepthAdd Direct Answer ParagraphsRestructure Content as Q&AAdd Owned Data SignalsAdd Answer Capsule PatternsAdd Entity DisambiguationImprove Citation-Ready WritingAdd Content Freshness SignalsPackage Evidence for AI

Improve Your Score

Guides for the criteria with the most room for improvement

Related Questions

Browse all FAQs →

Want us to improve your score?

We build citation-ready content that AI engines choose as the answer.

Let's Talk