I've been using prerender-node and only ever tested that it is working by appending <c

It would be something like this: <div class="snippet-clipboard-content notranslate

I agree! This is an old comment :) It should be: <div class="snippet-clipboard-con

Not rendering based on user agent, only ?_escaped_fragment_= about prerender-node HOT 8 CLOSED

prerender commented on August 21, 2024

Not rendering based on user agent, only ?_escaped_fragment_=

from prerender-node.

Comments (8)

thoop commented on August 21, 2024

Which user agents did you try? Using the Googlebot user agent should not cause a prerendered page because that would be cloaking. We use the _escaped_fragment_ protocol for Googlebot.

Here's the list of user agents we check for: https://github.com/prerender/prerender-node/blob/master/index.js#L37

Let me know if there are any user agents that we should add.

from prerender-node.

sabrehagen commented on August 21, 2024

Using my Chrome user-agent changing extension I tried Googlebot, Yahoo, and BingBot. That would explain why all three didn't work. Sorry to trouble you, and good to know you're looking out for us with cloaking.

I guess I would have to ask, is it guaranteed that Googlebot will always use escaped_fragment when querying? We had prerender in production for about a month and didn't see much happen to our indexes in google. For example, we still had angular curleys in our meta description.

Edit: I was just observing our logs and this came through: http://i.imgur.com/7C2Mjhk.png
Is it correct to say this is Googlebot crawling our site? If so, the prerendered version wasn't served back, as we log when that happens too and it wasn't in the log. At this point I don't expect the problem to be with the library, just me.

from prerender-node.

thoop commented on August 21, 2024

If you are using html5 push state (or any URL without the #!), you need to have <meta name="fragment" content="!"> in the <head> of the page. That is the signal to Google and Bing that you want them to use the _escaped_fragment_ when querying. They will then see that meta tag and re-request the page with the escaped fragment URL, which will then be matched by the middleware and proxied to our service.

So make sure you have that meta tag in your pages and then they should be requesting the escaped fragment URL.

from prerender-node.

sabrehagen commented on August 21, 2024

Ah! That was it! I've never come across that in my reading on the internet - how odd...you've saved me. Thank you.

I was just reading the code to see if there was a way to add our own bot user agents to the crawlerUserAgents array at runtime. Is this a planned feature?

from prerender-node.

thoop commented on August 21, 2024

It would be something like this:

var prerender = require('prerender-node');
prerender.set('crawlerUserAgents', ['facebook', 'twitter']);
prerender.set('prerenderToken', 'YOUR_TOKEN');
app.use(prerender);

That will override the crawlerUserAgents list so make sure you add all of them to that list.

from prerender-node.

sabrehagen commented on August 21, 2024

Ahh, nice convenience method. Didn't realise until I looked into the code how it worked. Thanks for that!

from prerender-node.

stephengardner commented on August 21, 2024

I'd recommend prerender.crawlerUserAgents.push('userAgent'); (use push, not set)

from prerender-node.

thoop commented on August 21, 2024

I agree! This is an old comment :) It should be:

var prerender = require('prerender-node');
prerender.crawlerUserAgents.push('userAgent'); //adds a user agent to the list instead of overriding
prerender.set('prerenderToken', 'YOUR_TOKEN');
app.use(prerender);

from prerender-node.

Not rendering based on user agent, only ?_escaped_fragment_= about prerender-node HOT 8 CLOSED

Comments (8)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

Jobs