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

8 open checks (5 failing) can be handed to an AI agent: D1, D2, D3, C3, B2, E1, E3, E5. 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://reventor.eu/”.

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://reventor.eu/" }.

Option D — REST API

curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Freventor.eu%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://reventor.eu/. Individual checks that need a specific probe list it in their own guide.

Quick Wins

Top 3 fixes ranked by score impact

01Fail
Explicit AI bot rules
+5 pts if fixed
Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
See full details
02Fail
XML sitemap
+4 pts if fixed
Publish /sitemap.xml and reference it in robots.txt.
See full details
03Fail
Correct 404 handling
+4 pts if fixed
Return a real HTTP 404 (not 200) for missing pages, with a body that names the site and links to your homepage, sitemap, and search so an agent can recover.
See full details

Hand-off prompt for your coding agent8 issues

# WordPress agent-readiness fixes

Site: https://reventor.eu/
Platform: wordpress (40% confidence)
AIScan score: 51/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
- **[D1] robots.txt present & sane** — PARTIAL
  - Evidence: 200 OK, 68668 bytes
  - Fix: Serve a non-blocking /robots.txt that references your Sitemap.
- **[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.
- **[D2] XML sitemap** — FAIL
  - Evidence: no /sitemap.xml or /sitemap_index.xml resolved
  - Fix: Publish /sitemap.xml and reference it in robots.txt.
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL
  - Evidence: h1: 0, title: true, meta description: false, JSON-LD: false
  - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[E1] Correct 404 handling** — FAIL
  - Evidence: GET /aiscan-404-probe-z3zht2 → HTTP 200 (soft 404 — returns 200 for a missing page), 68703 bytes, text/html
  - Fix: Return a real HTTP 404 (not 200) for missing pages, with a body that names the site and links to your homepage, sitemap, and search so an agent can recover.
- **[E3] Heading hierarchy & server-rendered text** — PARTIAL
  - Evidence: 28 words of server-rendered text, 2 <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.
- **[D3] Link header for discovery** — FAIL
  - Evidence: no Link header or <link> tag
  - Fix: Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
- **[E5] Content feed (RSS / Atom / JSON Feed)** — FAIL
  - Evidence: no RSS, Atom or JSON Feed found at the conventional paths
  - Fix: Publish an RSS, Atom, or JSON Feed of new content and declare it in <head> with <link rel="alternate" type="application/rss+xml">. Feeds give agents a cheap, dated changelog of your site that a sitemap doesn't.

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

11 / 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

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

113

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · D2
What we found
no /sitemap.xml or /sitemap_index.xml resolved
Measured against
Sitemaps XML protocol 0.9 RFC 9309 §2.2.3 (Sitemap directive)
How to fix it
Publish /sitemap.xml and reference it in robots.txt.
In ThinkRank
Go to ThinkRank → Sitemaps & Crawling → XML sitemaps and enable the sitemap. ThinkRank publishes a clean index of posts, pages, CPTs and terms.
Reference it in robots.txt
Back in ThinkRank → Robots.txt, confirm the file includes:
Sitemap: https://yoursite.com/sitemap_index.xml
Ping search + AI engines instantly
Enable ThinkRank → Instant Indexing (IndexNow) so new URLs are submitted the moment you publish.
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 · D3
What we found
no Link header or <link> tag
Measured against
RFC 8288 — Web Linking RFC 9727 — API catalog link relation
How to fix it
Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
Add a Link response header
ThinkRank doesn't manage arbitrary response headers. Add this as a snippet via the WPCode plugin (safer than editing functions.php):
PHP snippet
add_action('send_headers', function () { header('Link: </.well-known/api-catalog>; rel="api-catalog"', false); });
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 · E1
What we found
GET /aiscan-404-probe-z3zht2 → HTTP 200 (soft 404 — returns 200 for a missing page), 68703 bytes, text/html
Measured against
RFC 9110 §15.5.5 — 404 Not Found Google Search Central — soft 404s
How to fix it
Return a real HTTP 404 (not 200) for missing pages, with a body that names the site and links to your homepage, sitemap, and search so an agent can recover.
Return a real 404 status
A missing page must answer 404 (or 410), never 200. A soft 404 makes agents index your error page as real content.
Make the body recoverable
The 404 body should name the site and link to the homepage, sitemap, docs, and search so an agent can find its way back instead of dead-ending.
Verify
curl -sI https://yoursite.com/this-page-does-not-exist-123 | head -n 1
Fix in ChatGPT Fix in Claude

Content

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

221

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E5
What we found
no RSS, Atom or JSON Feed found at the conventional paths
Measured against
RFC 4287 — Atom Syndication Format JSON Feed 1.1
How to fix it
Publish an RSS, Atom, or JSON Feed of new content and declare it in <head> with <link rel="alternate" type="application/rss+xml">. Feeds give agents a cheap, dated changelog of your site that a sitemap doesn't.
Publish a feed
RSS, Atom, or JSON Feed — any of them gives agents a cheap, dated changelog of new content that a sitemap can't.
Declare it in <head>
<link rel="alternate" type="application/rss+xml" title="Blog" href="/feed.xml" />
Keep dates accurate
Each item needs a real publish date; that's the freshness signal agents actually use.
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.
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 reventor.eu on AIScan.site.

HTML

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

Markdown

[![AIScan.site Grade C — 51/100](https://aiscan.site/api/public/badge.svg?score=51&grade=C&host=reventor.eu)](https://aiscan.site/?u=https%3A%2F%2Freventor.eu%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

Automate your AI-readiness

Plug AIScan into your agent stack or chat with it on the go.

Use the MCP server

One line in Claude Code or Cursor to scan any site from your agent.

Chat with the Telegram bot

Scan sites and get fixes right from @AISiteScanBot.

Free · No signup · ~20 seconds

Scan your own site

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

Re-test this site Scan your site

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

Is reventor.eu AI agent ready? C · 51/100

reventor.eu

ThinkRank fixes 4 of your 8 issues

Fix automatically with AIScan

Quick Wins

Explicit AI bot rules

XML sitemap

Correct 404 handling

How this score is calculated

robots.txt present & sane

XML sitemap

In ThinkRank

Reference it in robots.txt

Ping search + AI engines instantly

Link header for discovery

Add a Link response header

PHP snippet

Correct 404 handling

Return a real 404 status

Make the body recoverable

Verify

HTTPS & canonical host

Markdown content negotiation

/llms.txt

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

Heading hierarchy & server-rendered text

Content feed (RSS / Atom / JSON Feed)

Publish a feed

Declare it in <head>

Keep dates accurate

Content Signals in robots.txt