Forem: Matthias Meyer

Why AI Can't Read Your Website — And What To Do About It

Matthias Meyer — Thu, 09 Apr 2026 21:51:21 +0000

Many websites are invisible to AI systems. Client-side rendering, missing semantics, and no machine interfaces cost visibility. What you can change today.

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

. 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

When 80% of the source code consists of design classes, ad banners, and tracking scripts while only 20% is actual content, the page has a poor text-to-HTML ratio. AI systems have to extract the relevant content from a sea of technical noise -- and they often fail at this.

Missing Semantic Structure

When every element is a

, all meaning is lost. AI systems need semantic HTML5 tags: for the primary content, for standalone pieces, for navigation, a clean

through

hierarchy for structure. Without this, AI cannot distinguish what matters from what is decoration.

What AI Actually Needs

AI systems read your website fundamentally differently than humans. They do not see colors, animations, or layout. They see the DOM -- the structured source code of your page. And they need three things:

Server-Side Rendering (SSR): The HTML code must be fully delivered by the server, not assembled in the browser. Frameworks like Next.js, Nuxt, or Astro provide this out of the box. Every crawler -- whether Google, Bing, or ChatGPT -- gets the complete content immediately.

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 , , , , , . 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

A plain text file in the root directory of your website that describes your company, services, and most important content in machine-readable form. No HTML tags, no CSS -- pure text with Markdown structure. AI systems like Claude and Perplexity actively look for this file.

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 solves a central problem: hallucinations. When an AI finds no structured data, it has to extract facts from running text -- and risks errors in the process. With JSON-LD you deliver machine-readable facts that require no interpretation.

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 is the standard for this. It connects your business with the global Knowledge Graph -- the structured knowledge that AI systems use to understand the world. And sameAs links to LinkedIn, GitHub, or industry directories confirm to the AI: "Yes, this entity actually exists."

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 your robots.txt: Make sure AI bots are allowed to crawl your site. GPTBot, ClaudeBot, PerplexityBot, Google-Extended -- many websites block these crawlers by default or accidentally.

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

The question is not whether AI systems will become the primary source of information, but when. For many users, it already is. Those who make their website machine-readable now will have an advantage over everyone who only reacts when Google forces the change.

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.

Matthias Meyer
Founder & AI Architect
Builds AI-ready websites and AI automations for SMBs and agencies.

Claude Mythos Preview found thousands of zero-days in every major OS and browser. Here's what the headlines are missing. published: true

Matthias Meyer — Tue, 07 Apr 2026 22:56:24 +0000

Anthropic dropped something big yesterday. Not a new chat model, not a productivity feature. They revealed that an unreleased model called Claude Mythos Preview has been quietly finding thousands of critical security vulnerabilities across every major operating system and every major web browser. Some of these bugs are 27 years old.

They are not releasing the model publicly. Instead, they launched Project Glasswing, a coalition with Apple, Microsoft, Google, AWS, CrowdStrike, NVIDIA, the Linux Foundation, and others. The goal: patch the bugs before attackers build similar AI.

Most of the coverage I have seen reads like a rewritten press release. The actual details buried in the red team report and system card tell a different story. Here is what stood out to me as someone who runs AI agents in production every day.

The exploit rate is the real headline

Finding bugs is one thing. Every static analysis tool finds bugs. The difference with Mythos is that it does not just find vulnerabilities. It builds working exploits for them.

In testing against Firefox's JavaScript shell, Mythos turned 72.4% of discovered vulnerabilities into successful exploits. It achieved register control in another 11.6% of cases. Previous Claude models could spot bugs but failed almost entirely at exploitation. That gap is gone now.

This is not a scanner. This is a model that reads code, understands the logic, finds the flaw, and writes a proof of concept that works. Autonomously.

Less than 1% is patched

Anthropic says thousands of critical zero-days were found. Fewer than 1% have been fully patched so far. The volume is simply too large for the affected organizations to keep up.

They are publishing cryptographic hashes of vulnerability details today, with plans to reveal specifics after fixes ship. This is standard responsible disclosure, but the scale is unprecedented. We have never had a single tool produce this many verified findings at once.

