1import{c9 as a,j as s,L as t}from"./index-DCkA9xGt.js";import{D as l}from"./DocsLayout-iRTJ5Cog.js";import{F as d,t as c}from"./FurtherReading-W7qHVTL-.js";import"./chevron-left-C0cOdp3D.js";import"./book-open-BY3KF-Tx.js";const n=[["/docs/platforms/wordpress","WordPress","robots.txt, llms.txt, sitemap, Yoast/Rank Math, AI bot rules."],["/docs/platforms/shopify","Shopify","robots.txt.liquid, product feeds, structured data, theme limits."],["/docs/platforms/lovable","Lovable","public/ files, server routes, MCP endpoints, llms.txt."],["/docs/platforms/replit","Replit","static assets, robots, llms.txt, deployment caveats."],["/docs/platforms/nextjs","Next.js / Vercel","App Router metadata, route handlers, public/ files, edge headers."]];function x(){const o=a.useLoaderData();return s.jsxs(l,{path:"/docs/platforms",children:[s.jsx("p",{children:"The same check needs a different fix on every platform. WordPress writes robots through a plugin, Shopify compiles it from a Liquid template, and Next.js owns it as a static file. Pick your stack:"}),s.jsx("ul",{children:n.map(([e,r,i])=>s.jsxs("li",{children:[s.jsx(t,{to:e,children:s.jsx("strong",{children:r})})," â ",i]},e))}),s.jsxs("p",{children:["Don't see your platform? Most static-site generators (Hugo, Eleventy, Astro, Jekyll) work like Next.js for AIScan purposes â drop files into ",s.jsx("code",{children:"public/"})," or ",s.jsx("code",{children:"static/"})," and they're served at the root. Longer walkthroughs for each stack live in the ",s.jsx(t,{to:"/guides",children:"guide library"}),"."]}),s.jsx(d,{items:c(o)})]})}export{x as component};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.