MatrixAdapt | Logiciel de gestion d'Entreprise, Création et référencement des sites web

salam every one, this is a topic from google web master centrale blog: Written by Mark Berghausen, Search Quality Team

We occasionally get questions on the Webmaster Help Group about how webmasters should work with Adobe Flash. I thought it would be worthwhile to write a few words about the search considerations designers should think about when building a Flash-heavy site.

As many of you already know, Flash is inherently a visual medium, and Googlebot doesn't have eyes. Googlebot can typically read Flash files and extract the text and links in them, but the structure and context are missing. Moreover, textual contents are sometimes stored in Flash as graphics, and since Googlebot doesn't currently have the algorithmic eyes needed to read these graphics, these important keywords can be missed entirely. All of this means that even if your Flash content is in our index, it might be missing some text, content, or links. Worse, while Googlebot can understand some Flash files, not all Internet spiders can.

So what's an honest web designer to do? The only hard and fast rule is to show Googlebot the exact same thing as your users. If you don't, your site risks appearing suspicious to our search algorithms. This simple rule covers a lot of cases including cloaking, JavaScript redirects, hidden text, and doorway pages. And our engineers have gathered a few more practical suggestions:

1. Try to use Flash only where it is needed. Many rich media sites such as Google's YouTube use Flash for rich media but rely on HTML for content and navigation. You can too, by limiting Flash to on-page accents and rich media, not content and navigation. In addition to making your site Googlebot-friendly, this makes you site accessible to a larger audience, including, for example, blind people using screen readers, users of old or non-standard browsers, and those on limited low-bandwidth connections such as on a cell phone or PDA. As a bonus, your visitors can use bookmarks effectively, and can email links to your pages to their friends.
2. sIFR: Some websites use Flash to force the browser to display headers, pull quotes, or other textual elements in a font that the user may not have installed on their computer. A technique like sIFR still lets non-Flash readers read a page, since the content/navigation is actually in the HTML -- it's just displayed by an embedded Flash object.
3. Non-Flash Versions: A common way that we see Flash used is as a front page "splash screen" where the root URL of a website has a Flash intro that links to HTML content deeper into the site. In this case, make sure there is a regular HTML link on that front page to a non-Flash page where a user can navigate throughout your site without the need for Flash.
   

If you have other ideas that don't violate these guidelines that you'd like to ask about, feel free to ask them in the Webmaster Help Group under Crawling, Indexing, and Ranking. The many knowledgeable webmasters there, along with myself and a cadre of other Googlers, will do our best to clear up any confusion.

Update: See our additional blog posts about Flash Indexing at Google.this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com

Seo Master present to you: The Developer Sandbox was a new addition to this year's Google I/O. The Sandbox featured a diverse range of developers and apps, all with one thing in common -- they've all built applications based on technologies and products featured at I/O. The Sandbox was very popular with attendees and saw a lot of foot traffic throughout both days of the event. Sandbox developers welcomed the opportunity to interact with fellow developers, discuss their products and answer questions.



We interviewed these developers about their apps, the challenges they faced and the problems they solved, and finally their learnings & hopes for web technologies going forward. We also asked these developers to create screencast demos of their apps, much like the demos they gave to people visiting their station during I/O.

These video interviews and demos are now available in the Developer Sandbox section of the I/O website. Each developer has their own page with a brief description of their company, their app, and their interview video (if one was filmed) and screencast demo video (if available). For instance, here's a video interview with Gustav Soderstrom of Spotify, who walks us through a demo of their Android app and then talks about the platform and why Spotify chose to develop their app on Android.



Are you building an app on one of Google's platforms or using Google APIs? Please send us a video about your company and your app and you could be featured on Google Code Videos. Click here for the submission form and guidelines.

Each Sandbox developer page also features a Friend Connect gadget that allows anyone visiting the page to sign in with their Friend Connect id and leave comments & feedback. It's a great way to continue the conversation or to ask questions if you did not get a chance to meet them at I/O.

By Neel Kshetramade, Google Developer Programs2013, By: Seo Master

Seo Master present to you:

.hrecipe{font:10px oswald;} #hrecipe-1{float:letf; width:100px; padding-height:5px} #hrecipe-2{float:right; width: auto;}

The Second Step

Code <body> and paste the following code just below the code <body>

<div itemscope="itemtype="http://data-vocabulary.org/Recipe"></div>  

The third step
Locate the following code < h3 class = ' post-title entry-title ' > If there isn't, perhaps the template code agan-agan utilize ("class" or h1 < < h2 class ").
If it is found, then replace it with the following code: 

<span itemprop='itemreviewed'><span itemprop='description'><h3 class='post-title entry-title' itemprop='name'>  

Don't forget to close the HTML code above to avoid error with this cover </span> </span>

For more details about the code will look like this: 

<span itemprop='itemreviewed'><span itemprop='description'>
<h3 class='post-title entry-title' itemprop='name'>
<b:if cond='data:post.link'><a expr:href='data:post.link'><data:post.title/></a>
<b:else/>
<b:if cond='data:post.url'><a expr:href='data:post.url'><data:post.title/></a>
<b:else/>
<data:post.title/>
</b:if>
</b:if>
</h3>
</span>
</span>  

Now find the code < data: post. body/>, for this code sometimes totaling 2-3 even 4 code-code-
If you've been to try agan-agan select code sequence is at no. 2, then put the following code underneath the code < data: post. body/>

The code follows: 

<div class='hrecipe'>
<div id='hrecipe-1'>
<img class='photo' expr:alt='data:post.title' expr:src='data:post.thumbnailUrl'/></div>
<div id='hrecipe-2'>
<span class='item'>
<span class='fn'>dns.kardian
</span>
</span><br/>
By <span class='author'><b><data:blog.title/></b></span><br/>
Published: <span class='published'><data:post.timestampISO8601/></span><br/>
<span class='summary'><data:post.title/></span><br/>
<span class='review hreview-aggregate'>
<span class='rating'>
<span class='average'>4.5</span>
<span class='count'>11</span>
reviews</span></span>
</div>
</div>  

If all is applied, check the result in the best hxxp://www.google.com/webmasters/tools/richsnippets

2013, By: Seo Master