For context: Google's Project Zero, one of the best human vulnerability research teams in the world, publishes around 50 to 80 bugs per year. Mythos found thousands in weeks.

The CyberGym benchmark gap

On the CyberGym evaluation benchmark, Mythos scored 83.1%. Claude Opus 4.6, the next best model, scored 66.6%. That is not a marginal improvement. That is a generational jump within the same model family.

For anyone tracking AI capabilities over time, this should raise questions about what the next generation looks like. If the gap between Opus and Mythos is this large, what happens when competitors catch up to where Mythos is today?

What they are actually giving away

Buried in the announcement is something I think matters more long term than the vulnerability findings themselves.

Anthropic is offering free Claude Max subscriptions to any verifiable open source maintainer. Not Mythos access, but Opus and Sonnet, which are still capable security tools. They committed $100M in usage credits for Project Glasswing partners and donated $4M to open source security organizations through the Linux Foundation and Apache Software Foundation.

If you maintain critical open source software and you have no security budget, which describes most open source maintainers, you can apply through the Claude for Open Source program.

This is a smart move. The vast majority of critical infrastructure runs on code maintained by small teams or individual volunteers. Giving them access to frontier AI for code review could prevent more bugs than any single audit.

The pricing tells you something

When Mythos eventually becomes available through the API, it will cost $25 per million input tokens and $125 per million output tokens. That is roughly 5x more expensive than Opus 4.6.

Anthropic is not positioning this as a general purpose model. The pricing alone ensures it will only be used for high value tasks where the cost of missing a bug is measured in millions. Security audits, compliance reviews, infrastructure hardening. Not chat, not content generation.

The uncomfortable question

Anthropic built this. They chose to handle it responsibly with controlled access and coordinated disclosure. But the capability exists now. It is a matter of time before other labs, or well funded adversaries, reach similar performance.

The 90 day disclosure window Anthropic set for publishing full vulnerability details is tight. With less than 1% of bugs patched, that creates real pressure on every affected vendor. And the affected vendor list is essentially everyone.

Project Glasswing is a starting point. Anthropic said that explicitly. The real question is whether the defenders can stay ahead when this class of capability becomes widely available.

What this means for developers

If you write code that touches the internet, your threat model just changed. Not because of anything you did wrong, but because the cost of finding vulnerabilities in your code just dropped by orders of magnitude.

The practical takeaways:

Audit your dependencies. If Mythos found 27 year old bugs in OpenBSD, your npm packages are not immune. The bugs that survived decades of human review are exactly the kind AI excels at finding.

Watch for the patches. Over the next 90 days, expect a wave of critical security updates across operating systems, browsers, and open source projects. Apply them quickly.

If you maintain open source, apply for Claude Max. Free access to Opus for security review is genuinely useful. Take it.

Rethink your security testing. Static analysis tools that pattern match against known vulnerability types are not enough anymore. The bar just moved.

The age of AI finding bugs faster than humans can fix them is not coming. It arrived yesterday.

StudioMeyer Crew: Turn Claude into a CEO, CFO, or CTO — Zero API Cost

Matthias Meyer — Tue, 07 Apr 2026 19:50:38 +0000

Switching between "act as my CFO" and "now think like a CTO" prompts works -- sort of. But every time you switch, Claude loses the role. The analysis gets shallow. There's no framework, no structure, no memory of what the CEO said when the CFO takes over.

StudioMeyer Crew is an MCP server that gives Claude 8 expert personas with real business frameworks. Activate a CEO, and Claude uses Porter's Five Forces. Switch to CFO, and Claude runs unit economics with your actual numbers. Zero extra API cost -- runs entirely in your Claude subscription.

What does Crew actually do?

Instead of writing long system prompts yourself, you activate a persona with one command:

"Activate the CEO persona."

Claude instantly adopts the role -- with domain-specific frameworks, output formats, decision patterns, and constraints. Not a generic "act like a CEO" prompt, but a battle-tested system prompt with few-shot examples and anti-patterns.

8 Built-in Personas

