title: Is search engine optimization on a mean.js full stack javascript application still a major issue an how should it be dealt with
body: <p>I am working on my first full stack javascript application using specifically mean.js as my start point, and I have started to become nervous and somewhat confused around the issue of search engine optimization (SEO).</p>
  
  <p>Has Googles recent efforts (within last year or so), to improve javascript crawling rendered this a non issue, or is this something I need to take account of in the planning and structuring of my project?</p>
  
  <p>If Google can crawl AngularJS/Ajax heavy applications now, why are we getting blog posts about solutions to the SEO issue:
  <a href="http://blog.meanjs.org/post/78474995741/mean-seo" rel="noreferrer">http://blog.meanjs.org/post/78474995741/mean-seo</a></p>
  
  <ul>
  <li>Is this type of solution necessary.</li>
  <li>Is this going to be as effective as server side rendering in terms of SEO.</li>
  <li>Are hash bang (#!) urls a necessary evil or just plain evil.</li>
  </ul>
  
  <p>I know questions about SEO and AngularJS have been asked before, but there seems to be so many differing opinions on this issue that I am lost, and it would be nice to have some thoughts that are more mean.js specific. My major worries are:</p>
  
  <ul>
  <li>If building a angularjs heavy implementation will make it an SEO black hole.</li>
  <li>If I will end up building practically the whole project again in static files just for SEO</li>
  <li>If I need to be looking at a server side rendering solution.</li>
  </ul>