4 ms·
ok I finally can read your article. And sorry you are missing the main point. Rendering static content client side using JavaScript is a bad idea, even if you
by kephra 12y ago
ok I finally can read your article. And sorry you are missing the main point.
Rendering static content client side using JavaScript is a bad idea, even if you have fast network in terms of latency and speed.
The main problem with this AJAX antipattern is, that it blocks all spiders and search engines. So you should not do that, if you are not Google docs, who can inject the content into their own search engine, and wants its content not to appear on other search engines.
As a rule of thump: Do not use JavaScript for anything that should be indexed by a search engine. Instead use JS only when interacting with humans, e.g. for blog comments, checkout and payment. Hiding comments by making the comment system AJAX might be a good policy for a blog, if you do not want the comments to appear in search. But the blog posting itself should be static content.
- nawitus 12y agoGoogle executes JavaScript for indexing these days.
- LoSboccacc 12y ago*Interpreter JavaScript to extract linked resources.
- Svenstaro 12y agoAs I saw the other day, whatever Google does is far from sufficient.
- user_0001 12y agoGoogle has been able to read js / ajax for years
- vbezhenar 12y agoIs there some definitive information about how good Google at this task? What JS constructions works, what does not work. I doubt that Google can index any JavaScript. And don't forget about other search engines. It's not very good to keep site indexable by Google and not indexable by other search engines.
- technomancy 12y agoSorry, but Google is not the only bot that matters.
- slifin 12y agoWhat do you guys think about ajaxing comments for SEO vs marking them up as UserComments in microdata? Do you think the latter would work?
- kephra 12y agoIt depends. There should be a way to find and index those user comments, if they have a positive SEO value. This conflicts with the goal, that blog post itself should be at delivered as a static content, at best from a static file, to withstand a HNDDoS even on low budget. So one solution could be to run the comment system as AJAX, moderate user comments a few times a day. Click [x] on every comment, you want to appear in the static page, and [generate comments] to generate a new static page, with the new public available comments. Give each user a cookie and a localStorage, to show their comments in their own AJAX version, even if you blocked them from both the AJAX comment system and the public one.