Is plantriverside.com AI agent ready? C · 55/100
plantriverside.com
Why we think this is WordPress (6 signals)
- · /wp-content/themes|plugins|uploads/
- · /wp-includes/js/
- · WP block/emoji/embed asset
- · wp-* body class
- · /wp-json/ REST API link
- · Yoast SEO plugin detected
3 failed · 2 partial out of 11 that apply to your site.
ThinkRank fixes 3 of your 5 issues
Runs alongside Yoast — an addition, not a replacement. Keep Yoast exactly as it is.
2 remaining issues need a different fix: E1 Correct 404 handling, E5 Content feed (RSS / Atom / JSON Feed). 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 WordPressFix automatically with AIScan
5 open checks (3 failing) can be handed to an AI agent: C1, C2, B2, E1, E5. Pick one route — each returns the full, check-by-check instructions.
npx add-skill https://aiscan.site/aiscan-skill.jsonThen ask your agent: “Fix the failing AI readiness checks for https://www.plantriverside.com/savannah-restaurants-bars/”.
curl -o CLAUDE.md https://aiscan.site/CLAUDE.mdDrop it in your project root, then ask Claude Code to fix the failing AIScan checks.
https://aiscan.site/api/mcpTools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://www.plantriverside.com/savannah-restaurants-bars/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fwww.plantriverside.com%2Fsavannah-restaurants-bars%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://www.plantriverside.com/savannah-restaurants-bars/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+8 pts if fixed
Markdown content negotiation
See full detailsServe text/markdown when the client sends Accept: text/markdown, or publish /index.md.
- 02Fail+6 pts if fixed
/llms.txt
See full detailsPublish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- 03Fail+5 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://www.plantriverside.com/savannah-restaurants-bars/ Platform: wordpress (99% confidence) AIScan score: 55/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 - **[C1] Markdown content negotiation** — FAIL - Evidence: Accept: text/markdown → 200 (text/html; charset=UTF-8) - Fix: Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md. - **[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. - **[E1] Correct 404 handling** — PARTIAL - Evidence: GET /aiscan-404-probe-zy28qm → HTTP 404, 60 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. - **[E5] Content feed (RSS / Atom / JSON Feed)** — PARTIAL - Evidence: RSS feed at https://www.plantriverside.com/feed (found by convention, not declared in <head>) - 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.
Baseline every site should meet.
Strong signals most sites benefit from.
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
90Can agents find your pages? robots, sitemaps, llms.txt.
Content
40Can 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 · C1
What we foundAccept: text/markdown → 200 (text/html; charset=UTF-8)
How to fix itServe text/markdown when the client sends Accept: text/markdown, or publish /index.md.
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.
Not something Yoast does
Install WPCode and add a snippet that listens for requests to
/index.mdand returns a plain markdown rendering of your homepage withContent-Type: text/markdown.Starter PHP snippet
add_action('init', function () { if (trim($_SERVER['REQUEST_URI'], '/') !== 'index.md') return; $page = get_page_by_path('home') ?: get_post(get_option('page_on_front')); header('Content-Type: text/markdown; charset=utf-8'); echo "# " . get_bloginfo('name') . "\n\n"; echo wp_strip_all_tags(apply_filters('the_content', $page->post_content)); exit; });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.
Ask your assistant first
With the ThinkRank MCP connection active, prompt: "Serve a markdown version of my homepage at /index.md." If your setup needs code, use the WPCode snippet below.
Starter PHP snippet
add_action('init', function () { if (trim($_SERVER['REQUEST_URI'], '/') !== 'index.md') return; $page = get_page_by_path('home') ?: get_post(get_option('page_on_front')); header('Content-Type: text/markdown; charset=utf-8'); echo "# " . get_bloginfo('name') . "\n\n"; echo wp_strip_all_tags(apply_filters('the_content', $page->post_content)); exit; });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
Measured againstHow to fix itPublish /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.txtfrom 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 towp-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.txtfrom 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
Bot Access
0Are 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 found0 known AI agent(s) addressed in robots.txt
Measured againstHow to fix itAdd 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: /
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of www.plantriverside.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fwww.plantriverside.com%2Fsavannah-restaurants-bars%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade C (55/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=55&grade=C&host=www.plantriverside.com" alt="AIScan.site Grade C — 55/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fwww.plantriverside.com%2Fsavannah-restaurants-bars%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
Automate your AI-readiness
Plug AIScan into your agent stack or chat with it on the go.
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.