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