Hi there,
I would like to ask you about best SEO practices in Meteor. How do you handle it on your sites and webapps?
Is it possible to get result like this?
Answers will be strongly appreciated. Thanks!
Hi there,
I would like to ask you about best SEO practices in Meteor. How do you handle it on your sites and webapps?
Is it possible to get result like this?
Answers will be strongly appreciated. Thanks!
As far as I know, Google generates this site links automatically. In one of our apps I get the same results if I type in it’s name on Google. We’ve used https://atmospherejs.com/manuelschoebel/ms-seo (for setting the recommended HTML tags) and https://github.com/jazeee/jazeee-meteor-spiderable (to generate a static HTML file for spiders) as packages in our project.
Thanks. Can you tell me more about results of using spiderable? Is it behaves like normal, static site for Google bot? And how to test it properly?
Using curl and command:
curl http://localhost:3000/?_escaped_fragment_=
gives me standard view-source page. Am I doing something wrong?
Yeah, Google’s bot get a fully rendered static HTML site. You have to install PhantomJS to make it run. The curl command should return the whole HTML code of your site, not only the initial HTML code which was generated by Meteor.
I would seriously consider using prerender.io - MDG seem to have given it their seal of approval for Galaxy deployments.
http://guide.meteor.com/deployment.html#seo
Prerender.io seems to be ok and they have a free plan
If you need you can also set up your own prerender.io: https://github.com/prerender/prerender
I’ve used it before, but it stopped working when I had to add force-ssl
to my project (because Chrome only allows camera access from secured sources).
You mean that you stopped using Prerender due to force-ssl
error, yes?
Yes, correct. Before Spiderable I’ve used a Prerender package from Node. When I got the problem with force-ssl
I’ve tried two Meteor packages, but they also didn’t work.
Hmmm this is strange because Galaxy pro accounts has Prerender.io as a standard preconfigured option and also they strongly recommend to always use SSL (this is also integrated). It will be good if someone from MDG could replay on this topic in the context of ssl and prerender.io.
Well, I’ve to say that it could be a problem that only occurs in my app, I’ve tried Prerender only on that one.
//Edit: Just saw that this issue seems to be fixed: https://github.com/dferber90/meteor-prerender/issues/10
Hi tomcio,
First of all sorry for my english as a Consultant SEO specialist maybe I can Give you some tips to help you get site links.
Remember what XTA said, Google generates these site links in an automated way, but you have several ways to help googlebot. Google shows these links on navigational queries like your “cnn” example. To make the things faster you had to find ways to get more links pointing to your website and using your brand name as anchor text. These links tends to point to your homepage, but try to get ones that point to some of the internal pages you would like to be shown through these site links.
Last thing to get in mind, Google tends to choose the internal pages that seems important to users. In almost of cases these pages are the ones shown in your navigation bar, because they are the ones that gets more Pagerank.
Hope this it helps
OK, thank you Walid. Your answer is very helpfull
Why you use Prerender before? Isn’t Prerender uses Phantom? I use Phantom and Spiderable and works great
Because Prerender saves CPU, they do the rendering on their servers.
How we do SEO in #meteor at scale. No prerender, no Galaxy - https://blog.zamphyr.com/how-we-do-seo-in-meteor-2f26706ec4f9
Thanks a lot for this!
As ES6 came into the game (Meteor doesn’t transpile NPM packages written in ES6) well known prerender is failed to render our pages. We’ve solved it with prerendering service.
I have written a guide for setting up basic SEO in Meteor here
Hope this helps someone.