ROBOTS: Difference between revisions

From NikkiWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 52: Line 52:
</highlight></code>
</highlight></code>


Below is the Robots Exclusion Protocol of "<u>[https://www.nicolesharp.net/robots.txt <code>nicolesharp.net/robots.txt</code>]</u>" showing hidden directories ("<code>/sandbox/</code>" and "<code>/testbox/</code>") for webdevelopment plus additional protocols and comments, including a comment line to provide <u>[[attribution]]</u> to the author of the file.
Below is the Robots Exclusion Protocol of "<u>[https://www.nicolesharp.net/robots.txt <code>nicolesharp.net/robots.txt</code>]</u>" showing hidden directories ("<code>/sandbox/</code>" and "<code>/testbox/</code>") for webdevelopment plus additional protocols and comments, including a comment line to provide <u>[[attribution]]</u> to the author of the file (<u>[[Nicole Sharp]]</u>).


<code><highlight lang="robots">
<code><highlight lang="robots">

Revision as of 2023-09-04T17:21:47

[Image.]  The Robots Exclusion Protocol will not prevent bad bots from accessing your website. [1]

One of the first files you should add to your website is "/robots.txt". [2]  This is a plaintext file for the Robots Exclusion Protocol (ROBOTS language).  What the robots.txt file does is instruct which webdirectories should be accessed or avoided by web bots.

An important thing to remember is that no bot is required to follow the Robots Exclusion Protocol.  The protocol only affects the behavior of compliant or well-behaved bots and anyone can program a bot to ignore the Robots Exclusion Protocol.  As such, you should not use the Robots Exclusion Protocol to try to hide sensitive directories, especially since publicly listing the directories in "/robots.txt" simply gives malicious bots an easy way to find the very directories you don't want them to visit.  To hide directories from public access (on Apache HTTP Server) you should use "/.htaccess" (hypertext access) instead.

Comments are added to the Robots Exclusion Protocol with a hash ("#") at the beginning of a new line.

For a public website, you want to allow access to all bots in order to get the site crawled and indexed by as many search engines as possible.  The following "/robots.txt" allows all bots access to all files and directories (minus anything excluded by "/.htaccess").

User-agent: *
Disallow:
# All bots can crawl/index all files and directories.

Websites and webdirectories that are not publicly indexed on search engines are referred to as the "deep web" or "darknet".  For example, you may want to create a mirror of your website for testing purposes, but don't want the development website publicly indexed since it will create duplicate or misleading results on search engines.  The following "/robots.txt" creates a darknet website that instructs all bots compliant with the Robots Exclusion Protocol to not crawl or index any part of the site.

User-agent: *
Disallow: /
# No bots can crawl/index any files or directories.

The following "/robots.txt" excludes two webdirectories ("/sandbox/" and "/testbox/") from crawling/indexing but permits access to all other files and directories on the site.

User-agent: *
Disallow: /sandbox/
Disallow: /testbox/
# Bots can crawl/index all files and directories except for "/sandbox/" and "/testbox/" (exclusion is applied recursively to all subdirectories of "sandbox" and "testbox").

"robots.txt" should always be placed in the root webdirectory ("/") if possible.

SITEMAP is an extension of the Robots Exclusion Protocol to allow listing a sitemap in the "robots.txt" file.  Having a precompiled list of links for the website available makes the bot's job to crawl and index the site a lot easier and more efficient.  Since the first thing a good bot does when accessing a website is to check for a "/robots.txt" file, it is best to have the link to the sitemap listed directly in the "/robots.txt" file so the bot doesn't have to guess whether or not the website has a sitemap available (which could be either "/sitemap.txt" or "/sitemap.xml"). The following example shows a "robots.txt" for a public website with a sitemap.  Note that unlike the other ROBOTS instructions, the sitemap should be provided with a full URL (uniform resource locator) and not with a relative link.

User-agent: *
Disallow:
Sitemap: https://www.example.net/sitemap.xml

Additional protocols such as SECURITY and HUMANS can also be added to the Robots Exclusion Protocol but these are not officially supported so should be commented out to avoid confusing bots while still allowing nonbot users to find the relevant files. Example below shows a "robots.txt" file for a public website that includes additional protocols for SITEMAP, SECURITY, and HUMANS.

User-agent: *
Disallow:
Sitemap: https://www.example.net/sitemap.txt
# Security: https://www.example.net/.well-known/security.txt
# Humans: https://www.example.net/humans.txt

Below is the Robots Exclusion Protocol of "nicolesharp.net/robots.txt" showing hidden directories ("/sandbox/" and "/testbox/") for webdevelopment plus additional protocols and comments, including a comment line to provide attribution to the author of the file (Nicole Sharp).

User-agent: *
Disallow: /sandbox/
Disallow: /testbox/
Sitemap: https://www.nicolesharp.net/sitemap.txt
# Security: https://www.nicolesharp.net/security.txt
# Humans: https://www.nicolesharp.net/humans.txt

# Robots Exclusion Protocol for Nicole Sharp's Website.
# 2023-09-04 Nicole Sharp
# https://www.nicolesharp.net/

see also

references

  1. commons:category:robots in art
  2. https://www.robotstxt.org/

keywords

bots, development, HUMANS, humans.txt, indexing, ROBOTS, robots.txt, SECURITY, security.txt, searchbots, SITEMAP, sitemap.txt, TXT, web, webcrawling, webdevelopment, WWW