Skip to Content (Press Enter)
How is your experience with the OutSystems Community?
2021-07-14 10-21-07
Krunal Vyas
5Views
4Comments
How to setup SEO URL for PWA Mobile app?
Question
Mobile
SEO
PWA
OutSystems 11
Service Center

I want to solve a problem of setting up SEO friendly URL for a PWA application.

When i go SEO setup, I cannot select my mobile application as root app.

So how do i setup this Right now my pwa looks like something xyz.enterprise.com/appname

But i am looking to set it up like frindlyname.com/appname

Can someone help with the steps which i can follow to achieve this?

0
0
17 Jun
Copy Link
2023-12-26 10-35-28
OutSystems Neo
Staff
AI Generated

You’re trying to solve two different (but related) things:

  1. Custom domain: friendlyname.com instead of xyz.enterprise.com
  2. SEO friendly root app / URL rules for a PWA / Mobile app

Below is what you can and cannot do in O11, and what to ask your infra team to configure.

1. Custom domain (friendlyname.com)

OutSystems URLs are always:

https://<environment-host>/<application>/<module or screen>

To get friendlyname.com/appname instead of xyz.enterprise.com/appname, you need:

  • A DNS entry pointing friendlyname.com (or app.friendlyname.com) to your OutSystems front-end/load balancer.
  • Reverse proxy / CDN / load balancer rules that:
    • Terminate SSL for friendlyname.com
    • Forward traffic to xyz.enterprise.com
    • Preserve the path /appname/...

This is typically done on:

  • IIS / Nginx / Apache
  • An API Gateway / Load Balancer (F5, Azure Front Door, etc.)
  • A CDN that supports reverse proxy rules

OutSystems itself doesn’t change the domain name; it just serves under whatever host is used to reach it. For ODC there is a similar recommendation using a reverse proxy / CDN to map a root domain to an app’s path, and the same concept applies for OutSystems 11 environments.Redirect domains

So:

  • Work with your infra/network team to:
    • Create DNS friendlyname.com → your OutSystems environment endpoint
    • Configure reverse proxy so https://friendlyname.com/appname maps to https://xyz.enterprise.com/appname

Once that is done, your PWA will be reachable at the friendly domain.

2. SEO / Root app setup for a PWA (mobile app)

In OutSystems 11:

  • SEO Friendly URLs / SEO Rules are mainly defined per (Reactive/Web) module as described in the SEO docs.OutSystems Platform SEO Friendly URLs
  • Mobile apps (PWAs included) are still served from a web entry point, but the “root application” selection in SEO setup only lists web/reactive modules, not mobile modules.

That’s why you cannot select your Mobile app as root in the SEO setup dialog.

Workaround pattern

To get user‑friendly URLs and a default entry for your PWA, use a small Reactive/Web “router” module:

  1. Create a Reactive Web app (e.g. PWA_Router).
  2. In PWA_Router:
    • Add a single screen (e.g. Entry).
    • On OnInitialize or OnReady, do a simple RedirectToURL to your PWA’s entry URL (/YourPWAApp/YourStartScreen?…).
  3. In SEO/URL Rules:
    • Set this PWA_Router web app as the root application.
    • Configure your SEO friendly rule(s) so that:
      • / or /appname → PWA_Router.Entry, which then redirects to your PWA.
  4. Combine this with your reverse proxy:
    • friendlyname.com/appname → xyz.enterprise.com/PWA_Router/Entry
    • User lands on PWA_Router, then is redirected into your PWA.

This pattern is similar to how a tenant router/root app is used to route users to different applications via friendly URLs.Master Class on Multi-Tenancy

3. What you cannot do directly

  • You cannot set a Mobile application itself as the “Root Application” in SEO settings.
  • You cannot configure domain name (friendlyname.com) purely via Service Studio or Service Center; this needs infra/DNS + proxy configuration.

4. Concrete steps to request / implement

A. Infra team

  1. Create DNS record:
    • friendlyname.com → your OutSystems front-end / load balancer.
  2. Configure reverse proxy:
    • Host: friendlyname.com
    • Path: /appname → https://xyz.enterprise.com/PWA_Router/Entry (or directly to your PWA app path if you skip the router).

B. In OutSystems

  1. Create PWA_Router Reactive Web app.
  2. Implement Entry screen that immediately redirects to your PWA app’s main URL.
  3. Go to SEO / URL rules and:
    • Set PWA_Router as root app (if you want / to hit it).
    • Add rules so /appname routes to Entry.
  4. Publish and test:
    • Open https://friendlyname.com/appname and verify it loads your PWA.

If you describe how your infra is hosted (OutSystems Cloud vs self‑managed, IIS vs Nginx), I can outline an example rule (pseudo-configuration) matching your setup.

0
0
17 Jun
Copy Link
This answer was AI-generated. Please read it carefully and use the forums for clarifications
2021-07-14 10-21-07
Krunal Vyas
So if i setup a small react app for just redirection
So how will the url look like

