Is jpcarpetandfloorcare.com AI agent ready? C · 64/100
jpcarpetandfloorcare.com
Why we think this is WordPress (2 signals)
- · /wp-content/themes|plugins|uploads/
- · Yoast SEO plugin detected
3 failed · 2 partial out of 12 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: D3 Link header for discovery, 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: D3, C1, B2, M4, 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.jpcarpetandfloorcare.com/”.
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.jpcarpetandfloorcare.com/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fwww.jpcarpetandfloorcare.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://www.jpcarpetandfloorcare.com/. 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.
- 02Partial+4 pts if fixed
Machine-readable pricing
See full detailsPublish 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.
- 03Fail+3 pts if fixed
Link header for discovery
See full detailsAdd a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
# WordPress agent-readiness fixes
Site: https://www.jpcarpetandfloorcare.com/
Platform: wordpress (40% confidence)
AIScan score: 64/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.
- **[M4] Machine-readable pricing** — PARTIAL
- Evidence: JSON-LD offer on homepage (no price fields, price 0 only — paid plans not described): { "@context": "https://schema.org", "@type": ["LocalBusiness", "HomeAndConstructionBusiness"], "name": "JP Carpet Cleaning Expert Floor Care", "telephone": "+18182639314", "foundin
- 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** — PARTIAL
- Evidence: 3 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** — 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.
Baseline every site should meet.
Strong signals most sites benefit from.
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
86Can agents find your pages? robots, sitemaps, llms.txt.
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 foundno Link header or <link> tag
Measured againstHow to fix itAdd a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
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
WordPress can't set arbitrary response headers without code. 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); });ThinkRank doesn't cover this check
This one isn't something ThinkRank fixes — use the Yoast / manual steps above. ThinkRank is a free WordPress plugin from the team behind AIScan.
Content
56Can 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 · E5
What we foundno RSS, Atom or JSON Feed found at the conventional paths
Measured againstHow to fix itPublish 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.
Bot Access
60Are AI crawlers explicitly allowed or blocked?
Commerce
33Can agents transact? Catalogs, checkout, agentic commerce.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of www.jpcarpetandfloorcare.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fwww.jpcarpetandfloorcare.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade C (64/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=64&grade=C&host=www.jpcarpetandfloorcare.com" alt="AIScan.site Grade C — 64/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fwww.jpcarpetandfloorcare.com%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.