Comments on: SEO for AJAX http://www.johnon.com/270/seo-for-ajax.html I think there's an opinion on that subject lying around here somewhere.... Fri, 12 Mar 2010 15:47:28 +0000 http://wordpress.org/?v=2.0.7 by: john andrews http://www.johnon.com/270/seo-for-ajax.html#comment-13489 Fri, 06 Apr 2007 19:54:50 +0000 http://www.johnon.com/270/seo-for-ajax.html#comment-13489 <b>UPDATE:</b> I never intended this post to be an SEO for AJAX tutorial. It's a blog post from an SEO working in the field of SEO, on AJAX and other, <a href="http://www.johnon.com" title="Advanced SEO" >advanced SEO</a> topics. BUT, I can certainly clarify and will do so in another AJAX/SEO post on www.johnon.com. UPDATE: I never intended this post to be an SEO for AJAX tutorial. It’s a blog post from an SEO working in the field of SEO, on AJAX and other, advanced SEO topics. BUT, I can certainly clarify and will do so in another AJAX/SEO post on www.johnon.com.

]]> by: johnon.com - John Andrews - » Does “Advanced SEO” Even Exist? http://www.johnon.com/270/seo-for-ajax.html#comment-13488 Fri, 06 Apr 2007 19:52:24 +0000 http://www.johnon.com/270/seo-for-ajax.html#comment-13488 [...] When I sit in a session at PubCon, the “SEO” panelists repeatedly say things like “you need to make your title tags unique” and “your non-www needs to 301 to your www” and I get so bored I choose to sit next to IncrediBill, just to keep things interesting. But when I work with SEO and AJAX, I get a headache from the depth of the challenge. [...] […] When I sit in a session at PubCon, the “SEO” panelists repeatedly say things like “you need to make your title tags unique” and “your non-www needs to 301 to your www” and I get so bored I choose to sit next to IncrediBill, just to keep things interesting. But when I work with SEO and AJAX, I get a headache from the depth of the challenge. […]

]]> by: john andrews http://www.johnon.com/270/seo-for-ajax.html#comment-11557 Sat, 31 Mar 2007 05:46:58 +0000 http://www.johnon.com/270/seo-for-ajax.html#comment-11557 @Daniel: It looks like you've assigned unique URLs to the content, but outside of context. That's a necesary step, right? But you know the context for a bulk of pages, if you know the rationale behind the asynchronous loading (as far as content inclusion goes). A step better is to clean up those URLs in typical SEO fashion,of course, using a front controller or rewrite mapper for your pseudo sitemap. But if possible, why not define views into that content that are context aware? You're almost there anyway. It's difficult to suppose solutions outside of the context of the app. Some of the AJAX stuff I have seen really fits the term "mashup" because that's what it is.. a mish-mash. So I leave it alone, and index a psuedo-sitemap that is structured. @Daniel: It looks like you’ve assigned unique URLs to the content, but outside of context. That’s a necesary step, right? But you know the context for a bulk of pages, if you know the rationale behind the asynchronous loading (as far as content inclusion goes).

A step better is to clean up those URLs in typical SEO fashion,of course, using a front controller or rewrite mapper for your pseudo sitemap. But if possible, why not define views into that content that are context aware? You’re almost there anyway.

It’s difficult to suppose solutions outside of the context of the app. Some of the AJAX stuff I have seen really fits the term “mashup” because that’s what it is.. a mish-mash. So I leave it alone, and index a psuedo-sitemap that is structured.

]]> by: Daniel R http://www.johnon.com/270/seo-for-ajax.html#comment-11153 Fri, 30 Mar 2007 06:33:10 +0000 http://www.johnon.com/270/seo-for-ajax.html#comment-11153 Sorry, I didnt realize HTML codes were valid for comments. Here's a retry: <blockquote> <p>Basically, the navigation system would be updated from</p> <p><a href="getContent('fiction','dickens');">Fiction &gt; Dickens</a></p> <p>to</p> <p><a href="http://client.com/books.jsp?scene=fiction&amp;author=dickens">Fiction &gt; Dickens</a></p> </blockquote> Sorry, I didnt realize HTML codes were valid for comments. Here’s a retry:

<p>Basically, the navigation system would be updated from</p>
<p><a href="getContent(’fiction’,'dickens’);">Fiction &gt;
Dickens</a></p>
<p>to</p>
<p><a href="http://client.com/books.jsp?scene=fiction&amp;author=dickens">Fiction
&gt; Dickens</a></p>

]]> by: Daniel R http://www.johnon.com/270/seo-for-ajax.html#comment-11146 Fri, 30 Mar 2007 06:12:37 +0000 http://www.johnon.com/270/seo-for-ajax.html#comment-11146 John, Interesting post, but I'm not sure if that absolutely works for an outside agency coming to a client with a large AJAX/DWR/FLEX driven website. We are working on a case where a JS-driven navigation links to over > 2,000 pages (or rather "content scenes" since its all AJAX). It is AJAX driven via a custom CMS system and it looks like the chief purpose of the asynchronous updates is to keep load time to a minimum (the "scenes" has plenty of copy and Flash). Strategically creating static pages is not an option because of the massive amount of content in AJAX and the CMS system that exist on the site already. What we've opted for is creating a hybrid system that is quasi-sitemap but not quite. Basically, the navigation system would be updated from <a href="getContent('fiction','dickens');">Fiction > Dickens</a> to <a href="http://client.com/books.jsp?scene=fiction&author=dickens">Fiction > Dickens</a> So now, the search engines follow the HREF, while the humans follow onClick. Look forward to hearing your thoughts. John,

Interesting post, but I’m not sure if that absolutely works for an outside agency coming to a client with a large AJAX/DWR/FLEX driven website.

We are working on a case where a JS-driven navigation links to over > 2,000 pages (or rather “content scenes” since its all AJAX). It is AJAX driven via a custom CMS system and it looks like the chief purpose of the asynchronous updates is to keep load time to a minimum (the “scenes” has plenty of copy and Flash).

Strategically creating static pages is not an option because of the massive amount of content in AJAX and the CMS system that exist on the site already. What we’ve opted for is creating a hybrid system that is quasi-sitemap but not quite.

Basically, the navigation system would be updated from

Fiction > Dickens

to

Fiction > Dickens

So now, the search engines follow the HREF, while the humans follow onClick.

Look forward to hearing your thoughts.

]]>