Just got html snapshots working with the help of html-snapshot node module & following htaccess.RewriteCond %{REQUEST_URI}  ^/$RewriteCond %{QUERY_STRING} ^_escaped_fragment_=/?(.*)$RewriteRule ^(.*)$ /snapshots/%1? [NC,L]It is an angular application, but the question is universal to javascript spas/seo. Looked around the web found a good amount of articles but nothing complete which is surprising since seo is pretty important. In any case 3 questionsUsing google fetch to confirm the proper outcomeThe rendering of the snapshot pages: Is the intention not to worry about the css or images or possible layout issues. For example, here is an example of a page of mine. The links and the main content are overlapping each other. Is that something we should be concerned about?Orange warming redirected label: This message is only warning us of the expected redirect, not that there is an issue that need to fix?See imageSubmit to index: Should we? My first assumption was not to and just make sure site and that is submitted.
Is this the expected/wanted outcomes using html snapshots and google fetch? SEO/SPA
seo;fetch as google
So with the help of @Quentin & this link that was provided, I got enough to answer to my question. It's recommended not to use the escaped fragment conventionAnd if you are looking to use it with the intention to degrade gracefully, suit other search engines the bottom line is to not use snapshots or at least in this convention. According to googleIn general, websites shouldn't pre-render pages only for Google -- we expect that you might pre-render pages for performance benefits for users and that you would follow progressive enhancement guidelines. If you pre-render pages, make sure that the content served to Googlebot matches the user's experience, both how it looks and how it interacts. Serving Googlebot different content than a normal user would see is considered cloaking, and would be against our Webmaster Guidelines.