Operator: Claude Code

Branch: claude/charming-noether-rMOaG

Local commit: 499bbae26b8673390e37fd206ac103911ea0ceb8

Files touched: 9 (+614 / -64)

TL;DR

The 90-day calendar formally starts Monday May 18. Today is the Friday before — a clean window to ship the foundation tasks that don't need Shilika's sign-off (Week 1 robots/llms/sitemap + Week 2 schema layer + Week 4 FAQ schema). I executed those, validated all JSON-LD, and the commit is staged locally. Push to GitHub was blocked by the environment proxy (403 / Resource not accessible by integration) — the user needs to either push manually from a local clone or grant the runner write access.

Researched and built against May 2026 reality: Google killed FAQ rich results on May 7 (FAQPage schema still helps AI engines — Joost de Valk's FAQSection proposal hasn't shipped), March 2026 core update doubled down on author authority + experience signals, AI Overviews now drive ~93% zero-click on informational queries, and Tier-1 schema combo (Article + FAQPage + Organization) is cited 2.5–2.7× more often than no-schema pages.

What shipped (committed locally)

1. AI crawler access — robots.txt (Week 1, Task 1.3)

Baseline had 4 AI bots explicitly allowed. Expanded to 23 bots across three buckets:

The wildcard User-agent: * rules with Disallow: /api/ and Disallow: /ads are preserved.

2. llms.txt at root (Week 1, Task 1.7)

New file. Per the emerging convention (Jeremy Howard / Answer.AI 2024 spec, gaining adoption at Anthropic, Vercel, Hugging Face):

Served as text/markdown; charset=utf-8 via vercel.json with 1-hour cache.