robots.txt tester
Enter a domain and a path, and see whether a crawler is allowed to fetch it, with the rule that decided it and the whole file it came from.
How a crawler decides
A crawler does not stop at the first matching line. It compares every rule in its group and takes the one with the longest path pattern, so Allow /blog/public beats Disallow /blog for a URL that starts with both. When two matching patterns are exactly the same length, Allow wins.
A crawler reads exactly one group. It takes the group whose user agent names it most specifically, falls back to the group named with an asterisk, and follows nothing at all if neither is there. Rules in the other groups are invisible to it, which is why a rule that looks right often turns out to sit in a group the crawler never reads.
Why this page exists
Google removed the robots.txt tester from Search Console, and what replaced it reports far less, saying only whether one URL is blocked, on a property you have verified, without naming the rule. Most of the time the question is not whether a path is blocked but which line blocked it, and on a site somebody else runs.
A rule in robots.txt stops a crawler fetching a URL. It does not remove that URL from a search result, and it does not hide the page from anyone who has the address. Anything that must stay private needs authentication, and anything that must stay out of the results needs a noindex tag on a page a crawler is still allowed to read.
Questions about robots.txt
Report the bug, not a description of it
Session Replay captures the page, the console, the network log and the browser details in one link, so the next person to look at a broken page already has the whole thing in front of them.