What problem does it solve? Adding machine-readable SEO and AEO metadata to an Astro 7 site on Cloudflare Workers involves scattered pieces — JSON-LD graphs, sitemaps, robots.txt, llms.txt, canonical and Open Graph tags — each with platform-specific traps like on-demand routes missing from the sitemap and CSP conflicts with inline scripts. ## Core Features & Use Cases - Typed JSON-LD @graph: Build a cross-linked schema-dts entity graph (Organization, WebSite, WebPage, BreadcrumbList, page entity) rendered as one CSP-exempt inline block per page. - Sitemap, robots.txt, llms.txt: Configure @astrojs/sitemap with lastmod wiring and on-demand-route workarounds, plus prerendered text endpoints with verified AI-crawler tokens. - Head component: Hand-rolled canonical, Open Graph, and Twitter meta derived from Astro.site, with seams for hreflang and dynamic OG images. - Use Case: When launching a brand site, generate the full structured-data layer, validate it with the exported CI script, and hand the merge gate to the perf-ci-gates workflow. ## Quick Start Add the complete SEO and structured-data layer to my Astro site on Cloudflare, including the JSON-LD graph, sitemap, robots.txt, and llms.txt.