The end of spiderable?


#1

Two days ago, on web master central blog, Google published an annoucement to say they will stop using the escaped url fragment to index AJAX generated pages.

It had be announced before. But now it’s real. What should we do ?


#2

I’m unsure about your question and not very deep into Meteor but they say:

Times have changed. Today, as long as you’re not blocking Googlebot from crawling your JavaScript or CSS files, we are generally able to render and understand your web pages like modern browsers. To reflect this improvement, we recently updated our technical Webmaster Guidelines to recommend against disallowing Googlebot from crawling your site’s CSS or JS files.

So does this not apply to Meteor?


#3

Nothing to worry. This is great.
Now Google can read our apps pretty well. But it can’t get data from DDP (as for our tests)

So, you need to use FastRender all the times.


#4

Oh, this is not great at all :frowning:

We have solutions but it would be nice if it could work out of the box.


#5

I’m quite not sure. Spiderable is always a bag. It causes a lot of RAM issues (even DDOS your app) and hard to debug issues.

We have to use services like prerender.io to get rid of these

But, now it’s easy. Just change your app to use FastRender if it isn’t. And it’s not that hard either.


#6

What does this mean for the SSR tutorial that you released on meteorhacks?


#7

That’s SSR. Like FlowRouter SSR. It could work without any issues.


#8

SSR solves everything :smile: