{"id":2176,"date":"2026-05-19T06:13:17","date_gmt":"2026-05-19T05:13:17","guid":{"rendered":"https:\/\/daveashworth.co\/blog\/?p=2176"},"modified":"2026-10-05T12:15:32","modified_gmt":"2026-10-05T11:15:32","slug":"a-rough-guide-to-llms-txt","status":"publish","type":"post","link":"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/","title":{"rendered":"A Rough Guide To: LLMS.txt &#8211; What It Is &amp; How To Create One"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>TL;DR:<\/strong> <br><code>llms.txt<\/code> is a proposed Markdown file that gives LLMs a simplified overview of the important content on a website. It isn&#8217;t required by Google, isn&#8217;t a ranking factor, and there&#8217;s no guarantee AI platforms will use it. But it&#8217;s easy to create, and can provide a clear, machine-readable summary of your key pages and topics. In this guide I&#8217;ll show you what goes into one, examples of different structures, and how I&#8217;ve built mine.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you want to create one for your own site, you can use my <strong><a href=\"https:\/\/daveashworth.co\/tools\/llms-txt-file-generator\/\">free llms.txt file generator<\/a><\/strong><\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_90 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#What_Is_LLMStxt\" >What Is LLMS.txt?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#Does_Google_Use_LLMStxt\" >Does Google Use LLMS.txt?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#Is_LLMStxt_Useful\" >Is LLMS.txt Useful?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#How_To_Create_an_LLMStxt_File\" >How To Create an LLMS.txt File<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#1_Add_the_Website_Name_and_Description\" >1. Add the Website Name and Description<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#2_Group_Important_Pages_by_Topic\" >2. Group Important Pages by Topic<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#3_Include_Important_Supporting_Content\" >3. Include Important Supporting Content<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#4_Upload_It_to_the_Root_of_Your_Website\" >4. Upload It to the Root of Your Website<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#LLMStxt_Example\" >LLMS.txt Example<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#LLMStxt_Best_Practices\" >LLMS.txt Best Practices<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#Keep_the_Structure_Simple\" >Keep the Structure Simple<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#Prioritise_Important_Pages\" >Prioritise Important Pages<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#Add_Useful_Descriptions\" >Add Useful Descriptions<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#Organise_Supporting_Content_by_Topic\" >Organise Supporting Content by Topic<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#Dont_Keyword-Stuff_It\" >Don&#8217;t Keyword-Stuff It<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#Keep_It_Updated\" >Keep It Updated<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#Dont_Expect_It_to_Fix_the_Website\" >Don&#8217;t Expect It to Fix the Website<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#My_Approach_to_LLMStxt\" >My Approach to LLMS.txt<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-19\" href=\"https:\/\/daveashworth.co\/blog\/a-rough-guide-to-llms-txt\/#Should_You_Create_an_LLMStxt_File\" >Should You Create an LLMS.txt File?<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_Is_LLMStxt\"><\/span>What Is LLMS.txt?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><code>llms.txt<\/code> is a proposed Markdown file designed to give Large Language Models a simplified, structured overview of the important content on a website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An <code>llms.txt<\/code> file is commonly placed at the root of a site:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>https:\/\/example.com\/llms.txt<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The current proposal also allows <code>llms.txt<\/code> files within subpaths, such as <code>\/docs\/llms.txt<\/code>, where the file describes content beneath that path.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, mine is:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code><a href=\"https:\/\/daveashworth.co\/llms.txt\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/daveashworth.co\/llms.txt<\/a><\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rather than trying to describe every URL on a website, the file can highlight things such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>what the website is about<br><\/li>\n\n\n\n<li>important pages<br><\/li>\n\n\n\n<li>key topic areas<br><\/li>\n\n\n\n<li>supporting resources<br><\/li>\n\n\n\n<li>relationships between sections of the site<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The idea is to provide LLMs with a <strong>cleaner, more concise representation of the website and its important content<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It&#8217;s useful to think of <code>llms.txt<\/code> as a reference document rather than an instruction file. It doesn&#8217;t tell an AI crawler what it can or can&#8217;t access in the way <code>robots.txt<\/code> does, and it isn&#8217;t a replacement for an XML sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Most importantly, <strong>having an <code>llms.txt<\/code> file doesn&#8217;t mean an AI platform will read or use it<\/strong>. That&#8217;s dependent on individual platforms and how they retrieve information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Does_Google_Use_LLMStxt\"><\/span>Does Google Use LLMS.txt?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Google has been fairly clear about its position on <code>llms.txt<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In its <a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/ai-features\" target=\"_blank\" rel=\"noopener\">guidance on AI features and your website<\/a>, Google says you don&#8217;t need to create new AI-specific files or markup to appear in its AI search features.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google specifically includes <code>llms.txt<\/code> in its guidance:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">\u201cLLMS.txt files and other \u2018special\u2019 markup: You don\u2019t need to create new machine readable files&#8230;\u201d<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">So, at the moment, you <strong>don&#8217;t need an <code>llms.txt<\/code> file for Google Search or Google&#8217;s AI features<\/strong>. Google has explicitly stated that having one won&#8217;t positively or negatively affect your visibility or rankings.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That&#8217;s an important distinction because <code>llms.txt<\/code> is sometimes discussed as though it&#8217;s the AI equivalent of <code>robots.txt<\/code> or an XML sitemap. It isn&#8217;t.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An XML sitemap is an established mechanism supported by search engines. <code>llms.txt<\/code> is a proposed format whose usefulness depends on whether individual AI systems actually choose to use it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That doesn&#8217;t necessarily make <code>llms.txt<\/code> pointless. Google is only one part of the wider AI ecosystem, and the file can still serve as a concise, structured summary of your website.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Is_LLMStxt_Useful\"><\/span>Is LLMS.txt Useful?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Potentially, yes, but I think expectations need to stay realistic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There is currently no guarantee that an AI platform will discover, read or make use of your <code>llms.txt<\/code> file. Creating one doesn&#8217;t mean you&#8217;ll suddenly gain citations in ChatGPT, appear more often in AI-generated answers or improve your search rankings.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For me, its usefulness is much simpler.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A well-structured <code>llms.txt<\/code> file can provide a concise summary of:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>what your website is about<br><\/li>\n\n\n\n<li>your main topic areas<br><\/li>\n\n\n\n<li>your most important pages<br><\/li>\n\n\n\n<li>useful supporting content<br><\/li>\n\n\n\n<li>how those areas relate to one another<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">That potentially gives systems capable of using the file a cleaner representation of your website than having to infer everything from navigation, internal links and individual pages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There&#8217;s also a useful side effect: <strong>creating the file forces you to think about your own website structure<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If it&#8217;s difficult to decide which pages belong under a particular topic, which pages are important, or how your content relates together, that can expose weaknesses in the site&#8217;s organisation itself.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That&#8217;s one reason my own <code>llms.txt<\/code> developed alongside the work I&#8217;ve been doing on <a href=\"https:\/\/daveashworth.co\/blog\/how-to-build-seo-content-hubs\/\">SEO content hubs<\/a>. The two serve different purposes, but both require you to think clearly about topics, supporting content and relationships between pages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So I wouldn&#8217;t create <code>llms.txt<\/code> because I expect an immediate SEO or AI visibility benefit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I&#8217;d create one because it&#8217;s <strong>easy to implement, provides a clean summary of the website, and may be useful to systems that choose to support it<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_To_Create_an_LLMStxt_File\"><\/span>How To Create an LLMS.txt File<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">You don\u2019t need any special software or plugin to create an llms.txt file. At its simplest, it\u2019s a Markdown-formatted text file placed at the root of your website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can create one manually using the structure below, or use my <a href=\"https:\/\/daveashworth.co\/tools\/llms-txt-file-generator\/\">free llms.txt file generator<\/a> to find your sitemap URLs, choose the pages you want to include and generate the file for you.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The proposed format is deliberately straightforward.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"1_Add_the_Website_Name_and_Description\"><\/span>1. Add the Website Name and Description<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Start with an H1 containing the website or project name, followed by a short description explaining what the site is about.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Example Website\n\n&gt; SEO consultancy specialising in ecommerce, technical SEO and analytics.<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"2_Group_Important_Pages_by_Topic\"><\/span>2. Group Important Pages by Topic<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use H2 headings to organise the main areas of the website, then list the most useful URLs beneath them.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>## Core Pages\n\n- &#91;Services](https:\/\/example.com\/services\/): Overview of consultancy services.\n- &#91;About](https:\/\/example.com\/about\/): Background and experience.\n\n## Ecommerce SEO\n\n- &#91;Ecommerce SEO](https:\/\/example.com\/ecommerce-seo\/): Ecommerce SEO consultancy and expertise.\n- &#91;Magento SEO](https:\/\/example.com\/magento-seo\/): Magento-specific SEO services and guidance.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The descriptions are useful because they provide additional context about <strong>what each page contains and why it&#8217;s relevant<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"3_Include_Important_Supporting_Content\"><\/span>3. Include Important Supporting Content<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can also include useful guides, case studies and supporting articles beneath the relevant topic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>## Supporting Guides\n\n- &#91;Canonicalisation Guide](https:\/\/example.com\/canonicalisation\/): How canonical URLs work and common implementation problems.\n- &#91;Crawlability Guide](https:\/\/example.com\/crawlability\/): Identifying and fixing website crawling issues.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You don&#8217;t necessarily need to include every URL on the website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I&#8217;d prioritise the pages that best explain your <strong>main topics, expertise and useful supporting content<\/strong>, rather than trying to turn <code>llms.txt<\/code> into another complete sitemap.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"4_Upload_It_to_the_Root_of_Your_Website\"><\/span>4. Upload It to the Root of Your Website<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Save the file as:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>llms.txt<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">and make it available at:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>https:\/\/example.com\/llms.txt<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It should be publicly accessible without requiring authentication.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That&#8217;s really all that&#8217;s required to create a basic version.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can keep it relatively small or build a much more detailed file containing multiple topic areas and supporting resources. The right level of detail depends largely on the size and complexity of the website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"LLMStxt_Example\"><\/span>LLMS.txt Example<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A basic <code>llms.txt<\/code> file doesn&#8217;t need to be complicated. For a small website, you could simply describe the site and organise the most important pages into a few logical sections.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Example Website\n\n&gt; SEO, analytics and ecommerce consultancy. Use the links below to understand the main services, areas of expertise and supporting resources.\n\n## Core Pages\n\n- &#91;Services](https:\/\/example.com\/services\/): Overview of the consultancy services available.\n- &#91;About](https:\/\/example.com\/about\/): Background, experience and expertise.\n- &#91;Blog](https:\/\/example.com\/blog\/): Guides, case studies and technical resources.\n\n## SEO\n\n- &#91;SEO Consultancy](https:\/\/example.com\/seo\/): SEO services and areas of expertise.\n- &#91;Technical SEO](https:\/\/example.com\/technical-seo\/): Technical SEO consultancy and guidance.\n\n## Analytics\n\n- &#91;Analytics](https:\/\/example.com\/analytics\/): Analytics, measurement and tracking services.\n- &#91;Google Analytics 4](https:\/\/example.com\/ga4\/): GA4 implementation and optimisation.\n\n## Supporting Guides\n\n- &#91;SEO Guide](https:\/\/example.com\/seo-guide\/): Practical guidance covering common SEO problems.\n- &#91;GA4 Guide](https:\/\/example.com\/ga4-guide\/): Guidance on GA4 configuration and tracking.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The important thing isn&#8217;t to copy this structure exactly. Your <code>llms.txt<\/code> should reflect <strong>how your own website and its topics are organised<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A small site might only need a handful of sections and URLs. A larger site could group pages into services, products, topic areas, documentation and supporting resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I&#8217;d avoid trying to list every page simply because it exists. An XML sitemap already serves that purpose. <code>llms.txt<\/code> is more useful as a <strong>curated overview of the content you consider important<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"LLMStxt_Best_Practices\"><\/span>LLMS.txt Best Practices<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Because <code>llms.txt<\/code> is still a relatively new proposal, I wouldn&#8217;t over-engineer it. The aim should be to create a file that&#8217;s <strong>clear, useful and easy to maintain<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A few principles I follow:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Keep_the_Structure_Simple\"><\/span>Keep the Structure Simple<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use descriptive headings to group related pages rather than creating a complicated hierarchy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Someone looking at the file should be able to understand the main areas of the website without having to decipher how you&#8217;ve organised it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Prioritise_Important_Pages\"><\/span>Prioritise Important Pages<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You don&#8217;t need to include every URL on the website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Focus on pages that help explain:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>your main topics<br><\/li>\n\n\n\n<li>products or services<br><\/li>\n\n\n\n<li>areas of expertise<br><\/li>\n\n\n\n<li>useful supporting content<br><\/li>\n\n\n\n<li>important documentation or resources<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Think <strong>curated overview rather than alternative XML sitemap<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Add_Useful_Descriptions\"><\/span>Add Useful Descriptions<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Don&#8217;t just provide a list of URLs. A short description can give additional context about what each page covers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>- &#91;Magento SEO](https:\/\/example.com\/magento-seo\/): Magento SEO consultancy covering crawlability, indexing, product optimisation and technical SEO.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">That&#8217;s more informative than simply listing the page title and URL.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Organise_Supporting_Content_by_Topic\"><\/span>Organise Supporting Content by Topic<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If you have lots of articles or resources, group them beneath the topics they actually support.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly relevant if you&#8217;ve already organised your website around content hubs. Your <code>llms.txt<\/code> can reflect those same relationships rather than presenting one enormous list of blog posts.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Dont_Keyword-Stuff_It\"><\/span>Don&#8217;t Keyword-Stuff It<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">I wouldn&#8217;t treat <code>llms.txt<\/code> as another place to repeat target keywords.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Write descriptions that accurately explain what pages contain. If the relevant terminology occurs naturally, that&#8217;s enough.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Keep_It_Updated\"><\/span>Keep It Updated<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If you add an important service, remove a page, change a URL or substantially reorganise a topic area, update the file.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A concise file that accurately reflects the current website is more useful than an elaborate one that gradually becomes outdated.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Dont_Expect_It_to_Fix_the_Website\"><\/span>Don&#8217;t Expect It to Fix the Website<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Most importantly, <code>llms.txt<\/code> shouldn&#8217;t compensate for poor site structure, weak internal linking or unclear content.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It should <strong>reflect a well-organised website, not attempt to manufacture one inside a text file<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"My_Approach_to_LLMStxt\"><\/span>My Approach to LLMS.txt<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">My own <code>llms.txt<\/code> is more detailed than the basic example above because it reflects the broader structure I&#8217;ve been building across the website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rather than simply listing a selection of URLs, I&#8217;ve organised it around areas such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>core services<br><\/li>\n\n\n\n<li>individual skills<br><\/li>\n\n\n\n<li>technical expertise<br><\/li>\n\n\n\n<li>supporting blog content<br><\/li>\n\n\n\n<li>related topic areas<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This developed naturally alongside the work I&#8217;ve been doing on <a href=\"https:\/\/daveashworth.co\/blog\/how-to-build-seo-content-hubs\/\">SEO content hubs<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, if I have a broader Ecommerce SEO topic, I can reference the main Ecommerce SEO page alongside more specific Magento expertise and supporting articles covering related technical problems.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same principle applies to Local SEO, website performance, analytics and other areas of the site.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The result is effectively a <strong>curated map of the topics and expertise across my website<\/strong>, rather than a flat list of URLs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can see the complete file here:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/daveashworth.co\/llms.txt\">View my llms.txt file<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I&#8217;m not doing this because I expect the file itself to improve rankings or guarantee that my content appears in AI-generated answers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I&#8217;ve created it because the structure already exists across the website, and representing those relationships in a lightweight, machine-readable file is relatively straightforward.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If AI systems make greater use of <code>llms.txt<\/code> in future, the file is there. If they don&#8217;t, I haven&#8217;t built my wider SEO or content strategy around something they may never support.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Should_You_Create_an_LLMStxt_File\"><\/span>Should You Create an LLMS.txt File?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">I think so, provided you keep your expectations realistic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An <code>llms.txt<\/code> file is relatively easy to create and maintain, and it gives you another way to provide a clear, structured overview of your website and its most important content.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What I <strong>wouldn&#8217;t<\/strong> expect it to do is:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>improve rankings simply because it exists<br><\/li>\n\n\n\n<li>guarantee visibility in AI-generated answers<br><\/li>\n\n\n\n<li>generate citations from ChatGPT or other LLMs<br><\/li>\n\n\n\n<li>compensate for weak content or poor site structure<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Google has already made it clear that <code>llms.txt<\/code> isn&#8217;t required for its AI search features, and support from other platforms remains uncertain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So I see it as a <strong>low-effort supporting layer<\/strong>, not something to build an AI or SEO strategy around.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your website already has strong content, clear topic relationships and sensible internal linking, creating an <code>llms.txt<\/code> file is straightforward enough that I think it&#8217;s worth doing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If broader support develops in future, you&#8217;re already prepared. If it doesn&#8217;t, you&#8217;ve spent relatively little time creating a useful, structured summary of your website.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A practical guide to LLMS.txt &#8211; what it is, what it isn\u2019t, and whether it actually matters for AI search. This article explores how LLMS.txt can help provide structure and context for AI systems like ChatGPT and Claude, why Google says it isn\u2019t required, and how it fits into broader content hub and website optimisation strategies.<\/p>\n","protected":false},"author":1,"featured_media":2177,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13,4],"tags":[],"class_list":["post-2176","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-on-page-seo","category-crawl-rate"],"_links":{"self":[{"href":"https:\/\/daveashworth.co\/blog\/wp-json\/wp\/v2\/posts\/2176","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/daveashworth.co\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/daveashworth.co\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/daveashworth.co\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/daveashworth.co\/blog\/wp-json\/wp\/v2\/comments?post=2176"}],"version-history":[{"count":0,"href":"https:\/\/daveashworth.co\/blog\/wp-json\/wp\/v2\/posts\/2176\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/daveashworth.co\/blog\/wp-json\/wp\/v2\/media\/2177"}],"wp:attachment":[{"href":"https:\/\/daveashworth.co\/blog\/wp-json\/wp\/v2\/media?parent=2176"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/daveashworth.co\/blog\/wp-json\/wp\/v2\/categories?post=2176"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/daveashworth.co\/blog\/wp-json\/wp\/v2\/tags?post=2176"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}