Persona	Category	What they bring
CEO	Business	Strategy, vision, Porter's Five Forces, SWOT, delegation frameworks
CFO	Business	Unit economics, ROI analysis, pricing models, budget planning
CMO	Business	Growth strategy, AARRR funnel, content marketing, SEO/GEO
CTO	Tech	Architecture review, DORA metrics, tech debt assessment, code review
PM	Business	RICE/ICE scoring, user stories, PRD generation, JTBD framework
Analyst	Ops	Market research, competitive intelligence, data analysis
Support	Ops	Customer communication, FAQ writing, onboarding guides
Creative	Creative	Brand voice, copy, storytelling, design briefs

10 Tools

Tool	What it does
`crew_activate`	Switch to a persona (loads frameworks + memory context)
`crew_deactivate`	Back to default Claude
`crew_list`	Show all available personas
`crew_status`	Who am I right now? Duration, token estimate
`crew_feedback`	Rate the persona (1-5)
`crew_create`	Build your own custom persona
`crew_delete`	Remove a custom persona
`crew_workflow_list`	Available multi-persona workflows
`crew_workflow_run`	Run a full workflow (e.g. CEO then CFO then CTO)
`crew_guide`	Help and onboarding

Getting started: 30 seconds

Add the server URL in Claude Desktop or Cursor:

https://crew.studiomeyer.io/mcp

Or via Claude Code:

claude mcp add crew --transport streamable-http https://crew.studiomeyer.io/mcp

Works with Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, and Zed.

What you can actually do with it

Strategy session in 5 minutes

"Activate CEO. Review our pricing strategy: we have 4 MCP products ranging from free to $49/month."

Claude as CEO runs a structured analysis: market positioning, competitive landscape, pricing psychology, revenue projections. Not a vague opinion -- a framework-driven assessment with clear recommendations.

Financial sanity check

"Switch to CFO. Are these unit economics sustainable?"

The CFO persona calculates: customer acquisition cost, lifetime value, margin per tier, break-even timeline. With actual numbers, not hypotheticals.

Multi-persona workflows

The real power: chaining personas. Three built-in workflows:

Workflow	Personas	What happens
Strategy Review	CEO, then CFO, then CTO	CEO defines strategy, CFO validates finances, CTO checks feasibility
Content Pipeline	CMO, then Analyst, then Creative	CMO plans content, Analyst fact-checks, Creative polishes
Product Launch	Analyst, PM, CEO, CMO, CTO	Full launch analysis from research to go-live checklist

"Run the strategy review workflow for our Q2 plans."

Each persona builds on the previous one's output. The CFO doesn't repeat what the CEO said -- they challenge it.

Memory Bridge

If you also use StudioMeyer Memory, Crew automatically loads relevant context when activating a persona. The CFO searches for "revenue, costs, pricing decisions" in your memory. The CTO loads "architecture, tech stack, dependencies."

No manual context switching. The persona knows your history.

What makes this different

Feature	StudioMeyer Crew	DollhouseMCP	Ruflo
Personas	8 (deep, with frameworks)	150+ (generic)	60+ (swarm)
Memory integration	StudioMeyer Memory	None	Own DB (AgentDB)
Multi-persona workflows	3 built-in	None	Swarm topology
Custom personas	Yes (Markdown + YAML)	No	No
API cost	$0 (Claude subscription)	$0	Requires API keys
Domain frameworks	DORA, Porter, AARRR, RICE	Generic prompts	Generic prompts

The key difference: Crew personas aren't just role descriptions. They include decision frameworks, few-shot examples, output format constraints, and anti-patterns. A CFO persona that says "consider ROI" is useless. A CFO persona that runs a 5-year DCF model with your inputs is useful.

Custom personas

Don't need a CFO but need a Legal Advisor? Create your own:

"Create a persona called Legal Advisor, focused on contract review, GDPR compliance, and risk assessment."

Crew saves it as a Markdown file with YAML frontmatter. Your custom personas persist across sessions and work exactly like built-in ones.

Pricing

Free. All 10 tools, all 8 personas, all 3 workflows. No API keys, no credit system, no hidden costs. Runs in your existing Claude subscription.

We built Crew because we got tired of writing the same "act as my CFO" prompts and getting shallow results every time. Eight personas, tested across hundreds of real business decisions at StudioMeyer. If you want Claude to think like an expert instead of a generalist -- try it.

Learn more about StudioMeyer Crew