Why we think this is WordPress (5 signals)
- · /wp-content/themes|plugins|uploads/
- · /wp-includes/js/
- · WP block/emoji/embed asset
- · Elementor (WordPress) markers
- · /wp-json/ REST API link
1 failed · 1 partial out of 7 that apply to your site.
Quick Wins
Top 2 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.
- 02Partial+2 pts if fixed
robots.txt present & sane
See full detailsServe a non-blocking /robots.txt that references your Sitemap.
# WordPress agent-readiness fixes Site: https://elementor.com/ Platform: wordpress (99% confidence) AIScan score: 82/100 — Level 4 (Interactive) Rubric: v2026-06-08.1 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, 24 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. ## 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.
Discoverability
85Can agents find your pages? robots, sitemaps, llms.txt.
Content
100Can agents read your content cleanly? Markdown, structured data.
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
How to fix itAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
⚡ Fix automatically with AIScan
Option A — Agent Skill (any agent runtime)
Install the AIScan skill in one command:
```
npx add-skill https://aiscan.site/aiscan-skill.json
```
Or download it directly: https://aiscan.site/aiscan-skill.json
Then ask your agent: "Fix the failing AI readiness checks for <your-url>"Option B — Claude Code skill (CLAUDE.md)
- Download
CLAUDE.mdfrom https://aiscan.site/CLAUDE.md and place it in your project root. - Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.
Option C — MCP (Claude Desktop, Cursor, or any MCP client)
- Endpoint:
https://aiscan.site/api/mcp - Tools:
scan_website,get_fixes,get_grade - Call
get_fixeswith your URL for machine-readable fix instructions.
Option D — REST API
```
GET https://aiscan.site/api/public/scan?url=YOUR_URL
```
Returns the full report with all checks and fix details.Re-scan at https://aiscan.site to verify after applying fixes.
Fix with ThinkRank (AI-first SEO for WordPress)
ThinkRank is a free WordPress plugin built for exactly these AI-readiness signals — robots rules, sitemaps, llms.txt, schema and instant indexing — all from wp-admin, no code.
- Install — Add ThinkRank to WordPress and run the setup wizard.
- Let your assistant do it — turn on ThinkRank → MCP → Enable MCP access, copy the connection URL, and add it as a custom connector in Claude (Settings → Connectors) or ChatGPT (Settings → Plugins, developer mode). Then prompt: "Fix the failing AIScan checks on my site." The assistant reads and writes your ThinkRank SEO through an approved WordPress login — no keys to paste. MCP setup docs
- Or do it manually — follow the per-check steps below in wp-admin.
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: /
Verify
Re-run this scan at https://aiscan.site, or ask your connected assistant to re-check. You can also test directly with
curl -I https://yoursite.com/<path>.- Download
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 elementor.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Felementor.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade A (82/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=82&grade=A&host=elementor.com" alt="AIScan.site Grade A — 82/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Felementor.com%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
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.