Top 3 reasons to not use prerender for AngularJS websites

AngularJS, the framework that pioneered Single Page Applications, has number of challenges when it comes to indexing web pages. 

Pre-Render started off as one-size fits all solution that can render pages using PhantomJS, however, the reality is strikingly different. Pre-render helps crawlers discover your website, however, it will not help you to increase search rankings. Here are some main reason why you should not use prerender.

When was the last time you saw an AngularJS website rank higher; NEVER! 

Top 3 reasons to not use AngularJS

pre-render pages differ significantly in content than your actual websites.

  1. Pre-Rendered pages are not always similar to your canonical website. Google heavily penalizes websites that are not consistent between the actual experience and what GoogleBot can detect.

  2. page-refresh caches are viewed negatively by Google Bot. PreRender on average, refreshes cache every 7-days, unless you explicitly ask for refresh. This hurts, BADLY! The reason, your visitor reads your home page that has content "X", GoogleBot however has content "Y" indexed, and now Google thinks that you are doing something nefarious just to gain high search rankings.
  3. GoogleBot can only crawl <a href> links that have an actual URL. <a href="/pricing.html"> can be perfectly crawled and indexed, however, <a ng-click=showPrice();> cannot be crawled by Google. About 60% of links on our dynamic pages use ng-click() and thereby cannot be seen or indexed by Google.

Troubled with some, if not all of these problems, for your AngularJS website? WebFast, our drop simple solution fixes all these problems with one single line of code.

Click here to contact us and we can get started right away!

Founder @ WebFast (
Making AngularJS websites rank higher.