# Technical SEO for search and AI answer engines. > Technical SEO for search engines and AI answer engines: prerendering, structured data, entity clarity, crawl paths, Core Web Vitals and llms.txt. Page: https://adjltechnology.com/services/seo/ Updated: 2026-11-12 SEO & AI Search Search has two readers now. Search engines rank pages. Answer engines read them and decide what to quote. Both start from the same HTML, and most sites hand them a mess. We fix that layer, then measure what changed. [See what a crawler reads](https://adjltechnology.com/services/seo/#machine) [Talk to Daniel](https://adjltechnology.com/services/seo/#contact) - **Inputs:** Your site, its templates and its build - **Fixes:** Rendering, structured data, entities, crawl paths, speed - **Measures:** What a crawler is served, and how fast real visitors get it - **Hands over:** The changes, the checks and the reasons, in your repository People read the top layer, crawlers follow the middle one and machines parse the bottom one. Two readers ## One ranks. One quotes. A search engine crawls your pages, ranks them and shows a link. An answer engine reads them, lifts out claims and may or may not credit you. Many AI crawlers never run your JavaScript, and the ones that do run it later. Both trust pages that say the same thing in the markup and in the copy. 1. Both readers start from the same HTML document. 2. A search engine crawls it, ranks it and shows a link. 3. An answer engine reads it, lifts out claims and decides what to quote. 4. Both trust a page more when its markup and its copy say the same thing. What we fix ## The layer both of them read. ### Prerendering Every page arrives as complete HTML. A reader with JavaScript off, a crawler in a hurry and a screen reader all get the same words. ### Structured data JSON-LD that describes real entities and matches the visible copy. Your company, its people, its services and the pages about them, joined by stable IDs. ### Entity clarity One name for each thing you sell, used the same way on every page. Answer engines stitch claims together across pages, and two names for one service reads as two services. ### Crawl paths Every page reachable in a few clicks from the home page, with link text that says where it goes. No orphan pages, no redirect chains and one canonical URL per page. ### Core Web Vitals Fast first paint, no layout shift and quick response to input. We set a budget, and the build fails when a page goes over it. ### Machine-readable surfaces A sitemap with real dates, a robots file that says what you mean, and llms.txt, a proposed plain-text summary some AI tools read. We’re clear that it’s a proposal and not a standard. Measured, not described ## Here’s what a crawler gets from this page. This page practices what it describes. When scripts run, the panel fetches it again and reads the raw HTML with no script run. Compare the readers. Then open the whole page in Machine view. Honest limits ## What we won’t promise. Nobody outside a search engine controls rankings, and nobody controls what an AI answer says. Anyone who guarantees either one is guessing. We promise the work we control. Pages that are fast, complete without JavaScript, consistent and easy to quote. Then we report what changed, with the measurements. Proof ## The proof is the page you’re on. This site was built as the case study. Every claim on this page can be checked against the page itself, and the build notes are public. - [How this site is built for search](https://adjltechnology.com/work/this-site/) - [The home page’s live readout](https://adjltechnology.com/#machine) Fair questions ## Questions about SEO and AI search. ### What’s llms.txt, and does it matter? It’s a proposed convention, a plain-text file at the root of a site that summarizes it for language models. Some AI tools read it and many don’t. It’s cheap to generate from pages you already have, so we do, and we don’t oversell it. This site’s own file is rebuilt from its pages on every deploy. ### Do you do traditional SEO too? Yes. Technical SEO is most of the work either way. Titles, descriptions, headings, internal links, speed and structured data help ranked results and quoted answers alike. We don’t write bulk content to chase keywords. ### Will you rebuild our site? Only if that’s the cheapest fix. Most technical SEO work happens inside the site you already have, in its templates and its build. When a rebuild is the honest answer, we’ll say so and price it separately. ### How do you measure results? With tools anyone can run. What a crawler is served, how fast real pages load, which pages get indexed and what the search consoles report. We report what changed and leave out what we can’t attribute. Start here ## Tell us what’s slow, or what can’t be found. One paragraph is plenty. Tell us what you want built, the step that costs the most, or the page that should rank and doesn’t. If you know why the obvious fix hasn’t worked, say that too. [Start a project](https://adjltechnology.com/start/) [daniel@adjlcapital.com](mailto:daniel@adjlcapital.com) [Email Daniel](mailto:daniel@adjlcapital.com) Daniel reads and answers these himself, usually within a day or two. No sequence, no drip, and nothing sold to anyone. [ADJL Technology](https://adjltechnology.com/) Today’s investment, tomorrow’s legacy. ADJL Technology builds AI systems, websites and apps, and the technical SEO that gets them found. Founded and led by Daniel Laskowski. [daniel@adjlcapital.com](mailto:daniel@adjlcapital.com) Built 2026-11-12 from commit 6afca01. No cookies, no trackers, no third-party scripts. ADJL Technology. Nothing on this site is an offer to sell or a solicitation of any security, and nothing here is investment advice. Descriptions of internal systems are general by design and omit parameters and thresholds.