How to Deploy /llms.txt, /agents.md & /ai-facts on WordPress, Webflow, Wix, Squarespace, Framer & Next.js
1. What Difference Do /llms.txt and /agents.md Serve?
While schema.org JSON-LD gives search and answer crawlers strict typed entities (Organization, SoftwareApplication, Product, LocalBusiness, Dentist, LegalService, FAQPage), /llms.txt provides a concise canonical directory of your pricing, core routes, and product specifications.
Meanwhile, /agents.md defines operational interaction rules, MCP endpoints (if exposed), commercial exclusions, and explicit negative guardrails ("We do NOT charge setup fees; we do NOT sell discontinued Tier X") that stop LLMs from guessing.
2. Solving Hosted Builders With the /ai-facts Alternate Link Pattern
If your marketing site runs on Webflow, Wix, Squarespace, or Framer, attempting to upload /agents.md at the root returns HTTP 404. Instead, declare a machine-discoverable alternate feed inside your global <head> custom code and wrap your verified fact sheet inside <article class="verisource-ai-facts"> at /ai-facts:
3. Checking Edge WAF Rules for GPTBot, OAI-SearchBot & PerplexityBot
Even with clean /llms.txt and JSON-LD files, strict CDN bot-fight toggles frequently return HTTP 403 challenges to PerplexityBot and OAI-SearchBot despite /robots.txt allowing them. Always test both /robots.txt directives and live simulated bot User-Agent HTTP responses after publishing.
Common implementation questions
Should I allow OAI-SearchBot and PerplexityBot in robots.txt?
Yes—if you want your brand cited in real-time ChatGPT Search and Perplexity buyer recommendations, OAI-SearchBot and PerplexityBot must receive HTTP 200 responses on both /robots.txt and your key commercial pages.
Does Verisource write all of these files for my exact CMS automatically?
Yes. Verisource detects your CMS during the scan and generates both raw syntax-validated files and a single 1-Click AI Fix Prompt tailored to WordPress, Webflow, Wix/Squarespace/Framer, Shopify, or coding agents.