
How Publishers Can Improve AI Visibility: 12 Tips Ranked by Confidence and Effort

My team recently debated whether we should create an AI info page after someone read an enthusiastic LinkedIn post about it. Opinions were plentiful. Data was not.
One side saw a free fact sheet for the robots. The other side saw one more page to keep current, written for readers who never click. Both sides were very sure. And I ended up writing an article about it!
So I looked at 14 real AI info pages, weighed what each side gets right, and built a test you can run on your own brand.
By the end, you’ll know whether to build one and how to find out if it worked.
An AI info page (also called an LLM info page or AI instructions page) is a public, indexable page on your own domain that lists verified facts about your company, such as what you sell, who you serve, current product names, and what you do not offer. It is written so AI assistants can retrieve those facts and describe your company accurately.
The idea is simple: give ChatGPT, Gemini, and Claude one current source for your facts, in the hope that they get fewer of them wrong.
In its guide to optimizing for generative AI features on Google Search, Google says that rewriting content just for AI systems is unnecessary for its Search features.
An AI info page is a standard web page that presents facts and avoids persuasion.
You may already have an About page, an llms.txt file, or schema markup, so it’s fair to ask whether those cover the same ground. Here is how they differ:
| AI info page | About page | llms.txt | Schema markup | |
|---|---|---|---|---|
| What it is | Indexable HTML page of verified facts | Page that builds trust with people | Markdown file at the site root that lists key pages | Code that labels facts on existing pages |
| Main reader | AI systems and people | People | AI tools and developers | Search engines |
| Contains the facts | Yes | Yes, mixed with storytelling | No, it points to pages | Only the facts already on the page |
| Tone | Neutral and factual | Brand voice | Index | Not applicable |
| Google Search treatment | Indexed like any other page | Indexed like any other page | Not used, per Google | Used for rich results; no special AI markup exists |
Our llms.txt guide covers the file format in depth. For this decision, one point matters: llms.txt lists where your information lives, and an AI info page holds the information itself.
You can have all four. The About page speaks to people, llms.txt points to pages, and schema labels facts that already sit on a page. An AI info page is the one that states those facts in plain, visible text.
I looked at 14 company AI info pages and checked what they have in common, what some do that others don’t, and what stands out. Most share a fact table, a product list, an FAQ, and guidance for AI assistants. They differ on dates, pricing, and negative statements: only nine show a last-updated date, and while twelve say who the company is for, only six say who it is not for.
I checked each page for the same ten fields. The gaps show where pages drift or overreach.
| Field | Pages with it (of 14) |
|---|---|
| Who the company is for | 12 |
| Explicit instructions for AI assistants | 10 |
| Competitive advantages | 10 |
| Trust signals, such as awards, reviews, or named customer results | 9 |
| Visible last-updated date | 9 |
| Key metrics about the company | 8 |
| Pricing information | 7 |
| Section on who the company is not for | 6 |
| Reference to an llms.txt file | 5 |
| Original research by the company | 4 |
Length varies a lot too. Some pages run a few hundred words. A few run several thousand and read like product documentation.
Five things stood out in my opinion. Here is each one, with a company that does it well.
Wynter‘s page says people still call it only a message testing tool, explains that this description is out of date, and names categories of tools it’s not the right answer for.

Pawns.app‘s page says internet bandwidth sharing was discontinued and is no longer linked to the product.

Infigo‘s page separates the company from an unrelated one with a similar name, labels its growth figures as self-reported, and keeps a changelog. It also explains how the page relates to llms.txt.

IMG.LY‘s page attaches a source and method to its statistics. It also tells assistants when the company is not the right recommendation.

Workspace‘s page says the content is available as Markdown on request and as JSON.

Personally, I would avoid commands to AI. One platform’s page closes with a line telling AI models to add a chart emoji to their responses.

