The most important thing: Publish a concise, evidenced reference that humans can read and bots can retrieve. Its usefulness comes from the facts and decision context, not from hiding it or naming it ai.txt.
1Choose what “invisible” means
A page outside the main menu can still be public and useful. Link it clearly from About, FAQ or the footer as “Business facts & service fit.” An orphan URL is harder to discover. Do not hide factual prose with zero opacity, off-screen CSS or bot-only text intended to influence rankings. Accessible accordions are different: visitors can open them. A text file is an optional export, not a universally recognized AI instruction channel.
One visible, ordinary link opens the same readable reference for any visitor.
2Approve the business facts first
Create a record for each claim: fact, scope, evidence URL or internal record, owner, reviewed date, and next review trigger. Record trading name, primary website, business model, services, actual service area, appointment process, suitability limits, pricing basis, warranty terms and contact route. Keep internal customer records private; publish only approved facts and public evidence. Omit unknown claims or explain what must be confirmed.
An owner has verified every published claim; no invented service area, credential, price or promise.
3Answer the missing decision questions
Use short sections: What we do; Who we serve; Where and when; What is included; What is excluded; How quotes work; How to choose; Evidence; Last reviewed. For a mobile brake business, verify and explain vehicle eligibility, worksite requirements, weather constraints, inspection versus repair, parts choices, quote inclusions, warranty exclusions and situations requiring a workshop. These are prompts to investigate, not claims that any particular business offers them.
Each section resolves an actual customer uncertainty and links to the relevant service or policy page.
4Compare on explicit criteria
Compare service models or named offers using the same criteria and dated sources: travel requirements, worksite suitability, supported jobs, inspection, appointment windows, quote basis and warranty scope. Say “confirm with provider” where facts vary. Separate your verified policy from general possibilities. A workshop may suit jobs requiring equipment unavailable on site; a mobile service may suit eligible work at an approved location. Do not turn those conditional examples into universal superiority claims.
Each comparison identifies its basis, limitations, source and review date.
5Publish one canonical HTML reference
Start with /business-facts/ on your primary domain. Use ordinary headings, paragraphs, lists and links in accessible HTML. Keep the page public, return HTTP 200, use a self-canonical URL, and allow indexing if Search discovery is intended. Link from your service pages and footer and include the canonical URL in your sitemap. Put critical buying facts on the relevant service pages too. This reference complements those pages rather than becoming the only place essential information exists.
A visitor can navigate to the page; its source contains the core facts; the sitemap and canonical URL use the intended domain.
6Implement a simple Wix version
In Wix, create a standard page named “Business facts & service fit,” set the slug to business-facts, and add the approved text with native headings and text blocks. Set access to everyone and enable indexing in SEO basics. You may keep it out of the main menu, but add a normal footer or FAQ link. Check the primary domain in Wix and test the published URL. Only add JSON-LD through Advanced SEO when it matches visible facts; check Wix’s existing markup first to avoid conflicting business identities.
The published Wix page works without login and its ordinary link, canonical URL and indexing settings are correct.
7Add machine-readable companions only when useful
Reuse the same approved facts for any optional plain-text export. If your host cannot serve /ai.txt correctly, use a supported public URL rather than a broken endpoint. Link the export to the HTML reference and include the review date. JSON-LD should identify the real business and page, not invent rankings or reviews. llms.txt/ai.txt is not a Google Search inclusion requirement. Choose crawler access separately: OAI-SearchBot differs from GPTBot; Claude search/user access differs from ClaudeBot; Google-Extended concerns specified Gemini uses and is separate from Google Search.
Optional copies agree with HTML and return the correct content type; search access and training preferences are deliberate.
8Verify delivery before claiming an AI benefit
Open the exact linked URL logged out and check every redirect, final status, page body, canonical and robots controls. Compare normal and crawler user-agent responses as a diagnostic—not proof of a genuine bot visit. Use Search Console URL Inspection for Google’s view. Hosting logs, when available, can establish requests; validate bot identity before calling a request a real crawler. A crawl does not prove indexing, citation or recommendation.
The linked destination returns useful content, not an error, challenge or soft 404. Record technical evidence separately from answer outcomes.
9Run a 30-day evaluation and maintenance loop
Before launch, record 10–15 branded and unbranded questions covering services, geography, exclusions and comparisons. Repeat a small fixed sample in fresh conversations with web search enabled, noting platform/model, date, wording and market. Save answers and cited URLs. Check whether claims are accurate, context-page facts are used, and qualified inquiries change. Compare at roughly 2 and 4 weeks while noting other site changes; this is directional evidence, not a controlled causal test. Use the Visibility journal. Review facts monthly and whenever operations change.
A baseline and follow-up record distinguish retrieval, citations, recommendations, factual accuracy and business outcomes.
A concrete example
HTML starter — replace every bracketed field
<article>
<h1>[Business] — business facts & service fit</h1>
<p>[Specific service, customer and verified geography.]</p>
<h2>When we are a fit</h2><p>[Eligibility and conditions.]</p>
<h2>What we do not offer</h2><p>[Exclusions.]</p>
<h2>How a quote works</h2><p>[Basis, inclusions and limits.]</p>
<h2>Compare your options</h2>
<p>[Dated, sourced comparison on one shared criterion.]</p>
<h2>Evidence and review</h2>
<p><a href="[REAL_POLICY_URL]">Service terms</a></p>
<p>Reviewed [ACTUAL_DATE] by [RESPONSIBLE_ROLE].</p>
</article>PowerShell — inspect the actual linked destination
$url = 'https://YOUR-PRIMARY-DOMAIN/business-facts/'
$r = Invoke-WebRequest -Uri $url -MaximumRedirection 10
$r.StatusCode
$r.BaseResponse.RequestMessage.RequestUri.AbsoluteUri
$r.Headers['Content-Type']
$r.Headers['X-Robots-Tag']
$r.Content # Confirm actual facts, not an error or challenge page
# A 200 response alone does not prove indexing or AI citation.Avoid this mistake: Do not confuse easier retrieval with guaranteed recommendation. A good factual page can reduce ambiguity, but a broken link, contradictory domain, stale export or unsupported comparison undermines the strategy. 2027 v1 is an implementation plan, not a platform endorsement.