<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:ai="https://sitesfor.ai/ai-sitemap/0.1">
  <url><loc>https://sitesfor.ai/</loc><lastmod>2026-06-23T20:21:50.932Z</lastmod><ai:summary>Homepage. Hero, standards grid, studio-vs-saas comparison, what we do, pricing, agents, founder, FAQ, contact. All sections addressable by anchor (#pricing, #agents, #about, #faq, #contact).</ai:summary></url>
  <url><loc>https://sitesfor.ai/check</loc><lastmod>2026-06-23T20:21:50.932Z</lastmod><ai:summary>Free Checker entry. Light-path scan, 43 signals, letter grade A-F in seconds, deterministic Quick Wins, global and vertical percentile. Single URL in, report rendered inline.</ai:summary></url>
  <url><loc>https://sitesfor.ai/methodology</loc><lastmod>2026-06-23T20:21:50.932Z</lastmod><ai:summary>AI Readiness Index methodology — what the 43-signal Checker tests, how a scan becomes an anonymised corpus row, (domain, day) deduplication, owner-retest exclusion, and the site-type-classification logic.</ai:summary></url>
  <url><loc>https://sitesfor.ai/about</loc><lastmod>2026-06-23T20:21:50.932Z</lastmod><ai:summary>Founder bio and studio-model framing. Alexander Poplavsky, operator from Poland EU, operates globally.</ai:summary></url>
  <url><loc>https://sitesfor.ai/blog</loc><lastmod>2026-06-23T20:21:50.932Z</lastmod><ai:summary>Long-form essays, explainers, and benchmarks on AI-agent readiness. Named author (Alexander Poplavsky) on every post. Tag-filtered: essay, explainer, benchmark.</ai:summary></url>
  <url><loc>https://sitesfor.ai/policy.txt</loc><lastmod>2026-06-23T20:21:50.932Z</lastmod><ai:summary>Plain-text privacy policy and security disclosure combined: data-controller identity, tracking-cookies stance, what-we-observe explanation, outbound-scan ethics, security contact (RFC 9116 mirror).</ai:summary></url>
  <url><loc>https://sitesfor.ai/blog/ai-readiness-score-is-not-enough</loc><lastmod>2026-06-07T00:00:00.000Z</lastmod><ai:summary>Free AI-readiness scanners are everywhere now. We scanned 97 leading B2B SaaS sites — 84 of them (87%) scored an F. The score was never the hard part. Shipping the fix into your codebase is.</ai:summary></url>
  <url><loc>https://sitesfor.ai/blog/build-time-vs-runtime-jsonld</loc><lastmod>2026-05-25T00:00:00.000Z</lastmod><ai:summary>Three failure modes of hand-rolled structured data — and the build-time fix that ships in your repo, not someone else&apos;s.</ai:summary></url>
  <url><loc>https://sitesfor.ai/blog/studio-not-platform</loc><lastmod>2026-05-25T00:00:00.000Z</lastmod><ai:summary>Why the GEO layer should ship into the customer&apos;s repository, not run on someone else&apos;s domain — and why a retainer can stay on the right side of that line.</ai:summary></url>
  <url><loc>https://sitesfor.ai/blog/what-does-ai-agent-ready-mean</loc><lastmod>2026-05-25T00:00:00.000Z</lastmod><ai:summary>A website is AI-agent-ready when crawlers, assistants, and buyer agents can each use it fluently against published, vendor-neutral standards.</ai:summary></url>
</urlset>