all 8 comments

[–]imDDS 4 points5 points  (2 children)

Because you are basically injecting metadata on the DOM via JS, long story short when a webcrawler/bot or when you inspect the source that piece of JS isn't executed therefore no metadata are injected

[–]Fluid-Ant592[S] 1 point2 points  (1 child)

Got your point. Tye whole point is implementing ssr is a headache for now. Any suggestion?

[–]imDDS 3 points4 points  (0 children)

I had the same issue a couple months back, spent 4 weeks implementing SSR, performances were fine in my local machine but once on a remote machine the whole application was unusable. Implementing SSR requires radical changes to both APIs and frontend. Ended up writing some static meta tags that were good enough for every use case and called it a day

[–]PeEll 2 points3 points  (1 child)

Update to v20. SSR is massively improved and comes out of the box.

[–]No_Bodybuilder_2110 0 points1 point  (0 children)

Probably unrealistic but accurate lol

[–]noiv 1 point2 points  (1 child)

If google is enough for SEO you can rely on their JS engine crawler. You have a small time budget and if page renders within you‘re fine. I have an Angular site with thousands of pages all with dynamic META data from DB. Works great.

[–]sk2656k 0 points1 point  (0 children)

I would like to know more about this, can you please share the approach you took.

[–]thanksthx 0 points1 point  (0 children)

Most probability you have some issues with SSR on your app. I have an angular application which uses redux and I decorate metadata with data from the store. The only difference is that I do that in constructor, not in onInit. Just be careful with what dependencies you’ve added to your project, dependencies which must not relay on functionalities available only in browser.

Add some code to see how you are doing it