Who this helps
- Site owners preparing crawl rules
- Developers reviewing a robots.txt change
Developer SEO Utility
Generate robots.txt content by entering crawler access rules, allowed paths, blocked paths, and a Sitemap URL.
Enter the site URL, crawler target, allowed paths, blocked paths, and Sitemap URL.
In general, allow public pages and block admin, search result, and private paths. However, robots.txt is not a security tool, so sensitive pages must be protected with server-side authentication and permissions.
Used to automatically create the Sitemap URL. Example: https://win-j.com
Use * to apply the rule to all search bots.
An optional directive supported by some search engines. Googlebot does not support Crawl-delay.
Enter one path per line. Example: /utility/
Enter paths you do not want search engines to crawl.
If left empty, /sitemap.xml will be generated based on the site URL.
Add commonly used robots.txt rules with simple checkboxes.
Save the content below as a robots.txt file in the site root path.
Enter settings and click Generate robots.txt.
Generate User-agent, Allow, Disallow and optional Sitemap lines for a site's robots.txt. These are crawling instructions, so review them separately from access control and indexing decisions.
List the public paths and paths you want crawlers to avoid.
Enter * or the intended crawler product token.
Enter one Allow or Disallow path per line.
Add an absolute sitemap URL or a site address for the default /sitemap.xml.
Generate, review and place the file at the site's /robots.txt.
Verify the deployed file and the target crawler's behavior.
This rule does not protect the admin page from visitors.
Check that the file actually exists before deployment.
The tool validates the agent token, accepts up to 10,000 entered rule lines and removes duplicate paths within each list. It checks HTTP(S) URL syntax without credentials. Optional Crawl-delay accepts a finite nonnegative decimal.
Rules are assembled in the browser without saving them to win-j. Review path names before publishing the public file.
Convert a URL list into XML, resolving relative paths and removing duplicates. Select canonical, indexable pages before generating the file; the tool cannot verify their live status.
Find missing, duplicate and questionable canonical links before publishing. The checker reads supplied HTML; it cannot confirm which canonical URL a search engine has selected.
It controls crawling, not guaranteed removal. Choose an indexing or access-control method appropriate to the page.
No. Check the documentation of any other crawler you intend to target.
Use a nonnegative decimal such as 2 or 0.5, without exponent notation, text or an infinite value.