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

5 open checks (2 failing) can be handed to an AI agent: D1, C2, B2, M4, E1. 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://wpgeodirectory.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://wpgeodirectory.com/" }.

Option D — REST API

curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fwpgeodirectory.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://wpgeodirectory.com/. 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
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
03Partial
/llms.txt
+3 pts if fixed
Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
See full details

Hand-off prompt for your coding agent5 issues

# WordPress agent-readiness fixes

Site: https://wpgeodirectory.com/
Platform: wordpress (99% confidence)
AIScan score: 75/100 — Level 4 (Interactive)
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, 56 bytes
  - Fix: Serve a non-blocking /robots.txt that references your Sitemap.
- **[C2] /llms.txt** — PARTIAL
  - Evidence: 200 OK, 118704 bytes
  - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- **[M4] Machine-readable pricing** — PARTIAL
  - Evidence: JSON-LD offer on https://wpgeodirectory.com/pricing (price, priceCurrency): {"@context":"http://schema.org","@type":"Product","description":"Create a Profitable Business Directory Pricing Manager is a powerful price manager that allows you to monetize your
  - Fix: Publish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.
- **[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.
- **[E1] Correct 404 handling** — FAIL
  - Evidence: GET /aiscan-404-probe-pmrmcq → HTTP 200 (soft 404 — returns 200 for a missing page), 118704 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.

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

20 / 31 pts

Baseline every site should meet.

Recommended

22 / 26 pts

Strong signals most sites benefit from.

Bonus earned

0 signals

Emerging standards. Can only add points.

Not counted (9): B1, B3, P1, P2, P3, P4, M1, M3, 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.

311

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-pmrmcq → HTTP 200 (soft 404 — returns 200 for a missing page), 118704 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.

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

Commerce

Can agents transact? Catalogs, checkout, agentic commerce.

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 wpgeodirectory.com on AIScan.site.

HTML

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

Markdown

[![AIScan.site Grade B — 75/100](https://aiscan.site/api/public/badge.svg?score=75&grade=B&host=wpgeodirectory.com)](https://aiscan.site/?u=https%3A%2F%2Fwpgeodirectory.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

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 wpgeodirectory.com AI agent ready? B · 75/100

wpgeodirectory.com

ThinkRank fixes 4 of your 5 issues

Fix automatically with AIScan

Quick Wins

Explicit AI bot rules

Correct 404 handling

/llms.txt

How this score is calculated

robots.txt present & sane

XML sitemap

Link header for discovery

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)

Content Signals in robots.txt

Explicit AI bot rules

Fix with Yoast SEO

In Yoast

Paste this block

Alternative: ThinkRank (runs alongside Yoast)

In ThinkRank

Paste this block

Web Bot Auth key directory

Machine-readable pricing

Universal Commerce Protocol (UCP)

x402 Payment Required signal

Share as a social image

Embed your AIScan badge

Create a free account to track this site over time

Dig deeper

Automate your AI-readiness

Scan your own site