Is wpmanageninja.com AI agent ready? B · 68/100

1 remaining issue needs a different fix: E3 Heading hierarchy & server-rendered text. ThinkRank does not solve those — see each check below for the manual steps.

ThinkRank is a free WordPress plugin from the team behind AIScan. Every check above is also fixable by hand — the per-check guides below keep the manual robots.txt, PHP and WPCode steps.

Get ThinkRank for WordPress

Fix automatically with AIScan

4 open checks (3 failing) can be handed to an AI agent: C2, C3, B2, E3. Pick one route — each returns the full, check-by-check instructions.

Option A — Agent Skill (any runtime)

npx add-skill https://aiscan.site/aiscan-skill.json

Then ask your agent: “Fix the failing AI readiness checks for https://wpmanageninja.com/”.

Option B — Claude Code (CLAUDE.md)

curl -o CLAUDE.md https://aiscan.site/CLAUDE.md

Drop it in your project root, then ask Claude Code to fix the failing AIScan checks.

Option C — MCP client

https://aiscan.site/api/mcp

Tools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://wpmanageninja.com/" }.

Option D — REST API

curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fwpmanageninja.com%2F'

Returns every check with its complete fix guide.

Verify: Re-scan at https://aiscan.site after applying fixes, or run npx aiscan-cli https://wpmanageninja.com/. Individual checks that need a specific probe list it in their own guide.

Quick Wins

Top 3 fixes ranked by score impact

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
03Fail
Heading hierarchy & server-rendered text
+4 pts if fixed
Server-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship.
See full details

Hand-off prompt for your coding agent4 issues

# WordPress agent-readiness fixes

Site: https://wpmanageninja.com/
Platform: wordpress (99% confidence)
AIScan score: 68/100 — Level 3 (Governed)
Rubric: v2026.08.2

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** — FAIL
  - Evidence: 0 known AI agent(s) addressed in robots.txt
  - Fix: Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL
  - Evidence: h1: 0, title: true, meta description: true, JSON-LD: true
  - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[E3] Heading hierarchy & server-rendered text** — FAIL
  - Evidence: 45 words of server-rendered text, 0 <h2>, 0 <h3>
  - Fix: Server-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship.

## 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.

How this score is calculated

Every check earns points against a weight. We divide the points you earned by the points that actually apply to a WordPress — so checks that don't apply never drag you down.

Essential

21 / 31 pts

Baseline every site should meet.

Recommended

14 / 20 pts

Strong signals most sites benefit from.

Bonus earned

0 signals

Emerging standards. Can only add points.

Not counted (7): B1, B3, P1, P2, P3, P4, E2 — either not applicable to this site profile or optional and not yet adopted. Expand any check to see the exact evidence we based it on.

Discoverability

100

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

Content

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

212

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
Measured against
llms.txt proposal
How to fix it
Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
Fix with Yoast SEO
Yoast SEO is installed on this site. It covers robots.txt, XML sitemaps, titles/meta and schema from wp-admin. It has no llms.txt or markdown features — those steps use WPCode or a file upload instead, and are marked as such below.
Automatic: switch to ThinkRank
ThinkRank generates and serves /llms.txt from your live content, and migrates from Rank Math, Yoast, AIOSEO and SEOPress — one plugin instead of several fighting over robots.txt.
Not something Yoast does
Yoast does not generate llms.txt. Build one with the free AIScan llms.txt Generator, then upload it next to wp-config.php (your WordPress root) via FTP, cPanel File Manager, or WPCode. A hand-made file goes stale as you publish, so revisit it.
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
Alternative: ThinkRank (runs alongside Yoast)
ThinkRank is a free WordPress plugin from the team behind AIScan. It installs next to Yoast — keep your current SEO plugin, nothing to migrate. Add ThinkRank to WordPress. Optional: the steps above already fix this check without it.
In ThinkRank
Go to ThinkRank → Sitemaps & Crawling → LLMs.txt for AI and enable it. ThinkRank generates and serves /llms.txt from your live content — no file uploads, and it stays current as you publish.
What good output looks like
# 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
Fix in ChatGPT Fix in Claude
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E3
What we found
45 words of server-rendered text, 0 <h2>, 0 <h3>
Measured against
HTML Living Standard — headings and outlines WCAG 2.2 SC 1.3.1 — Info and Relationships
How to fix it
Server-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship.
Server-render your main copy
Agents that don't execute JavaScript see only the HTML you ship. Aim for at least 150 words of real, server-rendered text on the homepage.
Use a real heading outline
One <h1> for the page topic, then descriptive <h2> sections and <h3> sub-sections. Don't fake headings with styled <div>s.
Verify what a crawler sees
curl -s https://yoursite.com/ | sed 's/<[^>]*>/ /g' | tr -s ' ' | head -c 800
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
Measured against
RFC 9309 — Robots Exclusion Protocol Google-Extended documentation
How to fix it
Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
Fix with Yoast SEO
Yoast SEO is installed on this site. It covers robots.txt, XML sitemaps, titles/meta and schema from wp-admin. It has no llms.txt or markdown features — those steps use WPCode or a file upload instead, and are marked as such below.
In Yoast
In Yoast SEO → Tools → File editor, add explicit Allow rules for each major AI crawler so your policy is unambiguous. (Yoast's Crawl optimization settings don't cover AI bots — this is the robots.txt file itself.)
Paste this block
User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: /
Alternative: ThinkRank (runs alongside Yoast)
ThinkRank is a free WordPress plugin from the team behind AIScan. It installs next to Yoast — keep your current SEO plugin, nothing to migrate. Add ThinkRank to WordPress. Optional: the steps above already fix this check without it.
In ThinkRank
Go to ThinkRank → Sitemaps & Crawling → Robots.txt and add explicit Allow rules for each major AI crawler so your policy is unambiguous.
Paste this block
User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: /
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 wpmanageninja.com on AIScan.site.

HTML

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

Markdown

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

Create a free account to track this site over time

Save scan history
See score trends
Re-scan anytime

Dig deeper

Scan any site from Telegram

Send a URL to @AISiteScanBot and get an instant AI-readiness score + top fixes.

Open in Telegram

wpmanageninja.com is built on WordPress. AI-agent readiness for WordPress walks through the same checks on that platform.

Scan any site from Telegram

Send a URL to @AISiteScanBot and get an instant AI-readiness score + top fixes.

Open in Telegram

This page always shows the most recent public scan for wpmanageninja.com.

Browse all public scans Scan your site

Is wpmanageninja.com AI agent ready? B · 68/100

wpmanageninja.com

Scan history · 2 public scans of wpmanageninja.com

ThinkRank fixes 3 of your 4 issues

Fix automatically with AIScan

Quick Wins

/llms.txt

Explicit AI bot rules

Heading hierarchy & server-rendered text

How this score is calculated

robots.txt present & sane

XML sitemap

Link header for discovery

Correct 404 handling

HTTPS & canonical host

Markdown content negotiation

/llms.txt

Fix with Yoast SEO

Automatic: switch to ThinkRank

Not something Yoast does

Template

Alternative: ThinkRank (runs alongside Yoast)

In ThinkRank

What good output looks like

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

Heading hierarchy & server-rendered text

Server-render your main copy

Use a real heading outline

Verify what a crawler sees

Content feed (RSS / Atom / JSON Feed)

Content Signals in robots.txt

Explicit AI bot rules

Fix with Yoast SEO

In Yoast

Paste this block