Is Your Business Ready for GPT-6 Astra?

OpenAI shipped GPT-6 Astra on 3 September. It is rolling out to every ChatGPT Plus, Pro, Business and Enterprise user as I write this.

Most of the SEO coverage so far is about benchmarks. I dont care about benchmarks. I care about 1 thing Astra does differently, because it changes the job for every clinic, law firm, agency, insurance broker and local service I work with.

Astra does not just read your website. It uses it.

It opens a browser, clicks through your pages, fills in your forms and tries to finish a task the way a person would. OpenAI's own framing is that Astra is built for end-to-end work: research, then action. For a service business that means the AI is no longer summarising your services page. It is trying to book the consultation, request the quote, or compare you against 2 competitors and pick 1.

So the question I have been asking clients this week is simple. If a customer tells ChatGPT "find me a dentist near Dallas who does implants and book me a consult," does your website let that happen, or does it quietly break?

That is what this audit is for. 6 checks. You can run most of them yourself in an afternoon, and I have put the exact prompts in the boxes below so you can copy them straight into ChatGPT.

Before Astra, AI search worked in 2 steps. The model pulled a snippet from your page, then handed the user a link. Whatever happened after the click was your problem.

Astra collapses that. It can browse live pages, evaluate what it finds, decide whether it needs another search, and then act. OpenAI also says Astra is trained to pull only the context that matters into its output instead of repeating everything it read. In plain terms: it is picky, and it skips your fluff.

One more thing worth knowing. The public version of Astra has safety monitors that can pause or stop a task. So if your site is confusing enough that the agent looks like it is doing something odd, the whole session may just end. No error message. No enquiry. Nothing in your inbox.

Here is the first test. Run it before you touch anything else. Swap in your own industry, city and service.

That 10 minutes will tell you more than the rest of this article. Most sites I have looked at since launch fail somewhere between the service page and the submit button, and the owner had no idea.

This sounds like 2015 local SEO advice. It is more important now, not less.

Astra can cross-check your site against what other sources say. Your Google Business Profile, your state bar listing, your medical board registry, Trustpilot, Healthgrades, Avvo, whatever applies to you. If your website footer says "Suite 4B" and your GBP says "Floor 4," a human shrugs. An agent that is trying to verify you are a real business at a real address may not.

What I check:

• Business name written identically across website, GBP, directories and registries.
• Phone number in the same format everywhere. Country code either always on or always off.
• Opening hours matching. A lot of businesses update GBP and forget the website.
• Every named practitioner, partner or advisor listed with the same credential string on your site as on their registry.
• Multi-location businesses: each branch gets its own page, its own address block and its own GBP, and none of them share a phone number unless that number genuinely routes to all of them.

This is where I expect most businesses to fail.

A generic "Contact Us" form with Name, Email, Message is fine for a human. It is a dead end for an agent that has been told to book a consultation, because the form does not tell it what happens next. Is this a booking? An enquiry? Does someone call back? When?

The businesses that will do well have intent-specific paths: "Book a consultation," "Request a case review," "Get a quote," "Check if we accept your insurance." Each one labelled clearly, each one reachable in 1 or 2 clicks from the service page.

Then there is the plumbing. The things that block an agent are usually invisible to you because you built the site and know where everything is:

• Booking calendars loaded inside an iframe from a third-party tool
• Date pickers that only work with a mouse drag
• Required drop-downs with 40 options and no logical default
• CAPTCHAs at the final step
• Chat widgets that cover the submit button on mobile
• Bot protection that treats a headless browser as an attacker and serves a blank page

That last one matters. If your hosting or CDN has aggressive bot management on, you may be blocking Astra without knowing it. Check your firewall rules before you check your copy.

Most service pages read like this: 400 words about how experienced and caring the team is, then a phone number.

Astra is looking for 4 things on a service page, and I have started structuring client pages around exactly these 4 blocks.

Number 3 feels counterintuitive and it is the block that builds the most trust. "We do not take medical malpractice cases" saves everyone time, including the agent. Add a short FAQ under the 4 blocks with the questions people actually ask, and keep the answers direct. The AI does not need a warm-up paragraph before the answer.

