bloggerrized

Sitemaps XML format - sitemaps.org - Protocol

<div dir="ltr" style="text-align: left;" trbidi="on"> This document describes the XML schema for the Sitemap protocol. The Sitemap protocol format consists of XML tags. All data values in a Sitemap must be <a href="http://www.sitemaps.org/protocol.html#escaping">entity-escaped</a>. The file itself must be UTF-8 encoded. The Sitemap must: <ul> <li>Begin with an opening <code><<a href="http://www.sitemaps.org/protocol.html#urlsetdef">urlset</a>></code> tag and end with a closing <code></urlset></code> tag.</li> <li>Specify the namespace (protocol standard) within the <code><urlset></code> tag. </li> <li>Include a <code><<a href="http://www.sitemaps.org/protocol.html#urldef">url</a>></code> entry for each URL, as a parent XML tag.</li> <li>Include a <code><<a href="http://www.sitemaps.org/protocol.html#locdef">loc</a>></code> child entry for each <code> <url></code> parent tag.</li> </ul> All other tags are optional. Support for these optional tags may vary among search engines. Refer to each search engine's documentation for details. Also, all URLs in a Sitemap must be from a single host, such as www.example.com or store.example.com. For further details, refer the <a href="http://www.sitemaps.org/protocol.html#location">Sitemap file location</a> <h3> Sample XML Sitemap</h3> The following example shows a Sitemap that contains just one URL and uses all optional tags. The optional tags are in italics. <pre><?xml version="1.0" encoding="UTF-8"?> <<a href="http://www.sitemaps.org/protocol.html#urlsetdef">urlset</a> xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">    <<a href="http://www.sitemaps.org/protocol.html#urldef">url</a>>       <<a href="http://www.sitemaps.org/protocol.html#locdef">loc</a>>http://www.example.com/</loc>       <<a href="http://www.sitemaps.org/protocol.html#lastmoddef">lastmod</a>>2005-01-01</lastmod>       <<a href="http://www.sitemaps.org/protocol.html#changefreqdef">changefreq</a>>monthly</changefreq>       <<a href="http://www.sitemaps.org/protocol.html#prioritydef">priority</a>>0.8</priority>    </url> </urlset> </pre> Also see our example with <a href="http://www.sitemaps.org/protocol.html#sitemapXMLExample">multiple URLs</a>. <h2> <a href="http://www.blogger.com/null" id="xmlTagDefinitions" name="xmlTagDefinitions"></a>XML tag definitions</h2> The available XML tags are described below. <table style="width: 80%px;"> <tbody> <tr><th>Attribute </th> <th></th> <th>Description </th> </tr> <tr> <td><a href="http://www.blogger.com/null" id="urlsetdef" name="urlsetdef"></a><code><urlset></code> </td> <td>required </td> <td>Encapsulates the file and references the current protocol standard.</td> </tr> <tr class="alt"> <td><a href="http://www.blogger.com/null" id="urldef" name="urldef"></a><code><url></code> </td> <td>required </td> <td>Parent tag for each URL entry. The remaining tags are children of this tag.</td> </tr> <tr> <td><a href="http://www.blogger.com/null" id="locdef" name="locdef"></a><code><loc></code> </td> <td>required </td> <td>URL of the page. This URL must begin with the protocol (such as http) and end with a trailing slash, if your web server requires it. This value must be less than 2,048 characters.</td> </tr> <tr class="alt"> <td><a href="http://www.blogger.com/null" id="lastmoddef" name="lastmoddef"></a><code><lastmod></code> </td> <td>optional </td> <td>The date of last modification of the file. This date should be in <a href="http://www.w3.org/TR/NOTE-datetime"> W3C Datetime</a> format. This format allows you to omit the time portion, if desired, and use YYYY-MM-DD. Note that this tag is separate from the If-Modified-Since (304) header the server can return, and search engines may use the information from both sources differently.</td> </tr> <tr> <td><a href="http://www.blogger.com/null" id="changefreqdef" name="changefreqdef"></a><code><changefreq></code> </td> <td>optional </td> <td>How frequently the page is likely to change. This value provides general information to search engines and may not correlate exactly to how often they crawl the page. Valid values are: <ul> <li>always</li> <li>hourly</li> <li>daily</li> <li>weekly</li> <li>monthly</li> <li>yearly</li> <li>never</li> </ul> The value "always" should be used to describe documents that change each time they are accessed. The value "never" should be used to describe archived URLs. Please note that the value of this tag is considered a hint and not a command. Even though search engine crawlers may consider this information when making decisions, they may crawl pages marked "hourly" less frequently than that, and they may crawl pages marked "yearly" more frequently than that. Crawlers may periodically crawl pages marked "never" so that they can handle unexpected changes to those pages.</td> </tr> <tr class="alt"> <td><a href="http://www.blogger.com/null" id="prioritydef" name="prioritydef"></a><code><priority></code> </td> <td>optional </td> <td>The priority of this URL relative to other URLs on your site. Valid values range from 0.0 to 1.0. This value does not affect how your pages are compared to pages on other sites—it only lets the search engines know which pages you deem most important for the crawlers. The default priority of a page is 0.5. Please note that the priority you assign to a page is not likely to influence the position of your URLs in a search engine's result pages. Search engines may use this information when selecting between URLs on the same site, so you can use this tag to increase the likelihood that your most important pages are present in a search index. Also, please note that assigning a high priority to all of the URLs on your site is not likely to help you. Since the priority is relative, it is only used to select between URLs on your site.</td> </tr> </tbody></table> <div class="backtotop"> <a href="http://www.sitemaps.org/protocol.html#top">Back to top</a></div> <h2> <a href="http://www.blogger.com/null" id="escaping" name="escaping"></a>Entity escaping</h2> Your Sitemap file must be UTF-8 encoded (you can generally do this when you save the file). As with all XML files, any data values (including URLs) must use entity escape codes for the characters listed in the table below. <table> <tbody> <tr><th colspan="2">Character </th> <th>Escape Code </th> </tr> <tr> <td>Ampersand </td> <td>& </td> <td><code>&amp;</code> </td> </tr> <tr class="alt"> <td>Single Quote </td> <td>' </td> <td><code>&apos;</code> </td> </tr> <tr> <td>Double Quote </td> <td>" </td> <td><code>&quot;</code> </td> </tr> <tr class="alt"> <td>Greater Than </td> <td>> </td> <td><code>&gt;</code> </td> </tr> <tr> <td>Less Than </td> <td>< </td> <td><code>&lt;</code> </td> </tr> </tbody></table> In addition, all URLs (including the URL of your Sitemap) must be URL-escaped and encoded for readability by the web server on which they are located. However, if you are using any sort of script, tool, or log file to generate your URLs (anything except typing them in by hand), this is usually already done for you. Please check to make sure that your URLs follow the <a href="http://www.ietf.org/rfc/rfc3986.txt"> RFC-3986</a> standard for URIs, the <a href="http://www.ietf.org/rfc/rfc3987.txt">RFC-3987</a> standard for IRIs, and the <a href="http://www.w3.org/TR/REC-xml/">XML standard</a>. Below is an example of a URL that uses a non-ASCII character (<code>ü</code>), as well as a character that requires entity escaping (<code>&</code>): <pre>http://www.example.com/ümlat.php&q=name</pre> Below is that same URL, ISO-8859-1 encoded (for hosting on a server that uses that encoding) and URL escaped: <pre>http://www.example.com/%FCmlat.php&q=name</pre> Below is that same URL, UTF-8 encoded (for hosting on a server that uses that encoding) and URL escaped: <pre>http://www.example.com/%C3%BCmlat.php&q=name</pre> Below is that same URL, but also entity escaped: <pre>http://www.example.com/%C3%BCmlat.php&amp;q=name</pre> <h3> <a href="http://www.blogger.com/null" id="sitemapXMLExample" name="sitemapXMLExample"></a>Sample XML Sitemap</h3> The following example shows a Sitemap in XML format. The Sitemap in the example contains a small number of URLs, each using a different set of optional parameters. <pre><?xml version="1.0" encoding="UTF-8"?> <<a href="http://www.sitemaps.org/protocol.html#urlsetdef">urlset</a> xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">    <<a href="http://www.sitemaps.org/protocol.html#urldef">url</a>>       <<a href="http://www.sitemaps.org/protocol.html#locdef">loc</a>>http://www.example.com/</loc>       <<a href="http://www.sitemaps.org/protocol.html#lastmoddef">lastmod</a>>2005-01-01</lastmod>       <<a href="http://www.sitemaps.org/protocol.html#changefreqdef">changefreq</a>>monthly</changefreq>       <<a href="http://www.sitemaps.org/protocol.html#prioritydef">priority</a>>0.8</priority>    </url>    <<a href="http://www.sitemaps.org/protocol.html#urldef">url</a>>       <<a href="http://www.sitemaps.org/protocol.html#locdef">loc</a>>http://www.example.com/catalog?item=12&amp;desc=vacation_hawaii</loc>       <<a href="http://www.sitemaps.org/protocol.html#changefreqdef">changefreq</a>>weekly</changefreq>    </url>    <<a href="http://www.sitemaps.org/protocol.html#urldef">url</a>>       <<a href="http://www.sitemaps.org/protocol.html#locdef">loc</a>>http://www.example.com/catalog?item=73&amp;desc=vacation_new_zealand</loc>       <<a href="http://www.sitemaps.org/protocol.html#lastmoddef">lastmod</a>>2004-12-23</lastmod>       <<a href="http://www.sitemaps.org/protocol.html#changefreqdef">changefreq</a>>weekly</changefreq>    </url>    <<a href="http://www.sitemaps.org/protocol.html#urldef">url</a>>       <<a href="http://www.sitemaps.org/protocol.html#locdef">loc</a>>http://www.example.com/catalog?item=74&amp;desc=vacation_newfoundland</loc>       <<a href="http://www.sitemaps.org/protocol.html#lastmoddef">lastmod</a>>2004-12-23T18:00:15+00:00</lastmod>       <<a href="http://www.sitemaps.org/protocol.html#prioritydef">priority</a>>0.3</priority>    </url>    <<a href="http://www.sitemaps.org/protocol.html#urldef">url</a>>       <<a href="http://www.sitemaps.org/protocol.html#locdef">loc</a>>http://www.example.com/catalog?item=83&amp;desc=vacation_usa</loc>       <<a href="http://www.sitemaps.org/protocol.html#lastmoddef">lastmod</a>>2004-11-23</lastmod>    </url> </urlset> </pre> <div class="backtotop"> <a href="http://www.sitemaps.org/protocol.html#top">Back to top</a></div> <h2> <a href="http://www.blogger.com/null" id="index" name="index"></a>Using Sitemap index files (to group multiple sitemap files)</h2> You can provide multiple Sitemap files, but each Sitemap file that you provide must have no more than 50,000 URLs and must be no larger than 10MB (10,485,760 bytes). If you would like, you may compress your Sitemap files using gzip to reduce your bandwidth requirement; however the sitemap file once uncompressed must be no larger than 10MB. If you want to list more than 50,000 URLs, you must create multiple Sitemap files. If you do provide multiple Sitemaps, you should then list each Sitemap file in a Sitemap index file. Sitemap index files may not list more than 50,000 Sitemaps and must be no larger than 10MB (10,485,760 bytes) and can be compressed. You can have more than one Sitemap index file. The XML format of a Sitemap index file is very similar to the XML format of a Sitemap file. The Sitemap index file must: <ul> <li>Begin with an opening <code><<a href="http://www.sitemaps.org/protocol.html#sitemapIndex_sitemapindex">sitemapindex</a>></code> tag and end with a closing <code></sitemapindex></code> tag.</li> <li>Include a <code><<a href="http://www.sitemaps.org/protocol.html#sitemapIndex_sitemap">sitemap</a>></code> entry for each Sitemap as a parent XML tag.</li> <li>Include a <code><<a href="http://www.sitemaps.org/protocol.html#sitemapIndex_loc">loc</a>></code> child entry for each <code><sitemap></code> parent tag.</li> </ul> The optional <code><<a href="http://www.sitemaps.org/protocol.html#sitemapIndex_lastmod">lastmod</a>></code> tag is also available for Sitemap index files. Note: A Sitemap index file can only specify Sitemaps that are found on the same site as the Sitemap index file. For example, http://www.yoursite.com/sitemap_index.xml can include Sitemaps on http://www.yoursite.com but not on http://www.example.com or http://yourhost.yoursite.com. As with Sitemaps, your Sitemap index file must be UTF-8 encoded. <h3> <a href="http://www.blogger.com/null" id="sitemapIndexXMLExample" name="sitemapIndexXMLExample"></a>Sample XML Sitemap Index</h3> The following example shows a Sitemap index that lists two Sitemaps: <pre><?xml version="1.0" encoding="UTF-8"?> <<a href="http://www.sitemaps.org/protocol.html#sitemapIndex_sitemapindex">sitemapindex</a> xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">    <<a href="http://www.sitemaps.org/protocol.html#sitemapIndex_sitemap">sitemap</a>>       <<a href="http://www.sitemaps.org/protocol.html#sitemapIndex_loc">loc</a>>http://www.example.com/sitemap1.xml.gz</loc>       <<a href="http://www.sitemaps.org/protocol.html#sitemapIndex_lastmod">lastmod</a>>2004-10-01T18:23:17+00:00</lastmod>    </sitemap>    <<a href="http://www.sitemaps.org/protocol.html#sitemapIndex_sitemap">sitemap</a>>       <<a href="http://www.sitemaps.org/protocol.html#sitemapIndex_loc">loc</a>>http://www.example.com/sitemap2.xml.gz</loc>       <<a href="http://www.sitemaps.org/protocol.html#sitemapIndex_lastmod">lastmod</a>>2005-01-01</lastmod>    </sitemap> </sitemapindex> </pre> Note: Sitemap URLs, like all values in your XML files, must be <a href="http://www.sitemaps.org/protocol.html#escaping">entity escaped</a>. <h3> <a href="http://www.blogger.com/null" id="sitemapIndexTagDefinitions" name="sitemapIndexTagDefinitions"></a>Sitemap Index XML Tag Definitions</h3> <table style="width: 80%px;"> <tbody> <tr> <th>Attribute </th> <th></th> <th>Description </th> </tr> <tr> <td><a href="http://www.blogger.com/null" id="sitemapIndex_sitemapindex" name="sitemapIndex_sitemapindex"></a><code><sitemapindex></code> </td> <td>required </td> <td>Encapsulates information about all of the Sitemaps in the file. </td> </tr> <tr class="alt"> <td><a href="http://www.blogger.com/null" id="sitemapIndex_sitemap" name="sitemapIndex_sitemap"></a><code><sitemap></code> </td> <td>required </td> <td>Encapsulates information about an individual Sitemap. </td> </tr> <tr> <td><a href="http://www.blogger.com/null" id="sitemapIndex_loc" name="sitemapIndex_loc"></a><code><loc></code> </td> <td>required </td> <td>Identifies the location of the Sitemap. This location can be a Sitemap, an Atom file, RSS file or a simple text file.</td> </tr> <tr class="alt"> <td><a href="http://www.blogger.com/null" id="sitemapIndex_lastmod" name="sitemapIndex_lastmod"></a><code><lastmod></code> </td> <td>optional </td> <td>Identifies the time that the corresponding Sitemap file was modified. It does not correspond to the time that any of the pages listed in that Sitemap were changed. The value for the lastmod tag should be in <a href="http://www.w3.org/TR/NOTE-datetime"> W3C Datetime</a> format. By providing the last modification timestamp, you enable search engine crawlers to retrieve only a subset of the Sitemaps in the index i.e. a crawler may only retrieve Sitemaps that were modified since a certain date. This incremental Sitemap fetching mechanism allows for the rapid discovery of new URLs on very large sites.</td> </tr> </tbody></table> <div class="backtotop"> <a href="http://www.sitemaps.org/protocol.html#top">Back to top</a></div> <h2> <a href="http://www.blogger.com/null" id="otherformats" name="otherformats"></a>Other Sitemap formats</h2> The Sitemap protocol enables you to provide details about your pages to search engines, and we encourage its use since you can provide additional information about site pages beyond just the URLs. However, in addition to the XML protocol, we support RSS feeds and text files, which provide more limited information. <h3> Syndication feed</h3> You can provide an RSS (Real Simple Syndication) 2.0 or Atom 0.3 or 1.0 feed. Generally, you would use this format only if your site already has a syndication feed. Note that this method may not let search engines know about all the URLs in your site, since the feed may only provide information on recent URLs, although search engines can still use that information to find out about other pages on your site during their normal crawling processes by following links inside pages in the feed. Make sure that the feed is located in the highest-level directory you want search engines to crawl. Search engines extract the information from the feed as follows: <ul> <li><link> field - indicates the URL</li> <li>modified date field (the <pubDate> field for RSS feeds and the <updated> date for Atom feeds) - indicates when each URL was last modified. Use of the modified date field is optional. </li> </ul> <h3> Text file</h3> You can provide a simple text file that contains one URL per line. The text file must follow these guidelines: <ul> <li>The text file must have one URL per line. The URLs cannot contain embedded new lines.</li> <li>You must fully specify URLs, including the http.</li> <li>Each text file can contain a maximum of 50,000 URLs and must be no larger than 10MB (10,485,760 bytes). If you site includes more than 50,000 URLs, you can separate the list into multiple text files and add each one separately.</li> <li>The text file must use UTF-8 encoding. You can specify this when you save the file (for instance, in Notepad, this is listed in the Encoding menu of the Save As dialog box).</li> <li>The text file should contain no information other than the list of URLs.</li> <li>The text file should contain no header or footer information.</li> <li>If you would like, you may compress your Sitemap text file using gzip to reduce your bandwidth requirement.</li> <li>You can name the text file anything you wish. Please check to make sure that your URLs follow the <a href="http://www.ietf.org/rfc/rfc3986.txt">RFC-3986</a> standard for URIs, the <a href="http://www.ietf.org/rfc/rfc3987.txt">RFC-3987</a> standard for IRIs</li> <li>You should upload the text file to the highest-level directory you want search engines to crawl and make sure that you don't list URLs in the text file that are located in a higher-level directory. </li> </ul> Sample text file entries are shown below. <pre>http://www.example.com/catalog?item=1 http://www.example.com/catalog?item=11 </pre> <div class="backtotop"> <a href="http://www.sitemaps.org/protocol.html#top">Back to top</a></div> <h2> <a href="http://www.blogger.com/null" id="location" name="location"></a>Sitemap file location</h2> The location of a Sitemap file determines the set of URLs that can be included in that Sitemap. A Sitemap file located at http://example.com/catalog/sitemap.xml can include any URLs starting with http://example.com/catalog/ but can not include URLs starting with http://example.com/images/. If you have the permission to change http://example.org/path/sitemap.xml, it is assumed that you also have permission to provide information for URLs with the prefix http://example.org/path/. Examples of URLs considered valid in http://example.com/catalog/sitemap.xml include: <pre>http://example.com/catalog/show?item=23 http://example.com/catalog/show?item=233&user=3453 </pre> URLs not considered valid in http://example.com/catalog/sitemap.xml include: <pre>http://example.com/image/show?item=23 http://example.com/image/show?item=233&user=3453 https://example.com/catalog/page1.php </pre> Note that this means that all URLs listed in the Sitemap must use the same protocol (http, in this example) and reside on the same host as the Sitemap. For instance, if the Sitemap is located at http://www.example.com/sitemap.xml, it can't include URLs from http://subdomain.example.com. URLs that are not considered valid are dropped from further consideration. It is strongly recommended that you place your Sitemap at the root directory of your web server. For example, if your web server is at example.com, then your Sitemap index file would be at http://example.com/sitemap.xml. In certain cases, you may need to produce different Sitemaps for different paths (e.g., if security permissions in your organization compartmentalize write access to different directories). If you submit a Sitemap using a path with a port number, you must include that port number as part of the path in each URL listed in the Sitemap file. For instance, if your Sitemap is located at http://www.example.com:100/sitemap.xml, then each URL listed in the Sitemap must begin with http://www.example.com:100. <h3> <a href="http://www.blogger.com/null" id="sitemaps_cross_submits" name="sitemaps_cross_submits"></a>Sitemaps & Cross Submits</h3> To submit Sitemaps for multiple hosts from a single host, you need to "prove" ownership of the host(s) for which URLs are being submitted in a Sitemap. Here's an example. Let's say that you want to submit Sitemaps for 3 hosts: <pre>www.host1.com with Sitemap file sitemap-host1.xml www.host2.com with Sitemap file sitemap-host2.xml www.host3.com with Sitemap file sitemap-host3.xml </pre> Moreover, you want to place all three Sitemaps on a single host: www.sitemaphost.com. So the Sitemap URLs will be: <pre>http://www.sitemaphost.com/sitemap-host1.xml http://www.sitemaphost.com/sitemap-host2.xml http://www.sitemaphost.com/sitemap-host3.xml </pre> By default, this will result in a "cross submission" error since you are trying to submit URLs for www.host1.com through a Sitemap that is hosted on www.sitemaphost.com (and same for the other two hosts). One way to avoid the error is to prove that you own (i.e. have the authority to modify files) www.host1.com. You can do this by modifying the robots.txt file on www.host1.com to point to the Sitemap on www.sitemaphost.com. In this example, the robots.txt file at http://www.host1.com/robots.txt would contain the line "Sitemap: http://www.sitemaphost.com/sitemap-host1.xml". By modifying the robots.txt file on www.host1.com and having it point to the Sitemap on www.sitemaphost.com, you have implicitly proven that you own www.host1.com. In other words, whoever controls the robots.txt file on www.host1.com trusts the Sitemap at http://www.sitemaphost.com/sitemap-host1.xml to contain URLs for www.host1.com. The same process can be repeated for the other two hosts. Now you can submit the Sitemaps on www.sitemaphost.com. When a particular host's robots.txt, say http://www.host1.com/robots.txt, points to a Sitemap or a Sitemap index on another host; it is expected that for each of the target Sitemaps, such as http://www.sitemaphost.com/sitemap-host1.xml, all the URLs belong to the host pointing to it. This is because, as noted earlier, a Sitemap is expected to have URLs from a single host only. <div class="backtotop"> <a href="http://www.sitemaps.org/protocol.html#top">Back to top</a></div> <h2> <a href="http://www.blogger.com/null" id="validating" name="validating"></a>Validating your Sitemap</h2> The following XML schemas define the elements and attributes that can appear in your Sitemap file. You can download this schema from the links below: For Sitemaps: <a href="http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd"> http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd</a> For Sitemap index files: <a href="http://www.sitemaps.org/schemas/sitemap/0.9/siteindex.xsd"> http://www.sitemaps.org/schemas/sitemap/0.9/siteindex.xsd</a> There are a number of tools available to help you validate the structure of your Sitemap based on this schema. You can find a list of XML-related tools at each of the following locations: <a href="http://www.w3.org/XML/Schema#Tools">http://www.w3.org/XML/Schema#Tools</a> <a href="http://www.xml.com/pub/a/2000/12/13/schematools.html">http://www.xml.com/pub/a/2000/12/13/schematools.html</a> In order to validate your Sitemap or Sitemap index file against a schema, the XML file will need additional headers as shown below. Sitemap: <pre><?xml version='1.0' encoding='UTF-8'?> <urlset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"          xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd"          xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">    <url>       ...    </url> </urlset> </pre> Sitemap index file: <pre><?xml version='1.0' encoding='UTF-8'?> <sitemapindex xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"          xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/siteindex.xsd"          xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">    <sitemap>       ...    </sitemap> </sitemapindex> </pre> <div class="backtotop"> <a href="http://www.sitemaps.org/protocol.html#top">Back to top</a></div> <h2> <a href="http://www.blogger.com/null" id="extending" name="extending"></a>Extending the Sitemaps protocol</h2> You can extend the Sitemaps protocol using your own namespace. Simply specify this namespace in the root element. For example: <pre><?xml version='1.0' encoding='UTF-8'?> <urlset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"          xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd"          xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"          xmlns:example="http://www.example.com/schemas/example_schema">     <url>       <example:example_tag>          ...       </example:example_tag>       ...    </url> </urlset></pre> <div class="backtotop"> <a href="http://www.sitemaps.org/protocol.html#top">Back to top</a></div> <h2> <a href="http://www.blogger.com/null" id="informing" name="informing"></a>Informing search engine crawlers</h2> Once you have created the Sitemap file and placed it on your webserver, you need to inform the search engines that support this protocol of its location. You can do this by: <ul> <li><a href="http://www.sitemaps.org/protocol.html#submit_engine">submitting it to them via the search engine's submission interface</a></li> <li><a href="http://www.sitemaps.org/protocol.html#submit_robots">specifying the location in your site's robots.txt file</a></li> <li><a href="http://www.sitemaps.org/protocol.html#submit_ping">sending an HTTP reques</a>t </li> </ul> The search engines can then retrieve your Sitemap and make the URLs available to their crawlers. <h3> <a href="http://www.blogger.com/null" id="submit_engine" name="submit_engine"></a>Submitting your Sitemap via the search engine's submission interface </h3> To submit your Sitemap directly to a search engine, which will enable you to receive status information and any processing errors, refer to each search engine's documentation. <h3> <a href="http://www.blogger.com/null" id="submit_robots" name="submit_robots"></a>Specifying the Sitemap location in your robots.txt file </h3> You can specify the location of the Sitemap using a robots.txt file. To do this, simply add the following line including the full URL to the sitemap: <pre>Sitemap: http://www.example.com/sitemap.xml</pre> This directive is independent of the user-agent line, so it doesn't matter where you place it in your file. If you have a Sitemap index file, you can include the location of just that file. You don't need to list each individual Sitemap listed in the index file. You can specify more than one Sitemap file per robots.txt file. <pre>Sitemap: http://www.example.com/sitemap-host1.xml Sitemap: http://www.example.com/sitemap-host2.xml</pre> <h3> <a href="http://www.blogger.com/null" id="submit_ping" name="submit_ping"></a>Submitting your Sitemap via an HTTP request </h3> To submit your Sitemap using an HTTP request (replace <searchengine_URL> with the URL provided by the search engine), issue your request to the following URL: <pre><searchengine_URL>/ping?sitemap=sitemap_url</pre> For example, if your Sitemap is located at http://www.example.com/sitemap.gz, your URL will become: <pre><searchengine_URL>/ping?sitemap=http://www.example.com/sitemap.gz</pre> URL encode everything after the /ping?sitemap=: <pre><searchengine_URL>/ping?sitemap=http%3A%2F%2Fwww.yoursite.com%2Fsitemap.gz</pre> You can issue the HTTP request using wget, curl, or another mechanism of your choosing. A successful request will return an HTTP 200 response code; if you receive a different response, you should resubmit your request. The HTTP 200 response code only indicates that the search engine has received your Sitemap, not that the Sitemap itself or the URLs contained in it were valid. An easy way to do this is to set up an automated job to generate and submit Sitemaps on a regular basis. Note: If you are providing a Sitemap index file, you only need to issue one HTTP request that includes the location of the Sitemap index file; you do not need to issue individual requests for each Sitemap listed in the index. <div class="backtotop"> <a href="http://www.sitemaps.org/protocol.html#top">Back to top</a></div> <h2> Excluding content</h2> The Sitemaps protocol enables you to let search engines know what content you would like indexed. To tell search engines the content you don't want indexed, use a robots.txt file or robots meta tag. See <a href="http://www.robotstxt.org/">robotstxt.org</a> for more information on how to exclude content from search engines. <div class="backtotop"> <a href="http://www.sitemaps.org/protocol.html#top">Back to top</a></div> <div class="date"> Last Updated: 27 February 2008 </div> <a href="http://www.sitemaps.org/protocol.html#top">sitemaps.org - Protocol</a> <div class="zemanta-pixie" style="height: 15px; margin-top: 10px;"> <img alt="" class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=3e95858a-8948-4e97-b63d-e65ebed7bec4" style="border: none; float: right;" /></div> </div>

