Which AI Answers Reveal That Patients Cannot Find Our Accepting-New-Patients Status?
Four kinds of AI answer reveal that patients cannot find your accepting-new-patients status. The first hedges: "I couldn't confirm whether the practice is taking new patients; call the office." The second changes between runs or between assistants. The third says "yes" for a practitioner who is full, on leave or retired. The fourth leaves your practice out of "accepting new patients near me" answers, even though it appears for general specialty searches. Usually your status is not stated in text on your site, it sits only inside a booking widget, or directories and insurer listings say something different. Fix it by stating status in plain text on every practitioner and location page. Keep your Business Profile, directories and insurer listings in step.
Which answer patterns point to the problem?
| Answer pattern | Example | What it usually means |
|---|---|---|
| Hedge | "I couldn't find whether Dr. [Name] accepts new patients." | Status is not stated anywhere assistants can read |
| Inconsistent | "Yes" in one run, "the waitlist is closed" in another | Your site and directories disagree |
| Wrong "yes" | A full, departed or retired practitioner shown as available | Stale directory, insurer or Business Profile data |
| Missing | Practice named for "[specialty] near me" but not for "accepting new patients" | Status not stated in a way that matches the question |
| Wrong conditions | "Accepting new patients" with no mention of referral or age limits | Only part of the policy is published |
| Third-party source | Answer cites a directory or insurer listing, not your site | Your own site does not state status |
The hedge can be costly: a patient told to "call the office" may call the next practice on the list instead.
Which questions should you test?
Run these in ChatGPT, Gemini, Perplexity and Google's AI features, several times each, from your area:
- "Is [practice] accepting new patients?"
- "Is Dr. [Name] taking new patients?"
- "[Specialty] accepting new patients in [town]"
- "Which [specialty] practices near [town] have short waits for a first appointment?"
- "Does [practice] need a referral for new patients?"
- "Is [practice] accepting new [insurance plan] patients?"
- "Where can I see a [specialty] for [condition] soon in [town]?"
Record the answer, the stance and the sources for each run. A step-by-step audit of healthcare visibility is covered in how healthcare providers audit AI search visibility.
Can AI tell whether my fertility clinic is accepting new patients from its website?
Only if the website says so in text, clearly and specifically. Many clinics show availability only in an online booking tool. Most AI crawlers do not run JavaScript, so a booking widget that loads open slots looks empty to them. A line such as "Book your consultation today" does not say whether new patients can actually get one.
Fertility clinics have an extra problem: status often differs by service and patient group. A clinic may be taking new IVF patients but have a waitlist for egg freezing. It may run a separate donor programme, require a referral for some services, or take international patients only for certain treatments. A single "accepting new patients" flag cannot say all that. State it in text:
- Overall status: "We are accepting new patients."
- By service: IVF, IUI, egg or embryo freezing, donor programmes, fertility preservation before cancer treatment.
- Typical wait for a first consultation, updated when it changes.
- Referral rules: whether patients can self-refer.
- Who you see: single patients, couples, same-sex couples and international patients, where relevant.
- Insurance and self-pay: plans accepted and whether self-pay patients are seen.
- By physician, on each physician's page, if their availability differs.
The schema.org property isAcceptingNewPatients lets a MedicalOrganization state a yes-or-no value in structured data. Add it if it matches your text, but it cannot carry service-level detail, so the text does the real work. How assistants handle insurance acceptance is covered in whether AI can identify a clinic's accepted insurance.
Why does Gemini describe a retired physician as accepting new patients?
Because some of the sources it draws on still show the physician as active. The usual suspects:
- The Google Business Profile for the physician is still live and shows the practice's hours. Gemini relies heavily on Google's local data.
- Your own website still has the physician's bio page, or lists them on the team page.
- Health directories kept the profile, sometimes with an "accepting new patients" default.
- Insurer directories were not updated. Under the No Surprises Act, US health plans must verify provider directory information at least every 90 days. They must process updates within two business days of receiving new information, and providers must send updates when a network agreement ends or their information changes. If nobody told the plan, the listing can persist.
- The NPI record is still active if nobody deactivated it through NPPES.
To fix it:
- Keep a short page for the physician stating that they have retired, with the year, and who is now caring for their patients. This helps assistants and patients more than a 404 does.
- Mark the physician's Business Profile as permanently closed, or ask Google to update it following its rules for individual practitioners. Removing the profile from your Google account does not remove it from Search and Maps, and it leaves you unable to manage it.
- Notify every insurer the physician was contracted with, in writing.
- Update or close directory profiles on the main health directories.
- Deactivate the NPI through NPPES if the physician is retiring from practice.
- Recheck the questions above after a few weeks, and keep checking until every assistant has caught up.
What should each page say?
On each location page: whether the location is accepting new patients, which services and practitioners are taking them, typical wait for a first appointment, referral rules, insurance plans accepted and how to book.
On each practitioner page: whether this practitioner is accepting new patients, any limits such as age group or condition, languages spoken and a link to book.
On the Google Business Profile: the same status. Keep the description, attributes and booking link current, and update them when status changes.
In directories and insurer listings: the same status, updated when your site changes.
Pick one person to own status changes, so that when a practitioner fills up, reopens or leaves, every source is updated within days rather than months.
What might an illustrative case look like?
Consider an illustrative dermatology group with six physicians. Patients ask ChatGPT and Gemini which dermatologists in town are taking new patients. The answers either hedge or name a physician who retired last year. The group's website says "call to book" everywhere. The retired physician's bio page is still up, and their Business Profile and two insurer listings still show the physician as active. The group adds a status line to each physician page and a new-patient section to each location page with typical waits. It replaces the retired physician's page with a notice naming the physicians taking over their patients and marks their Business Profile as permanently closed. It also sends written updates to each insurer. A month later, the hedging answers have mostly gone, and the retired physician no longer appears.
What do people ask about accepting-new-patients status and AI?
Should we say when we are not accepting new patients?
Yes. A clear "not accepting new patients; join our waitlist" is better than silence, which leads assistants to guess.
How often should status be updated?
Whenever it changes. Stale status causes more harm than no status, because it sends patients to practices that cannot see them.
Does the isAcceptingNewPatients property help?
It supports the text for systems that read it, but it is a single yes-or-no value. Clear text on the page matters more.
Published by The Kovmere Team · updated Sep 29, 2026 · More resources