--- title: Websites that people, search engines and AI read the same way — TechJapan LLC source: https://www.tech-japan.jp/services/ai-ready-web/ updated: 2026-09-18 facts: https://www.tech-japan.jp/facts.json --- # Not just found. Understood. *Websites where a person, a search engine and an AI assistant read the same facts.* Most company websites are written for one reader: a person with a mouse. A search engine reads the same page and finds no clear statement of what the company is. An AI assistant reads it and fills the gaps with guesses. We design the information structure underneath the site so that all three readers arrive at the same meaning, then we build it, measure it and hand it over. Search engine optimization, answer engine optimization and AI optimization are not three products here. They are one piece of design work, and this page says what it contains. From JPY 30,000, tax excluded, quoted in writing for an agreed scope. The audit that opens every engagement is free. ## The reader changed. The pages did not. Google now answers many queries with an AI Overview or in AI Mode before it shows a list of links, and its documentation states that a page appears there only if it is indexed and eligible for a snippet, like any other result. ChatGPT fetches web pages through a crawler of its own, OAI-SearchBot, to answer questions with citations. Microsoft reports, per URL, how often a site is cited in Copilot and in Bing’s AI summaries. None of this replaced the search engine. It added a second kind of reader on top of it, one that does not scan a page but extracts facts from it and composes an answer. That reader is unforgiving in a specific way. A person who lands on a vague homepage clicks around until the picture forms. A machine does not click around. It takes what the page states plainly, and where the page states nothing, it either says nothing about you or says something wrong. Neither outcome is a ranking problem. Both are information problems, and they are fixed on the page, not in a tag. ## What it looks like from your side | What you notice | What is usually underneath | | --- | --- | | Ranked, but not asked. Traffic arrives and nobody writes | The page ranks for a word but never says who the service is for, what it includes, or what it costs, so the visitor cannot tell whether to write | | Found only by name. Nothing but the company name brings anyone in | The site has no entity a search engine can attach a topic to: no page that states the category, the problem solved, and the relation between them | | More pages, same position. Monthly articles, flat results | Articles are stacked on a foundation that never defined the company. Each article competes alone instead of reinforcing one entity | | The assistant has never heard of you | Facts live in images, sliders, PDFs or JavaScript that a crawler did not render; or the crawler behind that assistant is blocked in robots.txt | | The assistant describes you wrongly: old price, a product you retired, a service you never offered | Two pages state two different facts, and nothing says which is current. There is no visible date, no status, and no single place a machine can treat as authoritative | | Google shows you, AI answers cite a competitor | The competitor’s page answers the question in one paragraph with a source. Yours answers it in a brochure, across four sections, with no evidence a machine can quote | | Structured data implemented, nothing happened | The markup describes content that is not on the page, or describes a page that is itself vague. Markup restates; it cannot add clarity the text lacks | | Told to add llms.txt, unsure it matters | It is a signpost, not a result. See section 07 for what the crawlers actually document | | Nobody can explain SEO, AEO and AIO in one breath | They are one foundation with three names. Section 03 | None of these is a reason for alarm. Each is a specific defect in how information is stated, and each one has a specific repair. The rest of this page is the list of repairs. ## SEO, AEO and AIO, defined without the marketing | Term | What it makes possible | What it needs from the site | | --- | --- | --- | | SEO search engine optimization | A search engine can discover the page, crawl it, understand it, index it and show it in results | Crawlable HTML, one canonical URL per page, a sitemap, sensible titles, internal links, speed, and text that says what the page is about | | AEO answer engine optimization | When a search or AI service answers a question, the information on the page is usable as material for that answer | Questions answered in one place, in plain sentences, with the evidence next to the claim; tables for facts; a visible date | | AIO AI optimization | The facts about the company, its services, products, people, prices and results, and the relations between them, are hard for an AI to misread | One term per concept, one source per fact, status stated (designed, built, available), what is not offered stated, entities connected in structured data | Read the right-hand column three times and it is the same list. Every row asks for facts stated once, clearly, in text, with their relations written down. That is an information architecture problem, and it is why we do not sell the three as separate services. A site with the foundation right is, as a consequence, in good shape for all three. A site without it cannot be patched into any of them. ## One source of facts. Every surface generated from it. Our other work is [ontology engineering](https://www.tech-japan.jp/services/ontology/): taking a company’s internal knowledge, choosing one term per concept, writing the relations down, and building retrieval on top so that an AI answers from a source it can point to. A public website is the same problem facing outward. The readers are a person, Googlebot and Bingbot, and the crawlers behind ChatGPT, Claude and Perplexity. The knowledge is who you are, what you sell, to whom, for how much, and what the evidence is. So we treat the site the way we treat a knowledge base. The facts are held in one internal source. From that source the site generates the HTML a person reads, the JSON-LD and sitemap a search engine reads, and the Markdown twins, fact ledger and llms.txt an AI assistant reads. Nothing is copied by hand from one to another, which is the only reliable way to make sure they never disagree. *Figure: Three readers, one source. A person, a search engine and an AI assistant each read the same website. Underneath all three sits one internal source of facts. From that source the site generates the HTML pages people read, the JSON-LD and sitemap search engines read, and the Markdown twins, fact ledger and llms.txt that AI assistants read. Because every surface is generated from the same source, no two of them can disagree.* ```text PERSON SEARCH ENGINE AI ASSISTANT | | | v v v HTML page JSON-LD, sitemap index.md, facts.json, llms.txt | | | +----------------+------------------+ | | generated, never copied v +=========================+ | ONE SOURCE OF FACTS | | who, what, for whom, | | price, status, updated | +=========================+ three readers, one meaning ``` This is also why the approach works for a company whose category does not exist yet. When no one searches for the name of what you do, the route in is through questions: what does this company do, for whom, instead of what. A site that states those relations plainly gives a search engine and an assistant something to reason from, even with no keyword to match. We are in that position ourselves, and this site is how we handle it. ## Four layers, from the bottom up The technical base comes first, and it is ordinary. Everything above it depends on a crawler being able to fetch the page and read its text without running a script. *Figure: What we design and build, as four layers from the bottom up. Layer one is the technical base: crawlable HTML, indexability, canonical URLs, sitemap, robots, redirects and speed. Layer two is information architecture: URL structure, page hierarchy, entities, topic clusters, internal links and breadcrumbs. Layer three is content: who, what, for whom, what it does and does not do, evidence and update dates. Layer four is machine-readable surfaces: JSON-LD, Markdown twins, a fact ledger and llms.txt. Each layer depends on the one below it.* ```text +----------------------------------------------------+ | 4 MACHINE-READABLE JSON-LD, index.md, facts, llms | +----------------------------------------------------+ | 3 CONTENT who / what / for whom / can / cannot | | evidence / updated | +----------------------------------------------------+ | 2 STRUCTURE URLs, hierarchy, entities, links, | | breadcrumbs, topic clusters | +----------------------------------------------------+ | 1 TECHNICAL crawlable HTML, canonical, sitemap, | | robots, redirects, speed | +----------------------------------------------------+ each layer stands on the one below it ``` ### 1. Technical base | | | | --- | --- | | Rendering | Server-rendered or static HTML. The whole text of every page is in the response. Google renders JavaScript but queues it, and its own documentation recommends server-side rendering because not all bots run JavaScript. We do not depend on any of them doing so | | Indexability | One canonical URL per page, self-referencing. An index directive, and a maximum snippet length that does not truncate the answer | | Discovery | A sitemap with each URL and the date its content last changed. A robots.txt that allows the crawlers you want, by name, and says nothing else | | HTTP | Every URL returns 200 or a deliberate 301. Retired URLs redirect to their successor rather than 404, because a page that ranked keeps its position only if the redirect exists | | Speed | No render-blocking requests. Inline CSS, no web fonts, no image the text depends on. The page is readable at the first byte | | Languages | If there is more than one, hreflang between them and one canonical per language, not one page trying to be both | ### 2. Information architecture | | | | --- | --- | | Entities | One page per thing that has to be understood on its own: the company, each service, each product, each person who is named as accountable. A page is the unit an engine attaches meaning to | | Hierarchy and URLs | Directory-style URLs that state the relation: /services/x/, /products/y/. The breadcrumb repeats it in text and in structured data | | Topic clusters | A service page is the hub; the pages that explain its parts, its evidence and its questions link to it and from it. Internal links are the relations a crawler can walk | | Relations | Company provides service; service is for audience; product is made by company; article is written by person. Stated in the text and repeated as identifiers in JSON-LD so the same node is meant everywhere | ### 3. Content Section 06, below, because it is the layer that decides whether the other three were worth building. ### 4. Machine-readable surfaces | Surface | What it is for | When we build it | | --- | --- | --- | | JSON-LD | States what entity each page is about, in schema.org vocabulary, using only facts visible on that page. Google recommends the format and requires the match | Always. It is the one machine-readable surface with documented consumers | | Markdown twin of each page | The page’s text without navigation, footer or decoration, at the same address plus a filename, for any agent that prefers text to HTML | When the site is generated from source, it is free. Otherwise, only for the pages that answer questions | | Fact ledger (JSON) | Names, numbers, dates, prices and status as atomic values, for an agent that wants to answer a question rather than read a page. Not a web standard; a convenience we publish and say so | When there are facts that change, such as prices and product status, and more than one page states them | | llms.txt | A signpost that says where to read what. It holds no facts of its own | Costs nothing when generated, so we include it. We do not claim an effect from it; see section 07 | | Feeds, APIs | An RSS feed for a site that publishes articles; an API only if a customer’s own systems will read it | Only when there is a reader. Not by default | ## Eight things a page has to state before anything else This is the list we audit against, and the list we write to. A page that answers all eight in plain sentences is usable by a person, a search engine and an assistant. A page that answers none of them cannot be rescued by markup. 1. **Who** — the legal entity, its other names, where it is, its registration number, who is accountable 2. **What** — the service or product, in one sentence a stranger could repeat 3. **For whom** — the buyer, by situation rather than by industry label 4. **What it can do** — scope, in a list, with the price model beside it 5. **What it cannot do** — what is out of scope, what is designed but not built, what is not offered at all 6. **What is different** — stated as a verifiable fact about the work, not as an adjective 7. **What the evidence is** — the measurement, the customer case, the award, with its source linked 8. **When it was last updated** — a visible date that is true, generated from the change rather than typed *Figure: Before and after, for one company page. Before: a hero says "solutions for your business", the service list is inside a slider image, the price is in a PDF, the founding year appears as two different values on two pages, and nothing says when the page was last updated. After: the first sentence says what the company does and for whom, the services are a table with what is included and excluded, the price and its conditions are in the text, the founding date comes from one source, and the last-updated date is visible. A machine reading the "before" has to guess; reading the "after" it does not.* ```text BEFORE hero: "solutions for your business" services: inside a slider image price: in a PDF founded: 2019 on one page, 2018 on another updated: nowhere a machine has to guess | v AFTER hero: what it does, for whom, first sentence services: a table: included, excluded, price price: amount and conditions, in the text founded: one source, shown everywhere updated: shown, and true a machine does not have to guess ``` The writing rules that follow from this are short. Say the fact once and link to it elsewhere rather than restating it. Put anything with more than two attributes in a table. Distinguish *designed*, *built* and *available* every time, because an assistant that reads “we offer” will tell your prospect you offer it. Answer each heading’s question in the first paragraph under it. And never write a sentence whose only content is that the company is good; a machine cannot use it, and a person has read it before. ## What the crawlers document, and what we do about it Everything in this section comes from the operators’ own documentation, checked on 2026-09-18. We separate three kinds of statement on purpose: what the specification says, what the industry believes, and what we decided. Only the first kind is in the table below. | Crawler | Operator says it is for | What that means for a site | | --- | --- | --- | | Googlebot | Search, and the AI Overviews and AI Mode built on it. There are no additional requirements to appear in those features; the page has to be indexed and eligible for a snippet | Ordinary indexability is the entire requirement. Appearance is controlled with the existing nosnippet, max-snippet and noindex directives | | Google-Extended | A robots.txt token controlling whether content may train Gemini models. It does not affect inclusion or ranking in Search | Blocking it does not remove a site from AI Overviews. Allowing it is a separate decision from search | | Bingbot | Bing search, and the Copilot answers and Bing AI summaries that cite web pages. Since February 2026 Bing reports those citations per URL in Webmaster Tools | Register the site in Bing Webmaster Tools. Bing’s stated recommendations are clear headings, tables, FAQ sections, cited sources, and consistent entities across text and media | | OAI-SearchBot | Used to surface websites in ChatGPT’s search features | If this is blocked, the site cannot appear in ChatGPT search answers. It is the one that matters for visibility there | | GPTBot | Crawls content that may train OpenAI’s models. Does not affect search results | A training decision, separate from search. Allowing or blocking it does not change ChatGPT search visibility | | ChatGPT-User | Fetches a page when a user’s action in ChatGPT asks for it. Because the request is user-initiated, robots.txt may not apply | The page will be read on request whether or not it was crawled, so the text has to be in the HTML | | ClaudeBot, Claude-User, Claude-SearchBot | Training, user-initiated fetches, and search quality respectively. All respect robots.txt | Same three-way split as OpenAI. Allow the user and search agents if you want to be read there | ### What we implement, given that - The full text of every page in server-rendered HTML, so that a fetch on request, which may not run JavaScript, gets everything a rendered crawl would - A robots.txt that names each crawler you want and allows it. Ours allows all of the above and is public - JSON-LD on every page, as a single graph with stable identifiers, so the company on the About page and the company on a product page are the same node. Only facts that are visible on that page - A sitemap whose dates are real, generated from the change history rather than set to today on every build, because a date that is always today is a date a crawler learns to ignore - Registration in Google Search Console and Bing Webmaster Tools before release, so the baseline exists on day one ### What we do not claim Google’s documentation says, in as many words, that you do not need to create new machine-readable files, AI text files or markup to appear in its AI features. In June 2025 Google’s John Mueller wrote that no AI system currently uses llms.txt, and OpenAI’s crawler documentation does not mention the file. We still generate one, because it costs nothing and describes where to read what, but anyone selling llms.txt as the thing that makes an AI cite you is selling a file the AI has not asked for. The same goes for structured data: it is required to match the visible page, it is recommended, and it is not a guarantee of anything, which Google also states. ### Sources for the table above | Source | What it states | | --- | --- | | [Google Search Central, AI features and your website](https://developers.google.com/search/docs/appearance/ai-features) | No additional requirements or special markup for AI Overviews and AI Mode; pages must be indexed and eligible for a snippet | | [Google Search Central, Structured data general policies](https://developers.google.com/search/docs/appearance/structured-data/sd-policies) | Structured data must represent visible page content; JSON-LD recommended | | [Google Search Central, JavaScript SEO basics](https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics) | Rendering is queued; server-side or pre-rendering is still recommended because not all bots run JavaScript | | [OpenAI, Overview of OpenAI crawlers](https://developers.openai.com/api/docs/bots) | OAI-SearchBot surfaces sites in ChatGPT search; GPTBot is for training and does not affect search | | [Anthropic, crawler documentation](https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler) | ClaudeBot for training, Claude-User for user-initiated fetches, Claude-SearchBot for search quality | | [Bing Webmaster Blog, AI Performance in Bing Webmaster Tools, February 2026](https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview) | Citations in Copilot and Bing AI summaries are reported per URL; clear headings, tables, FAQ, cited sources and consistent entities are recommended | ## We run this on ourselves, and you can check The site you are reading is the reference implementation. It was rebuilt on these rules in August 2026 and is kept as a live test environment: no images in the body, no JavaScript needed to read any page, every surface below generated from one internal source. Each row is a URL you can open now. | Surface | Where | Generated from | | --- | --- | --- | | This page as Markdown | [/services/ai-ready-web/index.md](https://www.tech-japan.jp/services/ai-ready-web/index.md) | The same page source, with navigation and footer removed | | Fact ledger | [/facts.json](https://www.tech-japan.jp/facts.json) | One internal file of facts. This service, its scope and its price model are in it under the same identifier as this page | | Signpost for AI | [/llms.txt](https://www.tech-japan.jp/llms.txt) | The page table. It links; it does not restate | | Entity graph | The JSON-LD in this page’s source | Organization, person, website, breadcrumb, this service and the FAQ below, as one graph with shared identifiers | | URL list | [/sitemap.xml](https://www.tech-japan.jp/sitemap.xml) | Every page’s canonical and the commit date of its last content change | | Crawl policy | [/robots.txt](https://www.tech-japan.jp/robots.txt) | Allow lines for each crawler in section 07, and nothing else | | Diagrams | Every figure on this page | Monospace text with a spoken description, so an assistant reads the diagram instead of skipping an image | | Last updated | 2026-09-18 | The date of the last change to this page’s inputs, the same value in the JSON-LD, the sitemap and the Markdown | Three things we can say from running it. First, the machine-readable surfaces cannot disagree, because there is nowhere to edit them by hand; a price changed in one file changes in the page, the ledger, the Markdown and the structured data on the next build, and a deployment is refused if they drift. Second, the site is a test environment for a company in exactly the position described in section 04: our category has no established name, so this site is where we find out what a search engine and an assistant make of a company that has to be understood before it can be matched. Third, we keep the observation log, with weekly Search Console readings and fixed questions put to Google’s AI Mode, ChatGPT and Perplexity, and we will show it to you in the first conversation, including the weeks where nothing moved. You can run the check yourself before writing to us: [ask Google’s AI Mode what TechJapan LLC builds and what it costs](https://www.google.com/search?udm=50&q=What+does+TechJapan+LLC+%28tech-japan.jp%29+build%2C+and+what+does+it+cost%3F), and compare the answer with [the front page](https://www.tech-japan.jp/). If they differ, that is a defect in our source, and we would like to know. ## Seven steps, and the audit is free *Figure: The seven-step process, in order. Audit, then information architecture, then content design, then development, then release, then measurement, then improvement. Measurement feeds back into improvement, and improvement goes back to content or structure. The audit is free and is written down.* ```text 1 AUDIT how the site reads today, in writing | v 2 ARCHITECTURE URLs, entities, hierarchy, links | v 3 CONTENT who / what / for whom / not / evidence | v 4 BUILD HTML, JSON-LD, ledger, Markdown twins | v 5 RELEASE deploy, submit, verify live | v 6 MEASURE search, AI referrals, inquiries | v 7 IMPROVE rewrite what the numbers say | +--> back to 2 or 3 ``` The audit comes back as a written document: how the site reads today to a person, to Googlebot and Bingbot, and to the crawlers behind the assistants, with each finding tied to one of the eight statements in section 06 and to a source in section 07. It is free, it is yours whether or not you continue, and it is what the quote is written against. ### What is included - **Audit** — how the site reads today to a person, to Googlebot and Bingbot, and to the crawlers behind ChatGPT, Claude and Perplexity, written down with sources - **Information architecture** — URL structure, page hierarchy, entity definitions, topic clusters, internal links, breadcrumbs, canonical URLs - **Content design** — who the company is, what it offers, for whom, what it does and does not do, what differs, what the evidence is, and when it was last updated, stated once - **Technical base** — crawlable server-rendered HTML, indexability, sitemap, robots.txt, redirects, HTTP status, page speed with no render-blocking requests - **Structured data** — JSON-LD for the entities that exist on the page (Organization, Service, Product, Person, Article, FAQPage, BreadcrumbList), never for content that is not visible - **Machine-readable surfaces where they earn their place** — Markdown twins of pages, a fact ledger, llms.txt, all generated from one source - **Measurement** — Search Console, GA4 referrals from AI assistants, Bing AI Performance, and inquiry tracking, with a written baseline - **Handover** — the generation scripts and the editing rules, so the site keeps its consistency after we leave ### What is not Article volume. We do not sell monthly article quotas, link buying, or any promise about rankings or AI citations. Visual redesign for its own sake is out of scope; we change appearance only where it changes what a reader or a machine can read. | | | | --- | --- | | Price | From JPY 30,000, tax excluded, quoted in writing for an agreed scope before work starts. The price holds for that scope | | Audit | Free, in writing, whether or not the engagement continues | | Setup fee | None | | Additions | Work outside the agreed scope is explained and quoted before it begins. Nothing is billed without prior agreement | | Starting size | One landing page, or the company and one service. A whole site is quoted after the audit counts its entities | | Handover | Inside the scope. You receive the generation scripts and the editing rules, and the exit date is written down at the start | | Who does the work | [Go Kyono](https://www.tech-japan.jp/about/), who writes the audit, does the design and the build. There is no account manager between you and the person doing it | ## What we count, and why rank is not the first number A rank is a position in a list that fewer people are reading from top to bottom. We record it, but the number that decides whether the work succeeded is the last row of the table. The baseline for every row is written down before the change, and the comparison is shown to you at the agreed interval, including rows that did not move. | Group | Metrics | Source | | --- | --- | --- | | Search | Impressions, clicks, click-through rate, average position, indexed pages, and the number of distinct queries the site appears for | Google Search Console, read weekly by a script that only reads | | AI | Referrals from ChatGPT, Perplexity, Copilot and Gemini; citations and cited pages in Bing’s AI Performance report; a fixed set of questions put to Google’s AI Mode, ChatGPT and Perplexity each week, with the answers recorded against what the site says | Analytics referrers, Bing Webmaster Tools, and a human probe with a written protocol | | Content | Time on the page, scroll depth, movement from this page to the next one, clicks on the two calls to action, return visits | Analytics, with events defined before release | | Business | Inquiries; inquiries that name what they read; inquiries that become a scoped quote; conversion rate; assisted conversions where this page was in the path | The contact form and a ledger we keep by hand | ## Questions we expect, answered the way we would answer them on a call **What is the difference between SEO, AEO and AIO?** SEO makes a page discoverable, crawlable, understandable and indexable by a search engine. AEO makes the information on it usable as material when a search or AI service answers a question. AIO organises the facts about a company, its services, people, products and prices, and the relations between them, so that an AI is unlikely to misread them. They are not three products. They share one foundation, which is a correct information structure, and that is what we design. **We already publish SEO articles every month. Why does nothing change?** Because the articles sit on top of a site that never states plainly what the company is, what it sells, to whom, and at what price. A search engine can rank an article and still have no clear entity to attach it to. We fix the entity first. Articles written after that have something to point at. **Will you get us cited by ChatGPT or shown in Google AI Overviews?** No one can promise that, and we do not. Google states that there are no additional requirements or special markup for AI Overviews and AI Mode; a page has to be indexed and eligible for a snippet, like any other. OpenAI documents that OAI-SearchBot decides what can appear in ChatGPT search. What we can do is make sure every one of those systems can fetch your pages, read the facts without running JavaScript, and find the same answer in every place it looks. Whether they then cite you is their decision, and we measure it rather than promise it. **Is llms.txt worth adding?** It costs nothing, so we generate one, but we do not sell it as a result. In June 2025 Google's John Mueller wrote that no AI system currently uses llms.txt, and OpenAI's crawler documentation does not mention it. We treat it as a signpost that says where to read what, and we keep the facts themselves in the pages and in the fact ledger, where crawlers already look. **We implemented schema.org structured data and saw no effect. Why?** Two usual reasons. The markup describes things that are not visible on the page, which Google's policies say not to do, or it describes the page correctly but the page itself is vague, so the markup is precise about nothing. Structured data can only restate what the page already says clearly. We write the page first, then mark it up, and we generate both from the same source so they cannot drift apart. **Our service is new and there is no keyword for it yet. Does any of this apply?** This is the case where it applies most. When no one searches for the category, the only route in is through questions: what does this company do, who is it for, what does it replace. A site that answers those in plain sentences, with the relations between company, service, problem and evidence written down, gives a search engine and an assistant something to reason from. We are in that situation ourselves, and this site is how we handle it. **Do you rebuild the whole site, or work with what we have?** Either. The audit says which. Often the fix is structural and editorial rather than visual: one page per entity, a table where a paragraph was, the price in text instead of a PDF, one founding date instead of two. If the current platform cannot serve crawlable HTML without JavaScript, we say so and quote the alternative. **What does it cost, and how long does it take?** From JPY 30,000, tax excluded, quoted in writing for an agreed scope before work starts. The audit that opens every engagement is free and comes back as a written document. A single landing page is typically weeks, not months; a full site depends on how many entities it has to describe, and the audit gives that number. **How do we know it worked?** We write the baseline down before the change: impressions, clicks, position and query count from Search Console; referrals from AI assistants in analytics; citations in Bing's AI Performance report where available; and the number of inquiries that mention what they read. Then we compare. Rankings alone are not the goal, and we say when a number has not moved.