I can’t see what a line like that adds for readers. It also looks like the manipulation tactics security teams are now tracking, which I cover below.
This is the side that saw a free fact sheet for the robots.
The strongest case for an AI info page is accuracy and control. It gives AI assistants one current, citable source for your facts, and it costs little to build.
Most AI search products use retrieval-augmented generation, which pulls relevant, current pages from an index to ground their answers. A page that search engines can’t access or index can’t be retrieved.
An indexed fact page is therefore a retrieval candidate. Whether it gets chosen over your homepage, your docs, or a third-party review is the open question.
This is the side that saw one more page to keep current.
The two strongest cases against an AI info page are the lack of a formal standard and the upkeep. A stale page feeds AI systems conflicting facts.
One more risk sits outside that list: instructions aimed at AI can read as manipulation. Microsoft’s Defender team reviewed 60 days of AI-related links and found more than 50 prompts from 31 companies across 14 industries trying to plant recommendations in AI assistants’ memory. That tactic came through “Summarize with AI” buttons, not AI info pages, but the idea is the same: text written to tell an AI what to do. It’s why I’d rather describe my company and let the assistant decide what to repeat.
Create an AI info page if AI assistants get your facts wrong, your name is easy to confuse, your footprint is thin or recently changed, and someone owns the upkeep. If none of those apply, spend the hours on the pages and sources AI systems already cite.
Score one point for each yes.
| # | Question | Yes means |
|---|---|---|
| 1 | Do AI answers about your company contain factual errors today? | You have a problem a fact page could address |
| 2 | Is your name or product easy to confuse with another? | Disambiguation has real value |
| 3 | Did you rename products, change pricing, or reposition in the past 12 months? | Old facts are still circulating |
| 4 | Is your online footprint thin, such as few reviews, few third-party mentions, or a new domain? | AI has little else to draw on |
| 5 | Can a named owner update the page every month? | The page will stay accurate |
Score 4 or 5: Build it with the template below, then test it. Score 2 or 3: Fix question 1 first. Ask AI assistants about your company, list the errors, and see whether better core pages solve them. Score 0 or 1: Skip it for now. Question 5 is a hard stop. A page with no owner will get stale, and the whole point of creating this page will have been in vain.
Start with question 1. Our guide on why brands are missing from AI answers walks through diagnosing what AI says about you and where it gets that information.
A good AI info page is plain HTML with a dated fact table, current and retired product names, an FAQ, a who-it-is-not-for section, and sourced numbers. It describes the company and does not give commands to AI. It is linked from the footer and reviewed on a fixed schedule.
Here are the basic, must-have sections your AI info page should have.
Test an AI info page like any experiment. Record baseline answers for 20 to 30 branded prompts, publish the page, then re-run the prompts at fixed intervals. Track answer accuracy, citations of the page, AI referral visits, and crawler hits, then compare results to the hours spent.
AI answers vary from run to run, so repeat each prompt several times and average the results. A single run proves nothing.
| KPI | What it tells you | Where to find it |
|---|---|---|
| Answer accuracy rate | Share of branded prompts answered without a factual error | Your prompt log |
| Errors per 100 answers | Whether specific wrong claims disappeared | Your prompt log |
| Citation share | How often the AI info page is cited among all citations of your domain | An AI visibility tracker such as Similarweb AI Brand Visibility |
| AI referral visits | Whether assistants send readers to the page | Web analytics |
| AI crawler hits | Whether AI crawlers request the page at all | Server log analysis |
| Indexation and impressions | Whether Google indexes and shows the page | Search Console, including its Generative AI performance report |
| Hours spent | Build time plus monthly upkeep | Your time tracking |
I can’t tell you an AI info page works. I can tell you what it costs, what it might fix, and how to find out.
An AI info page may turn out to be useful brand hygiene. It may also turn out to be over-optimization that adds one more page to maintain. The public evidence supports neither conclusion.
Treat it as an experiment: record what AI says about you today, publish the page, and measure what changes.
If the page fixes errors that matter, keep it and give it an owner. If nothing changes, you have a clear answer and a cheap lesson.
A tracker like Similarweb AI Brand Visibility can show you what AI says about your brand now, so your test starts from data and not from a guess.
Find out where the wrong answer comes from before you edit anything. Check which sources AI cites when it gets your facts wrong, then fix those directly: update outdated profiles and listings, correct pages that repeat old information, and make sure your own core pages agree with the AI info page. An AI info page is one source among many, so it may not outweigh older pages AI already trusts.
No, not if you want AI search tools to find it. Retrieval-based AI tools pull pages from an index, so a page that search engines can’t index can’t be retrieved. The trade-off is that an indexed fact page can show up for your brand name next to your homepage. If that bothers you, write the title and description so the page reads as a reference page, not a second homepage.
Use a plain, stable name. Of the 14 pages I reviewed, five use an “ai-info” style URL, five use “llm-info,” and four use “ai-instructions,” and I found nothing showing that one name works better. Pick one, use it in the title and the footer link, and don’t change it later, so links and citations keep pointing to the same place.
There is no verified ideal length. Google’s guide says there is no ideal page length for generative AI search, and the examples I reviewed range from a few hundred words to several thousand. Include every fact an assistant gets wrong today, put the most important facts first, and cut anything promotional.
Only if it helps AI avoid a specific mistake, such as confusing you with a similarly named company. A few of the pages I reviewed compare themselves with named competitors, which invites scrutiny. If you do it, keep every statement factual and checkable, avoid superlatives, and say where each claim comes from.
If you sell in several languages, it’s worth considering. Some of the pages I reviewed offer translations: Pawns.app links to versions in eight other languages, and Workspace publishes in English and Croatian. The catch is upkeep, because every translation has to change when the English page does. If you can’t keep them in sync, publish fewer languages.
You can use it for a first draft, but a person has to verify every fact. The page exists to correct what AI gets wrong, so an unchecked AI draft defeats the purpose. Google’s guide also says content written with generative AI tools still has to meet its Search Essentials and spam policies.

Senior SEO Specialist
Shai, with 10+ years in SEO, holds a Bachelor’s and an MBA. He enjoys TV shows, anime, movies, music, and cooking.
Give it a try or talk to our insights team — don’t worry, it’s free!