AI visibility for Next.js
SaaS products, marketing sites owned by engineering teams, and everything we build ourselves. Get named when someone asks ChatGPT, Perplexity, Claude or Gemini about your business. On Next.js specifically, this is what changes.
FindingImpact
GPTBot blocked by firewall403 from bot protection on every pageHigh
llms.txt missingNothing tells an AI crawler what the site is forHigh
Entity records unlinkedNo sameAs on Organization schemaMedium
31 pages without dateModifiedModels discount content they cannot dateMedium
- 200
- signals scored
- 4
- crawlers tested
- 6
- assistants tracked
What Next.js gets right, and what it does not
- The Metadata API covers titles and Open Graph but not JSON-LD; schema needs a script tag in the layout or page.
- Vercel's bot protection is off by default; if Attack Challenge Mode is on, AI crawlers get a challenge page.
- generateStaticParams makes programmatic pages cheap, which is why thin templated pages are the common failure.
AI visibility on Next.js
- llms.txt. Place llms.txt in /public. It deploys with the site and is served as text/plain.
- Schema. Render an @graph in app/layout.tsx for Organization and WebSite, and page-level blocks in each page component.
- Crawlers. Export a robots() function from app/robots.ts with explicit allow rules per AI user agent.
What we would ship first
- Technical crawlFetched as GPTBot, PerplexityBot and ClaudeBot, not as a browser, so we see what they see.
- Entity recordsOrganization schema with sameAs to Wikidata, Crunchbase and your profiles, so assistants know which company you are.
- Answer-shaped contentPages that answer the question in the first paragraph and carry an author and a date.
- Schema and llms.txtValidated JSON-LD and an llms.txt that tells crawlers what the site is for.
How the engagement runs
- Audit. Crawl Audit scores 200 signals. Findings are ranked by impact, each with the code to paste.
- Fix. Crawler access, schema and entity work first. Most sites clear the high-impact findings in two weeks.
- Write. Answer pages for the questions you should own, with an author and a date.
- Track. Weekly share-of-answer report across six assistants.
100
Lighthouse performance on this site. Same for SEO, accessibility and best practices
5
products of our own in production
3
practices, each with a named lead
1 day
reply time on every enquiry
4.9
from 9 reviews
Questions people ask
- Do you work inside our existing Next.js setup?
- Yes. The scoping sprint starts with what is there. We extend Next.js where that is honest and propose a move only when the platform is the constraint.
- Can you fix AI crawler access on Next.js?
- Export a robots() function from app/robots.ts with explicit allow rules per AI user agent.
- Is the audit manual?
- No. Crawl Audit is a tool. You enter a domain and it runs. Nobody reviews it by hand.
- Do I need the service if I run the audit?
- Not necessarily. Many teams fix the findings themselves with the free generators. The service is for teams who would rather we did it.