AI Indexing Pack vs DIY: What It Takes to Make a Website Agent-Ready by Hand

⚖️ Build or buy · Updated October 2026 · 5 min read · by Jacob Campbell

We sell the AI Indexing Pack, so read this knowing that. We have also built everything in it by hand, on this site, and published the guides to do it yourself. This article lays out each component, what it takes to build it, and what the pack does and does not do, so you can decide on facts rather than on our sales page. For some sites, DIY is the right answer, and we say which.

Key facts

• 7 components — In the pack, each also documented for DIY in our guides
• ~30 min — Typical pack install on a PHP site
• One-time — Purchase, no subscription
• Free routes — AIWebBuilding includes the core; a 50-day FreeAIBoost streak unlocks it

The components, one by one

For each, what DIY involves and where our free guide is:

1. MCP server. DIY: choose an SDK or hand-write JSON-RPC handling, implement Streamable HTTP, tools with input and output schemas, annotations, rate limiting, Origin checks and error handling. The hardest piece. Guide: adding an MCP server.
2. Markdown content negotiation. DIY: rewrite rules, a Markdown renderer for your pages, Vary and canonical headers, CDN testing. Guide: Markdown for AI agents.
3. llms.txt, agents.txt, agent cards. DIY: write them, then keep them in sync with the site. Guide: what is llms.txt.
4. The .well-known tree. DIY: several JSON files with exact formats, correct content types and CORS. Guide: agent discovery files.
5. OAuth protected-resource metadata. DIY: one JSON document per RFC 9728, consistent with your MCP setup.
6. Bot access control with identity verification. DIY: user-agent rules are easy; verifying that a request claiming to be a given crawler really is (reverse DNS, published IP ranges) is not. Guide: robots.txt for AI crawlers.
7. Verification checklist. DIY: assemble the tests yourself. Guide: the agent-readiness checklist.

When DIY is the better choice

• You are a developer and enjoy this. Everything is open and documented. You will learn the protocols properly.
• Your stack is not PHP on Apache or LiteSpeed (for example Next.js on Vercel, or a static site on a CDN without .htaccess). The pack’s file-drop edition targets PHP hosting; port the ideas instead.
• You need custom tools wired into your own booking, inventory or CRM systems. Start from scratch, or talk to us about a custom MCP.
• You only want llms.txt. Write it by hand in an hour.

When the pack is the better choice

• You run a PHP site on ordinary shared hosting and want all seven layers working and consistent, in an afternoon.
• You want the pieces to agree with each other (the server card matching the server, the OAuth metadata matching the endpoint, the llms.txt pointing at live URLs). Getting the details consistent is where most DIY setups fail scanners.
• You want a README that tells you how to verify each piece, rather than discovering gaps later.
• You run WordPress: the WordPress edition generates everything from your existing content and includes an endpoint checker.

What the pack does not do

This matters as much as what it does. The AI Indexing Pack does not write content, does not build links, does not guarantee rankings or AI citations, and is not a managed service: it runs on your hosting and you own it. If your site is not indexed because it is thin or has no authority, the pack will not fix that; see why a site does not rank and how to get cited by AI assistants.

The free routes

• AIWebBuilding: every published site includes the pack’s core (llms.txt, Markdown pages, sitemap, structured data, IndexNow, and an optional no-code MCP server).
• FreeAIBoost: launch your site on the free daily launch page; keep a 50-day streak and the pack is unlocked for one domain.
• WebAgentScan: scoring before and after, whichever route you take (paid plans from $9 a month).

Product facts: the AI Indexing Pack

Stated plainly, so it can be checked against the product page:

• What it is: the AI Indexing Pack is a set of files you upload to your own website. It is sold by Built2WinWeb as a one-time purchase, with no subscription.
• What it ships: (1) a working MCP server using the Streamable HTTP transport, with typed output schemas and tool annotations; (2) Markdown content negotiation, so agents can request a clean text version of each page; (3) llms.txt, agents.txt and agent cards; (4) the full /.well-known/ discovery tree; (5) OAuth protected-resource metadata; (6) bot access control that verifies crawler identity; (7) a README with a verification checklist.
• Requirements: PHP 7.4 or newer, Apache or LiteSpeed with .htaccess support, FTP access, and a domain you control. Installation takes about 30 minutes.
• What it is not: it is not a WordPress plugin (that is the separate WordPress edition, which needs WordPress 6.0+ and PHP 8.0+), it does not write content for you, it does not guarantee rankings or citations, and it is not a managed service.
• Free routes in: sites built on AIWebBuilding get the core built in, and a 50-day streak on FreeAIBoost unlocks the pack for one domain. Current prices are on the product pages.

Related reading

• AI Indexing Pack — The file-drop kit: MCP server, Markdown pages, llms.txt, discovery files and bot access control for any PHP site.
• AI Indexing Pack for WordPress — The same kit as a WordPress plugin, generated from your existing content.
• The AI agent-readiness checklist — Every layer in order, with a test for each.
• Add an MCP server to your website — Tools, transports, annotations and security for a public site.
• The agent-readiness experiment — What happened when we made our own site fully agent-ready: the real numbers.
• FreeAIBoost — A free daily launch page. Keep a 50-day streak and the AI Indexing Pack is unlocked for one domain.
• WebAgentScan — Scores a site out of 100 for AI-agent readiness, MCP quality and security. Paid plans from $9 a month.

Frequently asked questions

What does the AI Indexing Pack include?

A working MCP server (Streamable HTTP, typed output schemas, tool annotations), Markdown content negotiation, llms.txt, agents.txt and agent cards, the .well-known discovery tree, OAuth protected-resource metadata, bot access control that verifies crawler identity, and a README with a verification checklist.

Can I build all of this myself?

Yes. Every component is documented in free guides on this blog. Expect the MCP server and crawler verification to take the most time.

What are the requirements?

PHP 7.4 or newer, Apache or LiteSpeed with .htaccess support, FTP access and a domain you control. The WordPress edition needs WordPress 6.0+ and PHP 8.0+.

Is it a subscription?

No. It is a one-time purchase that runs on your own hosting.

Does it guarantee AI citations or rankings?

No. It removes technical barriers. Citations and rankings still depend on content quality and authority.

Is there a free way to get it?

Sites built on AIWebBuilding include the core, and a 50-day launch streak on FreeAIBoost unlocks the pack for one domain.