Is mdtechservices.com AI agent ready? B · 70/100
Why we think this is WordPress (5 signals)
- · /wp-content/themes|plugins|uploads/
- · WP block/emoji/embed asset
- · Elementor (WordPress) markers
- · /wp-json/ REST API link
- · Yoast SEO plugin detected
2 failed · 5 partial out of 12 that apply to your site.
ThinkRank fixes 4 of your 9 issues
Runs alongside Yoast — an addition, not a replacement. Keep Yoast exactly as it is.
- C2/llms.txt
- C3Structured HTML (title, meta, JSON-LD, single H1)
- B2Explicit AI bot rules
- M4Machine-readable pricing
5 remaining issues need a different fix: B3 Web Bot Auth key directory, P2 MCP Server Card, E1 Correct 404 handling, E4 HTTPS & canonical host, 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
9 open checks (2 failing) can be handed to an AI agent: C2, C3, B2, B3, P2, M4, E1, E4, 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://mdtechservices.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://mdtechservices.com/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fmdtechservices.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://mdtechservices.com/. 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.
- 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.
- 03Partial+3 pts if fixed
/llms.txt
See full detailsPublish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
# WordPress agent-readiness fixes
Site: https://mdtechservices.com/
Platform: wordpress (99% confidence)
AIScan score: 70/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
- **[C2] /llms.txt** — PARTIAL
- Evidence: 200 OK, 6506 bytes, has H1
- Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- **[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":"VideoObject","@id":"https:\/\/mdtechservices.com\/#videoobject","url":"https:\/\/mdtechservices.com\/","headline":"MDTECH Services: B
- 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.
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL
- Evidence: h1: 0, title: true, meta description: true, JSON-LD: true
- Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[E1] Correct 404 handling** — PARTIAL
- Evidence: GET /aiscan-404-probe-3ee900 → HTTP 429, 0 bytes
- 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://mdtechservices.com · http:// upgrades to https · www.mdtechservices.com 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.
- **[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 (3): B1, 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.
Content
72Can 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 · 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
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
81Can agents do things? APIs, auth, MCP, Agent Skills.
Commerce
64Can 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 mdtechservices.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fmdtechservices.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade B (70/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=70&grade=B&host=mdtechservices.com" alt="AIScan.site Grade B — 70/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fmdtechservices.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.