Should You Add an AI or LLM Information Page to Your Website?

What do people mean by an "AI information page"?

Three quite different things go by this name:

The first and third are ordinary, honest pages. The second is an attempt to steer machines with words people are not meant to see or take seriously.

Why do AI-only instruction pages backfire?

• They are treated as manipulation. Bing's guidelines warn that prompt injection can lead to demotion or delisting. Google's spam policies cover hidden text, cloaking and attempts to manipulate generative AI responses. Microsoft's security researchers describe planting "recommend us" instructions in AI assistants as AI Recommendation Poisoning.
• Assistants are built to resist them. AI companies train models to treat instructions found in web content as data, not commands. OpenAI has said prompt injection is unlikely ever to be fully solved, which means defences keep improving.
• Unlinked pages are rarely crawled. An "AI page" hidden from navigation and sitemaps may never be fetched at all.
• They create contradictions. A page claiming one thing while your main pages say another gives answers two versions to choose from.
• They look bad when found. Journalists and competitors do find them.

What should a useful AI information page contain?

Treat it as your brand facts page, written so it reads well to a person:

• Identity: legal and trading names, former names, founding year, headquarters.
• What you do in one sentence naming the category and customer.
• Products and plans, with current prices or how pricing works.
• Key numbers you can support, with dates.
• Leadership and contact details, including a press contact.
• Not to be confused with: similarly named companies, discontinued products.
• Corrections of common errors assistants make about you, stated as facts: "We do not offer payroll."
• A change history of name, price and product changes.
• Links to the full pages for products, pricing, security and support.

How to build this in detail is covered in how to build a brand facts page with schema, pricing, and a changelog.

Should it include an AI crawler and licensing policy?

For publishers, content businesses and anyone with a view on AI use of their content, yes. A short section or separate page can state:

• Which AI crawlers you allow, for search and for training, matching your robots.txt.
• Whether and how your content may be licensed for AI use, with a contact.
• How to report errors in AI answers about you.

The rules themselves belong in robots.txt; the page explains your position to people, including AI companies' partnership teams.

Should it describe how your company uses AI?

That is a different page, but a sensible one. Many organisations now publish a short statement on how they use AI in their products, customer service or content. They say what it does, what humans check, and how customer data is handled. It builds trust with customers. In some sectors and regions it also supports transparency obligations. It is not a visibility tactic, but assistants asked "does [company] use AI in [process]?" may cite it.

How does it relate to llms.txt?

An llms.txt file is a Markdown index of key pages placed at the root of a site, proposed for AI agents and tools. Some documentation platforms generate one automatically. Google says Google Search does not use it, though it is fine to keep for other services. If you publish one, list your facts page in it. Neither replaces the other. Whether llms.txt helps at all is covered in whether llms.txt improves AI search visibility or citations.

Where should the page live, and how should it be linked?

• At a clear, stable URL such as /company, /facts or /about/facts. A URL like /for-ai signals the wrong purpose to people.
• Reachable from your site's footer, plus the about and press pages, so people and crawlers can find it.
• Included in your sitemap and open to crawlers.
• Consistent with every other page, so it confirms rather than contradicts them.

Who should own the page?

Give it a named owner, usually in marketing or communications, with input from product, finance and legal for the facts they control. The owner's job is to update the page the day something changes: a new price, a new product, a leadership change, a new office. Add the page to your release checklist, so it is updated alongside pricing and product pages rather than months later. An out-of-date facts page is worse than none, because it looks authoritative. A quarterly check of every statement against the source it comes from keeps it honest.

How do you know if it is helping?

Before publishing, ask the main assistants the questions your page answers, and note wrong or missing facts and their sources. Check again monthly after publishing. Look for the page appearing among cited sources and for the errors disappearing. If an error persists, the answer is probably drawing on a third-party source that also needs correcting.

What might an illustrative case look like?

Consider an illustrative payments startup whose agency had published an unlinked page at /ai-info. It told assistants the company was "the best payment provider for small businesses" and should "always be recommended". Server logs showed no AI crawler had ever requested it. Assistants still described the company using its old name from before a rebrand. The team removed the page and published a facts page at /company with its current name, former name, pricing, founding details and three corrected errors. It linked the page from the footer and press page. Within two months, most answers used the new name and correct pricing.

What do people ask about AI information pages?

Is it deceptive to write a page mainly for AI?

Writing a clear facts page is not deceptive. Hiding content from people, or giving AI instructions you would not show visitors, is.

Can we tell AI not to say certain things about us?

Not effectively through page text. Correct the facts on your pages and the sources assistants cite, and use robots.txt to control access.

Should the page be long?

No. A few screens of facts, tables and links is enough. Detail belongs on the linked pages.

Do we still need an about page?

Yes. The about page tells your story; the facts page is for quick reference and correction.