For decades, Google was the gateway to the internet. You built a website, did your SEO, and hoped to land on page one. That dynamic is fundamentally shifting right now.
Today, millions of people no longer ask Google. They ask ChatGPT, Perplexity, Claude, or Gemini. And these AI systems answer directly, with concrete recommendations, facts, and links. If your website is not readable for these systems, you simply do not exist in this new world.
This does not only affect tech companies. It affects every tradesperson, every agency, every local business. Because the question is no longer "Are you on Google?". It is "Does the AI know you?"
The Problem: Beautiful Websites That AI Cannot See#
Many modern websites look fantastic. Animations, interactive elements, elaborate design. But under the hood, they deliver a problem: they are invisible to machines.
Empty HTML From Client-Side Rendering#
Single Page Applications (SPAs) and purely client-side JavaScript render content only in the browser. When an AI crawler requests the page, it often receives nothing but an empty HTML shell with a single <div id="root"></div>. The actual content loads through JavaScript. And many crawlers do not execute JavaScript.
The result: your page exists, but for AI systems it is empty.
Too Much Code, Too Little Content#
Excess markup and hidden content make a page harder to inspect. A fixed text-to-HTML ratio is not an established threshold for AI readability. Check the actual server response and whether the relevant text is accessible in it.
Missing Semantic Structure#
Semantic HTML makes structure explicit: main for primary content, article for standalone pieces, nav for navigation and suitable headings. Div containers do not automatically make text unreadable, but clear structure helps people, assistive technologies and machine processing.
What AI Actually Needs#
AI systems differ: some process fetched text, while others use rendered pages or other media. Directly accessible content, clear structure and verifiable facts form a robust foundation.
Server-delivered HTML: Include important text in the initial HTML response. SSR and static generation can achieve this. Implementation matters: check that services, prices and contact details are readable without later JavaScript. A framework name alone does not prove it.
Clean DOM: A low ratio of markup to content. Fewer nested containers, fewer empty wrapper elements, more actual text. The higher the information density in the source code, the better AI can process the content.
Semantic HTML5: Clear structure with <main>, <article>, <section>, <aside>, <header>, <footer>. A logical heading hierarchy. Alt texts for images. These tags are not optional. They are the language that machines understand.
The New Interfaces: Files That Exist Only for Machines#
Beyond clean HTML, there are now dedicated files that exist specifically for AI systems. They are the equivalent of a business card that you hand directly to the machine.
llms.txt#
llms.txt is a supplementary text-and-link overview under an open format proposal. It can help clients that explicitly read it. It is not an access rule like robots.txt or a requirement for Google AI Overviews or AI Mode. This does not establish automatic use by all AI search providers.
agents.json#
Defines what digital tools and interfaces your company offers. If you run APIs, chatbots, or other automated services, agents.json tells AI systems how to interact with them. It is the machine equivalent of a service overview.
Structured Data (JSON-LD)#
The oldest and most mature of the three formats. JSON-LD blocks in your HTML deliver structured facts: who you are (Organization), what you offer (Service, Product), where you are (PostalAddress), what customers say (Review). Google has used this for years. But for AI systems it is even more important.
Structured Data as a Fact Supplier#
JSON-LD makes facts explicit and easier to associate. It can support processing, but does not prevent hallucinations. Wrong or outdated facts remain wrong when structured. Markup must match visible content; Google AI answers require no additional special schema.
An example: Instead of burying "We are an agency in southern Germany" in a paragraph, you tell the machine explicitly:
- Type: Organization
- Founded: (your founding year)
- Location: (your city)
- Services: (your specific offerings)
Schema.org supplies a shared vocabulary for these facts. Relevant sameAs links can identify associated profiles. They do not independently verify the facts or guarantee inclusion in a knowledge graph.
Content That Works for AI#
Machine-readable structure alone is not enough. The content itself must also be AI-compatible. Three principles:
High Information Density#
Every paragraph should deliver a concrete piece of information. Vague marketing phrases like "We offer innovative solutions for your business" contain exactly zero usable information for an AI. Instead: concrete numbers, specific services, verifiable facts.
Inverted Pyramid#
Put the most important information at the beginning of each section. AI systems weight the first sentences more heavily. If your core argument sits in the last paragraph, it may get lost.
Context-Independent Paragraphs#
AI systems break texts into chunks and process them individually. If a paragraph only makes sense together with the previous one. "As mentioned above...". It loses its meaning once viewed in isolation. Every paragraph should be understandable on its own.
What You Can Do Right Now#
A practical checklist to get started:
-
Check crawlers: OAI-SearchBot for ChatGPT search, Googlebot for Google Search. GPTBot concerns training; Google-Extended controls other Google applications. Also check the firewall, CDN and actual response codes.
-
Enable Server-Side Rendering: If your website is a SPA, check the source code. Can you see the content directly in the HTML? If not, you need SSR or Static Site Generation.
-
Create an llms.txt: A simple text file with your company name, core services, and most important links. Place it at
yourdomain.com/llms.txt. -
Implement JSON-LD: Start with Organization schema on the homepage. Add Service schema on service pages. FAQ schema on pages with frequently asked questions.
-
Rework your content: Go through your most important pages. Remove filler phrases, add concrete facts, structure with clear headings.
-
Actively submit for indexing: Do not wait for search engines to find you. Submit your sitemap to Google Search Console and Bing Webmaster Tools. Use IndexNow for instant notifications when you publish new content.
The Future Is Machine-Readable#
Measure how much AI search matters to your business rather than assuming it. Crawlable content and clear facts help independently. Assess technical access, observed citations and actual visits separately; a successful fetch does not imply a recommendation.
The good news: most of these measures also make your website better for humans. Faster load times, clearer structure, better content. There is no downside.
Want to know how well your website is readable for AI systems? We help businesses make their online presence machine-readable. From technical foundations to content strategy. Learn more at studiomeyer.io/services/geo.
