Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

PWA SEO: Do Progressive Web Apps Rank Better?

Updated · 7 min read

Short answer No. Google ranks a progressive web app (PWA) by the same standards as any web page, and there is no PWA bonus. The things that help rankings, a fast page, HTTPS and a good phone layout, any website can have. The app parts, like a home-screen icon, offline mode and push alerts, help repeat customers, not search.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

Does a PWA rank better on Google?

No. Google judges the page, not the technology behind it. Its AMP documentation states the general rule:

"Google Search indexes AMP pages just like other web pages, and applies the same standard to all pages, regardless of the technology used to build the page." (Google Search Central: About AMP on Google Search)

What Google does reward is a good page experience, and that is not one switch you flip. Google's page experience guide says: "There is no single signal." Its checklist asks whether pages load securely (HTTPS), display well on phones and have good Core Web Vitals (Google's three speed and stability scores). A PWA can tick all three. So can a plain, well-built website.

Part of a PWAWhat it isDoes it change rankings?
Web app manifestA small file with the app's name and iconsNo. It only makes the site installable
Service workerA script that caches files and can work offlineNot directly. It can speed up repeat visits
HTTPSA secure connectionYes, it's on Google's page experience list. Every site should have it
Responsive layoutOne page that fits any screenYes, indirectly: Google ranks the phone version of your site

Even good speed scores are not a promise. Google wrote in 2023 that good Core Web Vitals "don't guarantee good rankings." Content and reputation still decide most of the order. For what speed is worth, see Core Web Vitals and ranking.

What is a PWA, in plain words?

A PWA is a website that can also behave like an app. Google's web.dev defines PWAs as "web apps built and enhanced with modern APIs" that still reach "any web user on any device with a single codebase."

In practice, three things turn a website into a PWA:

  1. HTTPS. Service workers only run on secure pages (MDN).
  2. A manifest. Chrome's install rules ask for a name, a start address, a display mode and two icon sizes, 192 and 512 pixels (web.dev: install criteria).
  3. A service worker, for caching and offline pages. Chrome no longer requires one to install from its menu, since version 108 on phones and 112 on desktop, but its install prompt still looks for one (Chrome for Developers).

On iPhone, the bar is now lower still. Since Safari 26, WebKit says: "By default, every website added to the Home Screen opens as a web app."

