Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Angular 6 SEO in legacy J2EE Apps - Suggestions are appreciated #453

Closed
swamytalam opened this issue Sep 23, 2018 · 1 comment
Closed

Angular 6 SEO in legacy J2EE Apps - Suggestions are appreciated #453

swamytalam opened this issue Sep 23, 2018 · 1 comment
Labels
comp: init Init Package status: wontfix Does not depend on this project type: question Conversation to figure out the action steps.

Comments

@swamytalam
Copy link

I'm submitting a...


[ ] Bug report  
[ ] Feature request
[x ] Documentation issue or request

In package


[x ] @ng-toolkit/init
[ ] @ng-toolkit/serverless
[ ] @ng-toolkit/universal
[ ] @ng-toolkit/pwa
[ ] @ng-toolkit/firebug

Current behavior

Hi, Thank you very much for this toolkit, it works amazing and providing SEO benefits for Angular apps for newly built apps or the Angular only apps. We have situation where we had homegrown Application build with J2EE and we are migrating to Angular on UI side but based on how its designed we cant convert the entire app as Angular so we are using hybrid approach which is main JSPs are bundled with Angular Apps. Its working great from the feature perspective. We are generating the /dist folder from angular app and copying the the resources of legacy ui/js code base, however we lost the SEO as we don't use NODE/ Express in the PROD run time. Can you recommend some options to achieve SEO here without writing entire UI layer in Angular at a time. Thanks a lot !!

Expected behavior

Minimal reproduction of the problem with instructions

Example repository

What is the motivation / use case for changing the behavior?

Environment


Angular version: X.Y.Z


- Node version: XX  
- Platform:  

Others:

@KingDarBoja KingDarBoja added the comp: init Init Package label Oct 25, 2019
@KingDarBoja
Copy link
Collaborator

Hello @swamytalam,

Even though the Angular documentation states at Universal Web Server section:

Any web server technology can serve a Universal app as long as it can call Universal's renderModuleFactory() function. The principles and decision points discussed here apply to any web server technology.

The reality is that we depend on Angular Universal and its core features to support SEO. So far, looks like it is only supported on NodeJS/Express and ASP.NET as you can check at the official repo.

But don't panic! The Angular Universal team is working on bringing this feature for different languages as seen in this issue

@KingDarBoja KingDarBoja added type: question Conversation to figure out the action steps. status: wontfix Does not depend on this project labels Oct 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp: init Init Package status: wontfix Does not depend on this project type: question Conversation to figure out the action steps.
Projects
None yet
Development

No branches or pull requests

2 participants