Madgicx
← board · madgicx.com · #24 of 80
Ready with a few material gaps
- B
- Grade
- 57
- Agent readiness
- Board average 77
Scanned 14 hours ago
Every outstanding fix in one prompt for your coding agent. Rescan →
Task
What does madgicx.com do and how do I use it? A fetch-only agent finds out.
12 fetches6 found6 missing
- /robots.txt⋯/sitemap.xml
- /llms.txt⋯/llms-full.txt
- /pricing
- /docs
- /openapi.json
- mcp.json⋯MCP initialize
- /privacy · /terms
every path the scanner fetched · replayed deterministically, no LLM
Evaluator notes
A fetch-only agent reached madgicx.com over HTTPS in 400 ms and identified it from its title as “Madgicx | Agentic Meta Ads Management AI Platform”. The copy is readable without JavaScript (17,868 chars of visible text, 17.5% of HTML). It found pricing. It looked for docs, an OpenAPI spec and an MCP server and found none.
Critical access is clean
Whether an ordinary agent can enter, read, and operate the public site.
- ✓4 / 4 passedAgents can reach the site
Crawler access and bot defenses.
- ✓2 / 2 passedCore content is available
Useful content remains accessible without a fragile browser-only path.
- ✓2 / 2 passedNavigation fails safely
Redirects and missing pages give agents a recoverable path.
- ✓2 / 2 passedControls are understandable
Forms and interactive controls expose usable names and structure.
Fix these gaps first
Critical access gaps come first, then the biggest remaining points.
- 01OpenAPI spec discoverableAgent-ready
Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
+7 pts - 02Docs or API link from the homepageAgent-ready
Link Docs or API from the homepage nav; it is the first thing an integrating agent looks for.
+3 pts - 03Agent manifest (MCP, A2A or ai-plugin)Agent-ready
Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.
+2 pts - 04Trust pages (privacy, terms, security)Agent-ready
Serve /privacy and /terms at those paths; agents deciding whether to use you look for them.
+2 pts - 05Organization schema completeAgent-ready
Give the Organization JSON-LD a name, url, logo, description and sameAs links.
+2 pts
Audit the checks behind the score
Grouped by what they measure. Not-applicable checks are excluded from scoring.
Crawlable5 of 5 passed · 19/19 pts›
- ✓Served over HTTPS5/5
https://madgicx.com/
- ✓Responds in under 1.5s5/5
400 ms to first byte
- ✓robots.txt present2/2
User-agent: * Disallow: /products/agency Disallow: /ocr-offer Disallow: /ocr-off…
- ✓sitemap.xml present2/2
/sitemap.xml → 200
- ✓Homepage is indexable5/5
HTTP 200
Metadata7 of 7 passed · 24/24 pts›
- ✓Title tag 10–70 characters5/5
"Madgicx | Agentic Meta Ads Management AI Platform" (49)
- ✓Meta description 50–160 characters5/5
"You just found the #1 AI performance marketer that runs your Facebook ads autonomously. Agentic camp…" (150)
- ✓Canonical URL set3/3
https://madgicx.com
- ✓Exactly one H14/4
1 × <h1>: "Dominate AI Ads Results"
- ✓Mobile viewport set3/3
width=device-width, initial-scale=1
- ✓Language declared2/2
<html lang="en">
- ✓Favicon declared2/2
https://cdn.prod.website-files.com/614069317241cba124a0dd3b/66a94c934a72a60e59cbfedc_Favicon.png
Shareable3 of 3 passed · 14/14 pts›
- ✓Open Graph title, description and image8/8
title, description, image
- ✓Twitter/X card type set3/3
twitter:card = summary_large_image
- ✓Links to X or LinkedIn3/3
64 social link(s)
Converts3 of 3 passed · 17/17 pts›
- ✓Clear call to action8/8
5 CTA(s), e.g. "Try for Free"
- ✓Pricing page linked6/6
→ /pricing
- ✓HTML under 2 MB3/3
100 KB of HTML
Measured1 of 1 passed · 6/6 pts›
- ✓Analytics installed6/6
detected: googletagmanager.com
Agent-ready11 of 19 passed · 26/46 pts›
- ✓Structured data (JSON-LD)4/4
@type: Corporation, WebSite, SoftwareApplication
- ✓Machine-readable pricing3/3
Offer / Product in JSON-LD
- ✓llms.txt present1/1
/llms.txt → 200, 4000+ chars
- ✕llms-full.txt present0/1
no /llms-full.txt
→ Publish /llms-full.txt with the full docs inlined, so agents can read everything in one fetch.
- ✓AI crawlers allowed in robots.txt2/2
none of 9 known AI crawlers blocked
- ✓No noai / TDM reservation2/2
no opt-out signals
- ✕Serves markdown on request0/1
Accept: text/markdown → text/html; charset=utf-8
→ Return text/markdown when the Accept header asks for it; agents skip the HTML entirely.
- ✕OpenAPI spec discoverable0/7
no /openapi.json or /.well-known/openapi.json
→ Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
- ✕Agent manifest (MCP, A2A or ai-plugin)0/2
no manifest at /.well-known/{mcp,agent,ai-plugin}.json
→ Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.
- ✕Docs or API link from the homepage0/3
no docs / API link and no /docs
→ Link Docs or API from the homepage nav; it is the first thing an integrating agent looks for.
- ✓Content readable without JavaScript3/3
17,868 chars of visible text, 17.5% of HTML
- ✓Semantic landmarks (main, single H1)3/3
<main> present, 1 × <h1>
- ✓Images have alt text2/2
78/78 images have alt
- —Form fields are labelledn/a
- ✓Descriptive link text2/2
0/120 links say "click here" / "learn more"
- ✓Agent-friendly 404s2/2
nonexistent path → HTTP 404
- ✕Trust pages (privacy, terms, security)0/2
none of /privacy, /terms, /security respond
→ Serve /privacy and /terms at those paths; agents deciding whether to use you look for them.
- ✕Organization schema complete0/2
no Organization in JSON-LD
→ Give the Organization JSON-LD a name, url, logo, description and sameAs links.
- ✓llms.txt says what you are and links out2/2
4000+ chars, has H1, has links
- ✕Contact route discoverable0/2
no contact link or email on the homepage
→ Link /contact or a mailto: so an agent (or a human it hands off to) can reach you.
APIn/a›
- —Spec parses and declares a versionn/a
- —Operations have summaries and operationIdsn/a
- —Error responses documentedn/a
- —Auth scheme declaredn/a
- —Versioned paths or serversn/a
- —Spec within a model context budgetn/a
MCPn/a›
- —Server answers initializen/a
- —Tools listedn/a
- —Tools carry descriptionsn/a
- —Tool parameters have schemasn/a
Fixed something? Scan again.
One scan per site every 10 minutes. Snapshot 2026-08-24T13:48:32.855Z.