Is wpamelia-clone.1wp.site AI agent ready? B · 74/100
Why we think this is WordPress (4 signals)
- · /wp-content/themes|plugins|uploads/
- · WP block/emoji/embed asset
- · /wp-json/ REST API link
- · Yoast SEO plugin detected
Fix this with Claude
Add the AIScan connector and ask Claude to walk you through each failing check for this site.
Scan history · 4 public scans of wpamelia-clone.1wp.site
3 failed · 3 partial out of 12 that apply to your site.
ThinkRank fixes 4 of your 8 issues
Runs alongside Yoast — an addition, not a replacement. Keep Yoast exactly as it is.
4 remaining issues need a different fix: B3 Web Bot Auth key directory, P2 MCP Server Card, E1 Correct 404 handling, E4 HTTPS & canonical host. 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
8 open checks (3 failing) can be handed to an AI agent: D1, D2, B2, B3, P2, M4, E1, E4. 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://wpamelia-clone.1wp.site/”.
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://wpamelia-clone.1wp.site/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fwpamelia-clone.1wp.site%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://wpamelia-clone.1wp.site/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+5 pts if fixed
Explicit AI bot rules
See full detailsAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- 02Fail+4 pts if fixed
XML sitemap
See full detailsPublish /sitemap.xml and reference it in robots.txt.
- 03Fail+4 pts if fixed
Correct 404 handling
See full detailsReturn 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.
# WordPress agent-readiness fixes
Site: https://wpamelia-clone.1wp.site/
Platform: wordpress (90% confidence)
AIScan score: 74/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, 26 bytes
- Fix: Serve a non-blocking /robots.txt that references your Sitemap.
- **[M4] Machine-readable pricing** — PARTIAL
- Evidence: JSON-LD offer on https://wpamelia-clone.1wp.site/pricing (price, priceCurrency): {"@context":"https://schema.org","@type":"SoftwareApplication","name":"Amelia","operatingSystem":"WordPress","applicationCategory":"BusinessApplication","applicationSubCategory":"A
- 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.
- **[P2] MCP Server Card** — PARTIAL
- Evidence: HTTP 200
- Fix: Optional: publish /.well-known/mcp/server-card.json if you expose an MCP server.
- **[D2] XML sitemap** — FAIL
- Evidence: no /sitemap.xml or /sitemap_index.xml resolved
- Fix: Publish /sitemap.xml and reference it in robots.txt.
- **[E1] Correct 404 handling** — FAIL
- Evidence: GET /aiscan-404-probe-l23cb7 → HTTP 200 (soft 404 — returns 200 for a missing page), 510630 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.
- **[E4] HTTPS & canonical host** — PARTIAL
- Evidence: final origin https://wpamelia-clone.1wp.site · http:// upgrades to https · www.wpamelia-clone.1wp.site serves its own copy (duplicate origin) · no HSTS header
- Fix: Serve the site over HTTPS, 301-redirect http:// to https://, and redirect the www/apex variant to a single canonical host so agents don't index two copies of every URL.
- **[B3] Web Bot Auth key directory** — PARTIAL
- Evidence: HTTP 200
- Fix: Optional: serve a JWKS-style key directory at /.well-known/http-message-signatures-directory.
## 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 (3): B1, P4, M3 — 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
48Can 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 · D2
What we foundno /sitemap.xml or /sitemap_index.xml resolved
Measured againstHow to fix itPublish /sitemap.xml and reference it in robots.txt.
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
Go to Yoast SEO → Settings → Site features and turn on XML sitemaps. Yoast publishes
/sitemap_index.xml. Use the see the XML sitemap link to confirm it loads.Reference it in robots.txt
Back in Yoast SEO → Tools → File editor, make sure the file includes:
Sitemap: https://yoursite.com/sitemap_index.xml
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 → 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.
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 foundGET /aiscan-404-probe-l23cb7 → HTTP 200 (soft 404 — returns 200 for a missing page), 510630 bytes, text/html
Measured againstHow to fix itReturn 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(or410), never200. 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
Content
100Can agents read your content cleanly? Markdown, structured data.
Bot Access
13Are 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: /
Capabilities
80Can agents do things? APIs, auth, MCP, Agent Skills.
Commerce
91Can agents transact? Catalogs, checkout, agentic commerce.
Share as a social image
Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.
Tip: for X and LinkedIn, upload the downloaded PNG with your post so the card shows in the feed. Posts that include just the link will still preview AIScan.site.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of wpamelia-clone.1wp.site on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fwpamelia-clone.1wp.site%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade B (74/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=74&grade=B&host=wpamelia-clone.1wp.site" alt="AIScan.site Grade B — 74/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fwpamelia-clone.1wp.site%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
wpamelia-clone.1wp.site is built on WordPress. AI-agent readiness for WordPress walks through the same checks on that platform.
This page always shows the most recent public scan for wpamelia-clone.1wp.site.