SEO/AEO operating case study
Sudoku Coach SEO/AEO baseline report
This page records the real optimization loop for Sudoku Coach: what is live, what search engines can read, what is not indexed yet, and which improvements are being tested next.
Current diagnosis
Sudoku Coach is AEO-ready but not yet AEO-validated. The site has strong machine-readable surfaces, but core learning pages still need indexing, discovery, and query evidence.
Health
OK
Live HTML, JSON, sitemap, robots, and llms.txt endpoints return successfully.
AEO surfaces
Strong
Technique pages include structured summaries, FAQs, JSON endpoints, and schema.
Indexing
Partial
The homepage is indexed; core technique pages are still mostly discovered but not indexed.
Search signal
Early
No meaningful technique-page query impressions yet; this cycle is designed to create first discovery signal.
What is already working
- Crawlable static pages: the homepage, technique library, support/privacy pages, and explanation pages are served as HTML.
- Machine-readable data:
/llms.txt,/techniques.json, and per-technique JSON endpoints expose structured technique knowledge. - Structured technique schema: technique pages use learning-resource, defined-term, FAQ, question, and answer data.
- Clear learning content: technique pages include quick answers, recognition rules, examples, common mistakes, and app practice CTAs.
What is blocking growth
- Technique pages are not indexed yet: several priority pages are known to Google but remain “Discovered - currently not indexed.”
- Few trusted entry links: the site needs more high-signal links into specific technique pages, not only the homepage.
- Search data is immature: current impressions are mostly legal/support pages, not Sudoku learning pages.
- Long-tail examples are still early: the first three one-move explanation pages are now being tested for discovery and indexing.
Current optimization cycle
Evaluation → recommendation → implementation → re-evaluation
1. Evaluate
Check live endpoints, sitemap, Search Console, URL inspection, and query/page data.
2. Optimize
Prioritize actions that can improve indexing, discovery, answerability, or app conversion.
3. Implement
Ship bounded improvements such as this public baseline, explanation pages, and query-shaped guides.
4. Re-evaluate
After Search Console data matures, record what changed and choose the next cycle.
Next actions
What we are testing next
These are not generic recommendations. They are the current operating plan for turning the site from technically ready into search-visible and citation-worthy.
P0 · Refresh sitemap and request indexing
Re-submit the sitemap and inspect priority pages until Google starts crawling and indexing the core learning URLs.
P1 · Publish real one-move explanation pages
Test three Sudoku stuck-puzzle explanations that target long-tail “what is the next move?” intent and link back to the technique guides.
P1 · Add query-shaped supporting guides
Add comparison and beginner-intent pages such as “Single Candidate vs Hidden Single” and “When should I use candidate notes?”
Priority URLs being watched
These pages are the current indexing and discovery focus for the next evaluation window.
- https://sudoku.franklab.us/techniques/
- https://sudoku.franklab.us/techniques/single-candidate/
- https://sudoku.franklab.us/techniques/hidden-single/
- https://sudoku.franklab.us/techniques/naked-pair/
- https://sudoku.franklab.us/reddit-puzzles/demo-naked-pair-box-6/
- https://sudoku.franklab.us/reddit-puzzles/demo-hidden-single-row-2/
- https://sudoku.franklab.us/reddit-puzzles/demo-locked-candidates-column-9/
FAQ
AI-search readiness questions
Is Sudoku Coach ready for AI search engines?
Sudoku Coach has an AI-readable foundation with llms.txt, JSON technique endpoints, structured technique pages, FAQ schema, and a sitemap. The next growth bottleneck is discovery: several core technique pages are known to Google but not indexed yet.
What is the current SEO/AEO bottleneck?
The main bottleneck is not crawlability or schema quality. The priority is getting core technique pages indexed, increasing trusted links into those pages, and publishing query-shaped Sudoku explanation pages that can earn impressions.
Evaluation checkpoint
What will count as progress?
3 days
Priority URLs show newer crawl or coverage states in Search Console.
7 days
At least one Sudoku learning page starts showing impressions or page-level query evidence.
14 days
Use the result to decide whether to expand explanation pages, improve internal links, or revise targeting.
Baseline recorded: June 22, 2026. Measurements come from live endpoint checks, generated sitemap output, and Google Search Console URL inspection/search performance data available on that date.