Set up your website for agents¶
Let AI assistants visiting your website find and question your official Rose agent. Your answers come from the same knowledge and guidelines you maintain for your website visitors.
Before you start¶
Ask your Rose account manager to enable Ask Rose for your website domain. You will need access to your website's code or its site-wide custom code settings.
Rose will confirm your agent's address:
Use your coding assistant¶
Open your website's repository in your coding assistant and ask it:
Follow https://userose.ai/rose-for-agents/ask-rose-website/SKILL.md to make this website compatible with Ask Rose.
The website skill guides your assistant through the setup and includes a verification script. It checks that Ask Rose is enabled for your domain before making changes.
What changes on your website¶
| Change | Why |
|---|---|
An "Ask" section in /llms.txt with your agent's address |
Assistants that read llms.txt find your official agent |
| A visible footer line on every page naming your agent's address | Most assistants never open llms.txt on their own: they read each page through a summary that drops a link to llms.txt, but keeps your agent's address when the line says what it answers |
/agents/webagents.md, and in the <head> two discovery tags and a window.askSalesAgent() script |
AI browsers call your agent directly from the page |
https://ask.userose.ai in your Content Security Policy, if you have one |
Lets the page script reach your agent |
/agents/index.md (optional) |
Lists your resources for AI agents, so llms.txt stays unchanged if Rose later serves more of them under /agents/. That will need a proxy rule on your site anyway, so you can skip it and add its llms.txt line then |
You can start with the first two: llms.txt and the footer line.
Add webagents.md and the <head> changes later, together: the file describes the script.
The footer line must stay visible. Do not hide it with CSS or the hidden attribute:
assistants that read the page as text may drop hidden elements, and search engines treat
hidden links as spam. A link to llms.txt in one of your footer's link lists is fine too,
but it does not replace the line: in our tests, Claude Code never reached the agent through it.
Install the skill in Claude Code¶
To keep the setup instructions available in this website's repository, download the skill and its verification script:
mkdir -p .claude/skills/ask-rose-website/scripts
curl --fail --location https://userose.ai/rose-for-agents/ask-rose-website/SKILL.md --output .claude/skills/ask-rose-website/SKILL.md
curl --fail --location https://userose.ai/rose-for-agents/ask-rose-website/scripts/verify-ask-rose-setup.sh --output .claude/skills/ask-rose-website/scripts/verify-ask-rose-setup.sh
Then ask Claude Code to make your website compatible with Ask Rose. Review the proposed website changes before publishing them.
Use a website builder¶
On Webflow, Wix, HubSpot CMS or another builder, ask your coding assistant for the
snippets and where to paste them in the site-wide head and footer code. Your builder must
also serve /llms.txt at your website's root and /agents/webagents.md. If your
builder cannot do this, contact Rose to review your setup.
Verify your setup¶
Read the downloaded verification script, then run it against your local or preview website. Replace the example address and domain with yours:
bash .claude/skills/ask-rose-website/scripts/verify-ask-rose-setup.sh https://www.example.com example.com
The checks should pass and identify the correct company. If you started with the first
two changes only, the <head>, webagents.md and askSalesAgent lines fail until you add them.
After publishing, run the check against your live website too. Contact Rose if the agent is not enabled for your
domain or answers as another company.
If your website uses a Content Security Policy, your developer must allow
https://ask.userose.ai in connect-src. See Content Security Policy
for the rest of your Rose installation.
Return to the Rose for Agents overview.