73% of the Web Runs on 3 CMS Platforms. That's an AI Visibility Problem.

New data from the Web Almanac, analyzed by SEO researcher Chris Green and covered this week by Search Engine Journal, delivers a conclusion that should unsettle every marketing leader: individual SEO practitioners have "minimal" web-wide impact compared to the default settings of CMS platforms.

Three platforms — WordPress, Shopify, and Wix — now control 73% of the CMS market. Their default configurations for metadata, structured data, crawlability, and page architecture shape the technical SEO of most of the web. Green's recommendation? If you want to have a real impact, "you need to be nudging WordPress or Wix or Shopify."

That's a striking finding for traditional SEO. For AI visibility, it's even more consequential.

Google has decades of experience parsing imperfect web content. Its crawler is sophisticated, forgiving, and constantly improving. If your CMS outputs slightly malformed structured data or renders JavaScript slowly, Google will probably figure it out.

AI systems are less forgiving. Here's why CMS defaults matter disproportionately for AI visibility:

The crawlers used by AI companies — OpenAI's GPTBot, Anthropic's ClaudeBot, Perplexity's PerplexityBot — are newer, less mature, and less tolerant of technical issues than Googlebot. Where Google might successfully render a complex JavaScript-heavy page, an AI crawler might see nothing.

Google recently shared updated information about Googlebot's crawl limits, confirming they're flexible and can be adjusted based on need. But AI crawlers don't have the same adaptive infrastructure. They're operating with tighter resource constraints and simpler rendering capabilities.

Here's a specific example of how CMS defaults create AI visibility problems: many CMS platforms ship with robots.txt configurations that only explicitly allow Googlebot, Bingbot, and a few other traditional crawlers. AI crawlers may not be explicitly blocked, but they're not explicitly allowed either.

Some enterprise CMS platforms have gone further, adding blanket blocks for AI crawlers in their default configurations — often in response to content licensing concerns. If your CMS provider made that decision for you, your entire site might be invisible to ChatGPT, Gemini, and Perplexity, and you wouldn't know unless you checked.

The Web Almanac data reveals significant differences in how CMS platforms implement structured data:

• WordPress (43% market share): Structured data quality depends heavily on which plugins are installed. Default WordPress outputs basic metadata. With Yoast or RankMath, you get comprehensive schema markup. Without them, you're invisible to AI systems looking for structured entity information.

• Shopify (18% market share): Strong default product schema markup, but limited support for organization-level and content-level structured data that AI models use to build entity understanding.

• Wix (12% market share): Has invested heavily in automated structured data generation, but the output can be generic and miss the specific entity attributes that AI models weight for brand recognition.

The gap between what each CMS provides by default and what AI systems need to correctly identify, categorize, and recommend a brand is significant.

Let's quantify why this matters.

If 73% of websites run on three CMS platforms, and those platforms' defaults determine most of the web's technical structure, then the AI training data that powers ChatGPT, Gemini, and other models is disproportionately shaped by those platforms' default configurations.

This creates a compounding effect:

1. CMS defaults shape the training data. Most websites that AI models were trained on use one of three CMS platforms with their default settings. The patterns AI models learned about "what a trustworthy website looks like" are heavily influenced by WordPress, Shopify, and Wix defaults.

1. CMS defaults shape the retrieval data. When AI systems use retrieval-augmented generation (RAG) to pull fresh information, they're crawling sites that overwhelmingly run on these same three platforms. The technical accessibility of that content depends on CMS defaults.

1. Brands that deviate from defaults face a choice. Either your deviations improve upon the defaults (better structured data, cleaner architecture, explicit AI crawler access) and you gain an advantage — or your deviations break things (JavaScript-heavy rendering, blocked crawlers, inconsistent metadata) and you become invisible.

Based on the Web Almanac analysis and our observations from AI Visibility Audits, here's how the three dominant CMS platforms perform on key AI visibility factors:

| Factor | WordPress | Shopify | Wix | |---|---|---|---| | AI crawler access | Depends on config | Generally open | Generally open | | Structured data depth | Plugin-dependent | Strong for products | Automated but generic | | Entity markup | Requires manual setup | Limited | Limited | | Content rendering | Usually clean HTML | Usually clean | JavaScript-dependent | | Schema consistency | Varies wildly | Consistent | Consistent |

The critical insight: none of these platforms are optimized for AI visibility by default. All three require deliberate configuration to maximize how AI systems crawl, understand, and cite your content.

If you're running on any of these platforms (and statistically, you probably are), here are the specific technical changes that improve your AI visibility:

Check whether your robots.txt explicitly allows GPTBot, ClaudeBot, PerplexityBot, and other AI crawlers. If it doesn't mention them, they may default to restricted access depending on your configuration. Add explicit allow directives:

` User-agent: GPTBot Allow: /

User-agent: ClaudeBot Allow: /

User-agent: PerplexityBot Allow: / `

Go beyond basic page-level metadata. Add Organization schema that clearly defines:

• Your company name and description
• Your industry and service categories
• Your geographic presence
• Key people and their roles
• Products and services with detailed attributes

This is the entity information AI models use to build their understanding of your brand.

If your CMS relies heavily on JavaScript for content rendering, AI crawlers may not see your content. Test your pages with JavaScript disabled. If the main content disappears, you have an AI visibility problem.

Consider creating a section of your site specifically designed for maximum AI accessibility: clean HTML, comprehensive structured data, and deep authoritative content about your brand, products, and category. Think of it as your brand's entry in the AI encyclopedia.

Check your server logs for AI crawler activity. Are GPTBot, ClaudeBot, and PerplexityBot actually crawling your site? How frequently? Which pages are they accessing? This data tells you whether your CMS configuration is helping or hindering AI visibility.

Green's finding from the Web Almanac encapsulates a fundamental shift in how digital visibility works: platform defaults matter more than individual page optimization.

For traditional SEO, this means lobbying your CMS provider for better defaults. For AI visibility, it means something more immediate: your CMS is either making your brand accessible to AI systems or it's hiding your brand behind technical walls that AI crawlers can't — or won't — climb.

The 73% concentration means this isn't a niche problem. It's the default state of the web. And as AI systems become the primary way people and autonomous agents discover, evaluate, and recommend brands, the brands that address their CMS-level AI accessibility first will compound that advantage over every competitor still relying on platform defaults.

Before you invest in AI content strategy, make sure AI can actually read what you already have.