Does the Perplexity Comet browser change how people find and use your website? My short answer is yes, but slowly. Comet puts an AI assistant inside the browser itself. A visitor can ask it to read, summarise, compare and even act on your pages, without scrolling through them the way they used to.
Perplexity announced Comet on 9 July 2025. For now it is only open to Perplexity Max subscribers and a small group of people invited from a waitlist. So the traffic impact right now is small. The direction it points in is not. I think the sites that prepare early will be easier for this kind of browser to understand and use. Apple has also said it is looking at AI search in Safari, with Perplexity among the options.
In this guide I explain what Comet is, how an AI browser reads a page, what it may do to your traffic and analytics, and the practical steps I’d take now.
What Is the Perplexity Comet Browser?
Comet is a web browser built by Perplexity, the company behind the AI answer engine of the same name. It runs on Chromium, the open-source project that Google Chrome is also built on. So it looks and works much like a normal browser.
The difference is that AI is built in, not added on later. Perplexity describes Comet as a browser that handles tasks based on what you are trying to do, not just the address you type.
Key Features at Launch
- Perplexity as the default search engine. Searches typed into the address bar go to Perplexity. It gives back an AI-written answer with cited sources, not a classic list of ten blue links.
- Comet Assistant. A sidebar assistant you can open on any page. It can see the page you are on, answer questions about it and summarise it.
- Agent-style tasks. The assistant can do jobs with several steps, such as comparing products, finding deals, managing tabs, writing or sending emails and working with calendar events. What it can do depends on the permissions the user gives it.
- Chrome extensions and import. Because it is built on Chromium, Comet supports Chrome extensions. Users can also import bookmarks and settings from their current browser.
Who Can Use It Right Now
At launch, Comet is available to subscribers on Perplexity’s Max plan, which costs $200 a month. Perplexity has said it will send invites to people on the waitlist over the summer.
That means today’s Comet users are a small group of early adopters. I’d treat it as a preview of where browsing is going, not a channel that will move your numbers this month.
How an AI Browser Reads and Acts on Your Pages
A normal browser just displays your page. A person then reads it, scrolls and clicks. An AI browser adds a layer in between: a language model (the AI that reads and writes text) that reads the page for the user and decides what matters.
Reading: The Page as Text and Structure
Say someone asks Comet Assistant “what is the return policy here?” or “summarise this article”. The assistant works from the content loaded in the tab. It has to work out which part of the page is the main content, which part is navigation, and which part is a cookie banner or a newsletter pop-up.
Pages with a clear structure make that job easier. A logical order of headings, real paragraphs and lists, and proper labels on buttons and form fields all give the model clean signals. Some pages are built from unlabelled div elements, with key details hidden in images or behind tabs that only open on click. Those give it less to work with.
Acting: Clicking, Filling and Navigating
The bigger change is that the assistant can take actions. A user might ask it to find a product in their size, add it to the basket, or fill in a booking form.
To do that, the assistant has to find the right button, field or link and use it correctly. Early hands-on testing found that Comet was good at answering questions about page content. It was less reliable on longer tasks with many steps, such as entering dates correctly in a booking flow. That gap is exactly where your site design matters.
Maybe your “Add to basket” button is an icon with no text label. Maybe your date picker only works with a mouse, or your form fields have no visible labels. Then an AI agent is more likely to get stuck. So is a person using a screen reader (software that reads the screen aloud for blind users). These are the same problems I most often find in accessibility checks.
Why Accessibility and AI Readability Overlap
Screen readers and other assistive tools depend on the same signals an AI agent is likely to use. These are semantic HTML (code that says what each part of the page is), headings in order, landmark regions such as main and nav, and controls with clear names. The web.dev guide to headings and landmarks is a good, practical reference for getting these basics right.
This is helpful, because it means you don’t need a separate “AI version” of your site. Work that makes your pages accessible to people also makes them easier for an AI browser to read and use. To me, that is the best part of this whole shift.
What Comet Means for Website Traffic
The honest answer is that nobody has reliable data on this yet. Comet has only just launched to a paying audience. What we can do is think through how it works.
Fewer Clicks From Search, More From Intent
Because Comet sends address-bar searches to Perplexity, users see an AI answer first. Some questions will be answered without a click, as already happens with AI answers elsewhere. Informational pages that just repeat common facts are most at risk.
On the other hand, Perplexity answers cite sources with links. Pages that get cited, and that offer something the summary can’t, still have a reason to be visited. Examples are a tool, a detailed comparison, original data or a product to buy.
Visits That Happen on the User’s Behalf
When Comet Assistant acts inside a tab, it is working in the user’s own browser session. Your page still loads. But the “visit” may look different. It might be very short, with a direct path to a form or checkout. Or the page might load mainly so the assistant can pull out an answer.
That may show up as strange engagement patterns, not lost traffic. A page might get the visit but lose the reading time, the scroll depth and the extra clicks you used to see.
Ranking Still Matters
None of this makes classic SEO useless. Perplexity, like other AI answer engines, still has to find and choose sources. Well-structured, trustworthy pages that already do well in search tend to be the ones worth citing. If you are reviewing performance after recent algorithm changes, our notes on Google’s June 2025 core update cover what to watch.
What It Means for Analytics
AI browsers create a measurement problem. I think it’s worth understanding now, before it grows.
Browser and Referrer Data
Comet is built on Chromium, so its traffic will likely look like Chrome in many analytics tools. It probably won’t appear as a clearly labelled “Comet” browser. Don’t expect a neat line in your browser report.
Clicks from Perplexity’s answer pages often arrive with Perplexity as the referrer (the site that sent the visit), which you can separate out. But activity that starts inside the Comet sidebar, or comes from a user who copied a link, may arrive with no referrer. Then it gets counted as direct traffic.
Agent Sessions and Engagement Metrics
If an assistant loads a page and acts on it in the user’s browser, your analytics tag may fire as normal, because the page is running in a real browser. The session will count. But numbers such as engagement time and pages per session may look unusual.
Here is what I’d set up now:
- Create a segment or exploration for sessions with Perplexity as the source, so you can watch the trend over time.
- Track key actions as conversions, such as form submissions and purchases. Don’t rely on time on page as a sign of quality.
- Add a note for 9 July 2025 in your reporting, so any later changes have context.
- Watch for rises in direct traffic to deep pages, which can point to AI-assisted visits with no referrer.
We will cover building organic reports in GA4 in more detail in our guide to GA4 reports for organic search traffic.
Crawlers Versus Browsers
Two things often get mixed up here, so let me separate them. Perplexity also runs crawlers (bots that fetch pages) for its answer engine. Those identify themselves with their own user agents, and you can manage them with robots.txt.
Comet is different. It is a browser the user controls, loading pages in their own session. Robots.txt controls automated crawlers, not a person’s browser. So it is not a tool for controlling how visitors use Comet on your site.
How to Prepare Your Site for AI Browsers Like Comet
The good news is that most of the work is solid web practice you should be doing anyway. Here is the order I’d work in.
- Audit your page structure. Check that each important template has one clear main heading, H2 and H3 sections in a logical order, and content wrapped in proper landmarks like
main,navandfooter. Lighthouse’s accessibility audit flags skipped heading levels and missing landmarks. - Put key facts in plain HTML text. Prices, opening hours, delivery times, return policies, specifications and contact details should be readable text on the page. Don’t bake them into images or load them only after a click.
- Label every interactive element. Buttons should have text or an accessible name (“Add to basket”, not just a cart icon). Form fields need visible labels linked to the input. Error messages should say what went wrong.
- Simplify critical journeys. Walk through your checkout, booking and enquiry flows using only a keyboard. If you get stuck on a date picker, a custom dropdown or a pop-up you can’t close, an AI agent may get stuck too. This keyboard test is the first thing I do on any new site.
- Write pages that answer questions directly. Give the answer first, then the detail. Use clear headings that match how people ask questions. A clear, accurate title also helps; see our guide to title tag best practices.
- Offer something a summary can’t replace. Original data, tools, calculators, detailed comparisons, real product pages and clear next steps give both people and assistants a reason to click through instead of stopping at the answer.
- Set up measurement. Separate out Perplexity referrals, set conversions on real actions, and watch direct traffic to deep pages. Then you can see AI-driven behaviour as it grows.
A Practical Example
Imagine a local furniture shop with a product page for a sofa. A Comet user asks the assistant: “Does this sofa come in grey, how wide is it, and can I get it delivered by Friday?”
If the colour options are listed as text, the sizes sit in a simple table, and delivery times are written on the page, the assistant can answer in seconds. The user may go straight to checkout. Now picture the opposite. The colours only appear as unlabelled swatches, the sizes are in an image, and delivery dates only show after you type a postcode into a pop-up. The assistant is more likely to give a vague or wrong answer, and the user may move on to a competitor.
The same fixes help a customer using a screen reader, someone on a slow mobile connection, and a search engine trying to understand the page.
What Not to Do
- Don’t build separate pages for AI. Showing assistants different content from people creates upkeep problems and trust risks. One clear, accessible page serves both.
- Don’t block what you can’t identify. Trying to detect and block AI browser sessions risks blocking real customers, since these are real people using a real browser.
- Don’t panic over small numbers. With access limited to a paid plan and waitlist invites, Comet is not yet a major traffic source. In my view, steady preparation beats rebuilding your site overnight.
The Bigger Picture: AI Moving Into the Browser
Comet is part of a wider shift. AI answers first appeared on search results pages. Now they are moving into the browser itself, where the assistant sits beside every page a user opens.
That changes the question site owners need to ask. It is no longer only “will Google rank this page?” It is also “can an assistant understand this page and help someone finish a task on it?”
Perplexity has also said it plans to add features based on user feedback. Other AI companies are clearly interested in agents that browse for the user, too. Expect more tools that read and act on websites, not fewer.
The sites that do well in that world will likely be the ones already doing the basics properly. That means fast, accessible, clearly structured pages with truly useful information and simple paths to conversion.
Conclusion: What to Do About the Perplexity Comet Browser
The Perplexity Comet browser is an early but clear sign that AI is moving from the search results page into the browser itself. Its audience is small for now. But it shows how visitors will more and more ask an assistant to read, compare and act on your pages for them.
You don’t need a separate AI strategy to respond. Tidy up your heading structure and landmarks, put key facts in plain text, label your buttons and forms, test your key journeys with a keyboard, and adjust your analytics so you can spot AI-assisted visits. I’d start with your most valuable page templates, then review how they show in search with our guide to writing clear, accurate title tags.
