Why we think this is WordPress (5 signals)
- · /wp-content/ asset in head
- · WP REST API link (api.w.org)
- · WP pingback link
- · /wp-content/themes|plugins|uploads/
- · WP block/emoji/embed asset
1 failed · 2 partial out of 7 that apply to your site.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+6 pts if fixed
/llms.txt
See full detailsPublish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- 02Partial+2 pts if fixed
Link header for discovery
See full detailsAdd a Link header with rel="api-catalog" or rel="describedby".
- 03Partial+2 pts if fixed
Explicit AI bot rules
See full detailsAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
# WordPress agent-readiness fixes Site: https://wpmudev.com/ Platform: wordpress (99% confidence) AIScan score: 72/100 — Level 4 (Interactive) 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 - **[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** — PARTIAL - Evidence: 1 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://wpmudev.com/api/>; rel="https://api.w.org/" - 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
85Can agents find your pages? robots, sitemaps, llms.txt.
Content
67Can 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 foundHTTP 404
How to fix itPublish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
1.⚡ Fix automatically with AIScanThe 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 rootFollows 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 WordPressUpload `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.VerifyAfter deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Bot Access
60Are AI crawlers explicitly allowed or blocked?
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of wpmudev.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fwpmudev.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade B (72/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=72&grade=B&host=wpmudev.com" alt="AIScan.site Grade B — 72/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fwpmudev.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.
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.
Scan your site