Création des Logiciels de gestion d'Entreprise, Création et référencement des sites web, Réseaux et Maintenance, Conception
Seo Master present to you:
By Vincent Nguyen, with Katie Miller, Google I/O Team
Google I/O 2012 is fast approaching, and to help energize you for three packed days of demos, announcements and developer fun, we chatted with a few attendees to see what excites them about this year’s agenda, and to get some tips on how to make the most of the event.
Today’s conversation is with Vincent Nguyen. Vincent is co-founder of Android Community and SlashGear, where he writes about mobile technology and consumer electronics. We asked Vincent for a look at what he expects during his I/O 2012 experience.
You’ve been to Google I/O before. How are you approaching this year’s event?
I've been attending Google I/O since the very first year back in 2008, and watched as the event has matured into a showcase for everything that we love about Google. Far-fetched ideas that somehow find their way into phones; ambitious plans to help users engage with data in new and intriguing ways; and a combination of enterprise and geeky glee that permeates all the way through, whether you're talking to a Google exec or a developer attendee.
We'll be covering I/O wearing two different hats, which is fitting considering Android has broken through into the mainstream as well as remaining a developer's playground. For SlashGear, we'll take a more consumer-centric approach: looking at the technologies and developments that will make a day-to-day difference in users' lives. It's really easy to put together a slick demo and presentation, but we'll be trying to make sure the SlashGear audience sees the context too, where they'll actually benefit once that technology reaches the market.
On the flipside there's the Android Community readership, which tends to be more advanced in its understanding of hardware, code and apps, as well as eager and willing to dig into the minutiae of what makes Google I/O special. There, we'll spend less time on context - though that's still important - and more on specifics, keeping readers up to speed on the cutting edge.
Android has become a huge part of I/O. What do you foresee happening with Android at this year’s conference?
Android's rise has been meteoric, and apps have grown in number and scope alongside it. Many Google I/O sessions will center on app accessibility, security and privacy, all hot-button topics in the months since last year's event. One of the great strengths of the platform is the freedom developers have to distribute their software, but with that comes no small amount of responsibility, and I'm expecting to hear more best-practice guidelines as Google shifts into broader areas.
That's where arguably the real meat of Google I/O comes about: the opportunity for developers to talk to Google's own engineers. As press attendees rather than as developers, the team and I are always mindful of the huge number of interested people who haven't been able to make it to I/O itself. We're their eyes and ears in the keynote, the backstage interviews, when talking with Sandbox partners and everywhere else. It's a big responsibility but I love the challenge of spotting the most important trends and stories and packaging them up in a way that makes sense to those not lucky enough to be on-site.
Is there anything you’re hoping to learn about that isn’t a major part of the current schedule?
Google has some challenges ahead, and like many I'll be very interested to see the latest developments in Google TV. I'm hoping the multi-screen strategy we've seen developing from other companies in home entertainment and gaming will find a counterpart in Google's platform, pulling the disparate elements of the cloud, smart mobility and entertainment together.
It's the surprise additions - the keynote items we never expect - that I'm most excited about, though. I'd be shocked if Google didn't bring the latest iteration of Project Glass on-stage, and disappointed if I don't get to try it myself sometime during I/O. I expect some talk about what Google has learned in wearable computing. After long speculation about Google Assistant, and with Samsung's S-Voice making its debut on the Galaxy S III recently, I'm also guessing that voice control will make itself heard too.
As a veteran of 4 previous Google I/O events, how are you feeling about this year’s I/O?
Ultimately, we want Google I/O to be a fun experience, and help convey that excitement and enthusiasm to our readers, developers and others through our coverage of the event. It's a huge, valuable opportunity for insight into one of the most important companies around today; a starting point for ripples that we'll see impact the tech world across the following months. It's a privilege to be involved, and I can't wait to be wowed.
Not coming to Google I/O 2012 in person? Not a problem. Watch the keynote and dozens of other sessions streamed live at developers.google.com/io.
Vincent Nguyen began his career in tech more than a decade ago as a provisioning manager and software developer. As the co-founder of Android Community and SlashGear, he specializes in mobile technology, and also writes about all aspects of consumer electronics with an independent perspective. You can follow Vincent on Google+, Twitter, and Facebook.
Edited and posted by Katie Miller and Scott Knaster, Google I/O Team
2013, By: Seo Master
 |
| Katie |
 |
