{"slug": "i-audited-websites-for-ai-readiness-here-s-what-i-found", "title": "I Audited Websites for AI Readiness: Here's What I Found", "summary": "A developer audited websites for AI readiness and found that having schema markup does not guarantee machine readability. The key is providing clear entity identity and relationships through structured data, not just valid JSON-LD.", "body_md": "AI search is changing how people discover information.\n\nGoogle has AI Overviews. ChatGPT can search the web. Perplexity answers questions using web sources. Other AI systems are also becoming interfaces for finding products, companies, services, and information.\n\nThat made me curious about something:\n\nHow well are normal websites actually prepared to be understood by AI systems?\n\nNot just from a traditional SEO perspective.\n\nI mean:\n\nCan a machine clearly understand what this website is, who is behind it, what it offers, and how the information on the site is connected?\n\nSo I started looking at websites through that lens.\n\nAnd one thing became obvious:\n\nHaving a website that is readable to humans doesn't necessarily mean it is equally understandable to machines.\n\nSchema markup is only part of the picture\n\nMost developers who have worked with technical SEO have probably seen JSON-LD.\n\nFor example:\n\n{\n\n\"[@context](https://dev.to/context)\": \"[https://schema.org](https://schema.org)\",\n\n\"@type\": \"Organization\",\n\n\"name\": \"Example Company\",\n\n\"url\": \"[https://example.com/](https://example.com/)\"\n\n}\n\nThat's useful.\n\nBut imagine a machine trying to understand this company.\n\nIt may still have questions:\n\nWhat exactly does this organization do?\n\nWhich website belongs to it?\n\nWhich social profiles represent the same organization?\n\nWhat products or services does it provide?\n\nWho are the people associated with it?\n\nWhat other entities is it connected to?\n\nAre different pages on the site talking about the same organization?\n\nSimply declaring:\n\n\"@type\": \"Organization\"\n\ndoesn't answer all of those questions.\n\nThe entity is more important than the markup itself\n\nConsider a fictional company:\n\nAcme Digital\n\nIts homepage might say:\n\nAcme Digital is a web development agency specializing in WordPress and ecommerce.\n\nA human can understand that immediately.\n\nBut we can provide machines with much more explicit context through structured data.\n\nFor example:\n\n{\n\n\"[@context](https://dev.to/context)\": \"[https://schema.org](https://schema.org)\",\n\n\"@type\": \"Organization\",\n\n\"[@id](https://dev.to/id)\": \"[https://example.com/#organization](https://example.com/#organization)\",\n\n\"name\": \"Acme Digital\",\n\n\"url\": \"[https://example.com/](https://example.com/)\",\n\n\"sameAs\": [\n\n\"[https://www.linkedin.com/company/acme-digital/](https://www.linkedin.com/company/acme-digital/)\"\n\n],\n\n\"knowsAbout\": [\n\n\"WordPress\",\n\n\"Ecommerce\",\n\n\"Web development\"\n\n]\n\n}\n\nThe important part isn't that every website needs exactly this structure.\n\nThe important part is the relationships and identity signals.\n\nWe're no longer just saying:\n\n\"This is an organization.\"\n\nWe're providing additional context about which organization we're talking about and what it represents.\n\nBut here's where things get interesting\n\nA website can have schema markup and still have a weak implementation.\n\nI've seen patterns such as:\n\nSchema that exists but doesn't accurately represent the page.\n\nMultiple plugins generating overlapping structured data.\n\nDifferent pages using inconsistent organization information.\n\nMissing or poorly implemented entity identifiers.\n\nMissing identity references.\n\nImportant relationships between entities not being expressed.\n\nSchema generated automatically without much thought about the underlying entity model.\n\nSo there is an important distinction:\n\nA website having schema is not the same as a website having useful structured data.\n\nValid JSON-LD is only one part of the problem.\n\nI started thinking about \"AI readiness\"\n\nInstead of asking one question:\n\n\"Does this website have schema?\"\n\nI wanted to look at several signals together.\n\nFor example:\n\nCan we clearly identify the primary entity represented by the website?\n\nThat might be a:\n\ncompany\n\nperson\n\nproduct\n\norganization\n\nlocal business\n\npublication\n\nDoes the website provide meaningful Schema.org information?\n\nAnd does that information actually correspond to the content?\n\nAre important relationships represented?\n\nFor example:\n\nOrganization\n\n↓\n\nWebsite\n\n↓\n\nWebPage\n\n↓\n\nProduct / Service\n\n↓\n\nPerson\n\nThe exact relationships depend on the website, but the concept is important.\n\nCan different sources on the web be connected to the same entity?\n\nThis is where properties such as sameAs can become useful.\n\nDoes the organization have the same name, URL, description and other important information throughout the website?\n\nCan a machine easily determine what a particular page is about?\n\nThese aren't a magic formula for getting into ChatGPT or Google AI results.\n\nThat's not what I'm claiming.\n\nThey're simply different pieces of the larger machine-understanding problem.\n\nWhy should developers care?\n\nI think this goes beyond SEO.\n\nWe're increasingly building websites that aren't only consumed by humans.\n\nThey're consumed by:\n\nsearch engines\n\ncrawlers\n\nknowledge graphs\n\nAI systems\n\nrecommendation systems\n\nautomated agents\n\nother software\n\nFor years, we've optimized websites primarily around the human experience.\n\nThat's obviously still important.\n\nBut we're entering a world where machine understanding is becoming another important consideration.\n\nIf a website represents a business, product, person, or organization, we should make that information as clear and consistent for machines as we do for humans.\n\nI built a free checker while working on this\n\nThis led me to build AI Schema Gen.\n\nIt started as a schema-focused project, but I gradually expanded it into an AI-readiness checker.\n\nYou can enter a website and get an assessment of things such as:\n\nstructured data\n\nschema implementation\n\nentity information\n\nidentity signals\n\nrelationships\n\nother AI-readiness signals\n\nYou can try it here:\n\n[https://www.aischemagen.com/ai-readiness-checker/](https://www.aischemagen.com/ai-readiness-checker/)\n\nThe scanner is free.\n\nI'm especially interested in seeing what developers discover when they run their own websites through it.\n\nOne thing I don't believe\n\nI don't think there's a magic Schema.org type that will suddenly make your website appear in ChatGPT.\n\nI also don't think adding dozens of schema types automatically makes a website \"more AI-ready.\"\n\nIn fact, inaccurate, irrelevant, duplicated or misleading structured data can create more problems than it solves.\n\nThe goal should be:\n\nAccurate information + clear entities + meaningful relationships + consistent implementation.\n\nNot:\n\n\"Add as much schema as possible.\"\n\nThat's the direction I'm exploring with AI Schema Gen.\n\nI'd genuinely like to hear from other developers:\n\nWhat do you think makes a website \"AI-ready\"?\n\nAnd if you run your website through the checker, let me know what it finds.", "url": "https://wpnews.pro/news/i-audited-websites-for-ai-readiness-here-s-what-i-found", "canonical_source": "https://dev.to/arshadmehmood/i-audited-websites-for-ai-readiness-heres-what-i-found-2k5c", "published_at": "2026-09-03 14:21:02+00:00", "updated_at": "2026-09-03 14:55:48.371200+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools"], "entities": ["Google", "ChatGPT", "Perplexity", "Schema.org", "JSON-LD"], "alternates": {"html": "https://wpnews.pro/news/i-audited-websites-for-ai-readiness-here-s-what-i-found", "markdown": "https://wpnews.pro/news/i-audited-websites-for-ai-readiness-here-s-what-i-found.md", "text": "https://wpnews.pro/news/i-audited-websites-for-ai-readiness-here-s-what-i-found.txt", "jsonld": "https://wpnews.pro/news/i-audited-websites-for-ai-readiness-here-s-what-i-found.jsonld"}}