Independent check without a wSEO audit

Confirm that robots.txt is available and does not block valuable URLs

The file's existence proves little. A good result returns 200, contains understandable rules and permits crawling of representative pages that should attract search visitors.

  • open the file as an ordinary visitor;
  • test a valuable and a service URL;
  • save the file and result evidence.
Independent robots.txt verification with a browser, search-engine tool and command line
The file, representative URLs and an independent test should agree.

How to assess the result

robots.txt issue levels
SituationLevelAction
The whole site or a valuable section is unintentionally blocked; the file returns a server errorCriticalRestore a safe version and retest immediately.
Sitemap is absent or rules are outdated or ambiguous, while valuable control URLs remain crawlableNoncriticalConfirm intent and schedule a correction.
The file is available, syntax is clear, valuable URLs are allowed and service restrictions are intentionalNo problemSave evidence and retest after website changes.

Quick browser check

  1. Open https://example.com/robots.txt.
  2. Confirm that it is a text file, not an HTML error or login page.
  3. Find User-agent, Disallow, Allow and Sitemap.
  4. Look for an unexpected Disallow: /.
  5. Compare broad restrictions with valuable site URLs.

Google Search Console check

Use URL Inspection in Google Search Console for a verified property. Enter a valuable URL and check whether crawling is allowed. Google may temporarily use a cached robots.txt after a change.

  1. Test one valuable indexable page.
  2. Test one service page intentionally blocked.
  3. Repeat for WWW or a separate subdomain when used.
  4. Save screenshots of both outcomes.

HTTP response check

curl -I https://example.com/robots.txt
curl -sS https://example.com/robots.txt

Expect 200 and the rule text. A redirect may work for compatibility, but direct availability on every used host is preferable.

Representative URL test

python -m pip install robotexclusionrulesparser
python - <<'PY'
from robotexclusionrulesparser import RobotExclusionRulesParser
import urllib.request
r = RobotExclusionRulesParser()
r.parse(urllib.request.urlopen('https://example.com/robots.txt').read().decode())
print(r.is_allowed('Googlebot', 'https://example.com/important-page'))
PY

True means the selected crawler may access the URL under these rules.

Differences and test limitations

robots.txt is evaluated separately for every protocol, hostname and subdomain. A CDN or cache may serve an old version, and crawlers do not all support identical extensions. Repeat without cache and test the crawler relevant to the task.

Allowed crawling does not guarantee indexing, while blocked crawling does not guarantee removal of a known URL from search. noindex, canonical, HTTP responses and index presence require separate checks.

The automated wSEO audit for this service assesses robots.txt for one entered website and representative rules; it cannot replace a business review of every filter and service area. If a problem is confirmed, follow the repair guide or order configuration.