Is sonardyne.com AI agent ready? C · 58/100

2 remaining issues need a different fix: E1 Correct 404 handling, 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 WordPress

Fix automatically with AIScan

5 open checks (3 failing) can be handed to an AI agent: D1, C1, B2, E1, E5. Pick one route — each returns the full, check-by-check instructions.

Option A — Agent Skill (any runtime)

npx add-skill https://aiscan.site/aiscan-skill.json

Then ask your agent: “Fix the failing AI readiness checks for https://www.sonardyne.com/”.

Option B — Claude Code (CLAUDE.md)

curl -o CLAUDE.md https://aiscan.site/CLAUDE.md

Drop it in your project root, then ask Claude Code to fix the failing AIScan checks.

Option C — MCP client

https://aiscan.site/api/mcp

Tools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://www.sonardyne.com/" }.

Option D — REST API

curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fwww.sonardyne.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://www.sonardyne.com/. Individual checks that need a specific probe list it in their own guide.

Quick Wins

Top 3 fixes ranked by score impact

01Fail
Markdown content negotiation
+8 pts if fixed
Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.
See full details
02Fail
robots.txt present & sane
+6 pts if fixed
Serve a non-blocking /robots.txt that references your Sitemap.
See full details
03Fail
Explicit AI bot rules
+5 pts if fixed
Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
See full details

Hand-off prompt for your coding agent5 issues

# WordPress agent-readiness fixes

Site: https://www.sonardyne.com/
Platform: wordpress (99% confidence)
AIScan score: 58/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.
- **[D1] robots.txt present & sane** — FAIL
  - Evidence: HTTP 200
  - 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.
- **[E1] Correct 404 handling** — PARTIAL
  - Evidence: GET /aiscan-404-probe-8sqrvg → HTTP 404, 60 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.
- **[E5] Content feed (RSS / Atom / JSON Feed)** — PARTIAL
  - Evidence: RSS feed at https://www.sonardyne.com/feed (found by convention, not declared in <head>)
  - 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.

Essential

18 / 31 pts

Baseline every site should meet.

Recommended

11 / 20 pts

Strong signals most sites benefit from.

Bonus earned

0 signals

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

Can agents find your pages? robots, sitemaps, llms.txt.

311

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 found
HTTP 200
Measured against
RFC 9309 — Robots Exclusion Protocol
How to fix it
Serve a non-blocking /robots.txt that references your Sitemap.
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 → Tools → File editor and use Create robots.txt (or edit the existing one). The editor accepts any directive, so add the Content-Signal line and AI bot rules here. If the File editor is missing, your host blocks file writes — upload robots.txt to the WordPress root instead.
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: /
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 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: /
Fix in ChatGPT Fix in Claude

Content

Can agents read your content cleanly? Markdown, structured data.

311

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 found
Accept: text/markdown → 200 (text/html; charset=UTF-8)
Measured against
RFC 9110 §12 — Proactive content negotiation llmstxt.org — markdown representations
How to fix it
Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.
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.
Not something Yoast does
Install WPCode and add a snippet that listens for requests to /index.md and returns a plain markdown rendering of your homepage with Content-Type: text/markdown.
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; });
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.
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; });
Fix in ChatGPT Fix in Claude

Bot Access

Are 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 found
0 known AI agent(s) addressed in robots.txt
Measured against
RFC 9309 — Robots Exclusion Protocol Google-Extended documentation
How to fix it
Add 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: /
Fix in ChatGPT Fix in Claude

Showcase your grade

Embed your AIScan badge

Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of www.sonardyne.com on AIScan.site.

HTML

<!-- AIScan.site agent-readiness badge -->
<a href="https://aiscan.site/?u=https%3A%2F%2Fwww.sonardyne.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade C (58/100) — AIScan.site">
  <img src="https://aiscan.site/api/public/badge.svg?score=58&grade=C&host=www.sonardyne.com" alt="AIScan.site Grade C — 58/100" width="240" height="64" loading="lazy" />
</a>

Markdown

[![AIScan.site Grade C — 58/100](https://aiscan.site/api/public/badge.svg?score=58&grade=C&host=www.sonardyne.com)](https://aiscan.site/?u=https%3A%2F%2Fwww.sonardyne.com%2F)

Create a free account to track this site over time

Save scan history
See score trends
Re-scan anytime

Dig deeper

Scan any site from Telegram

Send a URL to @AISiteScanBot and get an instant AI-readiness score + top fixes.

Open in Telegram

sonardyne.com is built on WordPress. AI-agent readiness for WordPress walks through the same checks on that platform.

Scan any site from Telegram

Send a URL to @AISiteScanBot and get an instant AI-readiness score + top fixes.

Open in Telegram

This page always shows the most recent public scan for sonardyne.com.

Browse all public scans Scan your site

Is sonardyne.com AI agent ready? C · 58/100

sonardyne.com

Scan history · 3 public scans of sonardyne.com

ThinkRank fixes 3 of your 5 issues

Fix automatically with AIScan

Quick Wins

Markdown content negotiation

robots.txt present & sane

Explicit AI bot rules

How this score is calculated

robots.txt present & sane

Fix with Yoast SEO

In Yoast

Paste this block

Alternative: ThinkRank (runs alongside Yoast)

In ThinkRank

Paste this block

XML sitemap

Link header for discovery

Correct 404 handling

HTTPS & canonical host

Markdown content negotiation

Fix with Yoast SEO

Not something Yoast does

Starter PHP snippet

Alternative: ThinkRank (runs alongside Yoast)

Ask your assistant first

Starter PHP snippet

/llms.txt

Structured HTML (title, meta, JSON-LD, single H1)

Heading hierarchy & server-rendered text

Content feed (RSS / Atom / JSON Feed)

Content Signals in robots.txt

Explicit AI bot rules

Fix with Yoast SEO

In Yoast

Paste this block

Alternative: ThinkRank (runs alongside Yoast)

In ThinkRank

Paste this block

Web Bot Auth key directory

Share as a social image

Embed your AIScan badge

Create a free account to track this site over time

Dig deeper