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 |
4507
|
daigle
|
be available in a web search. This is especially useful in Metacat for making
|
42 |
|
|
individual metadata entries available via web searches. This does not happen now
|
43 |
|
|
because of lack of a web accessible browse heirarchy of metadata.</p>
|
44 |
4506
|
daigle
|
|
45 |
|
|
<p>The site map file contains metadata about the available sites on your server. For
|
46 |
|
|
information on the sitemap protocol, please refer to
|
47 |
|
|
<a href="https://www.google.com/webmasters/tools/docs/en/protocol.html"> the Google
|
48 |
|
|
page on using the sitemap protocol</a>. The sitemap file must be available via the
|
49 |
|
|
web on your server.</p>
|
50 |
|
|
|
51 |
|
|
<p>Metacat generates the sitemap file automatically on a daily basis (more on this in
|
52 |
|
|
the next section). You will need to manually register the sitemap file with Google in
|
53 |
|
|
order for it to take effect. We discuss that in the
|
54 |
|
|
<a href="#SubmitSitemap">Submit Your Sitemap</a> section.</p>
|
55 |
|
|
|
56 |
4507
|
daigle
|
<p>The scope of this discussion encompasses Google
|
57 |
|
|
web searches only.</p>
|
58 |
|
|
|
59 |
4506
|
daigle
|
<a name="Implementation"></a><div class="header2">Metacat Implementation</div>
|
60 |
|
|
<p>Metacat automatically generates sitemap files for all public documents in
|
61 |
|
|
your catalog. You can view the sitemap files at:
|
62 |
|
|
<div class="code"><webapps_dir>/sitemaps</div>
|
63 |
|
|
You should see one or more files in this directory that look like
|
64 |
|
|
<div class="code">metacat<X>.xml</div>
|
65 |
|
|
Metacat limits the number of entries to 25,000 (Google's limit is 50,000). So for
|
66 |
|
|
every group of 25,000 public documents in Metacat, you will see additional sitemap
|
67 |
|
|
files where <X> increments for each file.</p>
|
68 |
|
|
|
69 |
|
|
<p>You should verify that your sitemap files are available to the web by browsing
|
70 |
|
|
to
|
71 |
|
|
<div class="code"><your_web_context>/sitemaps/metacat<X>.xml</div>
|
72 |
|
|
for instance
|
73 |
|
|
<div class="code">your.server.org/knb/sitemaps/metacat1.xml</div></p>
|
74 |
|
|
|
75 |
|
|
<a name="SubmitSitemap"></a><div class="header1">Submit Your Sitemap</div>
|
76 |
|
|
<a name="GoogleRegister"></a><div class="header2">Register With Google</div>
|
77 |
|
|
<p>You will need to register for a Google Webmaster Tools account in order to
|
78 |
|
|
register your sitemaps. A good description of how to do this is on
|
79 |
|
|
<a href="http://www.google.com/support/webmasters/bin/answer.py?answer=34575&topic=8496">
|
80 |
|
|
the Google help site</a>. Follow the instructions there to get your sitemaps registered.</p>
|
81 |
|
|
|
82 |
|
|
<p>One note: you should register the full url path to your sitemap files, including
|
83 |
|
|
the http:// (or https://) headers.</p>
|
84 |
|
|
|
85 |
|
|
<a name="GoogleReRegister"></a><div class="header2">Re-Register With Google</div>
|
86 |
|
|
<p>You will need to periodically revisit the Google Webmaster Tools utility to
|
87 |
|
|
refresh your sitemap registration as you add more publicly accessible data to
|
88 |
|
|
Metacat.</p>
|
89 |
|
|
<p>A future enhancement to Metacat will automatically refresh the sitemap
|
90 |
|
|
registration when necessary, although you will still need to do the initial
|
91 |
|
|
registration manually.</p>
|
92 |
|
|
|
93 |
|
|
<br>
|
94 |
|
|
<a href="./pagedreturn.html">Back</a> | <a href="./metacattour.html">Home</a> |
|
95 |
|
|
<a href="./unimplem.html">Next</a>
|
96 |
|
|
</ul>
|
97 |
|
|
|
98 |
|
|
|
99 |
|
|
</BODY>
|
100 |
|
|
</HTML>
|