I Built a Dynamic llms.txt for Next.js. Then Google Said Don't Bother.
The author created a dynamic llms.txt for a Next.js site, which is designed to provide AI assistants with a structured summary of the site's content. However, Google recently advised against creating such files, stating they are unnecessary. Despite this, the author plans to maintain the llms.txt due to its low maintenance cost and potential benefits for smaller AI engines.
- ▪The llms.txt spec was proposed in 2024 to help AI assistants summarize website content.
- ▪Google has publicly stated that it does not support the use of llms.txt files.
- ▪The author implemented a dynamic llms.txt in Next.js 16, which pulls content from a CMS.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/konstruction/i-built-a-dynamic-llmstxt-for-nextjs-then-google-said-dont-bother-4bjd |
| Publication time | Thu, 21 May 2026 02:32:17 +0000 |
| Retrieval time | 2026-05-21T02:35:03.339Z |
| Last seen | 2026-05-21T02:35:03.339Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | kg4Fim1sq6xo |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3943123) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } FADI MAMAR for Konstruction Group Inc. Posted on May 21 I Built a Dynamic llms.txt for Next.js. Then Google Said Don't Bother. #nextjs #ai #seo #webdev Two weeks ago I shipped a dynamic llms.txt and llms-full.txt for a Next.js 16 site I run. Hourly revalidation, pulls from the same content sources as the sitemap, auto-categorizes by URL pattern, returns proper text/plain. Took about 40 minutes to build. Last week Google published their AI Search optimization guide.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
