Strictly necessary
Supports security, server sessions, form protection, administrator sign-in, and remembering your privacy choice.
Use the email below for technical questions, corrections, crawler documentation updates or problems with the site.
Please include the relevant page URL and enough technical detail to review the request accurately.
The website welcomes reports that help keep the crawler reference and tools accurate. Appropriate messages include corrections to crawler names or purposes, links to updated official documentation, broken robots.txt examples, unexpected generator or checker behavior, accessibility issues, privacy requests, and legitimate project or business enquiries.
For a content correction, include the exact page URL, the statement you believe is wrong or outdated, and a reliable supporting source. For a technical problem, include the affected tool, the steps that produced the issue, the browser or device used, and the visible error message. Do not send passwords, API keys, private robots.txt files, customer data, or other secrets.
The active public contact address is configured by the site owner for the production website. If no working address is displayed with this page or in the site’s public contact details, the external support channel has not yet been activated. Do not use placeholder or example addresses.
For a privacy request, identify the nature of the request and provide only the information reasonably needed to locate the relevant record. For a security concern, describe the issue responsibly and avoid accessing, changing, downloading, or publishing data that does not belong to you.
Messages may be prioritised by severity and relevance. A response time is not guaranteed, and general SEO consulting, legal opinions, crawler-provider support, or requests to control third-party bots on another company’s behalf may not receive an individual reply. The operator of this site cannot change the policies or systems of OpenAI, Google, Anthropic, Perplexity, Common Crawl, or other third parties.
Include the affected page URL, the exact statement or token that needs review, and a current official or otherwise reliable supporting source.
No. This project can explain robots.txt and related controls, but only the crawler operator and your own server controls determine real request behavior.
No. Never send passwords, API keys, private configuration, customer data, or other secrets through a general contact channel.
Provide the tool URL, steps to reproduce the problem, the input used after removing sensitive data, and the visible error or unexpected result.
Use the active public contact method published by the site operator and identify the type of request without including unnecessary sensitive information.