OpenAI has released its own web browser. If you run a website, you are probably asking whether ChatGPT Atlas changes how people find you, how they reach you and how you measure it. The short answer: Atlas puts ChatGPT next to every page a person visits and lets it act for them. So your pages now need to work for an AI reader and an AI agent, not just a human.
It does not replace SEO. But it does make the basics matter more: clear content, crawl access for OpenAI’s search crawler, clean analytics tagging and well-built, accessible pages. In my view, a site that already does these things well has very little to worry about.
What Is ChatGPT Atlas?
ChatGPT Atlas is a web browser with ChatGPT built in. OpenAI announced it on 21 October 2025 and released it the same day for macOS, worldwide, to Free, Plus, Pro and Go users. Business users get it in beta. Enterprise and Edu users can use it if their admin turns it on.
OpenAI says versions for Windows, iOS and Android are coming soon, but gave no dates. For now, every Atlas user you see is on a Mac. Atlas isn’t the first AI browser, either. I’ve already covered Perplexity’s Comet browser and Gemini in Chrome. Atlas also arrives a few weeks after a court let Google keep Chrome.
On first launch, people can bring in bookmarks, saved passwords and browsing history from their old browser. That matters because it makes switching easy. Someone can try Atlas for an afternoon without losing their logins.
The Three Features That Matter for Site Owners
- The ChatGPT sidebar. An “Ask ChatGPT” button opens ChatGPT next to the page being viewed. The user can ask it to summarise, compare or explain what is on screen, without copying and pasting.
- Browser memories. If the user turns them on, ChatGPT can remember details from sites they visited and bring them back later. A request like “find the jackets I was looking at last week” becomes possible.
- Agent mode. ChatGPT can open tabs, click, fill in fields and move through a site to finish a task. It launched in preview for Plus, Pro and Business users only.
Each of these changes how a visitor experiences your page. The sidebar means your content gets summarised. Memories mean your site can be recalled later. Agent mode means a piece of software may be the one clicking your buttons.
How the ChatGPT Sidebar Changes a Visit
In a normal browser, a visitor reads your page and makes up their own mind. In Atlas, they can ask ChatGPT about your page while it is open. The answer is built from what is on screen.
Take a comparison page for project management software. A visitor could ask, “Which of these has the cheapest plan for five users?” ChatGPT reads the page and answers. If your pricing is stuck in an image, hidden behind tabs that only load on click, or spread across vague headings, the answer may be wrong or incomplete.
The lesson is simple. Put the facts people want in plain text, near clear headings, and state them exactly. Prices, specs, opening hours, delivery terms and who qualifies should be readable in the HTML, not only in images or PDFs. When I review a page, pricing locked inside an image is one of the first things I look for.
This is the same advice that helps search snippets and AI answers in general. Atlas just makes the cost of vague content easier to see, because the summary happens on your own page.
Browser Memories and Privacy Controls
Browser memories are optional. Users can view and archive them in settings. Clearing browsing history also deletes the memories linked to it.
OpenAI also gave users several other controls at launch:
- Page visibility toggle. A switch in the address bar lets the user stop ChatGPT from seeing a site. When it is off, ChatGPT can’t view the page and no memories are made from it.
- Incognito windows. These log the user out of ChatGPT for a while, so activity is not saved to their account.
- Training opt-in. OpenAI says that, by default, the content people browse in Atlas is not used to train its models. Users can opt in through an “include web browsing” setting in data controls.
- Parental controls. Existing ChatGPT parental controls carry over. Parents can also switch off browser memories and agent mode.
For site owners, the training point is the important one. OpenAI says that even if a user opts in to training, web pages that block GPTBot won’t be trained on. So your existing GPTBot rule in robots.txt also covers content seen through Atlas.
Agent Mode: When Software Clicks Your Buttons
Agent mode is where Atlas differs most from a normal browser. The user describes a task, and ChatGPT carries it out in browser tabs. OpenAI’s own example is adding the ingredients for a recipe to a grocery basket. Other examples it gave include research and booking appointments.
OpenAI set limits on what the agent can do:
- It can’t run code in the browser, download files or install extensions.
- It can’t reach other apps on the computer or the file system.
- It pauses on sensitive sites, like banks, so the user can watch what it does.
- It can run in a logged-out mode that keeps it away from the user’s accounts and saved data.
OpenAI calls agent mode an early experience that may make mistakes on complex tasks. It also warns that agents can be targeted by harmful instructions hidden in web pages (often called prompt injection). It suggests users keep an eye on the agent. I’d take that warning seriously if you show user content, like reviews or comments, next to your checkout or forms.
Why Agents Struggle With Some Sites
An agent has to work out what each element on your page does. It does this by reading the page structure, not by looking at it like a person does. Some sites use plain <div> elements styled to look like buttons. Some have icon-only links with no label, or custom dropdowns that don’t show their state. These are hard for an agent to understand.
These are the same problems that make a site hard to use with a screen reader. That is not a coincidence, and OpenAI has said so directly. I see these fake buttons all the time on sites built with heavy page builders.
OpenAI’s Guidance for Website Owners
OpenAI’s publishers and developers FAQ covers how sites appear in ChatGPT. It now has a section on ChatGPT agent in Atlas. The key points:
- Make your site accessible. OpenAI says Atlas uses ARIA tags (the same labels and roles that help screen readers) to understand page structure and interactive elements. It recommends following WAI-ARIA best practices by adding clear roles, labels and states to buttons, menus and forms.
- Don’t block OAI-SearchBot. This is the crawler that lets your pages show up in ChatGPT search results. If your robots.txt blocks it, your content is less likely to be shown and linked.
- Use GPTBot to control training. Blocking GPTBot is the way to keep pages out of possible model training. OpenAI says that applies to content gathered through Atlas when a user has opted in.
- Track referrals with the UTM tag. ChatGPT adds
utm_source=chatgpt.comto referral URLs. So links clicked from ChatGPT search results can be spotted in analytics.
A Note on ARIA: Semantic HTML Comes First
Accessibility experts quickly pushed back on the ARIA advice, and with good reason. ARIA is meant to fill gaps where normal HTML can’t describe an element. It is not a replacement for proper HTML.
A real <button> already tells browsers, screen readers and agents that it is a button. A real <label> tied to a form field already names the field. Adding ARIA on top of correct HTML usually adds nothing. Wrong ARIA can make things worse for disabled users.
So I read OpenAI’s advice as “make your pages accessible”, not “sprinkle ARIA everywhere”. And don’t be tempted to stuff keywords into aria-label values. That hurts people using assistive technology, and it’s the kind of trick that tends to backfire.
Here is the difference in practice:
<!-- Hard for screen readers and agents to understand -->
<div class="btn" onclick="addToBasket()"><i class="icon-cart"></i></div>
<!-- Clear to everyone -->
<button type="button" onclick="addToBasket()">Add to basket</button>
<!-- Icon-only button: ARIA fills a real gap -->
<button type="button" aria-label="Add to basket"><svg aria-hidden="true">...</svg></button>Can You Block ChatGPT Atlas?
Not in the way you block a crawler. OpenAI has not published a separate Atlas user agent to target in robots.txt. When a person browses your site in Atlas, it acts like any other browser visit.
What you can control is narrower, and more useful:
- Whether your content can be used for training, through GPTBot.
- Whether your pages can show in ChatGPT search, through OAI-SearchBot.
- What any visitor, human or agent, can reach, through logins, rate limits and your normal security.
Blocking a person’s browser because it has an assistant would also block a real customer. For most businesses, I don’t think that trade is worth it.
What ChatGPT Atlas Means for Traffic
Nobody outside OpenAI knows how many people will switch, and there was no usage data at launch. It is Mac-only for now, and it competes with browsers people have used for years. Treat it as an early signal, not a sudden shift.
Still, a few changes are worth planning for:
- More answers without a click. When a user types a question in Atlas, ChatGPT can answer directly. For simple information questions, some visits that used to come from a search results page may not happen.
- Better-qualified visits. When someone does click through from a ChatGPT answer, they often arrive with a clear task in mind. Expect fewer, more focused visits for some query types.
- Agent visits that look human. An agent working in a real browser loads your pages, runs your scripts and fires your analytics tags. Those sessions may look a bit odd, like very fast page sequences or form fields filled in with no pause.
- Tasks done on your site, not somewhere else. Unlike ChatGPT checkout features, Atlas agent mode works on your own website. If your checkout or booking form works well, the agent can still bring the sale to you.
That last point is the opportunity. If you followed ChatGPT Instant Checkout and the Agentic Commerce Protocol, Atlas is the other route. Instead of OpenAI connecting to shops, the agent uses the site like a person would. Both reward sites whose product data and buying steps are easy to understand.
Analytics Attribution: What You Can and Cannot See
This is where most site owners will notice Atlas first, mostly as confusion in reports. Here is what to expect.
What You Can Track
OpenAI says clicks on links in ChatGPT search answers carry utm_source=chatgpt.com. In Google Analytics 4 these show up under the session source chatgpt.com. Set up a saved exploration or a custom channel group for AI referrals, so you can watch the trend over time. This is one of the first things I set up on any site now.
What You Probably Cannot Separate
- Normal browsing in Atlas. If someone opens your site in Atlas by typing your URL or clicking a bookmark, it looks like any other desktop visit. OpenAI has not documented a separate label for analytics.
- Agent sessions. These run inside the user’s browser, so they will likely be counted as normal sessions. No official way to label them was published at launch.
- Sidebar reading. When ChatGPT summarises a page the user already has open, the visit is already counted. You won’t see what the user asked.
Practical Steps for Cleaner Data
- Write down your current numbers for engagement, conversion rate and direct traffic now. Then you have a starting point if behaviour changes.
- Watch macOS desktop sessions as a segment. Atlas is Mac-only for now, so any shift in Mac behaviour is where an early signal would show.
- Track conversions as events at the moment they finish, like an order confirmation or a sent form, not just page views.
- Look for odd sessions, like many pages viewed in a few seconds with no scrolling. Add notes to your reports for unusual periods.
Search Console won’t show Atlas activity directly, because it reports Google Search data. If you need a refresher on what it does show, see our guide to the Search Console reports that matter.
How to Prepare Your Site for ChatGPT Atlas
None of this needs a rebuild. Most of the work overlaps with good technical SEO and accessibility. So it pays off in Google, other browsers and assistive technology too.
- Check robots.txt for OpenAI’s crawlers. Make sure OAI-SearchBot is allowed if you want to show in ChatGPT search. Decide on its own whether to allow or block GPTBot for training. They are separate choices.
- Put key facts in text. Prices, specs, stock status, policies and contact details should be in the HTML near clear headings. Not only in images, PDFs or content that loads after a click.
- Use semantic HTML for every interactive element. Use real buttons, real links, labelled form fields and proper headings. Add ARIA only where normal HTML can’t describe the element, like icon-only buttons or custom widgets.
- Test your key journeys with a keyboard and a screen reader. If you can finish checkout, booking or a lead form without a mouse, an agent has a much better chance too. This is the quickest test I know, and it finds most of the real problems.
- Make forms predictable. Use clear labels and visible error messages next to the right field. Avoid hidden steps that depend on hover or timing.
- Set up AI referral reporting. Create a channel or segment for
chatgpt.comand similar sources, and track conversions as events.
If OpenAI’s crawler struggles to reach parts of a large site, the same fixes that help Googlebot apply. Our article on crawl budget covers how to cut wasted URLs and keep important pages easy to reach.
What Not to Do
- Don’t panic-block. Blocking OAI-SearchBot because of Atlas would remove you from ChatGPT search. That’s the part of this system that sends clicks you can track.
- Don’t stuff ARIA labels. They exist for people using assistive technology. Keyword-heavy labels hurt those users and have no proven ranking benefit.
- Don’t build separate “AI pages”. The sidebar reads the same page your human visitor sees. One clear, accurate page serves both.
- Don’t over-read early data. A small rise or dip in Mac traffic in the first weeks is more likely noise than a trend.
The Bigger Picture for SEO
Atlas joins a growing group of browsers with built-in AI assistants. And it comes from the company behind one of the most-used AI products. Its goal is clear: make ChatGPT the starting point for browsing, not a separate tab.
For SEO, the direction matches what search engines already reward. That means content that answers questions exactly, pages that are fast and well structured, and sites that work for every user, including people using assistive technology. Atlas adds one more reader to that list: an AI that both summarises and acts.
Conclusion: ChatGPT Atlas Rewards Well-Built Sites
ChatGPT Atlas is an early, Mac-only product. But it shows where browsing is going: an assistant next to every page and an agent that can finish tasks on your site. You can’t block it like a crawler, and I don’t think you should want to. What you can do is allow OAI-SearchBot, decide your GPTBot policy, tag and segment AI referrals, and make your key pages accessible with proper HTML.
If I had to pick one next step, it would be an accessibility check on your most valuable journey, like checkout or your main enquiry form. Then check your robots.txt rules for OpenAI’s crawlers.
