WordPress.com vs Webflow for AI agents
Webflow is more ready for AI agents than WordPress.com: 87 vs 49 out of 100. Webflow is ahead on letting AI agents in (no bot wall), llms.txt and a remote MCP server. WordPress.com is ahead on visible dates.
What an agent finds
| WordPress.com | Webflow | |
|---|---|---|
| Score | 49/100 | 87/100 |
| Blocks AI agents | bot wall | No |
| robots.txt disallows | No AI bots | No AI bots |
| llms.txt | none found | On the docs host |
| Remote MCP server | none found | mcp.webflow.com/mcp |
| Docs MCP server | none found | developers.webflow.com/mcp |
| OpenAPI spec | none found | none found |
| Developer docs | none found | developers.webflow.com/ |
| Public pricing | wordpress.com/de/pricing/ | webflow.com/pricing |
| Self-serve sign-up | No self-serve page we could open | No self-serve page we could open |
Check by check
60 core points every site needs, plus 40 split between letting an agent sign a team up and connecting through the API. Sign-up and API checks count half each.
| Check | Points | WordPress.com | Webflow |
|---|---|---|---|
| Core | 38 | 58 | |
| Agents get the real page, not a bot wall | 12 | · | ✓ |
| robots.txt lets user-triggered agents in | 6 | ✓ | ✓ |
| Answer-engine crawlers are allowed | 4 | ✓ | ✓ |
| Content is in the raw HTML | 6 | ✓ | ✓ |
| Semantic HTML (main, nav, header) | 4 | ✓ | ✓ |
| Icon buttons and links have names | 3 | ✓ | ✓ |
| Form fields have labels | 3 | · | ✓ |
| Images have alt text | 3 | ✓ | ✓ |
| The page has an H1 | 2 | ✓ | ✓ |
| Structured data (JSON-LD) | 5 | ✓ | ✓ |
| Meta description and Open Graph tags | 3 | ✓ | ✓ |
| sitemap.xml | 3 | · | ✓ |
| llms.txt | 4 | · | ✓ |
| Dates show the content is fresh | 2 | ✓ | · |
| Sign-up | 9 | 15 | |
| Public pricing page | 5 | ✓ | ✓ |
| A self-serve sign-up link | 4 | ✓ | ✓ |
| Sign-up page opens for agents | 3 | · | · |
| A free plan or trial | 3 | · | ✓ |
| No card needed to start | 2 | · | · |
| SoftwareApplication data | 3 | · | ✓ |
| API | 1.5 | 13.5 | |
| OpenAPI spec | 3.5 | · | · |
| Remote MCP server | 4 | · | ✓ |
| Docs as markdown | 2.5 | · | ✓ |
| Self-serve API keys | 3 | · | · |
| OAuth client self-registration | 2.5 | · | ✓ |
| OAuth discovery metadata | 1.5 | · | ✓ |
| SDKs and a CLI | 1.5 | ✓ | ✓ |
| Free tier or test keys | 1.5 | · | ✓ |
Automated, read-only scan of each homepage, robots.txt, llms.txt, docs, OpenAPI paths and MCP endpoints on 3 Nov 2026. How scoring works.
Check them again today
Sites change. Run the live scan for the current result, or check your own site.
Questions
Is WordPress.com or Webflow better for AI agents?
Webflow is more ready for AI agents than WordPress.com: 87 vs 49 out of 100. Webflow is ahead on letting AI agents in (no bot wall), llms.txt and a remote MCP server. WordPress.com is ahead on visible dates. Scores are from our scan on 3 Nov 2026.
Does WordPress.com have an MCP server?
Not one we could find. On 3 Nov 2026 our scan found no remote MCP server for WordPress.com at the usual addresses (mcp.wordpress.com/mcp, api.wordpress.com/mcp, the docs host, or any MCP URL linked from its homepage or llms.txt).
Does Webflow have an MCP server?
Yes. Our scan reached a remote MCP server at https://mcp.webflow.com/mcp on 3 Nov 2026.
Does WordPress.com block AI agents?
Yes. WordPress.com returned a bot challenge or an error page to an AI user-agent on 3 Nov 2026, so assistants can't read the site when a user asks them to.
Does Webflow block AI agents?
No. Webflow served its homepage to an AI user-agent and its robots.txt doesn't disallow any of the AI crawlers we check.