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

Seo Master present to you:

1. Initial project planning: Meet with an SEO expert. Pay them for their time. Have them map out when and how the SEO team should be involved in development.
   
2. Information architecture: Before you create your new site map, pick your keywords and verify that they matter. Organize your keywords into topics. Be sure your architecture reflects this. Remember, this isn't just how search engines see your site. It's how people look for you, too.
   
3. Tools selection: If you're using a shopping cart, content management system or something else, make sure they support SEO. And no, I don't mean "SEO friendly URLs" or other trite sales speak you'll hear. I mean that these tools support unique title tags, correct semantic markup and won't turn your web site into a pile of search-repellent spaghetti.
   
4. Content: Let the expert help you structure and write great copy that'll also get the search engines' attention.
   
5. Design: As your creative team gets to work, get your SEO expert to have a glance at the design. You don't want to take, say, headings and turn them into graphical text. The SEO can work with the designers and help them find the best balance. She may know a thing or two about image replacement and other tricks that can help create a beautiful, search-friendly site, too. Like Askbazar.com
   
6. Mockup: Sooo many companies ignore this. Have a truly great XHTML coder create templates for each unique page layout on your site. Then have your expert review for potential issues. This will make your developers' lives much, much easier, because they won't have to become HTML producers.
   
7. Development: Make sure the SEO team has access to the site-in-progress. They'll watch for alarm bells like uneditable title tags, straying from the mockup or hacked-up code.
   
8. Pre-launch: The SEO expert can use whatever tools they have to 'crawl' your site, checking for busted links, search engine roadblocks, etc..
   
9. Pre-launch, 2: The expert will give you a set of 301 redirects to set up, so that critical link authority isn't lost.
   
10. Launch: The SEO expert will join you in biting collective fingernails.
    
11. Post launch: Now the expert will start working on the stuff most people consider 'search engine optimization' - link building, tracking metrics, content optimization, strategy, etc..
    

 

2013, By: Seo Master

Seo Master present to you: Our very own Martin Omander can be found guest starring over at the O'Reilly Windows DevCenter. Martin has written a detailed and enjoyable tutorial on implementing a .NET application using the Google Checkout API. Insightful reading for Google Checkout users, even those that work on a different platform or in a different programming language. Read the full article at: Build a .NET App for Google Checkout.2013, By: Seo Master

Seo Master present to you:
By Fred Sauer, Developer Advocate

Cross-posted with the Google Web Toolkit Blog

Last week Angry Birds for Chrome was updated to use the Web Audio API for all its in-game audio for Chrome users, which means Chrome users get the full Angry Birds experience, without any plugins. The Web Audio API supports a wide variety of use cases, including the high fidelity and low latency requirements of games. Users of other supported browsers will still get sound via Flash or HTML5 audio.


How does this cross-browser audio magic work? As you may have seen or heard, Angry Birds was in no small part made possible by the cross-platform open source PlayN library. When building for the HTML platform, PlayN in turn relies heavily on Google Web Toolkit (GWT) to delivery a highly optimized web experience for users, and on gwt-voices to easily deliver a cross-browser audio experience.

The responsibility of choosing the appropriate audio API for the game's sound is (mostly) left up to gwt-voices, which chooses the audio API that will give the best experience. If you'd like to hear how other audio APIs perform, you can ask gwt-voices to try to use the Web Audio API, Flash, HTML5 Audio, or even native audio. Your mileage will vary by browser and platform and which plugins you have installed. Also, gwt-voices will select the best available fallback, if the desired audio API is not going to work at all in your environment.

Want to learn more? Check out the Web Audio API tutorial and don't let those pigs grunt too much.


Fred Sauer is a Developer Advocate at Google where most of his time is devoted to Google App Engine and Google Web Toolkit. He is the author of various GWT related open source projects including gwt-dnd (providing in browser Drag and Drop capabilities), gwt-log (an advanced logging framework) and gwt-voices (for cross browser sound support). Fred has dedicated much of his career to Java related development, with an increasing focus on HTML5.

Posted by Scott Knaster, Editor

2013, By: Seo Master