Sitemaps XML format - sitemaps.org - Protocol

This document describes the XML schema for the Sitemap protocol. The Sitemap protocol format consists of XML tags. All data values in a Site...

Membuat Peta Situs - Alat Webmaster Bantuan

<div dir="ltr" style="text-align: left;" trbidi="on"> <div class="article-container" data-tracking-cat="article-container"> <div class="main-section--answer main-section content-container"> Google dapat menerima Peta Situs Web dalam sejumlah format, namun sebaiknya buat Peta Situs berdasarkan protokol Peta Situs karena file yang sama dapat dikirimkan ke mesin telusur lainnya, seperti Bing dan Yahoo!, yang merupakan anggota <a href="http://www.sitemaps.org/">sitemaps.org</a>. Berikut adalah contoh Peta Situs dasar dengan entri tunggal untuk URL yang meliputi gambar dan video (demi kenyamanan, hanya ditampilkan sebagian informasi video yang tersedia). <div> <pre><?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:image="http://www.google.com/schemas/sitemap-image/1.1" xmlns:video="http://www.google.com/schemas/sitemap-video/1.1"> <url> <loc>http://www.example.com/foo.html</loc> <image:image> <image:loc>http://example.com/image.jpg</image:loc> </image:image> <video:video> <video:content_loc> http://www.example.com/video123.flv </video:content_loc> <video:player_loc allow_embed="yes" autoplay="ap=1"> http://www.example.com/videoplayer.swf?video=123 </video:player_loc> <video:thumbnail_loc> http://www.example.com/thumbs/123.jpg </video:thumbnail_loc> <video:title>Grilling steaks for summer</video:title> <video:description> Masak bistik dengan kematangan yang sempurna setiap saat </video:description> </video:video> </url> </urlset> </pre> </div> Anda dapat membuat Peta Situs secara manual. Selain itu, ada sejumlah <a href="http://code.google.com/p/sitemap-generators/wiki/SitemapGenerators">alat pihak ketiga</a> yang dapat membantu membuat Peta Situs. Selain format standar di atas, Google juga menerima yang berikut sebagai Peta Situs: <ul> <li>RSS, mRSS, dan Atom 1.0: Google menerima umpan RSS (Real Simple Syndication) 2.0 dan Atom 1.0. Jika Anda memiliki umpan RSS atau Atom, Anda dapat mengirimkan URL umpan sebagai Peta Situs. Umumnya perangkat lunak blog membuatkan umpan untuk Anda. Perhatikan bahwa umpan hanya dapat memberikan informasi di URL terbaru. Selain itu, Anda dapat menggunakan <a href="https://support.google.com/webmasters/answer/answer.py?answer=183265">umpan mRSS (media RSS) untuk memberikan detail konten video kepada Google</a> di situs Anda.</li> <li>File teks: Untuk Peta Situs Web dasar (Peta Situs yang hanya mencakup URL laman web, bukan gambar, video, atau data khusus lainnya), Anda dapat memberikan file teks sederhana yang berisi satu URL per baris kepada Google. Misalnya: <div> <pre> http://www.example.com/file1.html http://www.example.com/file2.html </pre> </div> Untuk mendapatkan hasil terbaik, ikuti pedoman berikut: <ul> <li>Anda harus menyebutkan URL secara lengkap sebab Google berusaha untuk merayapi URL tersebut sesuai dengan yang diberikan.</li> <li>Berkas teks tersebut harus menggunakan enkode UTF-8.</li> <li>File teks seharusnya tidak berisi apa-apa selain daftar URL.</li> <li>Anda dapat menamai berkas teks tersebut sesuai keinginan Anda. Sebaiknya berikan ekstensi .txt (misalnya, sitemap.txt) pada file.</li> </ul> </li> </ul> Setelah Peta Situs selesai, Anda dapat mengirimkannya ke Google menggunakan Alat Webmaster. <ul> <li><a href="https://support.google.com/webmasters/answer/183668#1">Pedoman untuk Peta Situs</a></li> <li><a href="https://support.google.com/webmasters/answer/183668#2">Ekstensi Peta Situs (video, gambar, Berita ...)</a></li> <li><a href="https://support.google.com/webmasters/answer/183668#3">Definisi tag Peta Situs</a></li> </ul> <h3> <a href="http://www.blogger.com/null" id="3" name="1"></a>Pedoman untuk Peta Situs</h3> <ul> <li>File Peta Situs tidak dapat berisi lebih dari 50.000 URL dan tidak dapat lebih besar dari 50 MB saat tidak terkompresi. Jika peta situs Anda lebih besar dari itu, pilah file peta situs Anda menjadi beberapa peta situs berukuran lebih kecil. Batas ini membantu memastikan bahwa server web Anda tidak kelebihan beban saat memroses file berukuran besar ke Google.</li> <li>Jika Anda memiliki lebih dari satu Peta Situs, Anda dapat mencantumkannya di <a href="https://support.google.com/webmasters/answer/answer.py?answer=71453">file indeks Peta Situs</a> lalu kirimkan file indeks Peta Situs ke Google. Anda tidak perlu mengirimkan setiap file Peta Situs secara individu.</li> <li>Tentukan semua URL menggunakan syntax yang sama. Contoh, jika Anda menetapkan lokasi situs seperti http://www.example.com/, maka daftar URL tidak boleh berisi URL yang diawali dengan http://example.com/.</li> <li>Jangan menyertakan ID sesi dalam URL.</li> <li>File Peta Situs Anda harus menyebutkan namespace XML berikut: <code>xmlns="http://www.sitemaps.org/schemas/sitemap/0.9".</code></li> <li>URL Peta Situs harus dikodekan dengan UTF8 dan dikodekan oleh server web di lokasinya agar dapat dibaca.</li> <li>Jika situs Anda dapat diakses di versi www dan non-www domain Anda, Anda tidak perlu mengirimkan Peta Situs terpisah untuk setiap versi. Namun, sebaiknya pilih salah satu versi www atau non-www, dan gunakan <a href="https://support.google.com/webmasters/answer/answer.py?answer=139066">metode standardisasi</a> yang disarankan untuk memberi tahu versi yang Anda gunakan kepada Google.</li> <li>Jika Anda mempertimbangkan untuk menyewa konsultan guna membantu Anda mengoptimalkan Peta Situs, sebaiknya baca rekomendasi kami tentang bekerja dengan Pengoptimal Mesin Telusur (Search Engine Optimizers/SEO). Selain itu, Anda harus memahami <a href="https://support.google.com/webmasters/answer/answer.py?answer=35769">Pedoman Webmaster</a> dan <a href="https://www.google.com/webmasters/docs/search-engine-optimization-starter-guide.pdf">Panduan Memulai SEO</a>. Juga bermanfaat jika Anda memeriksa situs atau bisnis yang serupa dengan kolega Anda.</li> <li>File Peta Situs tidak bergantung pada bahasa konten. Untuk memastikan bahwa versi setiap bahasa dapat dirayapi dan diindeks, gunakan URL yang unik. Semua URL tersebut dapat dimasukkan ke file Peta Situs Anda.</li> </ul> <h3> <a href="http://www.blogger.com/null" id="2" name="1"></a>Ekstensi Peta Situs (video, gambar, Berita ...)</h3> Seperti informasi URL dasar, Peta Situs dapat berisi informasi mendetail tentang jenis konten khusus di situs Anda, termasuk <a href="https://support.google.com/webmasters/answer/answer.py?answer=80471">video</a>, <a href="https://support.google.com/webmasters/answer/answer.py?answer=178636">gambar</a>, <a href="https://support.google.com/webmasters/answer/answer.py?answer=34627">seluler</a>, <a href="http://www.google.com/support/news_pub/bin/answer.py?answer=75717">Berita</a>, dan <a href="https://support.google.com/webmasters/answer/answer.py?answer=75225">kode sumber perangkat lunak</a>. Tergantung pada jenis konten yang dimasukkan di Peta Situs Anda, Anda seharusnya menentukan namespace yang sesuai, yang tercantum di tabel di bawah. Pastikan untuk menentukan namespace untuk setiap jenis informasi yang dimasukkan di Peta Situs Anda. <table class="nice-table"> <tbody> <tr> <td>URL Umum</td> <td><code>xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"</code></td> </tr> <tr> <td>Gambar</td> <td><code>xmlns:image="http://www.google.com/schemas/sitemap-image/1.1"</code></td> </tr> <tr> <td>Video</td> <td><code>xmlns:video="http://www.google.com/schemas/sitemap-video/1.1"</code></td> </tr> <tr> <td>Seluler</td> <td><code>xmlns:mobile="http://www.google.com/schemas/sitemap-mobile/1.0"</code></td> </tr> <tr> <td>Berita</td> <td><code>xmlns:news="http://www.google.com/schemas/sitemap-news/0.9".</code>Namun, sebaiknya buat Peta Situs terpisah untuk konten berita, Peta Situs tersebut akan sangat sering dirayapi untuk memeriksa artikel baru. <a href="http://www.google.com/support/news_pub/bin/topic.py?topic=11666">Informasi selengkapnya tentang Peta Situs baru.</a><a href="http://www.blogger.com/null"> </a></td> </tr> </tbody> </table> <h3> <a href="http://www.blogger.com/null" name="1"></a>Definisi tag Peta Situs</h3> Tabel berikut menguraikan tag yang diwajibkan untuk Peta Situs yang mencantumkan URL web. Untuk menambahkan informasi yang lebih mendetail tentang jenis konten khusus, lihat <a href="https://support.google.com/webmasters/answer/answer.py?answer=80471">video</a>, <a href="https://support.google.com/webmasters/answer/answer.py?answer=178636">gambar</a>, <a href="https://support.google.com/webmasters/answer/answer.py?answer=34627">seluler</a>, <a href="http://www.google.com/support/news_pub/bin/answer.py?answer=75717">Berita</a>, dan <a href="https://support.google.com/webmasters/answer/answer.py?answer=75225">kode sumber perangkat lunak</a>. <table class="nice-table"> <tbody> <tr> <td>Tag</td> <td>Wajib?</td> <td>Deskripsi</td> </tr> <tr> <td><code><urlset></code></td> <td>Wajib diisi</td> <td>Menyertakan semua informasi tentang kumpulan URL yang dimasukkan di Peta Situs.</td> </tr> <tr> <td><code><url></code></td> <td>Wajib diisi</td> <td>Menyertakan semua informasi tentang URL tertentu.</td> </tr> <tr> <td><code><loc></code></td> <td>Wajib diisi</td> <td>Menentukan URL. Untuk gambar dan video, menentukan laman landas (alias laman putar, laman perujuk). Harus berupa URL yang unik.</td> </tr> <tr> <td><code><lastmod></code></td> <td>Opsional</td> <td>Tanggal URL terakhir dimodifikasi, dengan format TTTT-BB-HHTjj:mmTZD (nilai waktu opsional).</td> </tr> <tr> <td><code><changefreq></code></td> <td>Opsional</td> <td>Memberikan petunjuk tentang seberapa sering laman kemungkinan berubah. Nilai yang valid adalah: <ul> <li><code>always</code>. Gunakan untuk laman yang berubah setiap saat laman tersebut diakses.</li> <li><code>hourly</code></li> <li><code>daily</code></li> <li><code>weekly</code></li> <li><code>monthly</code></li> <li><code>yearly</code></li> <li><code>never. </code> Gunakan nilai ini untuk URL yang diarsipkan.</li> </ul> </td> </tr> <tr> <td><code><prioritas></code></td> <td>Opsional</td> <td>Mendiskripsikan prioritas URL yang relatif terhadap semua URL lain di situs tersebut. Prioritas ini dapat berkisar mulai dari 1.0 (sangat penting sekali) hingga 0.1 (tidak penting sama sekali). Tidak memengaruhi peringkat situs Anda di hasil penelusuran Google. Karena nilai ini relatif terhadap laman lain di situs Anda, memberikan prioritas tinggi (atau menentukan prioritas yang sama untuk semua URL) tidak akan membantu peringkat penelusuran situs Anda. Selain itu, menyetel semua laman dengan prioritas yang sama tidak akan berpengaruh.</td> </tr> </tbody> </table> </div> </div> <a href="https://support.google.com/webmasters/answer/183668">Membuat Peta Situs - Alat Webmaster Bantuan</a> <div class="zemanta-pixie" style="height: 15px; margin-top: 10px;"> <img alt="" class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=3e95858a-8948-4e97-b63d-e65ebed7bec4" style="border: none; float: right;" /></div> </div>

