Some questions

[yubozhao]

Hi @ayal

First, good job on this package. I am just having some questions on this topic. I think you might have the answer I seek.

1. Could you tell me the difference or advantage add the header on the server side rather than client side? I am really new in this topic. Would love you to fill out some blanks in my head.
2. Do you happen to know in what order for connectHandler(WebApp) to handle incoming request? What if Iron router handle it before this package?(I am assuming the order matters for connectHandler)

Thank you for the package. Love to hear back from you.

[mitar]

Could you tell me the difference or advantage add the header on the server side rather than client side? I am really new in this topic. Would love you to fill out some blanks in my head.

You have to do it on the server side because this is what spiders fetch. They don't run JavaScript.

[yubozhao]

Hi @mitar Thank you so much for your answer. I am trying to understand this thoroughly, got couple more follow up questions. :)

So lets assumed a case that I have iron router installed and spiderable installed as well. I have set meta data with IR's beforeAction hook. When I do curl -i APPADDRESS?escaped_fragment=, it returns correct header. And this is not what google spider will get?

[yubozhao]

Also @mitar From Headly's code, it add metadata into headers, if useragent is one of the 2(facebook and twitter). How would it helps for Googlebot?

Oops Mybad, It said in description it works for facebook's og metadata.

[mitar]

If you want support for Google, use spiderable.

[mitar]

And yes, interaction between spiderable, headly, and iron-router is probably not well defined.

[yubozhao]

Just rereading the blog post from Matt about spiderable. He said "When a spider requests an HTML snapshot of a page, the Meteor server runs the client half of the application and returns the full HTML generated by the client code."

That is where I got really confused about adding meta data on the server side.