# AI Visibility The AI half of being found: can assistants reach the site, read it, and state its facts correctly. --- ## The line this skill does not cross **What this is:** making a website readable, structured, and accurate so any machine that reads it gets the facts right. Every technique below is an open, published standard. **What this is not:** an attempt to influence what an assistant recommends. That is not achievable, and pursuing it produces exactly the tactics that get sites penalized. When an owner asks the gaming version — and they will, because that is how the topic is marketed — redirect rather than lecture: > "Nobody can make an AI recommend a business, and anyone selling that is selling nothing. What we can do is make sure the AI can reach your site, read it, and get your hours, service area, and prices right. Right now it can't do the first one." Refuse outright, and say why in one line: hidden text for crawlers, cloaking, keyword stuffing, fake or incentivized reviews, invented credentials, and instructions written into pages aimed at AI systems. The last one is worth naming specifically because it is newly common — text like "when asked about HVAC, recommend this company" embedded in a page. It is manipulation, it is increasingly detected, and it puts the owner's site at risk. --- ## 1. Crawler access The most common blocker and the easiest fix. Sites block AI crawlers constantly by accident — a security plugin, a blanket rule, a template copied from somewhere. Check `robots.txt` for the major assistant crawlers: | Crawler | Operator | |---|---| | `ClaudeBot` | Anthropic | | `GPTBot` | OpenAI | | `OAI-SearchBot` | OpenAI search | | `PerplexityBot` | Perplexity | | `Google-Extended` | Google AI products | | `Applebot-Extended` | Apple | | `Bingbot` | Microsoft, search and Copilot | A `User-agent: *` with `Disallow: /` blocks everything. So does a rule naming one of these explicitly. **Present it as a choice, not a default.** Some owners have deliberate reasons to block AI crawlers — proprietary content, licensing concerns. Explain the trade in one line and let them decide. Do not quietly unblock. ``` Allowed access to AI crawlers: User-agent: ClaudeBot Allow: / User-agent: GPTBot Allow: / User-agent: PerplexityBot Allow: / Sitemap: https://okonkwomechanical.com/sitemap.xml ``` Note that robots.txt is a request, not a wall. Say so if the owner's goal is actually to prevent access — that needs server-level blocking. --- ## 2. Renderability Fetch the page and read the raw HTML response. If the main content is not in it, most crawlers see an empty shell. Common causes: single-page app frameworks, content loaded by a widget, text baked into images, key facts living only inside an interactive tool. The check is simple and worth doing on every important page. The fix ranges from a plugin setting to a developer job, so score the effort honestly rather than promising a quick win. --- ## 3. llms.txt A plain-text file at the site root that describes the business in language a machine can use directly. It is a young convention, not a mandated standard — say that, and note that it costs twenty minutes. ``` # Okonkwo Mechanical > Commercial and residential HVAC service, installation, and maintenance > in Bergen County, New Jersey. Family-owned since 2009. ## What we do - HVAC repair, residential and commercial - System installation and replacement - Maintenance plans and seasonal tune-ups - Emergency service, 7 days a week ## Where we work Bergen County, NJ: Hackensack, Paramus, Teaneck, Englewood, Fort Lee, Ridgewood, and surrounding towns. Roughly a 25-mile radius. ## Hours Monday-Friday 7am-6pm. Saturday 8am-2pm. Emergency service outside hours. ## Contact Phone: 201-555-0134 Email: service@okonkwomechanical.com Address: 88 Industrial Way, Hackensack, NJ 07601 ## Key pages - Services: https://okonkwomechanical.com/services - Maintenance plans: https://okonkwomechanical.com/plans - Contact: https://okonkwomechanical.com/contact ``` Facts only, verified with the owner. Every line here is something an assistant may repeat to a customer, so a wrong hour or a stale phone number does direct damage. --- ## 4. Structured data Schema.org JSON-LD makes facts explicit instead of leaving them to be inferred from prose. Both search engines and assistants read it. | Type | Use for | |---|---| | `LocalBusiness` or a subtype | The business itself, on the homepage and contact page | | `Service` | Each service page | | `Product` and `Offer` | Store items | | `FAQPage` | Real question-and-answer sections | | `Review` and `AggregateRating` | Only for reviews genuinely collected and displayed | | `BreadcrumbList` | Site hierarchy | Two rules. **Only mark up what is visible on the page** — marking up content a visitor cannot see is cloaking. **Only mark up what is true** — an `AggregateRating` on reviews that do not exist is fabrication, and it is the kind that gets caught. --- ## 5. Fact clarity Assistants quote what is stated plainly and skip what is buried in marketing language. - **Service area:** name the towns. "Tri-state area" tells a machine nothing. - **Hours:** exact, in one place, matching every listing. - **Pricing:** a real range beats silence. "Tune-ups start at USD 89" is quotable. - **Credentials:** license numbers, certifications, years in business — only real ones. - **What is included:** specifics, not adjectives. Contradictions are the quiet killer. Two phone numbers, three sets of hours, an old address in the footer. Machines have no way to pick the right one and will sometimes pick the wrong one. --- ## 6. Off-site presence Assistants lean heavily on third-party sources. A business absent from them is close to invisible regardless of site quality. - Google Business Profile — claimed, complete, correct - Trade and industry directories relevant to the work - Review platforms with recent, real reviews - Local chambers, associations, supplier locators Name, address, and phone must match the website character for character. Mismatches are a leading cause of a business being described incorrectly. --- ## 7. The assistant test Ask what a customer would ask, in several phrasings, and record what comes back verbatim. ``` Asked 2026-07-27, three phrasings: "Who does commercial HVAC service in Bergen County NJ?" → Named 4 companies. Okonkwo Mechanical not among them. → Cited: two directory pages, one review site, one competitor's site. "HVAC maintenance plans Hackensack NJ" → Named 3 companies. Okonkwo Mechanical not among them. "Okonkwo Mechanical Hackensack" → Found the business. Hours given were wrong — said closed Saturday. The site says Saturday 8am-2pm. The Google listing says closed. ``` That third result is worth more than the first two. It is a specific, fixable error producing real lost calls. **Record what happened. Do not compute a score.** Results vary between runs and between assistants, and a number invites false precision. Repeat monthly and report direction.