Making Your Site Legible To Machines And Humans

The test that keeps this honest is simple. Show the rewritten page to somebody who buys from you and ask whether it is clearer. If the answer is no, no amount of extraction friendliness makes it a good page. ai search visibility

The Types That Rarely Earn Their Keep Elaborate breadcrumb hierarchies, speakable markup, deeply nested item lists and most of the specialised types outside their intended vertical produce little observable difference in how a brand is understood or recommended.

The fix is not abandoning modern frameworks. Server side rendering or static generation produces the same interface with meaningful content in the initial response, and it is faster for humans too, which is the usual pattern in this area.

Equally, do not publish a stripped alternate version of your site for crawlers. Serving different content to machines than to people is cloaking, it has been penalised for two decades, and there is no reason to expect a more forgiving treatment here.

The difficulty with this proposal is that it asks for money before the problem is visible in any report the business already trusts. That is a genuinely hard sell, and overselling it is the fastest way to lose credibility when the numbers stay small for two quarters.

Days One to Fourteen: Find Out Where You Stand Somebody writes fifty questions your buyers would ask, in their words. They run each one three times across the two or three assistants your customers use, from a signed out session, and record the full answers and every source cited.

The second is content behind interaction. Accordions, tabs and modals are good interface patterns and their content is sometimes absent from the initial response. Check whether yours is present in the HTML even when collapsed, which is usually a configuration question rather than a design one.

The Assumption That Broke Twenty years of practice rested on a simple chain: rank higher, get seen more, get clicked more. Every tool, every report and every agency pitch was built on it, and for most of that period it held.

Days Fifteen to Thirty: Fix the Plumbing Someone technical checks that the crawlers feeding AI systems can reach your site, that your bot protection is not silently blocking them, and that your important pages contain real content without JavaScript running.

Statistics without sources. This field circulates figures faster than it checks them, and a number arriving without a publisher, a sample size and a date should be discounted rather than repeated to your board.

The output is a spreadsheet and it is the most important document in the project. It tells you whether you are named, whether what is said about you is true, who is named instead, and which pages your category's answers are actually built from.

The Rendering Question This is the one real technical constraint. Content that only exists after JavaScript executes may be invisible to a retrieval fetch, which is not a browsing session and does not always run scripts.

Every usability study for thirty years has said readers scan, look for the relevant section, and want the conclusion before the reasoning. Extraction wants the same thing for different reasons. When somebody claims that writing for machines requires sacrificing readability, they are usually describing keyword stuffing, which is a separate and obsolete practice.

What to Do About llms.txt and Similar Files Proposals for machine readable files aimed specifically at language model consumers appear periodically. Adoption is inconsistent and support varies by provider, so treat these as low cost and speculative rather than as a requirement.

Test it rather than assuming. Load your key pages with JavaScript disabled and see what survives. If the product specifications, pricing, service areas and contact details vanish, that is what a machine reads.

Read alongside the first displacement, the picture is consistent: the top of the list is worth less than it was on the results page, and worth considerably less again in a channel that does not use lists.

This is a plan rather than an explanation. It assumes you have already accepted that some of your buyers are asking an assistant for recommendations before they contact anybody, and that you would prefer to be named.

Keep a small number of deliberately hostile prompts in the set permanently. Questions asking whether you are expensive, slow or suitable only for large clients reveal what the system believes about your reputation, and the belief is often traceable to one specific source. Nobody enjoys reading those answers, and they generate more actionable work than the flattering prompts do.

In that setting your ranking is one input among several to a retrieval step, and often not a decisive one. Ahrefs found in July 2025, across 15,000 long-tail prompts, that around 80 percent of cited pages did not rank for the original query at all, with about 12 percent in the top ten.

Treat markup as something with a maintenance cost rather than a one off implementation. Prices change, people leave, products are discontinued, and structured data quietly keeps asserting the old version long after the visible page has been updated. Adding a schema review to whatever process already updates your pages costs minutes and prevents the most damaging failure mode, which is confidently stating something that is no longer true.