Front door builder

Build a front door answer engines can read

When a patient asks an AI where to go, the engine reads plain pages and matches the city they typed. This builds one page for a clinician or a practice: the CMS registry facts you keep or strike, every city you serve in plain words, structured data with your NPI, and a robots.txt that leaves search crawlers open. You host it yourself. The page loads nothing from this site and never names it, so it keeps working if this site changes or goes away.

Nothing you type leaves this device. Looking up an NPI sends only the ten digits to this site's public data API, which asks the CMS NPI Registry. Nothing is stored.

1. Your NPI

The registry is the record engines and payers check you against, so your page should agree with it. If the registry is wrong, fix it at NPPES first.

2. What only you can say

Name every city and town your patients come from. An engine asked about a city looks for that city's name on the page; a practice in one town is often missing from answers about the city next door.

    3. Check it, then take it away

      Put the three files at the top of your site. The page has no scripts and no outside fonts or trackers, so it opens fast on a cheap phone.

      The structured data on the page

      Then check whether the engines name you: surgeonvalue.com/found tallies the answers and reads your robots.txt.

      What helps, and what does not

      Helps

      • Search crawlers left open: OAI-SearchBot (ChatGPT search), PerplexityBot, Claude-SearchBot, Googlebot (Google Search, AI Overviews and AI Mode) and Bingbot (Copilot). Closing one removes the site from that engine's answers.
      • Plain text on the page that names each city served. Structured data alone is not enough; the words a patient types have to appear.
      • Facts that match the CMS registry: name, specialty, practice address, phone, NPI.
      • A facts block that says where each line came from, the registry or the clinician, with the date it was read.
      • One clear way to book or call.

      Does not help

      • Any promise of a placement. Nobody controls what an engine says, and answers change from one run to the next.
      • Reviews written or copied onto the page. Ratings belong on the site that collected them, and fake reviews break the FTC's rule (16 CFR 465).
      • "Best", "leading" or "top" without a named source beside it. Engines read it as advertising, and many state boards bar it.
      • An llms.txt file. This builder does not make one: answer engines have not said they rely on it.

      The page records where each fact came from and a fingerprint (SHA-256) of the facts block, so anyone can tell later whether it changed. A fingerprint is not a signature.