Seamless PWA Origin Migration: Move Domains Without Losing Users

Progressive Web Apps (PWAs) are increasingly used as installable, app-like experiences that businesses rely on for customer engagement and recurring traffic. However, changing a PWA’s domain has traditionally been risky, often resulting in broken installations, security issues, or lost users. With Chrome 150 and newer, you can now migrate a PWA to a new same-site origin far more seamlessly—preserving user trust, session continuity, and engagement.

Key Takeaways

• Chrome 150+ introduces support for seamless PWA origin migration between same-site domains.
• Proper planning of service workers, manifests, and redirects is essential to avoid user disruption.
• Same-site origin migration helps maintain installed PWAs, stored data, and user sessions during a domain change.
• Businesses can rebrand or restructure their domains without sacrificing performance, security, or SEO for their PWA.

---

Why PWA Origin Migration Has Been Hard Historically

PWAs are tightly bound to their origin (scheme, host, and port). This origin is central to browser security, caching, service workers, and how installed experiences are recognized by the operating system. Changing this origin has historically created pain points like broken icons, lost offline capabilities, and duplicated installations.

For businesses, this meant that domain changes—due to rebranding, mergers, or restructuring—could severely impact engagement. Users would often have to reinstall the PWA or manually discover the new domain, resulting in friction, support tickets, and sometimes churn.

Origin and the Security Model

The web’s security model treats each origin as an isolated container. A PWA installed from one origin cannot simply continue as the “same app” from another origin without explicit support. This isolation protects users but makes domain moves complex.

Before Chrome 150, switching a PWA from, for example, https://app.example.com to https://new.app.example.com typically required treating the new origin as a completely new app. That meant separate service workers, separate storage, and a new installation flow.

---

What Chrome 150 Changes for PWA Origin Migration

From Chrome 150 onwards, PWAs can transition between same-site origins in a way that is significantly smoother for the end user. While technical implementation details are controlled by the browser, the key idea is to allow the browser to recognize that a PWA at a new same-site origin is effectively the same application as the original.

Same-site origin migration enables you to move an installed PWA between related domains—such as subdomains or structured hostnames—without forcing users to reinstall or lose their stored data.

This is particularly important for organizations that:

• Move from subdomain-based apps to a more centralized structure, such as from https://app.example.com to https://example.com.
• Rebrand products and adjust domain naming, such as from https://oldbrand.example.com to https://newbrand.example.com.
• Consolidate multiple regional or product-specific origins into a unified app experience.

---

Understanding “Same-Site” in Practice

The term same-site does not merely mean "similar-looking" domains; it has a precise definition used by browsers for security and cookie handling. In simplified terms, two origins are same-site if they share the same registrable domain and are accessed with the same scheme (HTTP/HTTPS) and not across different top-level domains.

Typical Same-Site Migration Scenarios

• Subdomain to root domain: https://app.example.com → https://example.com
• Subdomain to subdomain: https://pwa.example.com → https://portal.example.com
• Path restructuring with origin shift: https://www.example.com/app → https://app.example.com

In these cases, origin migration support allows the browser to relate the old and new PWA installations, easing the transition.

---

Planning a Seamless PWA Domain Migration

To leverage Chrome 150’s capabilities effectively, you still need a careful plan. The browser provides support, but you must align your hosting, service worker, and application logic to avoid surprises.

1. Audit Your Current PWA Setup

Start by mapping the components that are tied to your existing origin:

• Service worker scope and file location (for example, /sw.js or /pwa/sw.js).
• Web App Manifest URL and fields (name, start_url, icons, id).
• Cache storage naming conventions and critical offline assets.
• IndexedDB/localStorage usage for user data or settings.
• Push notifications setup and any server-side logic tied to origin.

Understanding this baseline is crucial before making any changes at the domain or hosting level.

2. Align Manifests Across Origins

Chrome uses the Web App Manifest as one of the signals to identify a PWA as the “same” app. When moving to a new origin, keep core identity fields aligned so Chrome can associate them:

• Use a consistent id field across both origins where applicable.
• Maintain the same name and short_name unless rebranding is critical.
• Keep the icons set consistent, or at least maintain the primary icon set.
• Ensure the start_url makes sense on the new origin but remains functionally equivalent.

