SEO with Prerender
Galaxy provides an integrated pre-rendering service, Prerender.io, to optimize your Meteor app for search engines (SEO). The Prerender.io service is included as part of Galaxy at no additional cost. See https://prerender.io/ for more information about the Prerender.io service.
$ meteor add mdg:seo in your app’s directory to add the prerender package. Galaxy will automatically enable the Prerender.io service when you deploy your app.
If you’re using the spiderable package, please remove it, since the prerender and spiderable packages are not compatible with each other.
Confirm that the output contains the text that your site shows once the JS is run. If you only see a header and a reference to a script file, you may need to troubleshoot.
It’s easy to run a test prerender server on your machine to check for errors. As descibed at prerender, first run these commands:
git clone https://github.com/prerender/prerender.git
If your site is named example.com, then open another shell and use the command:
You should then see any relevant error messages, if you’re experiencing an issue.
Administration and Cache Freshness
The prerendering service offered by Galaxy is designed to provide a shared service across all apps in Galaxy, with pre-determined caching policies and no need for per app management or administration through the service.
We currently offer a guarantee of at most 4 days as the cache freshness policy. There is no login available to users.
If you need to trigger your recaches for specific pages, or need to recache more frequently, we recommend that you set up your own prerender.io service.
Using your own Prerender service
You can use your own Prerender service by configuring it in the application settings file (settings.json). If Galaxy finds a pre-configured Prerender service, then Galaxy will not configure the application to use Galaxy’s integrated Prerender.io service.
The token and service URL can be configured via your application’s settings.json like so:
If you intend to continue using Prerender’s hosted service with your own token, we recommend setting the
serviceUrl as above explicitly, because the npm package supporting prerender defaults to a non-secure
Refer to the package documentation for more information.