Everything above is about prose. Schema is about facts.

Structured data gives an agent your services, locations, credentials and fees as clean fields instead of forcing it to interpret sentences. For a regulated business this is where I spend real time, because the details that matter (board certification, accepted insurance, practice areas, licensing state) are precisely the details that get mangled when an AI has to infer them.

The baseline I implement:

• MedicalBusiness, LegalService, InsuranceAgency or the closest specific type, not just LocalBusiness, with full address, phone, hours, geo and sameAs links to GBP and registries
• A Service node per service you actually offer, linked to the business
• Physician, Attorney or Person nodes for each named professional, with credentials and their registry URL in sameAs
• FAQPage where the questions and answers match what is visibly on the page, word for word
• BreadcrumbList so the agent understands where the page sits

{
  "@type": "Dentist",
  "name": "Smith Family Dentistry",
  "address": { "@type": "PostalAddress",
    "streetAddress": "120 Main St, Suite 4B",
    "addressLocality": "Dallas", "addressRegion": "TX", "postalCode": "75201" },
  "telephone": "+1-214-555-0100",
  "openingHours": "Mo-Fr 08:00-17:00",
  "sameAs": ["https://g.page/...", "https://find.ada.org/..."],
  "makesOffer": { "@type": "Offer",
    "itemOffered": { "@type": "Service", "name": "Dental implants" },
    "price": "95", "priceCurrency": "USD",
    "description": "Initial consultation, credited to treatment" }
}

2 rules I do not break. First, schema has to match the visible page exactly. If the schema says the consult is free and the page says $95, you have just taught the AI to distrust you. Second, no fake AggregateRating data. Ever. It is a policy violation and agents that verify against external sources will catch it.

This is the section most SEO people will skip. Business owners should not.

An agent that can book is an agent that can book wrongly. Wrong practitioner, wrong service, a "free consult" that was only free for a specific case type. For a dental practice that is an awkward phone call. For a law firm it can be an intake conflict. For an insurance broker it can be a quote you cannot honour.

You want the agent to get as far as a draft enquiry, with every field filled, and then hand off to a person. That means:

• A confirmation step that says clearly "this is a request, not a confirmed appointment"
• Required fields that force the details your team needs to triage (matter type, insurance, urgency, budget)
• A plain statement of what happens next and how fast
• No instant booking for anything with clinical, legal or financial consequences unless a human reviews it first

The goal is not to stop the agent. It is to let it do the tedious part and stop exactly where your staff need to take over.

What I would do this month

Astra has been out for less than a week. The engines will change how they browse, and I will update this page when they do. What will not change is the underlying test: can a stranger, human or machine, land on your site with a job to do and finish it? Right now, for most businesses I have looked at, the answer is no. That is fixable. Nothing here needs a new website, just a clearer one.

If you want me to run this audit on your site, start with a free AI SEO audit or email hello@anshulrana.in. And if the terminology is still fuzzy, the plain-language version is in SEO vs AEO vs GEO: what is the difference.

Frequently Asked Questions

Sources

1. OpenAI: GPT-6 Astra, a new generation of intelligence
2. OpenAI: Path to Astra, critical capabilities and frontier safeguards
3. OpenAI Developers: GPT-6 Astra model page
4. CNBC: OpenAI begins rolling out Astra

Anshul Rana

SEO, AEO & GEO Specialist · Top Rated Plus on Upwork

I'm an SEO, AEO, and GEO specialist with 8+ years of experience helping businesses get found on Google and AI search platforms like ChatGPT, Claude, Gemini, and Perplexity. I hold the Top Rated Plus badge on Upwork (top 3% of freelancers) with a 100% Job Success Score, and I have worked with 1,000+ websites across India, Australia, the US, and the UK. I specialize in technical SEO, answer engine optimization, generative engine optimization, schema markup, and local SEO.

Website Upwork LinkedIn The Digital Geek

For model specifications and product availability, see the GPT-6 Astra model guide and the ChatGPT SEO guide.

Related Articles