example
Right now its like myenterprise.com/PWAapp/Home
So when i do the setup
It will redirect like this friendlyname.com/PWA_router
Which will then redirect to friendlyname.com/PWAapp/Home
Will this work?
0
0
17 Jun
Copy Link
2023-12-26 10-35-28
OutSystems Neo
Staff
AI Generated

Yes, that approach works, and you can avoid showing the PWA_Router in the URL if you configure it correctly.

There are two layers to think about:

  1. OutSystems SEO rules / routing
  2. Your external DNS / reverse proxy (friendlyname.com)

1. Inside OutSystems (SEO / Router app)

Assume:

  • PWA main URL:
    https://myenterprise.com/PWAapp/Home
  • Small Reactive router app: PWA_Router with screen Entry

What you do

  1. Create PWA_Router (Reactive Web app).
  2. Screen Entry:
    • On OnInitialize/OnReady, do a RedirectToURL to:
      • "/PWAapp/Home" (relative) or
      • GetEntryURL(PWAapp.Home) (if you prefer).
  3. In Service Center → Factory → SEO URLs:
    • Set PWA_Router as Root Application (if you want to handle / on that domain).
    • Create Site Rule:

How the internal URL behaves

From the OutSystems environment perspective:

  • User hits: https://myenterprise.com/appname
  • SEO rule maps /appname → PWA_Router.Entry
  • Entry executes and redirects to:
    https://myenterprise.com/PWAapp/Home

Notice that:

  • The user never sees .../PWA_Router/Entry in the URL.
  • They only see .../appname → then .../PWAapp/Home after redirect.

This is the same “traditional broker → reactive app” workaround described for SEO routing. SEO Friendly URLs not supported with Reactive Web Apps?

2. With friendly domain (external DNS / reverse proxy)

Now add your custom domain:

  • External domain: https://friendlyname.com
  • Internal OutSystems domain: https://myenterprise.com

You ask your infra team to configure:

  • DNS: friendlyname.com → your OutSystems front-end / load balancer.
  • Reverse proxy rule:
    • https://friendlyname.com/appname → https://myenterprise.com/appname

Because /appname in OutSystems is already mapped (via SEO rule) to PWA_Router.Entry, the flow becomes:

  1. User types: https://friendlyname.com/appname
  2. Reverse proxy forwards to: https://myenterprise.com/appname
  3. SEO rule: /appname → PWA_Router.Entry
  4. Entry redirects to: https://myenterprise.com/PWAapp/Home
  5. Proxy returns that as: https://friendlyname.com/PWAapp/Home (if it’s configured to preserve the host).

So, what does the user see?

  • Initial URL: https://friendlyname.com/appname
  • Final URL after redirect: usually
    https://friendlyname.com/PWAapp/Home
    (assuming your proxy doesn’t rewrite the host to myenterprise.com).

Direct answers to your examples

Right now its like myenterprise.com/PWAapp/Home

After the setup:

  • You configure a site rule so that /appname → PWA_Router.Entry.
  • You access it via custom domain:
    https://friendlyname.com/appname.

So when i do the setup
It will redirect like this friendlyname.com/PWA_router
Which will then redirect to friendlyname.com/PWAapp/Home
Will this work?

It will work, but you don’t need or want the /PWA_Router part to appear in the URL.

Correct flow should be:

  1. friendlyname.com/appname
    (proxy forwards to myenterprise.com/appname)
  2. SEO maps /appname → PWA_Router.Entry without changing the visible URL.
  3. Router redirects to /PWAapp/Home.
  4. Browser ends up at: friendlyname.com/PWAapp/Home.

If your SEO rule is created correctly as a site rule and not by navigating directly to /PWA_Router/Entry, the user should never see /PWA_Router in the address bar. SEO for OutSystems Reactive Web apps vs Traditional Web apps

If you tell me what you want the final visible URL to be (keep /PWAapp/Home or hide it also), I can suggest the exact SEO rule pattern to use.

0
0
17 Jun
Copy Link
This answer was AI-generated. Please read it carefully and use the forums for clarifications
2025-09-25 14-38-22
Lokesh Kumar Yadav

In OutSystems, SEO-friendly URLs can only be configured for Reactive Web or Traditional Web applications, not directly for Mobile/PWA applications. That’s why your mobile app does not appear as a selectable Root App in the SEO setup. For a PWA, the usual approach is to place the application behind a custom domain or reverse proxy. You can configure a custom domain such as friendlyname.com in your DNS and map it to your OutSystems environment (xyz.enterprise.com). Then, using a reverse proxy or web server configuration (like NGINX, IIS, or CloudFront), route requests from friendlyname.com/appname to the actual OutSystems PWA URL. After that, update the PWA manifest and base URLs if required, so the app loads correctly under the custom domain.

0
0
18 Jun
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.