I have successfully deployed my meteor website on amazon ec2. Website is available, but seems Google does not render the page when i try to search. I get “oops, looks like there’s no route on the client or the server for url meteor”, although the site is live and available.
I also tried Fetch as Google under Crawl menu in search console but i received the same response: “oops, looks like there’s no route on the client or the server for url meteor”.
I installed two packages: spiderable and prerenderio and added the following line in the head section:
In settings.json i added:
Have you tried testing how your site looks using prerender.io’s pre-render testing server? You can find their instructions on how to do this here. If you already have your meteor app running locally you’ll want to make sure you change the default pre-render test server port to something other than 3000. Then add the PrerenderIO .prerenderServiceUrl option to your settings.json pointing to your pre-render test server.
Yes, first i tested localy on port 3030. It showed the navigation bar and instead my home template, i got “oops, looks like there’s no route on the client or the server for url meteor”. Then i removed the prerenderServiceUrl from settings.json and deployed on ec2 with mup deploy. I have also installed the phantomjs on my server, but i still get this message “oops looks like…” when i try to crawl from search console.
I removed the spiderable package, and the “prerenderio.set(‘prerenderToken’, ‘67QTVPGuDP2tK9rVFMKC’);” from Meteor.startup. I have only the configuration in settings.json:
I tried once again to crawl with webmasters tool but no success.
Well, I can only tell you my setup. I’ve installed Spiderable on my server and used this package. Don’t forget to remove the original Spiderable and/or the Prerender package from your Meteor application.