The average person does not wake up choosing between "website" and "no website." They choose between opening an app, asking ChatGPT, tapping a map result, or typing a URL. Websites are still relevant when those paths need a place to land: confirm a business is real, compare two options side by side, pay for something, book a slot, or read instructions that outlive a chat thread. They become irrelevant when the destination is slow, broken, or empty, because the next tap is always available.
That shift is what agencies miss when the brief says "we need a website" as if presence alone still wins. In 2026 a site is less often where people first find you and more often where they check you are real, pay, or book after they found you somewhere else. Your job is not only to exist on the open web. It is to be the destination that still earns the click when someone is ready to act.
What does "still relevant" mean after apps and AI answers?
Relevance is not traffic volume. Pew Research analysis of tens of thousands of Google searches in 2025 found users clicked a traditional result on only about 8% of queries that showed an AI Overview, versus about 15% without one. Casual browsing traffic is thinner. The visits that remain often carry sharper intent: someone already heard a name and wants proof, or they are ready to buy and need a form that works on mobile.
Google's Search team has argued the same restraint in public: websites are not obsolete, but they are not mandatory for every goal (Search Off the Record). Whether you need one depends on audience, control, and what you are trying to deliver. For many businesses the answer is still yes, because apps and social profiles do not replace a site you control when AI systems and search features need structured facts to cite.
The relevance question therefore splits in two. Is the open web still where machines and sceptical humans go to verify claims? Yes, for most categories. Is every marketing site still the main place people discover you? Less often. Optimization playbooks for AI retrieval are a different job from this one: here the focus is when ordinary people still need a site in the loop, and what kills that need without anyone announcing "websites are dead."
When does the average person still open a website?
Four patterns show up repeatedly in support tickets, analytics, and client interviews. They are not exotic B2B edge cases.
Trust and verification. Someone saw a brand in an AI answer, a podcast, or a friend's message. Before they pay, they want hours, address, team names, or policy pages that do not fit in a bio field. A thin landing page or a broken mobile layout ends the visit faster than a sceptical review thread.
Transactions and account work. Checkout, invoicing, portal login, and document upload still live on the web for most industries. Native apps cover some retail and banking, but many small businesses never ship an app at all. The website is where those tasks happen.
Local and time-sensitive tasks. Maps and assistants surface names quickly. The user still opens the site for menus, appointment rules, parking, or service area boundaries that change more often than a static profile allows.
Documentation and how-tos. Long instructions, API references, and troubleshooting steps age poorly inside chat bubbles. People search, skim an answer, then open the canonical page to bookmark or share with a colleague.
In each case relevance is functional. The site is not wallpaper. It is where the task completes.
Websites vs apps vs AI answers: what each layer does
| Layer | What the average person uses it for | What it cannot replace alone |
|---|---|---|
| AI answer (ChatGPT, Gemini, AI Overviews) | Quick summary, comparison shopping ideas, "is this legit?" first pass | Owned checkout, signed contracts, authenticated account state, durable docs you control |
| Native app | Habitual repeat use (banking, delivery, social) | Broad discovery, long-form proof, SEO and citation for strangers who do not already have the app installed |
| Website | Verify, compare, pay, book, read docs, share a stable link | Nothing, if it is fast and clear; everything, if it fails under real devices and networks |
AI systems read websites; they do not invent your service area or pricing from nothing. Apps excel when the user already chose you. Websites bridge strangers to customers. Agencies that treat the three as interchangeable usually under-invest in the one place that still works when the user has never installed anything from the client.
Why slow and broken sites quietly stop being relevant
Irrelevance rarely arrives as a press headline. It shows up as fewer finished bookings, checkouts, or form submits on the same traffic.
A local restaurant with a four-second mobile Largest Contentful Paint loses menu readers to the map listing and the delivery app. A B2B vendor with heavy third-party tags fails Interaction to Next Paint on the pricing page; the buyer stays in the PDF someone emailed instead of starting a trial. A documentation site that errors for AI crawlers or returns bloated JavaScript may disappear from answers even when the product is fine.
Performance is not a vanity leaderboard. It is a filter on whether the destination still functions as a destination. We laid out the business case in numbers in The Real Cost of Poor Web Performance: A Data-Driven Analysis: delay shows up in bounce, conversion, and support load before it shows up in a board deck. For clients asking whether AI makes speed optional, the honest answer is the opposite. Smaller audiences mean each failed load costs more.
AI visibility adds a parallel failure mode. If crawlers cannot fetch the important pages quickly, or visitors leave before reading clear facts, citations and conversions both suffer. We split what agencies can measure first in Are We Visible in ChatGPT? What Agencies Can Measure First: whether models mention you for buyer-style questions, versus whether bots and humans can fetch and load your pages reliably. A site that is irrelevant to machines becomes easier to skip for people too.
What agencies should ship instead of "presence"
"Build us a website" should translate into deliverables a non-developer can test on a phone on a bad network.
- Name the pages people use to buy, book, or contact you. Home, pricing, booking, checkout, docs entry. Not every template deserves the same monitoring budget.
- Prove those pages load and respond. Scheduled lab runs plus field context where Chrome User Experience Report data exists. Occasional PageSpeed Insights pastes are not enough across a client portfolio.
- Publish facts AI and humans can extract. Hours, location, how pricing works, proof, policies. Vague marketing copy is invisible to both audiences.
- Report outcomes, not only scores. When analytics allow, tie Core Web Vitals changes on booking and checkout pages to form completions or booking starts.
Presence without performance is a brochure in a drawer. Relevance is a destination that survives the second click after an app, a map, or an AI answer sent the user your way.
If you manage many client sites, start a free trial to schedule PageSpeed monitoring on the pages that still matter, or run a free check on one important page and ask whether a stranger would finish the task there.
FAQ
Are websites dying in 2026?
No. Their role shifted. Fewer casual informational visits; more high-intent verification and transaction traffic. AI answers and apps handle discovery for many questions; the open web still anchors trust, payments, and durable content.
Do people still use websites or only apps?
Both. Apps win when people already use them every week. Websites win strangers, search, citations, and tasks that need a link someone can open without installing software.
Does AI search mean we do not need a fast website?
It increases the penalty for a bad one. AI systems read web content; users who follow citations arrive with sharper intent. Slow or broken pages waste visits that are already scarce.
What should a small business prioritize if it cannot redo everything?
Make the booking, checkout, or contact path fast on mobile, publish clear facts on one canonical page, and measure those URLs on a schedule. That beats a new blog theme.
References
- Search Off the Record podcast (Google Search Central)
- Google users are less likely to click on links when an AI summary appears in the results (Pew Research Center)
- The Real Cost of Poor Web Performance: A Data-Driven Analysis (Apogee Watcher)
- Are We Visible in ChatGPT? What Agencies Can Measure First (Apogee Watcher)
Top comments (0)