Is smartclipping.io AI agent ready? B · 76/100

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

7 open checks (2 failing) can be handed to an AI agent: B2, B3, P2, M4, E1, E4, 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://smartclipping.io/”.

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://smartclipping.io/" }.

Option D — REST API

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

Quick Wins

Top 3 fixes ranked by score impact

01Fail
Explicit AI bot rules
+5 pts if fixed
Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
See full details
02Partial
Machine-readable pricing
+4 pts if fixed
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.
See full details
03Fail
Content feed (RSS / Atom / JSON Feed)
+3 pts if fixed
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.
See full details

Hand-off prompt for your coding agent7 issues

# WordPress agent-readiness fixes

Site: https://smartclipping.io/
Platform: wordpress (99% confidence)
AIScan score: 76/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
- **[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","@graph":[{"@type":"Place","@id":"https://smartclipping.io/#place","address":{"@type":"PostalAddress","streetAddress":"New York City","addressRegio
  - 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.
- **[E1] Correct 404 handling** — PARTIAL
  - Evidence: GET /aiscan-404-probe-r334l5 → 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://smartclipping.io · http:// upgrades to https · www.smartclipping.io 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.

Essential

25 / 37 pts

Baseline every site should meet.

Recommended

17 / 20 pts

Strong signals most sites benefit from.

Bonus earned

6 signals

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

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

Content

Can 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 found
no RSS, Atom or JSON Feed found at the conventional paths
Measured against
RFC 4287 — Atom Syndication Format JSON Feed 1.1
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

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 Rank Math
Rank Math is already installed on this site, so you can manage most AI-readiness signals without touching code. Follow the per-check steps below. For anything Rank Math doesn't cover, use the WPCode plugin to add small PHP snippets safely.
In Rank Math
Go to Rank Math → General Settings → Edit 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: /
Alternative: ThinkRank (runs alongside Rank Math)
ThinkRank is a free WordPress plugin from the team behind AIScan. It installs next to Rank Math — 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

Capabilities

Can agents do things? APIs, auth, MCP, Agent Skills.

Commerce

Can agents transact? Catalogs, checkout, agentic commerce.

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 smartclipping.io on AIScan.site.

HTML

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

Markdown

[![AIScan.site Grade B — 76/100](https://aiscan.site/api/public/badge.svg?score=76&grade=B&host=smartclipping.io)](https://aiscan.site/?u=https%3A%2F%2Fsmartclipping.io%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

smartclipping.io 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 smartclipping.io.

Browse all public scans Scan your site

Is smartclipping.io AI agent ready? B · 76/100

smartclipping.io

Scan history · 2 public scans of smartclipping.io

ThinkRank fixes 2 of your 7 issues

Fix automatically with AIScan

Quick Wins

Explicit AI bot rules

Machine-readable pricing

Content feed (RSS / Atom / JSON Feed)

How this score is calculated

robots.txt present & sane

XML sitemap

Link header for discovery

Correct 404 handling

HTTPS & canonical host

Markdown content negotiation

/llms.txt

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

Heading hierarchy & server-rendered text

Content feed (RSS / Atom / JSON Feed)

Publish a feed

Declare it in <head>

Keep dates accurate

Content Signals in robots.txt

Explicit AI bot rules

Fix with Rank Math

In Rank Math

Paste this block

Alternative: ThinkRank (runs alongside Rank Math)

In ThinkRank

Paste this block

Web Bot Auth key directory

API Catalog (RFC 9727)

MCP Server Card

Agent Skills index

OAuth discovery metadata

Machine-readable API description

Machine-readable pricing

Universal Commerce Protocol (UCP)

x402 Payment Required signal

Share as a social image

Embed your AIScan badge

Create a free account to track this site over time

Dig deeper