Is techabyte.xyz AI agent ready? C · 61/100
Why we think this is WordPress (7 signals)
- · /wp-content/ asset in head
- · /wp-content/themes|plugins|uploads/
- · /wp-includes/js/
- · WP block/emoji/embed asset
- · Elementor (WordPress) markers
- · wp-* body class
- · /wp-json/ REST API link
3 failed · 1 partial out of 12 that apply to your site.
ThinkRank fixes 4 of your 4 issues
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
4 open checks (3 failing) can be handed to an AI agent: C1, C2, B2, M4. 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.techabyte.xyz/”.
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.techabyte.xyz/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fwww.techabyte.xyz%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.techabyte.xyz/. 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
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+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.techabyte.xyz/ Platform: wordpress (99% confidence) AIScan score: 61/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** — PARTIAL - Evidence: 200 OK, 268 bytes, has H1 - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links. - **[M4] Machine-readable pricing** — FAIL - Evidence: no pricing page found and no JSON-LD Offer on the homepage - 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. ## 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
100Can agents find your pages? robots, sitemaps, llms.txt.
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.
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; });
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: /
Commerce
0Can agents transact? Catalogs, checkout, agentic commerce.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · M4
What we foundno pricing page found and no JSON-LD Offer on the homepage
Measured againstHow to fix itPublish 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.
In ThinkRank
Open ThinkRank → Schema → Schema Manager and enable Product schema. On a WooCommerce store it emits
Product+OfferJSON-LD with realpriceandpriceCurrencyon every product page; for a pricing page, add a manual Product/Offer entry per plan.What agents need to see
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Product", "name": "Pro plan", "offers": { "@type": "Offer", "price": "29.00", "priceCurrency": "USD", "availability": "https://schema.org/InStock", "url": "https://yoursite.com/pricing" } } </script>Validate
Use ThinkRank → Schema → Validate your schema to confirm each offer carries a numeric price and currency before re-scanning.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of www.techabyte.xyz on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fwww.techabyte.xyz%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade C (61/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=61&grade=C&host=www.techabyte.xyz" alt="AIScan.site Grade C — 61/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fwww.techabyte.xyz%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.