Membuat Peta Situs - Alat Webmaster Bantuan

Google dapat menerima Peta Situs Web dalam sejumlah format, namun sebaiknya buat Peta Situs berdasarkan protokol Peta Situs karena file yan...

Krishna Vandanu invites you to check out beachlovi, tips and adult info

<div dir="ltr" style="text-align: left;" trbidi="on"> I'm following beachlovi, tips and adult info and think you'll be interested in it as well. To check it out, follow the link below: <a href="http://www.beachlovi.tk/?psinvite=ALRopfW2tCeuJZcOqt1dtRXLSCoYdT6275LndX4riCUtYN9hD7hX5uGyALov-XWnNLz6uvW-shRj_fnNf9tTMa3khRr0i2yUfQ" rel="nofollow" target="_blank">http://www.beachlovi.tk/?psinvite=ALRopfW2tCeuJZcOqt1dtRXLSCoYdT6275LndX4riCUtYN9hD7hX5uGyALov-XWnNLz6uvW-shRj_fnNf9tTMa3khRr0i2yUfQ </a> ----- <a class="zem_slink" href="http://www.google.com/friendconnect" rel="homepage" target="_blank" title="Google Friend Connect">Google Friend Connect</a> helps people with common interests discover interesting sites and interesting people. To learn more, visit http://www.google.com/friendconnect <div class="zemanta-pixie"> <img alt="" class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=5537f329-0b7f-4c72-b18e-fe714a15a698" /></div> </div>

