SEO Friendly URLs not supported with Reactive Web Apps?

Hi,

Does anyone know if SEO Friendly URLs don't work with Reactive Web modules?

In Create Site Rule on Root Application just appear Non-Reactive Modules.

Its a Bug or is not supported

Thanks.

Hi Marcior,

You are correct they are (not yet) supported for Reactive Web Applications.

This was mentioned on the Dutch OutSystems Meetup las Thursday by OutSystems.

So it is not a bug, it is not supported.

See also the below post from Tiago Simões (OutSystems).

Regards,

Daniel

Regards,

Daniel

Solution

Hi Marcior,

A temporary workaround was also mentioned:

To be able to use 'nice' url's, e.g. when you've got a publically accessible website, you can create a normal web-application that you can use the SEO URL's on. Under the hood you can navigate the user to the correct page in your reactive app.

Regards,
Lennart

Solution

Daniël Kuhlmann wrote:

Hi Marcior,

You are correct they are (not yet) supported for Reactive Web Applications.

This was mentioned on the Dutch OutSystems Meetup las Thursday by OutSystems.

So it is not a bug, it is not supported.

See also the below post from Tiago Simões (OutSystems).

Regards,

Daniel

Regards,

Daniel

Thanks Daniel.


Lennart Kraak wrote:

Hi Marcior,

A temporary workaround was also mentioned:

To be able to use 'nice' url's, e.g. when you've got a publically accessible website, you can create a normal web-application that you can use the SEO URL's on. Under the hood you can navigate the user to the correct page in your reactive app.

Regards,
Lennart


Yeah i could do that.
Thanks.

Lennart Kraak wrote:

Hi Marcior,

A temporary workaround was also mentioned:

To be able to use 'nice' url's, e.g. when you've got a publically accessible website, you can create a normal web-application that you can use the SEO URL's on. Under the hood you can navigate the user to the correct page in your reactive app.

Regards,
Lennart

Hi,

Just bumped into this SEO limitation thing and your workaround did it. Thanks for that.

Still, I have a neat subdomain (https://myapp.domain.com/) and, using your suggestion, I have the redirect to https://domain.com/myapp. Any idea on how to persist the https://myapp.domain.com/ from the traditional web to the reactive web app?

Thanks,

Bruno


Bruno Fonte wrote:

Lennart Kraak wrote:

Hi Marcior,

A temporary workaround was also mentioned:

To be able to use 'nice' url's, e.g. when you've got a publically accessible website, you can create a normal web-application that you can use the SEO URL's on. Under the hood you can navigate the user to the correct page in your reactive app.

Regards,
Lennart

Hi,

Just bumped into this SEO limitation thing and your workaround did it. Thanks for that.

Still, I have a neat subdomain (https://myapp.domain.com/) and, using your suggestion, I have the redirect to https://domain.com/myapp. Any idea on how to persist the https://myapp.domain.com/ from the traditional web to the reactive web app?

Thanks,

Bruno



I have the same question ... the other workaround using a traditional webapp as a "redirect engine" is okay for re-directs. BUT, if you want to keep the original URL we are stuck (e.g. so if users bookmark they get the nice SEO branded URL).

Has OutSystems given any ETA on when SEO URLs will be supported? 

Hi Bruce,

We have plans to address that until the end of the year, for now you can only use redirects.(BTW, there are other workarounds, like using JavaScript History.pushState(), but they are challenging). 

Cheers,
Tiago Simões

Bumping this thread as it's all I've been able to find...


We rely heavily on SEO urls for our public facing pages, and redirect entire domains to specific pages on specific applications, which cannot be done within React any more.
(And further, it throws the user outside of the domain they came in on, which compounds the confusion of the non-user friendly URLs)


Is there an updated ETA? This big push toward React doesn't seem likely to work well when established features are missing.


For others who are coming across this looking for the same information, I also created an Idea post to get more visibility to this oversight.

https://www.outsystems.com/ideas/8909/seo-urls-in-reactive-web-applications

Braxton wrote:

Bumping this thread as it's all I've been able to find...


We rely heavily on SEO urls for our public facing pages, and redirect entire domains to specific pages on specific applications, which cannot be done within React any more.
(And further, it throws the user outside of the domain they came in on, which compounds the confusion of the non-user friendly URLs)


Is there an updated ETA? This big push toward React doesn't seem likely to work well when established features are missing.


For others who are coming across this looking for the same information, I also created an Idea post to get more visibility to this oversight.

https://www.outsystems.com/ideas/8909/seo-urls-in-reactive-web-applications

Yes - us too - we really need SEO URLs badly!


Just be patient you guys. I’m sure the R&D team at OutSystems is working very hard to develop this feature for Reactive Web Applications.

Already, with the latest Platform Server 11.8.0 release, an impressive list of features were added, including a few important features for Reactive Web Apps.

Let’s give them the space to develop the SEO feature and I’m sure we will see it released soon.

Regards,

Nordin

Hi Bruce, Braxton,

We are currently working on improving multilingual support for reactive apps. Emails and SEO should come after that, we still do not have an ETA. 

In the meantime it's possible to redirect to different reactive apps depending on the domain, by using a SEO Friendly SEO rules in Service Center and a traditional web app acting as a broker (i.e. on the preparation of the traditional web default screen redirect to the reactive app, and you'll get something similar to when you navigate to http://www.apple.pt/ and are redirected to https://www.apple.com/pt/). Besides this workaround for site rules, redirect rules should also work.

If you are available we'll probably also get in touch with you both (and others in this thread) next week so we can understand your exact requirements. That can also help us determine how to better implement this feature in reactive.

Thanks,
Tiago Simões