Jude:
On 12-02-28 10:06 AM, "jude" <flexcapaci...@gmail.com> wrote: >Here is my comment [2]. > >I think SEO search results come down to popularity. Is everyone linking to >your page? It might have something to do with Google analytics. How long >people stay on your page. DN: Amen brother! That is correct. > >But as a content creator I think it's up to the search engine to find and >index my site. I'm not going to do the search engines job. It's their job >to find my site and index it. That doesn't mean I won't help them. DN: now you're two for two in my books. They usually do this based on everyone else linking. The best way to force google to index a site is to use blogger and build links. Google owns blogger and it seems to work much faster for indexing than other blog platforms. > >I think if we focused on making amazing Flash and Flex websites that >people >want to visit the search engine companies would spend more time on making >their search engines work with it. DN; now 3 for 3 in my books. > > >Solutions > Link Manager type of support with some or all of the below [3] [4] [5] > Site map that has user URL and content URL > Site map that has flash / ajax enabled URL, html page URL and content >URL > >With both of the above solutions we could create or have a gui to create a >sitemap.xml file that defines the fragments our apps listen for and the >redirect links to get the raw content. We could also have the compiler or >ant task support the creation of multiple HTML wrapper pages that are >identical to the main wrapper page except in their name and / or the >option >of embedding the content into the page (if html) or if dynamic content it >would point to a dynamic page. DN: This is perhaps one of the first solid ideas I have heard. This might involve extensions to the site map.xml (I haven't looked at it for a while) but very well worth the time. Being able to map to a page that has state 1, state 2 and state 3, but 2 and 3 are not put into active memory until the app is interacted with is problematic. Authoring using the deep linking is much better IMO as it adheres to the one resource <-> one URI principle. Now this comes back to the original question of "what can be done on this list via the SDK?". Being able to generate this artifact would be a good idea IMO. Thanks Duane > > > >Example sitemap.xml ><site> > <page name="home" url="http://example.com/main/#home"; rawcontent=" >http://example.com/main.php?page=home"; html="http://example.com/home.html"; >/> > <page name="products" url="http://example.com/main/#products"; >rawcontent=" >http://example.com/main.php?page=products"; >html="http://example.com/products.html"/> ></site> > >Site.xml ex 2 ><site> > <page name="home" url="http://example.com/main/#home"; ajax=" >http://example.com/main.php?p=10"; /> > <page name="products" url="http://example.com/main/#p=10"; ajax=" >http://example.com/main/main.php?p=10"; /> ></site> > > >If we supported something like this and just started using and uploading >it >in our projects it might remove the complexities for the search engines. > > >[1] >http://googlewebmastercentral.blogspot.com/2009/10/proposal-for-making-aja >x-crawlable.html >[2] >http://googlewebmastercentral.blogspot.com/2009/10/proposal-for-making-aja >x-crawlable.html?showComment=1256080765377#c3966241161139678970 >[3] http://www.assembla.com/wiki/show/flexcapacitor >[4] http://www.youtube.com/watch?v=dnrx30KahIc >[5] http://www.youtube.com/watch?v=KmIz6Upc6dY
