AIScan.site
W
Detected framework · 80% confidence

WordPress

https://www.omnisend.com/
C60 / 100
Grade C · Level 3GovernedFair — agents can find you, but a lot is left on the table.
Discoverability100
3/3 passing
Content50
1/3 passing
Bot Access0
0/3 passing
Score breakdown by dimension
Discoverability100
Content50
Bot Access0
Why we think this is WordPress (3 signals)
  • · /wp-content/ asset in head
  • · /wp-content/themes|plugins|uploads/
  • · HubSpot script/asset
3 checks need fixing

2 failed · 1 partial out of 7 that apply to your site.

See top fixes

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 expose /path/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
  • 03Partial

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

    +1 pts if fixed

    Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.

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

Site: https://www.omnisend.com/
Platform: wordpress (80% confidence)
AIScan score: 60/100 — Level 3 (Governed)
Rubric: v2026-06-08.1

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 expose /path/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: 0, title: true, meta description: true, JSON-LD: true
  - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.

## 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.

Discoverability

100

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

3

Content

50

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

111

  • 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 expose /path/index.md.

    1.⚡ Fix automatically with AIScan

    The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.

    2.Serve text/markdown on Accept negotiation

    When a client sends `Accept: text/markdown`, return a markdown rendering of the same content. The simplest path is to publish parallel `.md` files (e.g. `/about` → `/about.md`) and rewrite based on the Accept header.

    3.Test it
    curl -H "Accept: text/markdown" https://yoursite.com/
    4.Verify

    After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.

    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.

    1.⚡ Fix automatically with AIScan

    The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.

    2.Add explicit User-agent blocks

    Don't rely on `User-agent: *` alone. Address each major AI crawler so your policy is unambiguous.

    3.Recommended block
    User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Applebot-Extended
Allow: /
    4.Verify

    After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.

    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 — www.omnisend.com 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 www.omnisend.com on AIScan.site.

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

Track this over time

Coming soon: save sites, schedule re-scans, get email when something material changes. Standards land weekly — your tracker shouldn't be one-shot.

Free · No signup · ~20 seconds

Scan your own site

Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.

Scan your site
Or browse the community feed to see what others have scanned.