generatepress.com — C/100 agent-readiness

01Fail
/llms.txt
+6 pts if fixed
Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
See full details
02Fail
Explicit AI bot rules
+5 pts if fixed
Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
See full details
03Partial
robots.txt present & sane
+2 pts if fixed
Serve a non-blocking /robots.txt that references your Sitemap.
See full details

Hand-off prompt for your coding agent4 issues

# WordPress agent-readiness fixes

Site: https://generatepress.com/
Platform: wordpress (99% confidence)
AIScan score: 59/100 — Level 3 (Governed)
Rubric: v2026-06-08.1

Apply these in WordPress admin or via a small mu-plugin. Prefer the plugin route so changes survive theme updates.

## Failing checks
- **[D1] robots.txt present & sane** — PARTIAL
  - Evidence: 200 OK, 141 bytes
  - Fix: Serve a non-blocking /robots.txt that references your Sitemap.
- **[C2] /llms.txt** — FAIL
  - Evidence: HTTP 404
  - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- **[B2] Explicit AI bot rules** — FAIL
  - Evidence: 0 known AI agent(s) addressed in robots.txt
  - Fix: Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- **[D3] Link header for discovery** — PARTIAL
  - Evidence: Link: <https://generatepress.com/>; rel=shortlink
  - Fix: Add a Link header with rel="api-catalog" or rel="describedby".

## How to apply on WordPress
- **robots.txt / llms.txt**: drop static files at the web root (FTP / file manager), or use a small plugin that filters `robots_txt` and registers a rewrite rule for `/llms.txt`.
- **Markdown negotiation**: a mu-plugin hooking `template_redirect` can return `get_the_content()` as Markdown when `Accept: text/markdown` is present.
- **AI bot rules**: extend the robots.txt block above with user-agents (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, Bytespider, CCBot…).
- **MCP / Agent Skills cards**: place JSON files under `/.well-known/` via the same mu-plugin.

Avoid bloated SEO plugins — a single ~60-line mu-plugin covers all of this.

Discoverability

Can agents find your pages? robots, sitemaps, llms.txt.

Content

Can agents read your content cleanly? Markdown, structured data.

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · C2
What we found
HTTP 404
How to fix it
Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
1.⚡ Fix automatically with AIScan
The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.Create /llms.txt at the site root
Follows the llmstxt.org spec: a single H1, optional blockquote summary, then `##` sections of markdown links.
3.Template
# Example Co > One-line summary of what this site / product does. A short paragraph explaining the audience, what's here, and how to navigate it. ## Docs - [Getting started](/docs/quickstart): install, first call in 5 min - [API reference](/docs/api): all endpoints, params, examples ## Pages - [Pricing](/pricing): plans and limits - [Changelog](/changelog): recent releases ## Optional - [Brand assets](/press): logos and screenshots
4.On WordPress
Upload `llms.txt` to your site root via SFTP, or use a plugin like 'Website File Changes Monitor' / a custom must-use plugin that serves it from `wp-content/`.
5.Verify
After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Fix in ChatGPT Fix in Claude

Bot Access

Are AI crawlers explicitly allowed or blocked?

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · B2
What we found
0 known AI agent(s) addressed in robots.txt
How to fix it
Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
1.⚡ Fix automatically with AIScan
The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.Add explicit User-agent blocks
Don't rely on `User-agent: *` alone. Address each major AI crawler so your policy is unambiguous.
3.Recommended block
User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot-Extended Allow: /
4.Verify
After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Fix in ChatGPT Fix in Claude

Showcase your grade

Embed your AIScan badge

Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of generatepress.com on AIScan.site.

HTML

<!-- AIScan.site agent-readiness badge -->
<a href="https://aiscan.site/?u=https%3A%2F%2Fgeneratepress.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade C (59/100) — AIScan.site">
  <img src="https://aiscan.site/api/public/badge.svg?score=59&grade=C&host=generatepress.com" alt="AIScan.site Grade C — 59/100" width="240" height="64" loading="lazy" />
</a>

Markdown

[![AIScan.site Grade C — 59/100](https://aiscan.site/api/public/badge.svg?score=59&grade=C&host=generatepress.com)](https://aiscan.site/?u=https%3A%2F%2Fgeneratepress.com%2F)

Track this over time

Coming soon: save sites, schedule re-scans, get email when something material changes. Standards land weekly — your tracker shouldn't be one-shot.

Free · No signup · ~20 seconds

Scan your own site

Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.

Scan your site

Or browse the community feed to see what others have scanned.

WordPress

Quick Wins

/llms.txt

Explicit AI bot rules

robots.txt present & sane

Discoverability

robots.txt present & sane

XML sitemap

Link header for discovery

Content

Markdown content negotiation

/llms.txt

Structured HTML (title, meta, JSON-LD, single H1)

Bot Access

Content Signals in robots.txt

Explicit AI bot rules

Web Bot Auth key directory

Embed your AIScan badge

Track this over time

Scan your own site

WordPress

Quick Wins

/llms.txt

Explicit AI bot rules

robots.txt present & sane

robots.txt present & sane

XML sitemap

Link header for discovery

Markdown content negotiation

/llms.txt

Structured HTML (title, meta, JSON-LD, single H1)

Content Signals in robots.txt

Explicit AI bot rules

Web Bot Auth key directory

Share as a social image

Embed your AIScan badge

Track this over time

Scan your own site