What a PWA does for a business (that isn't SEO)

The real benefits are for people who already know you.

BenefitWhat it meansLimits
Home-screen iconCustomers open you like an app, no app storeThey have to choose to install it
Offline pagesSaved pages still open with no signalBooking and payment still need a connection
Push notificationsReminders and offers on the lock screenOn iPhone, only once installed on the Home Screen, since iOS 16.4 (WebKit)
App store listingGoogle Play through a Trusted Web Activity; Microsoft Store through PWABuilderApple wants more than a website

On iPhone push, WebKit adds that a web app may ask for permission only "in response to direct user interaction," such as a tap on a button. On the App Store, Apple's guideline 4.2 reads: "Your app should include features, content, and UI that elevate it beyond a repackaged website." A PWA wrapped with nothing added risks rejection under that rule.

The famous results, such as Lancôme's 17% rise in conversions, come from big brands rebuilding slow mobile sites in 2016 and 2017 (web.dev case study). The same study reports 84% less time until the page could be used. Speed was the main change, and a fast ordinary site delivers that too.

The SEO risks a PWA adds

Most PWAs are built with JavaScript frameworks, and that is where search trouble starts.

RiskWhy it hurtsThe fix
Text built by JavaScriptGoogle reads it only after running your code, and other crawlers may not run itSend each page's text as HTML. Google: "server-side or pre-rendering is still a great idea"
One address for many screensGoogle indexes URLs. Addresses with `#/` aren't separate pagesA real URL per service, using the browser's History API
Content behind a promptGoogle says it expects its crawler "to decline user permission requests"Never hide services behind a push, location or install prompt
Content behind a tapGoogle "won't load content that requires user interactions (for example, swiping, clicking, or typing) to load"Put the main text on the page, not inside tabs that load on click
Relying on saved dataGoogle's renderer "does not retain state across page loads"; storage and cookies are clearedEvery page must work for a first-time visitor
Old cached filesA service worker can keep serving yesterday's versionVersion your files so updates replace the cache

Google's mobile-first indexing guide explains why the phone view matters most: "Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking."

How do I check my PWA's SEO in 2026?

Two tools from older guides are gone. Google retired the Mobile-Friendly Test and its Search Console report on December 1, 2023 (Search Central Blog); its old address now forwards to Lighthouse documentation (checked November 16, 2026). Lighthouse itself dropped its PWA score in version 12, used by PageSpeed Insights since May 10, 2024 (release notes), because Chrome changed its install rules.

What to use now:

  1. URL Inspection in Search Console, or Google's Rich Results Test: both show the page as Google renders it (Google: Fix search-related JavaScript problems).
  2. View source (Ctrl+U, or Cmd+Option+U on a Mac): search for a sentence from the page. If it's missing, crawlers that skip JavaScript see nothing.
  3. PageSpeed Insights or the Core Web Vitals report for speed.
  4. The Pages report in Search Console: count indexed pages against real ones. See crawled or discovered, not indexed.

Should a small business build a PWA?

Usually not for SEO. Build one when customers come back often and would use an icon on their phone.

Your situationGood fit?
Service business: plumber, dentist, accountant, salonNo. A fast, responsive site does the SEO job for less
Customers book or reorder weekly: gym, café, meal prepMaybe. The icon and reminders can earn repeat visits
You'd otherwise pay for an iPhone and Android appYes. One web app covers both, plus search
Your site builder already makes pages installableFine to leave on. It won't hurt rankings if pages are HTML

Example

Illustrative cases with invented numbers.

A roofing company (US dollars)

A developer quotes $12,000 to rebuild a 15-page site as a PWA "for SEO." Customers hire a roofer once a decade and won't install an icon. The owner spends $3,000 speeding up the current site and writing city service pages instead.

A yoga studio in Vancouver (Canadian dollars)

Members book classes three times a week. A C$6,000 PWA adds a home-screen icon and class reminders. Class and pricing pages stay pre-rendered as HTML, so search traffic holds.

A bakery with an app-builder site

The builder offers an "install as app" switch. The owner turns it on, checks URL Inspection, and sees each product page still has its own address and full text.

FAQ

Does Google treat a PWA as an app or a website?

As a website. Google crawls and ranks each URL by the same standard it uses for every page.

Will turning my site into a PWA hurt my rankings?

Only if the rebuild changes URLs or moves text into JavaScript. Keep every address, redirect changed ones, and check URL Inspection after launch.

Do I need a native app as well?

Rarely, for a local service business. Customers find you through search and maps, and a PWA can already sit on a home screen.

Is AMP better than a PWA for SEO?

Neither earns a bonus. Google applies the same standard to AMP pages as to any other page, so speed and content decide.

Different for you?

Keep learning

NextMobile-First Indexing: Why Responsive Design Keeps You SafeGoogle ranks the phone version of your pages. What mobile-first indexing checks, why responsive design avoids gaps, and how to find what your phone pages miss.

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: About AMP on Google Search
  2. Google Search Central: Understanding page experience in Google Search results
  3. Google Search Central Blog: The role of page experience in creating helpful content (April 2023)
  4. Google Search Central: Mobile site and mobile-first indexing best practices
  5. Google Search Central: Understand the JavaScript SEO basics
  6. Google Search Central: Fix search-related JavaScript problems
  7. web.dev: What are Progressive Web Apps?
  8. web.dev: What does it take to be installable?
  9. Chrome for Developers: Revisiting Chrome's installability criteria
  10. PageSpeed Insights release notes (Lighthouse 12.0, May 10, 2024)
  11. Chrome for Developers: Lighthouse overview
  12. MDN: Service Worker API
  13. WebKit Blog: Web Push for Web Apps on iOS and iPadOS
  14. WebKit Blog: News from WWDC25, Safari 26 beta
  15. Android Developers: Trusted Web Activities overview
  16. Microsoft Learn: Publish a PWA to the Microsoft Store
  17. Apple: App Store Review Guidelines
  18. web.dev case study: Lancôme rebuilds their mobile website as a PWA