Module 03 · Website Agentic Optimization
The foundation. Makes your site readable + trusted by AI crawlers.
Schema.org markup (Organization, Person, Article, FAQ, Speakable, mentions). llms.txt + robots.ai. Core Web Vitals. AI-crawler accessibility. Optional full migration from WordPress / Webflow / Tilda. The technical layer that lets Hermes + ContentOS actually compound.
Crawled by
- ChatGPT
- Claude
- Perplexity
- Gemini
- Grok
- DeepSeek
- Kimi
- Google AIO
- Copilot
Why the foundation matters
You can ship perfect content into a broken foundation. It will not get cited.
AI engines do not browse the way humans do. They send a crawler (ClaudeBot, Gptbot, PerplexityBot, OAI-SearchBot, etc), read the structured data + page text in one pass, and decide whether the page is citation-worthy. If your robots.txt blocks them, your schema is missing, your llms.txt does not exist, or your Core Web Vitals fail — they often do not re-crawl. You can be the best-written page in your category and remain invisible.
Website Agentic Optimization is the layer Hermes measures lift against. Without it, the work ContentOS ships goes nowhere.
Schema.org
Full markup, not just Organization
Organization (with sameAs entity graph), Person (with knowsAbout + sameAs LinkedIn/GitHub), Article (with author + datePublished + speakable + wordCount), FAQPage (with Question/Answer), BreadcrumbList, SpeakableSpecification, mentions array per page for entity disambiguation.
AI accessibility
llms.txt + robots.ai + AI-crawler allowlist
llms.txt as the AI-readable site summary. llms-full.txt with the long-form corpus. robots.ai allowing ClaudeBot, Gptbot, PerplexityBot, OAI-SearchBot, Google-Extended explicitly. Server logs surface crawler hit count as a leading indicator of citation lift.
Performance
Core Web Vitals + image CDN
INP / LCP / CLS targets baked into the build pipeline. Image CDN migration (Sanity, Cloudflare R2). Font preload. CSS bundle discipline. No client-side hydration on static pages. Lighthouse 95+ on every shipped page.
Migration scope · what a Done-for-you engagement covers
WordPress → Astro / Next.js / Hugo. Every URL traceable, every signal preserved.
- URL inventory + redirect map — every legacy URL audited (we audited 787 on humanswith.ai itself). 301 redirects preserve link equity; no 404s on legacy backlinks.
- Content migration — WP REST API or MDX export → new framework's content collections. EN + RU + AR preserved. Frontmatter + body + media + canonical mapping.
- Schema upgrade — every page gets the full schema.org graph. Article on blog, FAQ on /pricing, Person on /team, Service on /platform, etc.
- llms.txt + sitemap rebuild — sitemap-index.xml + per-locale sitemaps + lastmod + priority + changefreq. llms.txt + llms-full.txt with up-to-date corpus.
- AI-crawler verification — robots.ai allowlist deployed; server log access to track first-crawl events from each major bot.
- Performance budget — Lighthouse 95+ pre-launch on representative pages. CWV monitored post-launch via PageSpeed Insights API.
- Hermes baseline + 60-day lift measurement — citation share measured pre-migration; re-measured at +30, +60 days. Target: +15% citation lift attributable to the technical upgrade.
Reference dogfood: we ran this exact playbook on humanswith.ai itself in 2026 — 787 URLs, 143 blog posts, 35 case studies, EN+RU+AR locales. Two-month rebuild, every redirect preserved, every schema upgraded. Read the case →
FAQ
Website Agentic Optimization — common questions.
What is the difference between traditional SEO and Website Agentic Optimization?
Traditional SEO optimises for Google ranking: keywords, internal links, page speed, backlinks. Website Agentic Optimization adds the layer AI engines need to TRUST and CITE you: schema.org markup (Organization, Person, Article, FAQ, Speakable, mentions), llms.txt declaration, robots.ai allowlist, AI-crawler accessibility, canonical entity graph. AI engines do not click into your site — they read the structured data on first crawl and re-cite based on it.
Is llms.txt actually used by AI engines?
OpenAI, Anthropic, and Perplexity have all signalled support; adoption is partial but growing fast in 2026. Even when the engine ignores llms.txt directly, the file forces you to maintain a structured public summary of your site — which the AI crawler reads anyway. Cost to ship: ~30 min. Cost to skip: invisible re-crawl signal.
Which schema.org types matter most for AEO?
In order of citation impact: Organization (with sameAs entity graph), Person (with knowsAbout + sameAs), Article (with author + datePublished + speakable), FAQPage (with Question/Answer), BreadcrumbList (with itemListElement), SpeakableSpecification (cssSelector hint for voice). Most sites have Organization + Article but skip Speakable + mentions — the two with highest AEO leverage today.
Do you handle the migration from WordPress / Tilda / Webflow?
Yes — full WP → Astro/Next.js/Hugo migration on Done-for-you tier. We migrated humanswith.ai itself in 2026 (787 legacy URLs, 143 blog posts, 35 case studies, EN+RU+AR locales) — every redirect preserved, every schema upgraded, every URL traceable. The migration runbook is our own dogfood case.
What about Core Web Vitals?
Part of the package on Scale + Done-for-you. INP / LCP / CLS targets baked into the build pipeline. Image CDN migration, font preload, CSS bundle discipline, no client-side hydration on static pages. Lighthouse 95+ on every shipped page (vs. WP averages of 50-70).
Can you fix my schema without a full migration?
Yes — schema-only engagement on Done-for-you ($5K+). Schema audit + JSON-LD generation + integration into your existing CMS (WP plugin, Webflow embed, Shopify metafield, custom). No site migration required. Output: validated structured data on every page within 4-6 weeks.
How do you measure technical-SEO impact?
Three signals: (1) Hermes citation lift after schema deploy (target +15% in 60 days); (2) Google Search Console Rich Results coverage for FAQ/Article/Breadcrumb (target 100% valid); (3) AI-crawler hit count from server logs (Gptbot, ClaudeBot, PerplexityBot, OAI-SearchBot — target 50+ hits/week post-deploy). All three reported monthly.
Audit your foundation. Free.
You arrive to a per-engine technical-readiness map, the closeable gaps, and an honest read on whether full migration is worth the lift vs. schema-only fix.