| Vincent |
By Vincent Nguyen, with Katie Miller, Google I/O Team
Google I/O 2012 is fast approaching, and to help energize you for three packed days of demos, announcements and developer fun, we chatted with a few attendees to see what excites them about this year’s agenda, and to get some tips on how to make the most of the event.
Today’s conversation is with Vincent Nguyen. Vincent is co-founder of Android Community and SlashGear, where he writes about mobile technology and consumer electronics. We asked Vincent for a look at what he expects during his I/O 2012 experience.
You’ve been to Google I/O before. How are you approaching this year’s event?
I've been attending Google I/O since the very first year back in 2008, and watched as the event has matured into a showcase for everything that we love about Google. Far-fetched ideas that somehow find their way into phones; ambitious plans to help users engage with data in new and intriguing ways; and a combination of enterprise and geeky glee that permeates all the way through, whether you're talking to a Google exec or a developer attendee.
We'll be covering I/O wearing two different hats, which is fitting considering Android has broken through into the mainstream as well as remaining a developer's playground. For SlashGear, we'll take a more consumer-centric approach: looking at the technologies and developments that will make a day-to-day difference in users' lives. It's really easy to put together a slick demo and presentation, but we'll be trying to make sure the SlashGear audience sees the context too, where they'll actually benefit once that technology reaches the market.
On the flipside there's the Android Community readership, which tends to be more advanced in its understanding of hardware, code and apps, as well as eager and willing to dig into the minutiae of what makes Google I/O special. There, we'll spend less time on context - though that's still important - and more on specifics, keeping readers up to speed on the cutting edge.
Android has become a huge part of I/O. What do you foresee happening with Android at this year’s conference?
Android's rise has been meteoric, and apps have grown in number and scope alongside it. Many Google I/O sessions will center on app accessibility, security and privacy, all hot-button topics in the months since last year's event. One of the great strengths of the platform is the freedom developers have to distribute their software, but with that comes no small amount of responsibility, and I'm expecting to hear more best-practice guidelines as Google shifts into broader areas.
That's where arguably the real meat of Google I/O comes about: the opportunity for developers to talk to Google's own engineers. As press attendees rather than as developers, the team and I are always mindful of the huge number of interested people who haven't been able to make it to I/O itself. We're their eyes and ears in the keynote, the backstage interviews, when talking with Sandbox partners and everywhere else. It's a big responsibility but I love the challenge of spotting the most important trends and stories and packaging them up in a way that makes sense to those not lucky enough to be on-site.
Is there anything you’re hoping to learn about that isn’t a major part of the current schedule?
Google has some challenges ahead, and like many I'll be very interested to see the latest developments in Google TV. I'm hoping the multi-screen strategy we've seen developing from other companies in home entertainment and gaming will find a counterpart in Google's platform, pulling the disparate elements of the cloud, smart mobility and entertainment together.
It's the surprise additions - the keynote items we never expect - that I'm most excited about, though. I'd be shocked if Google didn't bring the latest iteration of Project Glass on-stage, and disappointed if I don't get to try it myself sometime during I/O. I expect some talk about what Google has learned in wearable computing. After long speculation about Google Assistant, and with Samsung's S-Voice making its debut on the Galaxy S III recently, I'm also guessing that voice control will make itself heard too.
As a veteran of 4 previous Google I/O events, how are you feeling about this year’s I/O?
Ultimately, we want Google I/O to be a fun experience, and help convey that excitement and enthusiasm to our readers, developers and others through our coverage of the event. It's a huge, valuable opportunity for insight into one of the most important companies around today; a starting point for ripples that we'll see impact the tech world across the following months. It's a privilege to be involved, and I can't wait to be wowed.
Not coming to Google I/O 2012 in person? Not a problem. Watch the keynote and dozens of other sessions streamed live at developers.google.com/io.
Vincent Nguyen began his career in tech more than a decade ago as a provisioning manager and software developer. As the co-founder of Android Community and SlashGear, he specializes in mobile technology, and also writes about all aspects of consumer electronics with an independent perspective. You can follow Vincent on Google+, Twitter, and Facebook.
Edited and posted by Katie Miller and Scott Knaster, Google I/O Team
2013, By: Seo Master
salam every one, this is a topic from google web master centrale blog: Webmaster Level: Beginner
Looking through all of the information in Webmaster Central can feel overwhelming, especially if you’re just getting started with a website. This is why we’re excited to introduce a new set of educational materials in a program called Webmaster Academy. Webmaster Academy provides practical and easy-to-understand lessons for beginner webmasters to help you improve your site with topics like getting your site in our index, providing search engines with helpful information about your video and image content, and understanding Webmaster Tools features.
We’ve organized the content to represent what beginner webmasters should know in a way that’s both structured and modular, meaning you can go through the whole curriculum, or pick and choose your own path. Once you’ve read the articles, you can easily delve deeper into each topic, as we provide links to more in-depth articles. Most lessons are also accompanied by a video from the Webmaster Central YouTube Channel. If you’re looking to understand search and improve your site, Webmaster Academy is for you!
Have feedback? Excellent. Post it in our Webmaster Help Forum.
this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
Looking through all of the information in Webmaster Central can feel overwhelming, especially if you’re just getting started with a website. This is why we’re excited to introduce a new set of educational materials in a program called Webmaster Academy. Webmaster Academy provides practical and easy-to-understand lessons for beginner webmasters to help you improve your site with topics like getting your site in our index, providing search engines with helpful information about your video and image content, and understanding Webmaster Tools features.
We’ve organized the content to represent what beginner webmasters should know in a way that’s both structured and modular, meaning you can go through the whole curriculum, or pick and choose your own path. Once you’ve read the articles, you can easily delve deeper into each topic, as we provide links to more in-depth articles. Most lessons are also accompanied by a video from the Webmaster Central YouTube Channel. If you’re looking to understand search and improve your site, Webmaster Academy is for you!
Have feedback? Excellent. Post it in our Webmaster Help Forum.
this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
salam every one, this is a topic from google web master centrale blog: Last month, several of us with Webmaster Central hit the "good times" jackpot at PubCon Vegas 2007. We realize not all of you could join us, so instead of returning home with fuzzy dice for everyone, we've got souvenir conference notes.
Listening to the Q&A, I was pleased to hear the major search engines agreeing on best practices for many webmaster issues. In fact, the presentations in the duplicate content session were mostly, well, duplicate. When I wasn't sitting in on one of the many valuable sessions, I was chatting with webmasters either at the Google booth, or at Google's "Meet the Engineers" event. It was exciting to hear from so many different webmasters, and to help them with Google-related issues. Here are a few things that were on the minds of webmasters, along with our responses:
Site Verification Files and Meta Tags
Several webmasters asked, "Is it necessary to keep the verification meta tag or HTML file in place to remain a verified owner in Webmaster Tools?" The answer is yes, you should keep your verification file or meta tag live to maintain your status as a verified owner. These verification codes are used to control who has access to the owner-specific tools for your site in Webmaster Tools. To ensure that only current owners of a site are verified, we periodically re-check to see if the verification code is in place, and if it is not, you will get unverified for that site. While we're on the topic:
Site Verification Best Practices
What's the difference between using subdomains and subdirectories? When it comes to Google, there aren't major differences between the two, so when you're making that decision, do what works for you and your visitors. Following PubCon, our very own Matt Cutts outlined many of the key issues in a post on his personal blog. In addition to those considerations, if you use Webmaster Tools (which we hope you do!), keep in mind that you'll automatically be verified for deeper subdirectories of any sites you've verified, but subdomains need to be verified separately.
Underscores vs. Dashes
Webmasters asked about the difference between how Google interprets underscores and dashes in URLs. In general, we break words on punctuation, so if you use punctuation as separators, you're providing Google a useful signal for parsing your URLs. Currently, dashes in URLs are consistently treated as separators while underscores are not. Keep in mind our technology is constantly improving, so this distinction between underscores and dashes may decrease over time. Even without punctuation, there's a good chance we'll be able to figure out that bigleopard.html is about a "big leopard" and not a "bigle opard." While using separators is a good practice, it's likely unnecessary to place a high priority on changing your existing URLs just to convert underscores to dashes.
Keywords in URLs
We were also asked if it is useful to have relevant keywords in URLs. It's always a good idea to be descriptive across your site, with titles, ALT attributes, and yes, even URLs, as they can be useful signals for users and search engines. This can be especially true with image files, which otherwise may not have any text for a search engine to consider. Imagine you've taken a picture of your cat asleep on the sofa. Your digital camera will likely name it something like IMG_2937.jpg. Not exactly the most descriptive name. So unless your cat really looks like an IMG_2937, consider changing the filename to something more relevant, like adorable-kitten.jpg. And, if you have a post about your favorite cat names, it's much easier to guess that a URL ending in my-favorite-cat-names would be the relevant page, rather than a URL ending in postid=8652. For more information regarding issues with how Google understands your content, check out our new content analysis feature in Webmaster Tools, as well as our post on the URL suggestions feature of the new Google Toolbar.
Moving to a new IP address
We got a question about changing a site's IP address, and provided a few steps you can take as a webmaster to make sure things go smoothly. Here's what you can do:
A few webmasters were concerned that proxy services are being indexed with copies of their content. While it's often possible to find duplicate copies of your content in our results if you look hard enough, the original source is most likely going to be ranked higher than a proxy copy. However, if you find this not to be the case, please drop us some URLs in the Webmaster Help Group. There are many Googlers including myself who monitor this group and escalate issues appropriately.
It was great talking with webmasters at the conference -- we hope those of you unable to join us found this post useful. If you want to continue to talk shop with me, other Googlers, and your fellow webmasters, join the follow-up conversation in the Webmaster Help Group.
Update: Additional PubCon notes from Jonathan Simon are available in our discussion group.this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
Listening to the Q&A, I was pleased to hear the major search engines agreeing on best practices for many webmaster issues. In fact, the presentations in the duplicate content session were mostly, well, duplicate. When I wasn't sitting in on one of the many valuable sessions, I was chatting with webmasters either at the Google booth, or at Google's "Meet the Engineers" event. It was exciting to hear from so many different webmasters, and to help them with Google-related issues. Here are a few things that were on the minds of webmasters, along with our responses:
Site Verification Files and Meta Tags
Several webmasters asked, "Is it necessary to keep the verification meta tag or HTML file in place to remain a verified owner in Webmaster Tools?" The answer is yes, you should keep your verification file or meta tag live to maintain your status as a verified owner. These verification codes are used to control who has access to the owner-specific tools for your site in Webmaster Tools. To ensure that only current owners of a site are verified, we periodically re-check to see if the verification code is in place, and if it is not, you will get unverified for that site. While we're on the topic:
Site Verification Best Practices
- If you have multiple people working on your site with Webmaster Tools, it's a good idea to have each person verify the site with his or her own account, rather than using a shared login. That way, as people come and go, you can control the access appropriately by adding or removing verification files or meta tags for each account.
- You may want to keep a list of these verification codes and which owner they are connected to, so you can easily control access later. If you lose track, you can always use the "Manage site verification" option in Webmaster Tools, which allows you to force all site owners to reverify their accounts.
What's the difference between using subdomains and subdirectories? When it comes to Google, there aren't major differences between the two, so when you're making that decision, do what works for you and your visitors. Following PubCon, our very own Matt Cutts outlined many of the key issues in a post on his personal blog. In addition to those considerations, if you use Webmaster Tools (which we hope you do!), keep in mind that you'll automatically be verified for deeper subdirectories of any sites you've verified, but subdomains need to be verified separately.
Underscores vs. Dashes
Webmasters asked about the difference between how Google interprets underscores and dashes in URLs. In general, we break words on punctuation, so if you use punctuation as separators, you're providing Google a useful signal for parsing your URLs. Currently, dashes in URLs are consistently treated as separators while underscores are not. Keep in mind our technology is constantly improving, so this distinction between underscores and dashes may decrease over time. Even without punctuation, there's a good chance we'll be able to figure out that bigleopard.html is about a "big leopard" and not a "bigle opard." While using separators is a good practice, it's likely unnecessary to place a high priority on changing your existing URLs just to convert underscores to dashes.
Keywords in URLs
We were also asked if it is useful to have relevant keywords in URLs. It's always a good idea to be descriptive across your site, with titles, ALT attributes, and yes, even URLs, as they can be useful signals for users and search engines. This can be especially true with image files, which otherwise may not have any text for a search engine to consider. Imagine you've taken a picture of your cat asleep on the sofa. Your digital camera will likely name it something like IMG_2937.jpg. Not exactly the most descriptive name. So unless your cat really looks like an IMG_2937, consider changing the filename to something more relevant, like adorable-kitten.jpg. And, if you have a post about your favorite cat names, it's much easier to guess that a URL ending in my-favorite-cat-names would be the relevant page, rather than a URL ending in postid=8652. For more information regarding issues with how Google understands your content, check out our new content analysis feature in Webmaster Tools, as well as our post on the URL suggestions feature of the new Google Toolbar.
Moving to a new IP address
We got a question about changing a site's IP address, and provided a few steps you can take as a webmaster to make sure things go smoothly. Here's what you can do:
- Change the TTL (Time To Live) value of your DNS configuration to something short, like five minutes (300 seconds). This will tell web browsers to re-check the IP address for your site every five minutes.
- Copy your content to the new hosting environment, and make sure it is live on the new IP address.
- Change your DNS settings so your hostname points to the new IP address.
- Check your logs to see when Googlebot starts crawling your site on the new IP address. To make sure it's really Googlebot who's visiting, you can verify Googlebot by following these instructions. You can then log into Webmaster Tools and monitor any crawl errors. Once Googlebot is happily crawling on the new IP address, you should be all set as far as Google is concerned.
- To make sure everyone got the message of your move, you may want to keep an eye out for visits to your old IP address before shutting it down.
A few webmasters were concerned that proxy services are being indexed with copies of their content. While it's often possible to find duplicate copies of your content in our results if you look hard enough, the original source is most likely going to be ranked higher than a proxy copy. However, if you find this not to be the case, please drop us some URLs in the Webmaster Help Group. There are many Googlers including myself who monitor this group and escalate issues appropriately.
Update: Additional PubCon notes from Jonathan Simon are available in our discussion group.this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com