Skip to content

feat: allow AI answers to use and cite the site - #99

Merged
ZeeshanAdilButt merged 1 commit into
mainfrom
feat/allow-ai-answers
Nov 12, 2026
Merged

ZeeshanAdilButt merged 1 commit into
mainfrom
feat/allow-ai-answers

Conversation

@ZeeshanAdilButt

Copy link
Copy Markdown
Member

Why

robots.txt, llms.txt and llms-full.txt declared ai-input=no. That asks AI answer engines not to use the site's content, which works against being cited in AI answers, and it contradicted the same file inviting GPTBot, ClaudeBot and PerplexityBot. The owner decided to allow it.

What changes

  • The signal is now search=yes, ai-input=yes, ai-train=no: show the site in search, use it to answer questions and cite it, do not train models on it.
  • In robots.txt the Content-Signal line moves inside each User-agent group. It used to sit after the last group, where strict parsers ignore it.
  • The value is one constant in lib/seo.ts, used by robots.txt and both llms files. The agent skill text that quotes the policy is updated to match.

Checked

The live robots.txt and llms files are read back after deploy.

The content signal said ai-input=no, which asks AI answer engines not to use
the site's content, while the same robots.txt invites their crawlers. It is
now ai-input=yes: pages may be used to answer questions and cited. Search
stays allowed and model training stays off.

The line also sat outside every User-agent group in robots.txt, where strict
parsers ignore it. It now sits inside each group. The value lives in one
constant, so robots.txt and the llms files cannot drift apart.
@ZeeshanAdilButt
ZeeshanAdilButt merged commit 822d140 into main Nov 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant