| 1 |
4506
|
daigle
|
<!--
|
| 2 |
|
|
* sitemaps.html
|
| 3 |
|
|
*
|
| 4 |
|
|
* Authors: Michael Daigle
|
| 5 |
|
|
* Copyright: 2008 Regents of the University of California and the
|
| 6 |
|
|
* National Center for Ecological Analysis and Synthesis
|
| 7 |
|
|
* For Details: http://www.nceas.ucsb.edu/
|
| 8 |
|
|
* Created: 2008 November 4
|
| 9 |
|
|
* Version:
|
| 10 |
|
|
* File Info: '$ '
|
| 11 |
|
|
*
|
| 12 |
|
|
*
|
| 13 |
|
|
-->
|
| 14 |
|
|
<HTML>
|
| 15 |
|
|
<HEAD>
|
| 16 |
|
|
<TITLE>Search Engine Sitemaps</TITLE>
|
| 17 |
|
|
<link rel="stylesheet" type="text/css" href="./default.css">
|
| 18 |
|
|
</HEAD>
|
| 19 |
|
|
<BODY>
|
| 20 |
|
|
<table width="100%">
|
| 21 |
|
|
<tr>
|
| 22 |
|
|
<td class="tablehead" colspan="2"><p class="label">Search Engine Sitemaps</p></td>
|
| 23 |
|
|
<td class="tablehead" colspan="2" align="right">
|
| 24 |
|
|
<a href="./pagedreturn.html">Back</a> | <a href="./metacattour.html">Home</a> |
|
| 25 |
|
|
<a href="./unimplem.html">Next</a>
|
| 26 |
|
|
</td>
|
| 27 |
|
|
</tr>
|
| 28 |
|
|
</table>
|
| 29 |
|
|
|
| 30 |
|
|
<div class="header1">Table of Contents</div>
|
| 31 |
|
|
<div class="toc1"><a href="#Intro">About Sitemaps</a></div>
|
| 32 |
|
|
<div class="toc2"><a href="#Overview">Overview</a></div>
|
| 33 |
|
|
<div class="toc2"><a href="#Implementation">Metacat Implementation</a></div>
|
| 34 |
|
|
<div class="toc1"><a href="#SubmitSitemap">Submit Your Sitemap</a></div>
|
| 35 |
|
|
<div class="toc2"><a href="#GoogleRegister">Register With Google</a></div>
|
| 36 |
|
|
<div class="toc2"><a href="#GoogleReRegister">Re-Register With Google</a></div>
|
| 37 |
|
|
|
| 38 |
|
|
<a name="Intro"></a><div class="header1">About Sitemaps</div>
|
| 39 |
|
|
<a name="Overview"></a><div class="header2">Overview</div>
|
| 40 |
|
|
<p>Sitemaps are xml files that tell search engines which sites you would like to
|
| 41 |
|
|
be available in a web search. The scope of this discussion encompasses Google
|
| 42 |
|
|
web searches only.</p>
|
| 43 |
|
|
|
| 44 |
|
|
<p>The site map file contains metadata about the available sites on your server. For
|
| 45 |
|
|
information on the sitemap protocol, please refer to
|
| 46 |
|
|
<a href="https://www.google.com/webmasters/tools/docs/en/protocol.html"> the Google
|
| 47 |
|
|
page on using the sitemap protocol</a>. The sitemap file must be available via the
|
| 48 |
|
|
web on your server.</p>
|
| 49 |
|
|
|
| 50 |
|
|
<p>Metacat generates the sitemap file automatically on a daily basis (more on this in
|
| 51 |
|
|
the next section). You will need to manually register the sitemap file with Google in
|
| 52 |
|
|
order for it to take effect. We discuss that in the
|
| 53 |
|
|
<a href="#SubmitSitemap">Submit Your Sitemap</a> section.</p>
|
| 54 |
|
|
|
| 55 |
|
|
<a name="Implementation"></a><div class="header2">Metacat Implementation</div>
|
| 56 |
|
|
<p>Metacat automatically generates sitemap files for all public documents in
|
| 57 |
|
|
your catalog. You can view the sitemap files at:
|
| 58 |
|
|
<div class="code"><webapps_dir>/sitemaps</div>
|
| 59 |
|
|
You should see one or more files in this directory that look like
|
| 60 |
|
|
<div class="code">metacat<X>.xml</div>
|
| 61 |
|
|
Metacat limits the number of entries to 25,000 (Google's limit is 50,000). So for
|
| 62 |
|
|
every group of 25,000 public documents in Metacat, you will see additional sitemap
|
| 63 |
|
|
files where <X> increments for each file.</p>
|
| 64 |
|
|
|
| 65 |
|
|
<p>You should verify that your sitemap files are available to the web by browsing
|
| 66 |
|
|
to
|
| 67 |
|
|
<div class="code"><your_web_context>/sitemaps/metacat<X>.xml</div>
|
| 68 |
|
|
for instance
|
| 69 |
|
|
<div class="code">your.server.org/knb/sitemaps/metacat1.xml</div></p>
|
| 70 |
|
|
|
| 71 |
|
|
<a name="SubmitSitemap"></a><div class="header1">Submit Your Sitemap</div>
|
| 72 |
|
|
<a name="GoogleRegister"></a><div class="header2">Register With Google</div>
|
| 73 |
|
|
<p>You will need to register for a Google Webmaster Tools account in order to
|
| 74 |
|
|
register your sitemaps. A good description of how to do this is on
|
| 75 |
|
|
<a href="http://www.google.com/support/webmasters/bin/answer.py?answer=34575&topic=8496">
|
| 76 |
|
|
the Google help site</a>. Follow the instructions there to get your sitemaps registered.</p>
|
| 77 |
|
|
|
| 78 |
|
|
<p>One note: you should register the full url path to your sitemap files, including
|
| 79 |
|
|
the http:// (or https://) headers.</p>
|
| 80 |
|
|
|
| 81 |
|
|
<a name="GoogleReRegister"></a><div class="header2">Re-Register With Google</div>
|
| 82 |
|
|
<p>You will need to periodically revisit the Google Webmaster Tools utility to
|
| 83 |
|
|
refresh your sitemap registration as you add more publicly accessible data to
|
| 84 |
|
|
Metacat.</p>
|
| 85 |
|
|
<p>A future enhancement to Metacat will automatically refresh the sitemap
|
| 86 |
|
|
registration when necessary, although you will still need to do the initial
|
| 87 |
|
|
registration manually.</p>
|
| 88 |
|
|
|
| 89 |
|
|
<br>
|
| 90 |
|
|
<a href="./pagedreturn.html">Back</a> | <a href="./metacattour.html">Home</a> |
|
| 91 |
|
|
<a href="./unimplem.html">Next</a>
|
| 92 |
|
|
</ul>
|
| 93 |
|
|
|
| 94 |
|
|
|
| 95 |
|
|
</BODY>
|
| 96 |
|
|
</HTML>
|