Is staging.atxtravelph.com AI agent ready? B · 68/100
staging.atxtravelph.com
Why we think this is WordPress (6 signals)
- · /wp-content/themes|plugins|uploads/
- · /wp-includes/js/
- · WP block/emoji/embed asset
- · wp-* body class
- · /wp-json/ REST API link
- · All in One SEO detected
2 failed · 4 partial out of 12 that apply to your site.
ThinkRank fixes 5 of your 6 issues
Runs alongside AIOSEO — an addition, not a replacement. Keep AIOSEO exactly as it is.
- D1robots.txt present & sane
- C1Markdown content negotiation
- C3Structured HTML (title, meta, JSON-LD, single H1)
- B2Explicit AI bot rules
- M4Machine-readable pricing
1 remaining issue needs a different fix: E4 HTTPS & canonical host. 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
6 open checks (2 failing) can be handed to an AI agent: D1, C1, C3, B2, M4, E4. 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://staging.atxtravelph.com/trip/4d3n-balabac-shared-tour/”.
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://staging.atxtravelph.com/trip/4d3n-balabac-shared-tour/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fstaging.atxtravelph.com%2Ftrip%2F4d3n-balabac-shared-tour%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://staging.atxtravelph.com/trip/4d3n-balabac-shared-tour/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+8 pts if fixed
Markdown content negotiation
See full detailsServe text/markdown when the client sends Accept: text/markdown, or publish /index.md.
- 02Fail+5 pts if fixed
Explicit AI bot rules
See full detailsAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- 03Partial+2 pts if fixed
robots.txt present & sane
See full detailsServe a non-blocking /robots.txt that references your Sitemap.
# WordPress agent-readiness fixes
Site: https://staging.atxtravelph.com/trip/4d3n-balabac-shared-tour/
Platform: wordpress (99% confidence)
AIScan score: 68/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** — PARTIAL
- Evidence: 200 OK, 25 bytes
- Fix: Serve a non-blocking /robots.txt that references your Sitemap.
- **[M4] Machine-readable pricing** — PARTIAL
- Evidence: JSON-LD offer on homepage (price, priceCurrency): {"@context":"https:\/\/schema.org","@type":"Trip","name":"4D3N Balabac Shared Tour","description":"\n\n\n\n\n\n","image":"https:\/\/staging.atxtravelph.com\/wp-content\/uploads\/20
- 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.
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL
- Evidence: h1: 1, title: true, meta description: false, JSON-LD: true
- Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[E4] HTTPS & canonical host** — PARTIAL
- Evidence: final origin https://staging.atxtravelph.com · http:// upgrades to https · www.staging.atxtravelph.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.
## 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 (9): B1, B3, P1, P2, P3, P4, M1, 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
64Can 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 · C1
What we foundAccept: text/markdown → 200 (text/html; charset=UTF-8)
How to fix itServe text/markdown when the client sends Accept: text/markdown, or publish /index.md.
Fix with All in One SEO
All in One SEO (AIOSEO) is installed on this site. It covers robots.txt, XML sitemaps, titles/meta and schema from wp-admin. Anything it doesn't generate is called out below with the manual route.
Not something AIOSEO does
Install WPCode and add a snippet that listens for requests to
/index.mdand returns a plain markdown rendering of your homepage withContent-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 AIOSEO)
ThinkRank is a free WordPress plugin from the team behind AIScan. It installs next to AIOSEO — 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; });
Bot Access
0Are 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 All in One SEO
All in One SEO (AIOSEO) is installed on this site. It covers robots.txt, XML sitemaps, titles/meta and schema from wp-admin. Anything it doesn't generate is called out below with the manual route.
In AIOSEO
In All in One SEO → Tools → Robots.txt Editor, add an Allow rule per AI crawler user-agent (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) so your policy is explicit rather than inferred from
User-agent: *.Equivalent robots.txt
User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: /
Alternative: ThinkRank (runs alongside AIOSEO)
ThinkRank is a free WordPress plugin from the team behind AIScan. It installs next to AIOSEO — 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: /
Commerce
83Can agents transact? Catalogs, checkout, agentic commerce.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of staging.atxtravelph.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fstaging.atxtravelph.com%2Ftrip%2F4d3n-balabac-shared-tour%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade B (68/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=68&grade=B&host=staging.atxtravelph.com" alt="AIScan.site Grade B — 68/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fstaging.atxtravelph.com%2Ftrip%2F4d3n-balabac-shared-tour%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.