Création des Logiciels de gestion d'Entreprise, Création et référencement des sites web, Réseaux et Maintenance, Conception
Création des Logiciels de gestion d'Entreprise, Création et référencement des sites web, Réseaux et Maintenance, Conception
Tell us about moving your content via Google Webmaster Tools |
<title><data:blog.pageTitle/></title>4. Setelah kode tag tadi ketemu, highlight (blok) lalu ganti dengan kode dibawah ini:
<b:if cond='data:blog.pageType == "index"'>
<title><data:blog.title/></title>
<b:else/>
<title><data:blog.pageName/> - <data:blog.title/></title>
</b:if>
<meta content='disini tempat anda menuliskan deskripsi blog anda secara singkat dan jelas' name='description'/>ganti tulisan berwarna merah diatas dengan deskripsi blog anda, lalu klik save template untuk menyimpan perubahan.
<meta content='keyword1, keyword2, keyword3, keyphrase1, keyphrase2, keyphrase3' name='keywords'/>
ganti tulisan berwarna merah diatas dengan keyword atao keyphrase yang anda bidik pada blog anda, lalu klik save template untuk menyimpan perubahan
untuk lebih jelasnya lihat contoh di bawah:
<?xml version="1.0" encoding="UTF-8" ?>Demikianlah SEO Tutorial | Blogger sederhana yang sedikit banyak akan membantu menaikkan SERP web atau blog anda. semaga bermanfaat.2013, By: Seo Master
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html expr:dir='data:blog.languageDirection' xmlns='http://www.w3.org/1999/xhtml' xmlns:b='http://www.google.com/2005/gml/b' xmlns:data='http://www.google.com/2005/gml/data' xmlns:expr='http://www.google.com/2005/gml/expr'>
<head>
<b:include data='blog' name='all-head-content'/>
<b:if cond='data:blog.pageType == "index"'>
<title><data:blog.title/></title>
<b:else/>
<title><data:blog.pageName/> | <data:blog.title/></title>
</b:if>
<meta content='isi menurut petunjuk di atas' name='description'/>
<meta content='isi menurut petunjuk di atas' name='keywords'/>
<!-- Notification code start -->
<style type='text/css'>
#ut-sticky
{
background: #7d7e7d; /* Old browsers */
background: -moz-linear-gradient(top, #7d7e7d 6%, #7d7e7d 9%, #0e0e0e 99%); /* FF3.6+ */
background: -webkit-gradient(linear, left top, left bottom, color-stop(6%,#7d7e7d), color-stop(9%,#7d7e7d), color-stop(99%,#0e0e0e)); /* Chrome,Safari4+ */
background: -webkit-linear-gradient(top, #7d7e7d 6%,#7d7e7d 9%,#0e0e0e 99%); /* Chrome10+,Safari5.1+ */
background: -o-linear-gradient(top, #7d7e7d 6%,#7d7e7d 9%,#0e0e0e 99%); /* Opera 11.10+ */
background: -ms-linear-gradient(top, #7d7e7d 6%,#7d7e7d 9%,#0e0e0e 99%); /* IE10+ */
background: linear-gradient(top, #7d7e7d 6%,#7d7e7d 9%,#0e0e0e 99%); /* W3C */
filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#7d7e7d', endColorstr='#0e0e0e',GradientType=0 ); /* IE6-9 */
border-bottom:2px solid #999;
color:#fff;
text-align: center;
margin:-12px auto;
padding-bottom:1px;
border-top: 1px solid #333;
height:38px;
font-size:13px;
position:fixed;
vertical-align: baseline; overflow:hidden;
z-index:999;
width:100%;
border-bottom-left-radius:6px;
border-bottom-right-radius:6px;
display:block;
font-weight: bold;
font-family: arial,"Helvetica";
font-color:#fff;
-moz-box-shadow: 0 2px 4px hsla(0,0%,0%,.35);
-webkit-box-shadow: 0 2px 4px hsla(0,0%,0%,.35);
}
#ut-sticky:hover
{
background-color:#333;background-image:-moz-linear-gradient(top,#555555,#434343);background-image:-ms-linear-gradient(top,#555555,#434343);background-image:-webkit-gradient(linear,0 0,0 100%,from(#555555),to(#434343));background-image:-webkit-linear-gradient(top,#555555,#434343);background-image:-o-linear-gradient(top,#555555,#434343);background-image:linear-gradient(top,#555555,#434343);background-repeat:repeat-x;filter:progid:DXImageTransform.Microsoft.gradient(startColorstr='#555555',endColorstr='#434343',GradientType=0)
-webkit-transition:all 1.3s ease-in-out;-moz-transition:all 1.3s ease-in-out;-o-transition-duration:all 1.3s ease-in-out;transition:all 1.3s ease-in-out;
-moz-box-shadow: 0 2px 4px hsla(0,0%,0%,.35);
-webkit-box-shadow: 0 2px 4px hsla(0,0%,0%,.35);
}
#ut-button {background:#fff; padding:4px; color:black;text-shadow:0 -1px 0 rgba(255,255,255,0.25);background-color:white}
#ut-sticky p{line-height:5px; font-size:13px; text-align:center; width:95%; float:left;}
#ut-sticky p a{ text-decoration:underline; padding:4px; color:#FFFF33;}
.ut-cross{display:block; position:relative; right:15px; top:4px;float:right;}
.ut-cross a{font-size:18px; font-weight:bold; font-family:"Arial"; color:#FF0000; line-height:30px;}
.ut-cross, a:hover{color:#DDD; text-decoration:none;}
</style>
<div id='ut-sticky'>
<p style='padding-top:17px;'>Welcome To Entertainment<a class='ut-button' href='http://www.entertainer001.tk/2012/06/how-to-add-floating-notification-bar-in.html' target='_blank'>Get this!</a></p>
<div class='ut-cross'><a href='javascript:hide_cross();'>X</a></div>
</div>
<script language='JavaScript'>
function hide_cross() {
crosstbox = document.getElementById("ut-sticky");
crosstbox.style.visibility = 'hidden';
}
</script>
<br/><br/>
<br/><br/>
<!-- End of Notification code, info - http://www.entertainer001.blogspot.com -->
Our iPhone SDK is compatible with iPhone OS 3.0, and our Android SDK is compatible with Android 1.5 SDK. The SDKs include a library that can be linked in to your application which exposes methods to fetch and show ads. You must place a maximum of one ad per screen at the top or bottom (see the screenshot from the Backgrounds iPhone application). When a user clicks on the ad in your application, you can choose whether the user should view the advertiser's website in iPhone Safari or a full-screen UIWebView on the iPhone. For Android applications, our API defaults to opening the advertiser's website in the native browser.
To get started with monetizing your iPhone or Android application, sign up today on the AdSense for Mobile Applications website. We can't wait to have you join our beta network!
<video:tvshow>
element:<video:video>
<video:title>The Sample Show, Season 1, Episode 2</video:title>
 <!-- other required root level video tags omitted -->
 <video:tvshow>
<video:show_title>The Sample Show</video:show_title>
<video:video_type>full</video:video_type>
<video:episode_title>A Sample Episode Title</video:episode_title>
<video:season_number>1</video:season_number>
<video:episode_number>2</video:episode_number>
</video:tvshow>
</video:video>
Hi, I'm Michael, but I go by "Wysz" in the Webmaster Help Group. When I'm not talking to webmasters or doing other search-related work, I like to tinker with my personal blog, take photos, and edit videos. Blogs, videos, podcasts, and other online media often come to my rescue when I'm searching for information online, so I'd love to talk to fellow content providers about how to make sure their sites can be understood by Google.
Hi, I'm Reid. I'm originally from St. Louis, Missouri, but have fallen in love with the weather, biking trails, and culture of the Bay Area. I studied to be a historian and even wrote a Senior honors thesis on Japanese American resettlement in San Francisco after WWII, but as an avid blogger, found myself increasingly interested in the transaction of knowledge and information through the Internet. I'm particularly passionate about helping small businesses build out high quality websites and helping them understand how Google's tools can help them in the process.this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
Webmaster level: All
In December 2011 we announced annotations for sites that target users in many languages and, optionally, countries. These annotations define a cluster of equivalent pages that target users around the world, and were implemented using rel-alternate-hreflang link elements in the HTML of each page in the cluster.
Based on webmaster feedback and other considerations, today we’re adding support for specifying the rel-alternate-hreflang annotations in Sitemaps. Using Sitemaps instead of HTML link elements offers many advantages including smaller page size and easier deployment for some websites.
To see how this works, let's take a simple example: We wish to specify that for the URL http://www.example.com/en, targeting English language users, the equivalent URL targeting German language speakers http://www.example.com/de. Up till now, the only way to add such annotation is to use a link element, either as an HTTP header or as HTML elements on both URLs like this:
<link rel="alternate" hreflang="en" href="http://www.example.com/en" >
<link rel="alternate" hreflang="de" href="http://www.example.com/de" >
As of today, you can alternately use the following equivalent markup in Sitemaps:
<url>
<loc>http://www.example.com/en</loc>
<xhtml:link
rel="alternate"
hreflang="de"
href="http://www.example.com/de" />
<xhtml:link
rel="alternate"
hreflang="en"
href="http://www.example.com/en" />
</url>
<url>
<loc>http://www.example.com/de</loc>
<xhtml:link
rel="alternate"
hreflang="de"
href="http://www.example.com/de" />
<xhtml:link
rel="alternate"
hreflang="en"
href="http://www.example.com/en" />
</url>
Briefly, the new Sitemaps tags shown in bold function in the same way as the HTML link tags, with both using the same attributes. The full technical details of how the annotations are implemented in Sitemaps, including how to implement the xhtml namespace for the link tag, are in our new Help Center article.
A more detailed example can be found in our new Help Center article, and if you need more help, please ask in our brand new internationalization help forum.
Written by Pierre Far, Webmaster Trends Analyst
this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com<body itemscope itemtype="http://schema.org/Article">
<h1 itemprop="name">This is the article name</h1>
<img itemprop="image" src="thumbnail.jpg" />
<p itemprop="description">This is the description of the article.</p>
</body>
Text Ad - Medium Rectangle (300x250) | Video Ad - Medium Rectangle (300x250) |
Image Ad - Leaderboad (728x90)