loading...

Discussion on: What I learned about SEO from using the 10 most used JS frameworks

Collapse
jbobbink profile image
Jan-Willem Bobbink Author

Hi Lauri, how do you come to the conclusion that bringing in valuable traffic from search engines is solving a problem for myself? There are numerous examples where sites lost traffic due to depending on Google taking care of the client side rendering setup. Those companies had to sent people home because revenue was gone.

Collapse
lauriy profile image
Lauri Elias

What I mean is why use SPA frameworks at all if you're going to be building a full server-side app AND a SPA on top. You're resorting to workarounds-for-workarounds: 'we need tree shaking in the CI pipeline' - 'why?' - 'the app is too big' - 'why?' - 'we used a framework and 11000 packages' - 'why?' - 'you wanted autocomplete...' You admit that even the most powerful indexer, Google, is going to have trouble with your content at some point, you have to keep monitoring messing up your ranking at all times, every new dev joining is going to stumble on deciding whether something should be pre-rendered, how to do cache invalidation, etc. It all sounds like you're building Facebook while not working at Facebook.

Thread Thread
jbobbink profile image
Jan-Willem Bobbink Author

Ahh like that. Yes, fully agree. Ideally we all work with a much more simple approach to web interfaces but unfortunately to many grab the trending technologies instead of looking to what is the most suitable one aligning with the company objectives.