Sitemap 파일이란 무엇이며 왜 필요한가요?
Sitemap은 사이트에 대한 URL과 각 URL에 대한 추가 정보가 함께 나와 있는 XML 파일입니다. Sitemap을 통해 Google과 기타 검색엔진은 웹사이트에 대해 다음과 같은 중요한 정보를 얻을 수 있습니다.
비텍스트 페이지나 여러 매개변수가 포함된 URL 등과 같이 Google의 일반적인 크롤링 과정에서 발견되지 않는 URL을 포함하여 전체 사이트 URL 목록
사이트의 페이지가 변경되는 빈도. 예를 들어, 제품 페이지는 매일 업데이트되지만 내 정보 페이지는 몇 달에 한번씩 업데이트됩니다.
각 페이지가 최종 수정된 일자
사이트 페이지간의 상대적인 중요도. 예를 들어, 홈페이지의 상대적인 중요도를 1.0이라고 하면 카테고리 페이지는 0.8, 개별 블로그 항목이나 제품 페이지는 0.5라고 할 수 있습니다. 이 우선순위는 특정 URL과 기타 URL을 비교한 상대적인 중요도만 나타낼 뿐 실제 검색결과에서 페이지의 순위에는 영향을 미치지 않습니다.
Sitemap이 특히 유용하게 사용되는 경우는 다음과 같습니다.
동적 콘텐츠가 있는 사이트
AJAX 또는 Flash 등과 같이 크롤링 과정 동안 Googlebot이 쉽게 검색하지 못하는 페이지가 있는 사이트
연결되는 링크가 많지 않은 새로운 사이트
사이트에 서로 잘 연결되지 않거나 전혀 연결되지 않는 콘텐츠 페이지를 보관하는 대형 보관함이 있는 사이트
Sitemap를 사용하면 페이지의 크롤링 및 색인생성 속도가 향상됩니다. 그러나 크롤링/색인생성 과정에 영향을 주는 요소는 이외에도 다양합니다. 그 요소는 다음과 같습니다.
페이지로 링크되는 사이트의 수
콘텐츠의 고유성 및 관련성 정도
페이지를 성공적으로 크롤링하는 Google의 능력
Google의 웹마스터 가이드라인에 나와 있는 모든 요소
Sitemap에서는 홈페이지와 HTML 사이트맵에서와 마찬가지로 사이트를 다른 각도에서 볼 수 있지만, Sitemap의 웹 크롤링 방식이 Google의 일반적인 웹 크롤링 방식과 다르지는 않습니다. Google은 이 프로그램의 사용 여부와 관계없이 일반적인 방식으로 계속해서 사이트를 검색하고 색인을 생성합니다. 이 서비스를 사용한다고 해서 사이트에 유해하지는 않습니다. URL이 크롤링되거나 색인에 추가되는 시기 또는 여부에 대해 예측하거나 보증할 수 없습니다. 그러나 시간이 지나 Google이 이런 과정들을 보완하고 웹마스터의 요구사항을 더 잘 파악할 수 있게 되면 색인 추가에 걸리는 소요 시간이 짧아지고 도달 범위가 확대될 것으로 기대하고 있습니다.
Google은 sitemaps.org 사이트에 명시된 바와 같이 Sitemap Protocol 0.9를 따릅니다. 따라서 Sitemap Protocol 0.9를 사용하여 Google용으로 만든 Sitemap은 sitemaps.org의 기준을 채택한 다른 검색엔진과 호환됩니다.
표준 Sitemap이 대부분의 사이트에 작동하지만 특정 유형의 콘텐츠에 대한 특수 Sitemap을 만들어 제출할 수도 있습니다. 사용 가능한 Sitemap 유형은 다음과 같습니다.
동영상 Sitemap
모바일 Sitemap
online holdem poker
뉴스 Sitemap
코드 검색 Sitemap
구글 Sitemap Generator는 Sitemap Protocol을 사용한 당신의 사이트 Sitemap을 생성하는 Python script 이다. 이 스크립트는 URL 리스트들, 웹 서버의 디렉토리들, 또는 엑세스 로그들로 부터 사이트 맵을 생성할 수 있다. 이 스크립트를 사용하기 위해서는 :
만약 당신이 이런것들에 대해 알고 있지 않다면, 당신의 웹 호스팅 회사에 문의하기 바란다.
자 이제 당신은 시작할 준비가 되어 있을 것이다. 여기 당신이 해야할 것들에 대한 요약이 있다.
만약 당신이 Sitemap Generator를 사용할 수 없다면, 단순한 text 파일과 같이 다른 형태로 당신의 Google webmaster 툴에 Sitemap을 추가할 수 있다. 또한 Google Sitemap을 지원하는 다른 제품의 프로그램들(여기)을 찾아볼 수도 있다.
뉴스 유형의 사이트맵 생성과 관련하여 : 이 Sitemap Generator를 Google News Sitemap을 생성하는데 사용하는 것은 추천하지 않는다. 이는 News Sitemap만의 특별한 충족조건이 있기 때문이다. News Sitemap은 최근에 새로 쓰여진 것들만(사이트의 전체가 아니라)으로 동적으로 리스트되는 경향이 있고, 자주 업데이트 되어진다.
Sitemap Generator 파일은 다음의 주소로 부터 Zip 또는 GZ 포맷의 파일로 다운로드 할 수 있다.
http://sourceforge.net/project/showfiles.php?group_id=137793&package_id=153422
일단 여러분이 파일을 다운로드 했다면, 로컬 디렉토리에 그것을 풀기바란다. 다음의 파일들이 들어있다.
이 주제에서는 설정파일 생성을 위한 단계적인 절차를 제공한다. 또한 이용가능한 옵션에 대한 전체 참고문서도 제공한다. 만약 당신이 Mobile Sitemap을 생성할 것라면, 추가적인 모바일 가이드라인을 보기바란다.
당신의 사이트에 대한 설정파일을 생성하기 위해, 당신은 다음의 정보들을 가지고 있어야 한다.
Create the configuration file as follows:
<site base_url="http://www.example.com/" store_into="/var/www/docroot/sitemap.xml.gz" verbose="1">
URL
Locate the following section:
<!-- ** MODIFY or DELETE ** "url" nodes specify individual URLs to include in the map. <br> Required attributes: href - the URL Optional attributes: lastmod - timestamp of last modification (ISO8601 format) changefreq - how often content at this URL is usually updated priority - value 0.0 to 1.0 of relative importance in your site --> <url href="http://www.example.com/stats?q=name" /> <url href="http://www.example.com/stats?q=age" lastmod="2004-11-14T01:00:00-07:00" changefreq="yearly" priority="0.3" />
This section gives two examples: the first includes only the required attribute and the second includes the required attribute as well as the optional attributes.
Use this format for each of the URLs you want to include. The changefreq attribute gives Google a general idea of how often the URL is updated. This helps Google know how often to visit the page for new content. The priority attribute gives Google information about the relative importance of this page compared to the other pages of your site. This attribute has no effect on how Google compares your page to pages on other sites, it just helps Google know which pages of your site that you think are most important.
URL list
Locate the following section:
<!-- ** MODIFY or DELETE ** "urllist" nodes name text files with lists of URLs. An example file "example_urllist.txt" is provided. Required attributes: path - path to the file Optional attributes: encoding - encoding of the file if not US-ASCII --> <urllist path="example_urllist.txt" encoding="UTF-8" />
Use this format to point to the path and name of the text file that contains your list of URLs. You can use the provided example_urllist.txt file as a template for that text file. You can specify either a relative or complete path to your web server. For instance, if the Sitemap Generator and urlist.txt file are located in the same directory, you can simply specify the filename of the .txt file, If you create a text file with an encoding other than UTF-8, you can use the encoding attribute to indicate this encoding. If you have multiple .txt files, you can use wildcards. For instance:
<urllist path="example_urllist*.txt" encoding="UTF-8" />
For each URL you include in the text file, you can specify the last modification date, change frequency, and priority. See the URLlist text file reference section for complete information about the structure of this file.
Directory paths
Locate the following section:
<!-- ** MODIFY or DELETE ** "directory" nodes tell the script to walk the file system and include all files and directories in the Sitemap. Required attributes: path - path to begin walking from url - URL equivalent of that path Optional attributes: default_file - name of the index or default file for directory URLs --> <directory path="/var/www/icons" url="http://www.example.com/images/" /> <directory path="/var/www/docroot" url="http://www.example.com/" default_file="index.html" />
This section gives two examples. If all of your pages are contained in subdirectories of one path, then you only need to include one entry. However, if you have multiple paths to pages on your site, include an entry for each.
Remember that each URL must begin with the base URL you specified in step 3. For instance, the examples given in the example_config.xml file both have URLs that begin with http://www.example.com/. Therefore, both URLs are valid.
Replace the example entries with entries for your site. Many sites will only have one entry that points to the base URL. Ensure that path value is the complete path to the directory on your web server. Ensure that the url value is the complete URL, including the protocol (such as http) and a trailing slash, if required.
You can use the default_file parameter to specify the filename that your server uses as the default page for a directory. In the above example, /var/www/docroot resolves to http://www.example.com/index.html. You are not required to specify this. However, if you do, the Sitemap Generator will include the page that maps to each subdirectory only once (rather than list both the directory URL and filename URL) and will use the last modified date of the file (rather than the directory) to extract the lastmod attribute for that page.
Access logs
Locate the following section:
<!-- ** MODIFY or DELETE ** "accesslog" nodes tell the script to scan webserver log files to extract URLs on your site. Both Common Logfile Format (Apache's default logfile) and Extended Logfile Format (IIS's default logfile) can be read. Required attributes: path - path to the file Optional attributes: encoding - encoding of the file if not US-ASCII --> <accesslog path="/etc/httpd/logs/access.log" encoding="UTF-8" /> <accesslog path="/etc/httpd/logs/access.log.0" encoding="UTF-8" /> <accesslog path="/etc/httpd/logs/access.log.1.gz" encoding="UTF-8" />
This section gives three examples. You should replace these entries and include an entry for each log file. Ensure that the path value is the complete path and filename on your web server. If the log files are not encoded as US-ASCII or UTF-8, then use the optional encoding attribute to specify the encoding. Rather than list each log file, you can use wildcards. For instance, in the above example, you could include the following entry that would include all three log files:
<accesslog path="/etc/httpd/logs/access.log*" encoding="UTF-8" />
The Sitemap Generator assigns priority to URLs it finds in the logs based on how often each URL is accessed. For instance, a URL that has been accessed 100 times will be given a higher priority than a URL that has been accessed twice. The actual priority assignment is relative and depends on each URL as compared to other URLs in the site.
sitemap
Locate the following section:
<!-- ** MODIFY or DELETE ** "sitemap" nodes tell the script to scan other Sitemap files. This can be useful to aggregate the results of multiple runs of this script into a single Sitemap. Required attributes: path - path to the file --> <sitemap path="/var/www/docroot/subpath/sitemap.xml" />
This section gives one example. You should replace this entry and include an entry for each Sitemap you want to include. Ensure that the path value is the complete path and filename on your web server. You can list gzipped Sitemaps as well, as long as they have a .gz extension. Rather than list each Sitemap, you can use wildcards. For instance, the following entry would include any Sitemaps that begin with the word “sitemap” and have an .xml extension:
<sitemap path="/var/www/docroot/subpath/sitemap*.xml" />
The Sitemap Generator extracts all URLs and the optional data listed for each URL for every Sitemap you list and creates one Sitemap with this information. At this time, we can't guarantee that this method will work Sitemaps created with tools other than the Sitemap Generator.
Locate the filter definition section:
<!-- ******************************************************** FILTERS Filters specify wild-card patterns that the script compares against all URLs it finds. Filters can be used to exclude certain URLs from your Sitemap, for instance if you have hidden content that you hope the search engines don't find. Filters can be either type="wildcard", which means standard path wildcards (* and ?) are used to compare against URLs, or type="regexp", which means regular expressions are used to compare. Filters are applied in the order specified in this file. An action="drop" filter causes exclusion of matching URLs. An action="pass" filter causes inclusion of matching URLs, shortcutting any other later filters that might also match. If no filter at all matches a URL, the URL will be included. Together you can build up fairly complex rules. The default action is "drop". The default type is "wildcard". You can MODIFY or DELETE these entries as appropriate for your site. However, unlike above, the example entries in this section are not contrived and may be useful to you as they are. ********************************************************* --> <!-- Exclude URLs that end with a '~' (IE: emacs backup files) --> <filter action="drop" type="wildcard" pattern="*~" /> <!-- Exclude URLs within UNIX-style hidden files or directories --> <filter action="drop" type="regexp" pattern="/\.[^/]*" />
You can use filtering to exclude specific URLs from the generated Sitemap. You might want to do this to create a cleaner list, to reduce redundant listings, or to keep certain URLs from being indexed. Note that if you use a robots.txt file to keep URLs from being indexed, then even if the URLs are included in your Sitemap, Google will not search or index them.
You can use any or all of the filtering methods. You can delete the entries you don’t need and can create additional entries, if desired. Below are sample usages.
<filter action="drop" type="wildcard" pattern="*.jpg" />
This filter excludes URLs that end in .jpg. You might want to include a similar filter if all of your site’s images are embedded within HTML pages and should not be accessed as standalone URLs.
<filter action="pass" type="wildcard" pattern="*.htm*" /> <filter action="drop" type="wildcard" pattern="*" />
This filter includes all .htm* files but excludes everything else.
Once you have made all the changes for your site, save the file. Config File Syntax Reference
A complete explanation of the config file syntax is below. Each tag begins with a code sample, followed by a description of the attributes.
site Required tag at the beginning of each config file.
<site base_url="http://www.example.com/" store_into="/var/www/html/sitemap.xml.gz" verbose="1" supress_search_engine_notify="1" default_encoding="UTF-8">
base_url
required The HTTP path of the base of your website - only URLs that begin with this base can be included in the Sitemap
store_into
required The web server path to the desired output file. The script will create this file - there's no need to create the file before running the script.
verbose
optional Enter a number from 0-3, with higher numbers corresponding to increased debug information
suppress_search_engine_notify
optional Disable search engine notification by entering “1” for testing purposes
default_encoding
optional Specify a character encoding to be applied to file system paths and URLs
url
Optional tag that you can use to list each URL in your site.
<url href="http://www.example.com/stats?q=age" lastmod="2004-11-14T01:00:00-07:00" changefreq="yearly" priority="0.3" />
href
required The HTTP path of the base of your website - only URLs that begin with this base can be included in the Sitemap
lastmod
optional The time the URL was last modified in W3C Datetime format (YYYY-MM-DDThh:mm:ss+00:00). You may omit the time portion. Examples:
"2005-02-21T18:00:15+00:00" "2005-02-21"
changefreq
optional The frequency with which the URL is likely to change. This is considered a hint and not a command. The value must be one of “always”, “hourly”, “daily”, “weekly”, “monthly”, “yearly”, or “never”.
priority
optional The priority of this page relative to other pages on the same site. The value is a number between 0.0 and 1.0, where 0.0 is the lowest priority and 1.0 is the highest priority. The priority can affect the order that search engines select URLs to explore on your site. Since the priority is relative, it is only used to select between URLs within your own site; the priority of your pages will not be compared to the priority of pages on other sites.
urllist
Optional tag that you can use to point to a text file that contains a list of the URLs in your site.
<urllist path="/var/www/html/urllist.txt" encoding="UTF-8" />
path
required The path and filename of the .txt file. You can specify either a relative or complete path.
encoding
optional The encoding of the file, if not UTF-8.
The urllist.txt file is a simple text file containing a list of URLs to map. You can also include optional attributes for each URL. Attributes are entered on the same line as the URL and are separated by a single space. For example:
http://www.example.com/abc/something http://www.example.com/abc/xyy.pdf lastmod=2001-12-31T14:05:06+00:00 http://www.example.com/abc/def?x=12&y=23 changefreq=weekly priority=0.3 lastmod optional The time the URL was last modified in W3C Datetime format (YYYY-MM-DDThh:mm:ss+00:00). You may omit the time portion. Examples:
"2005-02-21T18:00:15+00:00" "2005-02-21"
changefreq optional The frequency with which the URL is likely to change. This is considered a hint and not a command. The value must be one of “always”, “hourly”, “daily”, “weekly”, “monthly”, “yearly”, or “never”. priority optional The priority of this page relative to other pages on the same site. The value is a number between 0.0 and 1.0, where 0.0 is the lowest priority and 1.0 is the highest priority. The priority can affect the order that search engines select URLs to explore on your site. Since the priority is relative, it is only used to select between URLs within your own site; the priority of your pages will not be compared to the priority of pages on other sites.
directory Optional tag that you can use to specify directories in your site so the Sitemap Generator can create a list of URLs from the files found in those directories.
–> <directory path=”/var/www/icons” url=“http://www.example.com/images/” /> <directory path=”/var/www/docroot” url=“http://www.example.com/” default_file=“index.html” /> path required States the initial path. Sitemap Generator will traverse this directory and all subdirectories. url required Specifies the URL equivalent of the path value. default_file optional Specifies the default file for a directory on the server.
accesslog Optional tag that you can use to specify the path and filename of IIS and Apache-style access logs so the Sitemap Generator can automatically pick up URLs from them.
<accesslog path=”/etc/httpd/logs/access-0.log” encoding=“UTF-8”/> path required States the path to the file. encoding optional Specifies encoding of the file, if not UTF-8.
sitemap Optional tag that you can use to specify the path and filename of existing Sitemaps that you have created with the Sitemap Generator. The Sitemap Generator will create a single Sitemap that includes the URLs contained in each Sitemap.
<sitemap path=”/var/www/docroot/subpath/sitemap.xml” /> path required States the path to the Sitemap file.
filter Optional tag that you can use to build rules that include or exclude specific files. Filters are obeyed in the order in which they appear in the config.xml file. However, intermixing filter entries and input entries (url, urllist, directory, or accesslog) has no additional effect - every URL the Sitemap Generator adds to the Sitemap is first compared against every filter. If no filter matches a URL, the default is to include the URL in the Sitemap.
<filter action=“drop” type=“wildcard” pattern=“*/internal/*” /> action optional The action the filter should take. Valid values are:
drop - excludes matching URLs. This is the default action, so if no action is specified, the generator assumes “drop”. pass - includes matching URLs.
type optional The type of filtering. Valid values are:
wildcard - standard path wildcards (? and *) are used to compare against URLs. This is the default type, so if no type is specified, the generator assumes “wildcard”. regexp - regular expressions are used. pattern required Specifies the pattern to match against.
Encodings
Files referenced by your configuration file, either URL lists or web server logs, can use encodings other than the default UTF-8. You can specify alternate encodings in config.xml to affect how the Sitemap Generator reads your files. Some common encodings are:
encoding=“utf-8” is the assumed default encoding=“ascii” is a subset of UTF-8 so you don't have to specify it encoding=“iso-8859-1” is common for many west European languages 2b. Additional information for creating a mobile configuration file
You create a configuration file for a Mobile Sitemap in the same way as for a non-mobile Sitemap. However, you must create a separate config file for each markup language and run the Sitemap Generator with each config file separately so that you create a separate Sitemap for each.
Each config file must:
Specify a different filename for the store_into value. Use filters to specify the URLs to exclude and include for the markup language. Remember that each Sitemap should include URLs for only one markup language. This means that the same URL may be included in multiple Sitemaps, if those URLs serve multiple markup languages. Examples of filtering
Below are some examples of how you can use extension-based filters to generate Mobile Sitemaps for different markup languages. The specific filtering you use should be based on the types of markup languages used in your site, and how you specify each type. If you have implemented the details of your site differently (for instance, you may organize URLs with different markup languages in separate folders), you should filter based on the specifics of your site implementation. Remember that filters are applied in the order you list them in the config file. So, the first filter you should list is a “pass” action that specifies the URLs you want to include in the Sitemap.
To create a Sitemap for WML (WAP 1.2) content:
<filter action=“pass” type=“wildcard” pattern=“*.wml” /> <filter action=“drop” type=“wildcard” pattern=“*.*” />
To create a Sitemap for XHTML mobile profile (WAP 2.0) content:
<filter action=“pass” type=“wildcard” pattern=“*.xhtml” /> <filter action=“drop” type=“wildcard” pattern=“*.*” />3. Uploading the files to your web server
You should upload the following files to your web server in a location you can access from a command line:
config.xml —this is the configuration file you just created using example_config.xml. sitemap_gen.py —this is the Python script that generates your Sitemap. urllist.txt —this file is optional; you only need to include it if you used the text file method of generating a Sitemap. The method you use to upload these files depends on your environment. Common methods include FTP and SCP. For more information, contact your web host.
4. Running the Sitemap Generator script (sitemap_gen.py)
In order to run the Sitemap Generator, you’ll need to connect to your web server. The method you use to connect depends on your environment. For instance, you can generally access a UNIX-based server using SSH. For more information on connecting to your web server and running scripts, talk to your web host.
Once you have copied the files to your web server, you'll need to run the Sitemap Generator script. Connect to your web server and run the following command (replace <path/config.xml> with the path to and filename of your configuration file; if you have uploaded this file to the same location as the Python script, you can exclude the path):
python sitemap_gen.py –config=<path/config.xml>
For instance, a UNIX-based command line might look similar to this:
A MS-DOS-based command shell might look similar to this:
Tip: If you're testing your configuration and are not ready to submit your Sitemap, the following syntax will prevent Sitemap Generator from contacting Google:
$ python sitemap_gen.py --config=config.xml --testing
You'll see the status of your request in the command prompt:
Reading configuration file: /path/config.xml Opened URLLIST "/path/urllist.txt" Walking DIRECTORY "/var/www/html/dir" Walking DIRECTORY "/var/www/html/dir2" Opened ACCESSLOG "/etc/httpd/logs/access-0.log" Sorting and normalizing collected URLs. Writing Sitemap file "/path/sitemap.xml.gz" with 1092 URLs Notifying search engines. Notifying www.google.com Count of file extensions on URLs: 208 .html 574 .jpg ... Number of errors: 0 Number of warnings: 0
If you don't see very much output like this, remember that the verbose setting in your configuration file affects how much information is printed on the screen. This example is representative of setting verbose to “1”.
Any errors in the file will also be returned. For instance, if you leave the url= attribute off a directory entry, the script will output the following:
[ERROR] Directory entries must have both "path" and "url" attributes Number of errors: 1
Correct any errors in your config.xml file and re-run the script. If no errors are present, the Sitemap Generator will create a new sitemap.xml.gz file in the location you specified in the config file.
5. Submitting your Sitemap to Google
The Sitemap Generator creates a sitemap.xml.gz file in the location you specified in the config file. Once this file is successfully created, make sure it is accessible through a web browser. Then, add it to your Google Sitemaps account. This enables Google to provide you with useful status and statistical information. If Google reports problems with your Sitemap, you can correct the problems and resubmit it. You only have to add the Sitemap manually once. After that, you can use an HTTP request to notify Google about changes to your Sitemap (although you can also resubmit it through your Google webmaster tools account).
6. Setting up a recurring script
We suggest setting up Sitemap Generator to run as often as your content is changed, to a maximum frequency of once per hour.
Webmasters with a UNIX web server may consider setting this up as a cron job.
Webmasters using other platforms should contact their system administrator for help in configuring recurring scripts. You may also benefit from peer advice in the Google Sitemaps Group on Google Groups.
You can use an HTTP request to let Google know about changes to your Sitemap. However, please make sure that you log in to Google webmaster tools with your Google Account once to manually add your Sitemap to your Google webmaster tools account.
Troubleshooting
In this section we talk about some common questions or issues that some people run into while using Sitemap Generator, and what you can do if you come across one of these.
Web-accessible
Issue: Sitemap Generator returns the following error and warning:
[ERROR] When attempting to access your generated Sitemap at the following URL: http://www.example.com/sitemap.xml.gz we failed to read it. Please verify the store_into path you specified in your configuration file is web-accessible. Consult the FAQ for more information. [WARNING] Proceeding to notify with an unverifiable URL.
What just happened? Sitemap Generator created the file where you specified, then attempted to retrieve it using HTTP just as a search engine would, and failed. It went ahead and notified search engines anyway, but it's outputting the error and warning to let you know that your Sitemap may be not readable by search engines.
Sitemap Generator creates your Sitemap file at the path specified in the store_into attribute of your config.xml file. Sitemap Generator then builds a URL to that file using the base_url attribute, and reports the URL to search engines. For instance, if you set the configuration to:
<site base_url="http://www.example.com/"
store_into="/var/www/html/sitemap.xml.gz">
Sitemap Generator will notify search engines to look for your Sitemap at:
http://www.example.com/sitemap.xml.gz
The file must be accessible through this URL. If the file can not be retrieved using this URL, search engines have no way of finding your Sitemap.
What can you do? You need to verify that your config.xml is specifying the correct base_url and store_into paths for your Sitemap. You also need to confirm that web browsers can retrieve the Sitemap file off of the base_url. If you find errors in the path or URL, you may need to re-run Sitemap Generator, or just move the Sitemap file to the correct place and notify search engines manually through their web sites.
Support for XML
Issue: Sitemap Generator gives the following error:
Some installs of Python 2.2 do not include complete support for XML. Please try upgrading your version of Python and re-running the script.
What just happened? As the message says, some platforms have a version of Python (the language the Sitemap Generator script is written in) that is missing support libraries needed for processing XML files. This script requires full XML support in order to run.
What can you do? Try upgrading your installed version of Python to a newer version. You will probably need to contact your system administrator to do this.
Note that this just affects the Sitemap Generator, not Sitemaps overall. If you have another method or tool for creating Sitemaps, you can certainly use it and submit your Sitemaps to search engines.
What are all the extra files in the .gz or .zip?
When you extract the sitemap_gen.py script, you'll probably see quite a few more files than we refer to above. The full file list looks closer to this:
AUTHORS ChangeLog COPYING example_config.xml example_urllist.txt PKG-INFO README setup.py sitemap_gen.py test_sitemap_gen.py
The extra files tend to be information on the package and licensing terms. You are encouraged to look through these files.
The one exception is test_sitemap_gen.py, which is a unit-test script that other developers may find useful if they wish to contribute to this open source project. If you intend to use Sitemap Generator without modifying any of the source code - this is the expected case for nearly everyone - you probably don't need this test script.
If you are interested in helping with this project, please visit http://sourceforge.net/projects/goog-sitemapgen. You can also find links to some third party programs that support Google Sitemaps here.
Non-ASCII characters
Issue: Your site domain name or URLs within it contain non-ASCII characters.
Generally, non-ASCII URLs should be encoded using UTF-8 before being percent-escaped. However, some webservers only respond correctly if URLs are encoded using an encoding other than UTF-8. All URLs within your Sitemap, as well as the URL of the Sitemap itself must be encoded for readability by the web server on which they are located. Within the site definition section, use the optional default_encoding attribute to specify the encoding used by your webserver. If you don't use this tag and your webserver uses an encoding other than UTF-8, we can't know which encoding to use.
If your URLs contain non-ASCII characters, we recommend that you run the Sitemap Generator script using Python 2.3 or higher. This version of Python has increased non-ASCII support. If your domain name contains non-ASCII characters, you must use Python 2.3 or later, as Internationalizing Domain Names in Applications (IDNA) support wasn't added until this version. Without IDNA support, the Sitemap Generator can't correctly encode a non-ASCII domain name.
Last modified: 15 April 2006
©2007 Google - Privacy Policy - Terms and Conditions - About Google
Discussion