ScoreGeo

Blog · 7 min read

10 GEO mistakes to absolutely avoid in 2026

Published on May 5, 2026 · Updated on May 25, 2026

Here are the 10 most frequent GEO mistakes on websites in 2026, sorted by score impact. For each: why it's penalizing, and the concrete fix. Most are resolved in less than an hour of technical work.

1. Pure SPA without server rendering — Critical (-20 pts)

Why: AI crawlers do not read your JavaScript. Without SSR, they see an empty <div id="root">.

Fix: Switch to Next.js Server Components, Nuxt SSR, Astro, or pre-render via Prerender.io as transition.

2. robots.txt with User-agent: * Disallow: / — Critical (-10 pts)

Why: Inherited from a badly cleaned staging or a default CMS config, it blocks all bots including AI.

Fix: List explicitly GPTBot, ChatGPT-User, Google-Extended, ClaudeBot, PerplexityBot, CCBot with Allow: /.

3. No JSON-LD block on key pages — Heavy (-20 pts max)

Why: LLMs need structured data to precisely identify the entity a page represents.

Fix: At minimum Organization global. FAQPage on FAQs, HowTo on tutorials, LocalBusiness if you are local.

4. No /llms.txt at root — Moderate (-5 pts)

Why: Emerging standard followed by the main LLMs to identify a site's priority pages.

Fix: Create a /llms.txt in Markdown: site H1, intro in > blockquote, sections with absolute links.

5. Content without dateModified nor <time> tag — Moderate (-7 pts)

Why: Without a date, LLMs cannot evaluate freshness — and prefer to cite a dated source.

Fix: Add datePublished + dateModified in Article/WebPage JSON-LD, and a visible <time datetime="...">.

6. No structured FAQ section — Moderate (-15 pts cumulated)

Why: FAQPage is one of the JSON-LD types most exploited by ChatGPT, Perplexity and AI Overviews.

Fix: Add a real FAQ (explicit questions in "How…?" format) with FAQPage JSON-LD.

7. Multiple <h1> on the same page — Moderate (-7 pts)

Why: Confuses LLMs about the main subject of the page and breaks the logical hierarchy.

Fix: A single <h1> per page (the main subject), <h2> for sections, <h3> for subsections.

8. Intro paragraph buried under marketing hero — Moderate (-10 pts)

Why: LLMs extract the first paragraph after the H1 in priority. If it's empty or too verbose, they skip.

Fix: 15 to 80 words of factual response right after the H1. Inverted pyramid: essential, then detail.

9. No canonical tag — Light (-1.5 pts)

Why: Without canonical, LLMs may index multiple variants (with/without UTM, www vs apex) and dilute the signal.

Fix: Add <link rel="canonical" href="..."> on all pages — pointing to the canonical version.

10. No OpenGraph image nor Twitter Card — Light (-3.5 pts)

Why: LLMs use og:image in some syntheses; without OG, your shared pages on social networks look ugly.

Fix: Dynamically generate a 1200×630 OG image (Next 16 has app/opengraph-image.tsx native).

Audit in 5 seconds

ScoreGeo automatically detects the 10 mistakes above (and a few others more subtle). The report tells you exactly which ones are present on your site, their impact in points and the recommended fix.

Frequently asked questions

How many of these mistakes do I have on average?

On the ~200 French sites we audited in 2025-2026, the median is 6 mistakes out of 10. Most frequent: no /llms.txt (90%), no dateModified (75%), no structured FAQ (65%), weak intro paragraph (55%).

Where to start if I have several critical mistakes?

Prioritize by impact (1 and 3 are worth 20 pts each) and by effort. #2 (robots.txt) takes 5 minutes. #4 (llms.txt) takes 10 minutes. #5 (dateModified) takes 30 minutes per page template. Start with quick wins, they give you a fast positive signal.

Do I need to fix all 10 to reach 100/100 on ScoreGeo?

Not necessarily. If your partial sub-scores are already good, you can tolerate 1-2 minor imperfections. ScoreGeo adds normalized scores: a site at 92/100 with 8 perfect criteria and 1 "warn" criterion at 0.5 is acceptable. Only for the full score do you need to tick everything.