The 15-Minute Audit: Making Your Website AI-Readable

AI is being positioned to your customers before they ever open a browser tab. They are asking Claude and ChatGPT for vendor recommendations, comparing options, and forming opinions based on whatever the AI can scrape from your site.

If your website is full of JavaScript that only loads after a fancy animation, marketing fluff hidden inside five-paragraph stories, and a header structure that makes no semantic sense, the AI scrapers move on. Your business gets summarised as "a company in this space" or, worse, does not get mentioned at all.

This is a 15-minute audit you can run yourself. No developer required. Three basic engineering shifts, plus a validation step. By the end, you will know whether AI can actually understand what your business does, and you will have a punch list of fixes that take a morning to ship.

The 15-Minute Audit

Three shifts. Each one takes about 5 minutes to audit and an hour or so to fix if you find a problem. Run them in order. Stop at any point where you find something to fix.

Step 1: Strip the JavaScript Bloat

AI scrapers do not have eyeballs, and they do not wait for loading screens. If your core value proposition only renders after a JavaScript animation fires, the AI bot has already left before the page finishes.

The audit. Open your homepage in a browser. Turn off JavaScript (most browsers have this in Developer Tools settings, or use a "Disable JavaScript" extension). Reload the page. If your headline, services, and contact details are still readable, you pass. If they vanish or show a loading spinner, you fail.

The fix. Move your core text into the HTML so it loads immediately. JavaScript should enhance the page, not deliver the message. This is rarely a rebuild. Usually it is moving the same text out of a script-rendered component and into a static <h1> or <p> tag the server sends with the page.

Step 2: Structure the Data, Kill the Stories

AI does not care about your brand journey. It wants hard facts. If you are burying what you actually do inside five paragraphs of "synergistic workflows tailored to empower your unique enterprise journey," the LLM cannot extract it.

The audit. Open your Services and Pricing pages. Are your deliverables buried in heavy paragraphs? Are your prices hidden in an accordion that requires a click? Are you describing what you do in adjectives when you could be describing it in nouns?

The fix. Serve product details and pricing in structured formats an LLM can parse instantly. Lists, bullet points, clean tables. This site does this on every pricing and feature block, which is why an AI can answer "what does Practical AI offer and at what price" without hallucinating.

Step 3: Fix Your Semantic Tree

H1, H2, and H3 tags are not font sizes. They are a database schema that tells the LLM exactly how to index your business. Most websites get this wrong. Multiple H1s on a single page, H2s used purely for visual decoration, an H3 that contains the company name and tagline in a single run-on.

The audit. Run a free SEO checker (W3C validator, Lighthouse, or the ahrefs free audit) and look at the header tag tree. You are looking for exactly one H1 per page, H2s for major sections, H3s for items within those sections.

The fix. Your H1 should explicitly state what the business does, in plain language. Your H2s should be your core services or sections. Your H3s should be the features, deliverables, or pricing tiers. Use them logically. While you are in there, check whether you have structured data (Schema.org JSON-LD) for your products, services, or organisation. It is the same idea at a deeper level, and most AI engines prefer it to unstructured prose.

Step 4: Validate With an AI

The closing test. Open Claude, ChatGPT, or Gemini and ask, out loud: "What does [your company] do, what do they offer, and at what price?" Do not look at your site while you ask. Then ask: "Which of their services would suit a [your target customer]?"

If the answer is wrong, hedged, or vague (if it hallucinates a service you do not offer, or misses one you do), your prospects are getting the wrong information too. The audit fixes above directly address whatever the AI got wrong. Run the same validation in a month, after the fixes have shipped, and compare the answers.

Beyond the Basics: /llms.txt for Builders

If you have a developer on hand, there is one more thing worth doing. /llms.txt is a new standard (live at llmstxt.org) where you publish a clean Markdown file at the root of your site describing what your business does, what it offers, and how to contact you. AI scrapers are starting to look for it the way they look for sitemap.xml or robots.txt.

This site has one. You can read it at practical-ai.space/llms.txt. It is around 30 lines of plain Markdown. A developer can write it in an hour, and it gives AI engines a clean, structured summary to cite from. Not a replacement for the audit above. A complement. Most businesses do not need this yet, but if you are serious about being recommended by AI, it is the next step.

Where to Start

Run Step 1 in the next 15 minutes. Open your homepage with JavaScript off. If the AI can read your value proposition, you are ahead of most of your competitors. If it cannot, you have a punch list of fixes that will pay back every time a prospect asks an AI about your category.

Once the basics are solid, the free "5 AI Wins You Can Action This Week" guide on this site shows how to put AI to work inside your business once your website is doing its job.