DEV Community

Cover image for How I implemented 4 AI agent standards on a vanilla PHP blog (with code)
Shinobis IA
Shinobis IA

Posted on • Originally published at shinobis.com

How I implemented 4 AI agent standards on a vanilla PHP blog (with code)

#php #ai #webdev #seo

Cloudflare released isitagentready.com a scanner that grades your site's readiness for AI agents. My blog scored 50/100. No frameworks. No Node. Just PHP, MariaDB, and shared hosting.

Here's the thing: 6 of the 10 standards don't apply to blogs (OAuth, MCP, API Catalog). The 4 that matter took me under an hour to implement.

1. llms.txt your AI business card

A Markdown file at your domain root that tells LLMs who you are and what pages matter. Think robots.txt but for ChatGPT and Claude.

# Your Site Name

> Description of your site for AI models.

## Key Pages
[About](https://yoursite.com/about)
[Best Article](https://yoursite.com/best-article)
Enter fullscreen mode Exit fullscreen mode

Apache config so your PHP router doesn't eat it:

RewriteRule ^llms\.txt$ - [L]
Enter fullscreen mode Exit fullscreen mode

I built a free generator if you want to skip writing it manually.

2. Content Signals in robots.txt

One line. That's it:

Content-Signal: ai-train=no, search=yes, ai-input=yes

Translation: don't train on my content, but do cite me when answering questions.

3. Markdown for Agents

When an AI agent sends Accept: text/markdown, serve Markdown instead of HTML. Agents skip your nav, scripts, and layout they just want the content.

The .htaccess rule:

RewriteCond %{HTTP_ACCEPT} text/markdown
RewriteRule ^(.*)$ markdown-negotiator.php [L,QSA]
Enter fullscreen mode Exit fullscreen mode

The PHP side converts your HTML content: strip tags, convert <h2> to ##, <a> to [text](url), <strong> to **bold**. About 50 lines of regex.

4. Agent Skills discovery

A JSON file at /.well-known/agent-skills/index.json listing what agents can do on your site:

{
  "skills": [
    {
      "name": "llms.txt Generator",
      "url": "https://yoursite.com/tools/llmstxt-generator",
      "description": "Generate a valid llms.txt file"
    }
  ]
}
Enter fullscreen mode Exit fullscreen mode

What I ignored (and why you should too)

OAuth, MCP Server Card, WebMCP, API Catalog, Link headers all designed for SaaS platforms with public APIs. A blog doesn't need authentication tokens or API catalogs. Implementing them would be like putting airbags on a bicycle.

Results

50/100 with 4 standards implemented. Most blogs score 0. If you have these four things, you're more prepared for AI agents than 95% of the internet.

What's your site's score? Run the test at isitagentready.com and share your results in the comments. Curious to see what other stacks look like.

Top comments (0)