Krishna Vandanu invites you to check out beachlovi, tips and adult info

I'm following beachlovi, tips and adult info and think you'll be interested in it as well. To check it out, follow the link below: ...

Do more with Google Translate

<div class="g-doc-1024 standard"> <div class="g-section header"> <a href="http://translate.google.com/?hl=en"><img alt="Google" src="http://www.google.com/intl/en/images/logos/translate_logo.gif" /></a></div> <div class="g-section"> <div class="g-unit"> <a href="http://www.google.com/images/icons/illustrations/translate_robot-lb80.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"> </a> <h1 id="tour-heading"> Harness the power of <a class="zem_slink freebase/en/google_translate" href="http://translate.google.com/translate_t?hl=en#" rel="homepage nofollow" title="Google Translate">Google Translate</a> in your favorite <a class="zem_slink freebase/en/google" href="http://google.com/" rel="homepage nofollow" title="Google">Google</a> products.</h1> </div> <div class="g-unit"> <table border="1" cellpadding="0" cellspacing="0" class="MsoTableGrid" height="114" style="border-collapse: collapse; border: medium none; width: 558px;"> <tbody> <tr> <td style="border: 1pt solid windowtext; padding: 0mm 5.4pt; width: 87.2pt;" valign="top" width="116"><div style="text-align: center;"> </div> <div class="separator" style="clear: both; text-align: center;"> <a href="http://www.google.com/images/icons/illustrations/translate_search-lb80.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="http://www.google.com/images/icons/illustrations/translate_search-lb80.png" /></a></div> <h3 style="text-align: center;"> Search</h3> </td> <td style="border-color: windowtext windowtext windowtext -moz-use-text-color; border-style: solid solid solid none; border-width: 1pt 1pt 1pt medium; padding: 0mm 5.4pt; width: 87.2pt;" valign="top" width="116"><div class="separator" style="clear: both; text-align: center;"> <a href="http://www.google.com/images/icons/illustrations/translate_webpage-lb80.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="http://www.google.com/images/icons/illustrations/translate_webpage-lb80.png" /></a></div> <h3 style="text-align: center;"> Explore</h3> </td> <td style="border-color: windowtext windowtext windowtext -moz-use-text-color; border-style: solid solid solid none; border-width: 1pt 1pt 1pt medium; padding: 0mm 5.4pt; width: 87.2pt;" valign="top" width="116"><div class="separator" style="clear: both; text-align: center;"> <a href="http://www.google.com/images/icons/feature/mail-lb80.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="http://www.google.com/images/icons/feature/mail-lb80.png" /></a></div> <h3 style="text-align: center;"> Communicate</h3> </td> <td style="border-color: windowtext windowtext windowtext -moz-use-text-color; border-style: solid solid solid none; border-width: 1pt 1pt 1pt medium; padding: 0mm 5.4pt; width: 87.2pt;" valign="top" width="116"><div class="separator" style="clear: both; text-align: center;"> <a href="http://www.google.com/images/icons/feature/mobile_ad-blb80.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="http://www.google.com/images/icons/feature/mobile_ad-blb80.png" /></a></div> <h3 style="text-align: center;"> Mobile</h3> </td> <td style="border-color: windowtext windowtext windowtext -moz-use-text-color; border-style: solid solid solid none; border-width: 1pt 1pt 1pt medium; padding: 0mm 5.4pt; width: 87.25pt;" valign="top" width="116"><div class="separator" style="clear: both; text-align: center;"> <a href="http://www.google.com/images/icons/illustrations/translate_robot-lb80.png" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="http://www.google.com/images/icons/illustrations/translate_robot-lb80.png" /></a></div> <h3> Professional</h3> </td> </tr> </tbody></table> <div class="topnav g-section"> <div class="page-button page-button-off" id="icon-professional"> <h3>   Communicate globally<a name="more"></a></h3> </div> </div> <div class="hidden" id="icon-communicate-content" style="display: block;"> <div class="h3-content"> <h4> <a class="zem_slink freebase/en/gmail" href="http://gmail.com/" rel="homepage nofollow" title="Gmail">Gmail</a></h4> <div class="item"> What if you receive an important email – but it's not in your language? If you use Gmail, it can automatically translate foreign email messages into your own language. Just enable the feature in Gmail <a class="zem_slink freebase/en/google_labs" href="http://www.googlelabs.com/" rel="homepage nofollow" title="Google Labs">Labs</a>. <a href="http://mail.google.com/support/bin/answer.py?hl=en&answer=139503">Here’s how</a>.</div> <img class="screenshot" src="http://translate.google.com/about/images/tour/mail.gif" /> <a href="http://www.blogger.com/post-edit.g?blogID=3861076408851542502&postID=3900884021933331883" name="chat"></a> <div class="item"> While in Gmail, you can also have a multilingual chat with your <a class="zem_slink freebase/en/pen_pal" href="http://en.wikipedia.org/wiki/Pen_pal" rel="wikipedia nofollow" title="Pen pal">pen-pal</a> from overseas. Add the <a href="http://www.google.com/support/talk/bin/answer.py?hl=en&answer=89921">Google Translate Chat Bot</a> to your conversation and break down the <a class="zem_slink freebase/en/language_barrier" href="http://en.wikipedia.org/wiki/Language_barrier" rel="wikipedia nofollow" title="Language barrier">language barrier</a>.</div> <a href="http://www.google.com/support/talk/bin/answer.py?hl=en&answer=89921"><img class="screenshot" src="http://translate.google.com/about/images/tour/chat.gif" /></a> <h4> Google Groups</h4> <div class="item"> Ever wanted to have a discussion with people from across the world? Take a look at the translate features in <a href="http://groups.google.com/?hl=en">Google Groups</a> – you can post messages in your language and see responses from users from all over the world, translated into your language. We love the feature and use it on our <a href="https://groups.google.com/group/google-translate?hl=en">own discussion group</a> to connect with our users.</div> Try it now: Visit the <a href="https://groups.google.com/group/google-translate?hl=en">Google Translate Discussion Group</a>. <h4> <a class="zem_slink" href="http://moderator.appspot.com/" rel="homepage nofollow" title="Google Moderator">Google Moderator</a></h4> <div class="item"> Want to have a multilingual debate? Use <a href="http://moderator.appspot.com/?hl=en">Google Moderator</a> – it automatically translates questions and comments from other languages to yours.</div> Try it now: Visit <a href="http://moderator.appspot.com/?hl=en">Google Moderator</a>. <a href="http://www.blogger.com/post-edit.g?blogID=3861076408851542502&postID=3900884021933331883" name="docs"></a> <h4> <a class="zem_slink" href="http://docs.google.com/" rel="homepage nofollow" title="Google Docs">Google Docs</a></h4> <div class="item"> Translate entire documents, and phrases and words within documents, in Google Docs. Learn how to <a href="http://docs.google.com/support/bin/answer.py?hl=en&answer=159659">here</a>.</div> Try it now: Start a document in <a href="http://docs.google.com/?hl=en">Google Docs</a>. <a href="http://www.blogger.com/post-edit.g?blogID=3861076408851542502&postID=3900884021933331883" name="youtube"></a> <h4> <a class="zem_slink freebase/en/youtube" href="http://www.youtube.com/" rel="homepage nofollow" title="YouTube">YouTube</a></h4> <div class="item"> Want to attract an international audience on YouTube? With a few clicks, you can transcribe your videos automatically and add translated closed captions. Learn how to <a href="http://www.youtube.com/static?hl=en&template=captions_about">here</a>.</div> <img class="screenshot-border" height="245" src="http://translate.google.com/about/images/tour/youtube.jpg" width="400" /></div> </div> <div class="hidden" id="icon-mobile-content" style="display: none;"> <a href="http://www.blogger.com/post-edit.g?blogID=3861076408851542502&postID=3900884021933331883" name="mobile-solutions"></a> <h3> Mobile solutions</h3> <div class="h3-content"> <h4> Google Translate Mobile Website</h4> <div class="item"> Visit <a href="http://translate.google.com/m?hl=en">translate.google.com/m</a> on your <a class="zem_slink freebase/en/mobile_phone" href="http://en.wikipedia.org/wiki/Mobile_phone" rel="wikipedia nofollow" title="Mobile phone">mobile phone</a> to view Google Translate, optimised for your mobile device.</div> <img class="screenshot" src="http://translate.google.com/about/images/tour/mobile-barcode.png" /> <h4> Google Translate Android Application</h4> <div class="item"> To unleash the true power of Google Translate, download our Android application. You can speak to it and hear back a spoken translation. The application also supports History, Starring and a rich dictionary for all you logophiles.</div> <div class="item"> Try it now! Scan this barcode, using the "Barcode scanner" application, to download Google Translate for Android:</div> <img class="screenshot" src="http://translate.google.com/about/images/tour/android-barcode.png" /></div> </div> <div class="hidden" id="icon-professional-content" style="display: none;"> <a href="http://www.blogger.com/post-edit.g?blogID=3861076408851542502&postID=3900884021933331883" name="professional-business-and-developer-tools"></a> <h3> Professional, business and developer tools</h3> <div class="h3-content"> <div class="item"> Machine translation is an excellent way to expose your website or business to a global audience. Here are some of the ways that Google Translate can help you and your business:</div> <h4> Google Translate AJAX API</h4> <div class="item"> Engineer a translation solution for your website, using the Google Translate AJAX API. Learn more on our <a href="http://code.google.com/intl/en/apis/ajaxlanguage/">Google Code page</a>.</div> <h4> Translator Toolkit</h4> <div class="item"> Are you a professional translator? You can increase your productivity by using <a href="http://translate.google.com/toolkit?hl=en">Google Translator Toolkit</a>. Translator Toolkit features WYSIWYG UI for context when translating, machine translation, glossaries and the ability to upload and download your translation memories.</div> <h4> Translate Web Element</h4> Your browser does not support iframes.</div> </div> </div> <div class="g-unit footer"> <a class="noline" href="http://www.google.com/intl/en/about.html"> </a> </div> </div> </div> <a href="http://translate.google.com/about/intl/en_ALL/tour.html#chat">Do more with Google Translate</a> <div class="zemanta-pixie"> <img alt="" class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=f90a6852-7ff7-461a-b9bd-55535c885c71" /><script defer="defer" src="http://static.zemanta.com/readside/loader.js" type="text/javascript"> </script></div>

Do more with Google Translate

Harness the power of Google Translate in your favorite Google products. Search Explore Communicate Mobile Professional Commu...