Machine Readability Checker: Can AI Systems Read Your Content?

What Is Machine Readability?

Machine readability means your web content can be accessed and parsed by automated systems without requiring JavaScript execution or human interaction. Most AI crawlers do not execute JavaScript, so content rendered only on the client side is effectively invisible to them.

What Glippy Checks

• SSR detection - Whether your pages are server-side rendered or client-only
• JS framework analysis - Detection of React, Vue, Angular, Svelte, and other frameworks
• Bot blocking - Whether GPTBot, ClaudeBot, or Google-Extended are blocked via robots.txt
• Robots meta tags - Checking for noindex, nofollow, noai, or noimageai directives
• Content availability - Whether meaningful content exists in the initial HTML response

Agent-readiness signals (new in v1.6)

Glippy now also checks the emerging machine-readability standards from specification.website that help AI agents discover and ingest your content:

• llms-full.txt - A concatenated Markdown corpus of your llms.txt pages for full-context AI ingestion
• Content-Signal in robots.txt - Machine-readable search / ai-input / ai-train usage preferences
• HTTP Link header discovery - rel="describedby", api-catalog, sitemap and more, so agents discover resources without parsing HTML
• Markdown source endpoints - A .md version of each page advertised via <link rel="alternate" type="text/markdown">
• Feed discovery - RSS, Atom, or JSON Feed for a machine-readable content stream

These emerging-standard signals are scored as a bonus: present earns credit, absent is surfaced as a tip with no penalty.

Common Machine Readability Issues

Single-page applications (SPAs) built with React, Vue, or Angular often rely on client-side rendering, making their content invisible to AI crawlers. Glippy detects these frameworks and checks whether SSR or static generation is in place. Additionally, many sites inadvertently block AI bots through overly restrictive robots.txt rules.