Next.js, and what an answer engine can read of it

What to do

1. 1.Read your own homepage the way a crawler does

   Before changing anything. If this number is in the hundreds rather than the thousands, your copy is arriving after hydration and nothing else on this page matters until that is fixed.

   In a terminal

   curl -s https://yourdomain.com | wc -c

2. 2.Put the Organization JSON-LD in the root layout

   The Metadata API covers titles, descriptions and canonicals, and stops short of JSON-LD, so this one is a script tag written by hand. The root layout puts it on every page, which is where an Organization statement belongs.

   app/layout.tsx

   const org = {
     '@context': 'https://schema.org',
     '@type': 'Organization',
     name: 'Your company',
     url: 'https://yourdomain.com',
     sameAs: ['https://www.linkedin.com/company/yourcompany'],
   };
   
   // inside the layout's returned JSX
   <script
     type="application/ld+json"
     dangerouslySetInnerHTML={{ __html: JSON.stringify(org) }}
   />

3. 3.Serve llms.txt from a route handler if it should stay current

   public/llms.txt is fine and it is a file somebody has to remember to update. A route handler builds it from the same modules your pages render from, so a new page appears in it without anybody editing anything.

   app/llms.txt/route.ts

   export const dynamic = 'force-static';
   
   export function GET() {
     return new Response(buildLlmsTxt(), {
       headers: { 'content-type': 'text/plain; charset=utf-8' },
     });
   }

The readiness checks on Next.js

CueScout runs eight checks on whether an answer engine can read a site at all. These are the ones whose answer is different on Next.js — the rest are the same everywhere.

These describe Next.js’s own settings, which move without warning us. Last checked against the product on 2026-08-14.