Bot policy
Other languages:
Bahasa Indonesia • ‎Deutsch • ‎English • ‎Esperanto • ‎Napulitano • ‎Nederlands • ‎Ripoarisch • ‎Sunda • ‎Türkçe • ‎dansk • ‎español • ‎français • ‎galego • ‎italiano • ‎magyar • ‎occitan • ‎polski • ‎português • ‎português do Brasil • ‎română • ‎slovenčina • ‎svenska • ‎čeština • ‎ślůnski • ‎Ελληνικά • ‎Кыргызча • ‎беларуская • ‎български • ‎македонски • ‎русский • ‎српски / srpski • ‎тоҷикӣ • ‎українська • ‎ייִדיש • ‎עברית • ‎العربية • ‎فارسی • ‎नेपाली • ‎भोजपुरी • ‎मैथिली • ‎हिन्दी • ‎বাংলা • ‎ਪੰਜਾਬੀ • ‎മലയാളം • ‎ไทย • ‎中文 • ‎日本語 • ‎한국어

Bot policy and guidelines
This page outlines standards and guidelines related to bots which are enforced on some projects (see Bot policy/Implementation​); this can be checked by visiting "Project:Bot policy" on that wiki, which should point here or redirect to the local policy. This page is also policy on Meta, including automatic approval and global bots. To request bot access on Meta, please go to Meta:Requests for adminship#Requests for bot flags.
Bots are automated or semi-automated processes that edit pages with reduced or no direct human supervision. Because bots may potentially strain server resources or accidentally disrupt the project, bots must follow the policy and guidelines outlined below. The policy outlines the way bots may be used on applicable projects; bots which do not follow the policy may be blocked immediately until the operator has resolved any issues or non-compliance.
Policy
Bot account
A bot must be run using a separate account from the operator, as no human editor should be granted a bot flag. Its user page should clearly and visibly denote it as a bot to distinguish it from human editors, and operators must be available to answer any comments themselves. No user is permitted to make use of automated answering scripts. Some operators may choose to redirect the bot's talk page to their own, if their bot is not configured to detect messages.
Authorisation
There are three ways to obtain bot access on a wiki.
Global bots
Global bots are given access on all wikis that allow global bots (this must be explicitly permitted by local policy, see list). To qualify for global bot access, the following requirements must be met:
Automatic approval
If automatic approval is explicitly allowed on the wiki, bot operators can request a local bot flag directly from stewards. To qualify for this, the following requirements must be met:
Community consensus
Otherwise if there is a local community interested in processing bot applications, bots must obtain community approval on the most relevant local discussion page before editing without a bot flag at high speeds or without human supervision. Once there is consensus, a local bureaucrat will add the flag, or a steward may be requested to do so.
If there is no local community and the above does not apply, the bot must operate without a bot flag or not at all.
Unacceptable usage
Removal of global bot status
Global bot permissions will be removed:
Guidelines
Name
Although not required, the bot name should clearly contain the word "bot" in its user name to more easily distinguish it from human editors; the most common forms are derived from the operator's username (such as Pathosbot), or using disambiguation style (such as Xenophon (bot)).
Edit throttle and peak hours
Bots running without a bot flag should edit at intervals of over 1 minute between edits (= less than 1 edit per minute). Once they have been authorised and appropriately flagged, they should operate at an absolute minimum interval of 5 seconds (12 edits per minute). Bots should try to avoid running during the busiest hours, as they rapidly use server resources that should be reserved for human readers and editors. During these hours, they should operate at intervals of 20 seconds (3 edits per minute) to conserve resources.
Bots' editing speeds can be automatically adjusted based on server load (slave database server lag) by appending an extra parameter to the query string of each requested URL; see maxlag documentation on mediawiki.
Supervision
Unless the bot is publicly stated to run autonomously, the operator should remain available, occasionally check for messages, and be ready to shut down the bot if it does not perform as desired or if complaints are received. If the operator is not available, the bot may be blocked until any issues are resolved.
Best practices
Please read wikitech:Help:Toolforge/Developing successful tools for strong recommendations that will make life easier for you and for everyone else in the future!
Briefly:
See also
Last edited on 2 June 2021, at 22:07
Meta
Content is available under CC BY-SA 3.0 unless otherwise noted.
Privacy policy
Terms of Use
Desktop
HomeRandomLog inSettingsDonateAbout MetaDisclaimers
LanguageWatchEdit