# Untitled # 7 GEO Mistakes WordPress Sites Make (And How to Fix Them) Most WordPress sites score below 40/100 on AI readiness. Not because the content is bad, but because the technical layer makes it invisible to AI systems. Here are the seven most common failures. ## 1. Page Builders Destroying Content Structure The problem: Elementor, Divi, and WPBakery wrap your content in dozens of nested
elements with CSS classes. What should be a simple heading + paragraph becomes: ```

Your Heading

``` AI extraction systems struggle with this nesting. They can't reliably determine which text is content and which is structural noise. The fix: - If using a page builder, ensure heading elements are actual

–

tags (not styled
s) - Use the text editor for content-heavy pages (blog posts, documentation) - Install Zitably — the Markdown converter strips builder chrome and extracts semantic content - Consider WordPress's native block editor (Gutenberg) — it produces much cleaner HTML ## 2. Multiple or Missing H1 Tags The problem: Some themes output the site title as H1, then the post title as another H1. Others use H2 for post titles. Page builders let users add H1s anywhere. Result: AI systems can't determine the primary topic of the page. The fix: - One H1 per page: the post/page title - All section headings: H2 - Subsections: H3 - Verify with browser DevTools: right-click → Inspect → search for

## 3. No Schema.org Markup The problem: WordPress Core doesn't output Schema.org JSON-LD by default. Unless you have a plugin (Yoast, Rank Math, Zitably) or a theme that adds it, your pages have zero structured data. Pages with Schema.org get cited approximately 3.2× more often by AI systems. Without it, AI has to guess what your content is about — author, publish date, content type, entity relationships. The fix: - Install a Schema.org plugin (Zitably adds it automatically for Article, FAQPage, Organization) - At minimum, add Article schema with headline, datePublished, dateModified, author - Validate at Google's Rich Results Test ## 4. Content Locked Behind JavaScript The problem: Single-page apps, lazy-loaded content sections, tab interfaces, and accordion widgets that require JavaScript to display content. AI crawlers typically don't execute JavaScript. If your product specifications are in a tab that requires a click to reveal, AI crawlers see nothing. The fix: - Ensure all important content is in the initial HTML response - Lazy-load images, not text content - If you must use JS-dependent UI (tabs, accordions), include the content in HTML and use CSS/JS for the UI behavior - Test by disabling JavaScript and checking if content is visible ## 5. Vague, Marketing-Heavy Content The problem: Content written for "engagement" rather than extraction: > "Transform your digital presence with our innovative, cutting-edge platform that delivers unparalleled results across all channels." Zero extractable facts. No verifiable claims. Nothing an AI can cite. The fix: - Replace adjectives with measurements: "innovative" → "reduces load time by 340ms" - Replace vague claims with evidence: "unparalleled results" → "2.3× increase in AI citations across 450+ sites" - Target 12+ facts per 500 words - Use the Zitably Fact Density analyzer to identify weak sections ## 6. Missing llms.txt File The problem: Without an llms.txt file, AI systems must crawl your entire sitemap to find your important content. With limited context windows, they may never reach your best pages. The fix: - Create llms.txt in your WordPress root - List your 10–20 most important URLs with one-line descriptions - Update when you publish new key content - Or install Zitably and use the built-in editor (auto-generation available on Pro) ## 7. No Content Negotiation The problem: AI agents that request Accept: text/markdown receive HTML anyway. They waste tokens parsing navigation, sidebars, footers, and formatting noise — leaving less context window for your actual content. Cloudflare measured an 80% token reduction when serving Markdown vs. HTML. That means 5× more of your content fits in an AI's context window. The fix: - Install Zitably — content negotiation is active immediately for all published posts - Or implement manually with a template_redirect filter that checks the Accept header - Add Vary: Accept header to enable proper CDN caching of both formats ## Impact Summary | Mistake | GEO Score Impact | Fix Difficulty | |---|---|---| | Page builder nesting | -10 to -15 points | Medium (change workflow) | | Multiple/missing H1 | -5 to -8 points | Easy (theme fix) | | No Schema.org | -8 to -12 points | Easy (plugin) | | JS-locked content | -10 to -20 points | Medium (refactor) | | Vague marketing copy | -15 to -25 points | High (rewrite needed) | | Missing llms.txt | -3 to -5 points | Easy (create file) | | No content negotiation | -5 to -10 points | Easy (plugin) | Total potential improvement from fixing all seven: 50–90 points on a 100-point scale. ## The Fast Path Install Zitably. It handles mistakes #3, #6, and #7 automatically (Schema.org, llms.txt, content negotiation). It diagnoses mistakes #1, #2, #4, and #5 through the GEO score with specific recommendations. One plugin, 15 minutes, and you've addressed the majority of technical GEO issues on your WordPress site. --- Get your GEO score and see which of these 7 mistakes affect your site. Start free →