AI visibility for an IR website means making official company information easier to discover, interpret, and verify when an AI-enabled service answers a relevant question. The company can improve its source pages and technical access; it cannot control every answer or guarantee a citation.
Start with the information the company wants accurately represented: its business, issuer identity, current results, leadership, governance, and investor events. The goal is a dependable source record, not copy written to imitate an AI response.
Build pages that answer real questions
Give each important page a clear purpose and a direct opening. Identify the company and the relevant date or reporting period without relying on context from the homepage. Explain specialist terms where necessary, and link claims to the appropriate approved documents.
An effective results page, for example, should make it clear which quarter is covered and where the release, filing, presentation, and webcast can be found. Do not publish several near-identical pages for variations of the same question.
Google's current AI optimization guidance rejects a prescribed writing formula, ideal page length, and special AI text files as requirements for Google Search. [1] Write for the reader's task and the company's disclosure context.
Make identity and provenance consistent
Use the approved company name, business description, and relevant identifiers consistently. Review pages that may remain visible after a name change or transaction. Clearly distinguish current facts from historical material.
Connect summaries to the original source rather than presenting an isolated number or statement. For financial content, preserve the reporting period, units, and explanatory context supplied in the approved materials. Have the company review any new summary before publication.
Use structured data to describe what is actually on the page. Avoid adding unsupported credentials, fabricated authors, or hidden claims simply because the markup accepts a field.
Treat access controls according to their purpose
Google's AI features use the underlying Search foundations; eligible supporting pages must be indexed and available for snippets. Special schema is not required. [2]
OpenAI separately documents OAI-SearchBot for search and GPTBot for potential model-training use. Those settings can be managed independently. [3] Do not interpret a blanket “allow AI” or “block AI” setting as a sufficiently precise policy.
Have the website operator check the actual robots directives and infrastructure rules. The search and AI discovery guide explains how crawling, indexing, retrieval, and user-requested access differ.
Measure observations rather than promises
Create a small, repeatable set of questions about public company information. Record the service, date, exact question, answer, cited URLs, and any error. Distinguish an incorrect fact from a missing citation and from a page that is technically inaccessible.
Use these observations to choose specific improvements. If an answer cites an obsolete company description, strengthen the current official page and make the old context clearer. If a key source is blocked, investigate access before rewriting it.
Review available webmaster reporting and referral data alongside these tests. Bing's guidelines connect discovery and indexing with eligibility for grounding and citations. [4] Neither a crawler visit nor a single successful answer proves sustained visibility.
Keep the work within the disclosure process
Do not release new material information through a search-optimization exercise. Use the company's existing approval and disclosure process for public content. AI-facing readability should preserve the meaning and qualifications of the approved source.
The SEO guide covers the underlying website foundations. Maintain those foundations and revisit observations when important content changes, rather than chasing every suggested optimization tactic.
Questions companies ask
Does AI visibility require a chatbot on the IR site?
No. This guide concerns how external services discover and use public pages. An on-site chatbot would be a separate product with its own content and disclosure controls.
Is llms.txt required for Google visibility?
No. Google's current guidance says Google Search ignores it; maintaining one for another documented use is a separate decision. [1]
Can a company guarantee its pages will be cited?
No. Treat citation outcomes as observations to measure, not contractual certainty about an external service's answers.
What should be improved first?
Correct inaccurate or ambiguous public content, verify access to important pages, and connect summaries to authoritative documents before testing specialized tactics.
Bring the priority questions and observed source gaps to VendorGroup when scoping improvements to the IR website.
Related VendorGroup resources
- SEO for Investor Relations Websites
- How Search Engines and AI Systems Find Public Company Information
- Structured Data and Schema for Investor Relations Websites
