Fix: robots.txt Case-Sensitive Path Issues
robots.txt paths are case-sensitive on Linux servers. Disallow: /Admin/ does not block /admin/. If your server serves URLs at both cases or if a URL in your robots.txt does not match the actual case of the path, the directive has no effect.
The Problem
CMS platforms like WordPress serve paths in lowercase by default. But some content management systems or frameworks generate URLs with mixed case (camelCase, PascalCase) or inconsistent capitalisation. If your robots.txt blocks /Products/ but the actual URL is /products/, the Disallow rule never fires.
The Fix
# Check your actual URL structure first: # curl -sI https://yourdomain.com/Admin/ | grep -i location # (If it redirects to /admin/, use /admin/ in robots.txt) # WRONG — wrong case: # Disallow: /Admin/ # Disallow: /WordPress/wp-admin/ # CORRECT — match actual URL case: Disallow: /admin/ Disallow: /wp-admin/ Disallow: /wp-login.php
Use ConfigClarity's robots.txt Validator URL Tester to test paths with different cases. Verify your actual URL paths by checking your server's access logs or by using curl -sI https://yourdomain.com/PATH/ to see if the server redirects to a differently-cased URL.
Validate your robots.txt live — fetch any URL and get a corrected file in one click.
Open robots.txt Validator →