AIScan.site

Is websure.digital AI agent ready? C · 56/100

Re-test this site

websure.digital

WordPress · 99% confidenceYoast
https://websure.digital/
C56 / 100
Grade C · Level 3GovernedFair — agents can find you, but a lot is left on the table.
Discoverability
76Content
52Bot Access
0Capabilities
—Commerce
—
Why we think this is WordPress (6 signals)
  • · /wp-content/ asset in head
  • · /wp-content/themes|plugins|uploads/
  • · /wp-includes/js/
  • · WP block/emoji/embed asset
  • · wp-* body class
  • · Yoast SEO plugin detected

Scan history · 2 public scans of websure.digital

WhenScoreGradeSnapshot
Sep 5, 2026, 12:42 AM729fb7c456/100CView →
Sep 2, 2026, 11:44 AMed5f9aaa56/100CView →
6 checks need fixing

4 failed · 2 partial out of 11 that apply to your site.

See top fixes

ThinkRank fixes 3 of your 6 issues

Runs alongside Yoast — an addition, not a replacement. Keep Yoast exactly as it is.

3 remaining issues need a different fix: D3 Link header for discovery, 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

6 open checks (4 failing) can be handed to an AI agent: D3, C1, C3, 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://websure.digital/”.

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://websure.digital/" }.

Option D — REST API
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fwebsure.digital%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://websure.digital/. 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

    Explicit AI bot rules

    +5 pts if fixed

    Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.

    See full details
  • 03Fail

    Link header for discovery

    +3 pts if fixed

    Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.

    See full details
Hand-off prompt for your coding agent6 issues
# WordPress agent-readiness fixes

Site: https://websure.digital/
Platform: wordpress (99% confidence)
AIScan score: 56/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.
- **[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.
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL
  - Evidence: h1: 2, 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-1k0756 → 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.
- **[D3] Link header for discovery** — FAIL
  - Evidence: no Link header or <link> tag
  - Fix: Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
- **[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.

Essential
23 / 31 pts

Baseline every site should meet.

Recommended
6 / 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

76

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 · D3

    What we found

    no Link header or <link> tag

    How to fix it

    Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.

    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

    WordPress can't set arbitrary response headers without code. Add this as a snippet via the WPCode plugin (safer than editing functions.php):

    PHP snippet

    add_action('send_headers', function () {
  header('Link: </.well-known/api-catalog>; rel="api-catalog"', false);
});

    ThinkRank doesn't cover this check

    This one isn't something ThinkRank fixes — use the Yoast / manual steps above. ThinkRank is a free WordPress plugin from the team behind AIScan.

    Fix in ChatGPT Fix in Claude

Content

52

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

212

  • 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)

    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

  • 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 found

    no RSS, Atom or JSON Feed found at the conventional paths

    How to fix it

    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.

    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.

    Fix in ChatGPT Fix in Claude

Bot Access

0

Are AI crawlers explicitly allowed or blocked?

1

  • 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

    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
Share the result

Share as a social image

Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.

AIScan share card — websure.digital graded C
Post on X Share on LinkedIn Share on Facebook

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.

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 websure.digital on AIScan.site.

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

Create a free account to track this site over time

  • Save scan history
  • See score trends
  • Re-scan anytime
Sign up free Already have an account? Sign in →

Dig deeper

Scan any site from Telegram
Open in Telegram

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

Scan any site from Telegram
Open in Telegram

This page always shows the most recent public scan for websure.digital.

Browse all public scansScan your site