Is devzahid.com AI agent ready? D · 49/100
Why we think this is WordPress (4 signals)
- · /wp-content/themes|plugins|uploads/
- · /wp-includes/js/
- · WP block/emoji/embed asset
- · wp-* body class
4 failed · 4 partial out of 11 that apply to your site.
ThinkRank fixes 5 of your 8 issues
- D1robots.txt present & sane
- D2XML sitemap
- C2/llms.txt
- C3Structured HTML (title, meta, JSON-LD, single H1)
- B2Explicit AI bot rules
3 remaining issues need a different fix: E1 Correct 404 handling, E3 Heading hierarchy & server-rendered text, 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 (4 failing) can be handed to an AI agent: D1, D2, C2, C3, B2, E1, E3, 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://devzahid.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://devzahid.com/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fdevzahid.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://devzahid.com/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+6 pts if fixed
robots.txt present & sane
See full detailsServe a non-blocking /robots.txt that references your Sitemap.
- 02Fail+5 pts if fixed
Explicit AI bot rules
See full detailsAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- 03Fail+4 pts if fixed
XML sitemap
See full detailsPublish /sitemap.xml and reference it in robots.txt.
# WordPress agent-readiness fixes Site: https://devzahid.com/ Platform: wordpress (99% confidence) AIScan score: 49/100 — Level 2 (Readable) 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** — FAIL - Evidence: no response - Fix: Serve a non-blocking /robots.txt that references your Sitemap. - **[C2] /llms.txt** — PARTIAL - Evidence: 200 OK, 67887 bytes - 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. - **[D2] XML sitemap** — FAIL - Evidence: no /sitemap.xml or /sitemap_index.xml resolved - Fix: Publish /sitemap.xml and reference it in robots.txt. - **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL - Evidence: h1: 1, title: true, meta description: false, JSON-LD: false - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD. - **[E1] Correct 404 handling** — FAIL - Evidence: GET /aiscan-404-probe-svgah6 → HTTP 200 (soft 404 — returns 200 for a missing page), 67887 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. - **[E3] Heading hierarchy & server-rendered text** — PARTIAL - Evidence: 45 words of server-rendered text, 2 <h2>, 0 <h3> - Fix: Server-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship. - **[E4] HTTPS & canonical host** — PARTIAL - Evidence: final origin https://devzahid.com · http:// unreachable · www.devzahid.com unreachable (fine) · 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. ## 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
29Can 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 · D1
What we foundno response
Measured againstHow to fix itServe a non-blocking /robots.txt that references your Sitemap.
In ThinkRank
Go to ThinkRank → Sitemaps & Crawling → Robots.txt and edit your rules there. Add the Content-Signal directive plus explicit AI bot rules.
Paste this block
User-agent: * Allow: / Sitemap: https://example.com/sitemap.xml # Content Signals (Cloudflare proposal) Content-Signal: search=yes, ai-train=no, ai-input=yes # Explicit AI agent rules User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot-Extended Allow: /
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.
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-svgah6 → HTTP 200 (soft 404 — returns 200 for a missing page), 67887 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
72Can 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
Measured againstHow to fix itAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
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 devzahid.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fdevzahid.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade D (49/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=49&grade=D&host=devzahid.com" alt="AIScan.site Grade D — 49/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fdevzahid.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.