For example, if the old PWA starts at /dashboard and the new origin does the same, try to preserve this pattern: https://app.example.com/dashboard → https://example.com/dashboard.

---

Service Worker and Caching Considerations

The service worker is at the core of the PWA experience: offline access, caching, background sync, and more. When transitioning origins, you need to ensure that:

• The new origin serves a service worker with compatible logic.
• Old caches are cleaned up gracefully, and new caches are initialized effectively.
• Critical assets are pre-cached at the new origin to avoid performance regressions.

Transition Patterns for Service Workers

A common pattern is:

1. Deploy an updated service worker to the old origin that:
   • Serves strong redirects (such as 301) to the new origin for relevant routes.
   • Displays a lightweight notification or banner informing users of the new domain, if necessary.
2. Deploy a fully configured service worker to the new origin that:
   • Initializes required caches and offline routes.
   • Handles edge cases where users arrive via old bookmarks or deep links.

By controlling both ends of the transition, you minimize disruption while the browser aligns the installed experience with the new origin.

---

User Experience and Security During Migration

Origin migration is not only about technical correctness; it also affects trust and usability. A poorly handled transition can look like a phishing attempt, or it may raise security warnings.

Maintaining User Trust

To maintain confidence:

• Ensure HTTPS is enforced on both the old and new origins.
• Keep branding, design, and navigation recognizably consistent during the transition period.
• Use clear messaging in the UI if the domain name changes significantly (for example, new brand or new top-level path).

From a cybersecurity perspective, consistency and clarity help users distinguish legitimate changes from malicious redirects.

Handling Old Shortcuts and Bookmarks

Users may access your PWA via:

• Home screen or desktop shortcuts.
• Bookmarks and saved links.
• Push notification URLs.

Ensure that all these routes redirect cleanly to the new origin and that the PWA continues to open in its installed window or app shell instead of a generic browser tab where possible.

---

Impact on SEO and Web Hosting Strategy

While PWAs primarily impact user experience, domain moves are also tightly coupled with SEO and web hosting strategies. Search engines rely on stable URLs, redirects, and structured metadata when a site or app moves.

SEO Considerations During PWA Domain Moves

To minimize SEO disruption:

• Use permanent 301 redirects from old URLs to their equivalents on the new origin.
• Update your sitemaps and canonical tags to reference the new domain.
• Submit updated sitemaps to major search engines after the transition.

These steps help search engines understand that the content has moved, preserving rankings where possible and avoiding duplicate content issues.

Hosting and Infrastructure Alignment

From a web hosting perspective, origin migration may involve:

• Shifting to a new hosting provider or infrastructure stack.
• Reconfiguring CDN rules, edge caching, and SSL termination.
• Optimizing your performance budget, as new routes and domains may affect latency.

Aligning your hosting setup with PWA requirements—service worker caching, HTTP/2 or HTTP/3, and effective TLS—ensures that the migrated app remains fast and reliable.

---

Practical Example: Moving from app.example.com to example.com

Consider a SaaS product initially deployed as a PWA at https://app.example.com. The company decides to consolidate everything under the root domain, making the PWA available at https://example.com.

A high-level migration plan could include:

1. Prepare the new origin: Deploy the PWA shell, service worker, and manifest to https://example.com, mirroring existing functionality.
2. Maintain identity: Use a consistent app id, name, and icons in the manifest so Chrome associates the new origin with the installed experience.
3. Implement redirects: Configure 301 redirects at https://app.example.com to point to equivalent routes at https://example.com.
4. Monitor traffic: Track how users and installations shift from the old origin to the new one over time, using analytics and server logs.
5. Decommission gradually: Once the majority of users are consistently using the new origin, phase out the old one with appropriate sunset messaging.

With Chrome 150’s origin migration support, this process can preserve the installed PWA’s presence on user devices while smoothly re-pointing it to the new host.

---

Conclusion

Changing the domain of a PWA used to be a high-risk operation that could cost you users, performance, and search visibility. With enhanced support for same-site origin migration in Chrome 150 and above, businesses now have a more reliable path to evolve their domains while preserving user installations and trust.

By carefully coordinating your manifest configuration, service workers, redirects, and hosting infrastructure, you can deliver a domain transition that feels almost invisible to end users. This opens the door to rebranding, restructuring, or optimizing your web presence without sacrificing the hard-won adoption of your PWA.

---