@hv_ is on PowPing!

PowPing is a place where you can earn Bitcoin simply by socializing, for FREE.
Never tried Bitcoin? It's OK! Just come, socialize, and earn Bitcoin.
Check out hv_'s activities


visit channel home
Total Economy: 0 USD
Going serverless you might lose SEO - but here is help https://www.ironpaper.com/webintel/articles/what-is-an-seo-page-definition-and-best-practices/ / maybe actioncable, pre-rendering (server-fake html stuff ) ... ? Some examples appreciated!
People use "Serverless" to mean different things, but the trendy usage is something like AWS Lambda. It's not actually "Serverless" because the server does exist on AWS server. So what they actually mean by "serverless" is "not having to manage server". I think what you're talking about is SPA (Single Page App). These are the trendy Javascript frameworks like React and Vue, which construct UI on the frontend instead of rendering server side. This has SEO issues like you said. So they came up with server side rendering of the client side rendered apps, so that the UI is already rendered when the page loads for the first time. But nowadays you don't have to worry too much about these things if you follow the best practices because search engines like Google have started handling SPAs well.
hv_ replied:
I wonder how that ll go on client side esp if content is created behind oauth / 'private'. How could google sneak in here ? So some publish function needed I d say + proper disclaimer....
musiq replied:
Google crawls SPAs by letting their crawlers simulate the "server side rendering". Server side rendering has nothing to do with crawling private content. Those are off limits for Google. What you're thinking of is called "Deep Web" https://en.wikipedia.org/wiki/Deep_web and by definition those are not crawled by Google or any other search engines.