1. Nguồn
Tải trực tiếp robots.txt. Kết quả xác định nguồn gốc của bằng chứng.
The Novaverb robots.txt tester fetches the live robots.txt file at a site's root and reports its HTTP status, user-agent groups, Allow and Disallow counts, sitemap declarations and any site-wide Disallow rule.
Chạy một kiểm tra thực tế ở trên
Gửi một URL công khai, tên miền, hoặc từ khóa. Novaverb sẽ chỉ hiển thị bằng chứng mà công cụ này thực sự có thể lấy hoặc đo lường.
A robots.txt tester is a tool that fetches a site's robots.txt file and shows the crawl rules written in it. The Novaverb Robots.txt Checker reads the live file at the root of the exact hostname you submit and summarizes its status, user-agent groups, Allow and Disallow rules and sitemap lines.
The robots.txt tester checks the HTTP status of the file, the user-agent values it names, the number of Allow and Disallow directives, every Sitemap line and the file size in bytes. A literal Disallow: / rule is flagged as a block on every path for its group, and the fetched file is displayed with its comments preserved.
The robots.txt tester is for developers who just deployed and need to confirm a staging block did not ship, SEO specialists auditing which crawler groups a site addresses, site owners deciding how to treat AI crawlers named in the file, and migration leads checking that the new host serves the file at its root.
A robots.txt tester catches a crawl rule mistake before crawlers act on it. One Disallow: / line left in place can stop compliant crawlers from fetching site content, a file returning an error status gives crawlers no explicit guidance, and a missing Sitemap line removes a discovery route. A visitor using a browser notices none of these.
The robots.txt tester works by keeping the exact hostname you submitted, resolving it to a public address and fetching /robots.txt from the root with safe redirect handling. The returned text is then counted by User-agent, Allow, Disallow and Sitemap directive. An empty Disallow value stays permissive, and only the literal root rule is flagged as a block.
Enter a domain, or any URL on it, into the robots.txt tester. The host is taken from the address and the file is fetched from the root, the only location the specification recognizes. A robots.txt placed in a subfolder is not read and is reported as missing. Hosts that do not resolve to a public address are refused.
yourdomain.comBất kỳ hình thức địa chỉ nào cũng hoạt động - chúng tôi lấy /robots.txt tại gốc máy chủ cho bạn. http hoặc https, có hoặc không có www, chỉ tên miền hay một đường dẫn đầy đủ - chúng tôi chuẩn hóa cho bạn.https://www.yourdomain.com/anythingNgay cả một URL ở tầng sâu cũng được; chúng tôi quy về máy chủ và đọc robots.txt ở gốc của máy chủ đó.Expecting a subfolder robots.txt to countrobots.txt chỉ có hiệu lực tại thư mục gốc của máy chủ; bản sao đặt trong thư mục con sẽ bị crawler bỏ qua.A robots.txt tester report contains a header with the fetched URL and status, counts for user-agent groups, Disallow and Allow rules and declared sitemaps, a warning when a Disallow: / rule exists, the list of user-agent values, the file as served, each Sitemap directive found and an analysis panel with findings and priority fixes.
Read a robots.txt tester result by checking the status first: 200 means the file was served and its rules apply, while 404 means no file exists and crawlers assume full access. Next look for the Disallow: / warning and find which user-agent group owns the rule. Then confirm that at least one sitemap is declared.
robots.txt cho các crawler tuân thủ biết chúng được phép yêu cầu những đường dẫn nào. Đây là tệp đầu tiên mà hầu hết crawler tải về, nên chỉ một dòng sai cũng có thể âm thầm khiến cả website nằm ngoài kết quả tìm kiếm - hoặc để các đường dẫn riêng tư bị thu thập dữ liệu.
Một robots.txt rõ ràng giúp giảm sự mơ hồ cho các crawler tìm kiếm và AI. Novaverb có thể dùng tín hiệu này như một phần của mô hình bằng chứng kỹ thuật và thu thập dữ liệu rộng hơn, bên cạnh khả năng lập chỉ mục, thẻ canonical và liên kết nội bộ.
The robots.txt tester gets its data from a live fetch of /robots.txt on the exact hostname you submit, made when you run the check. The rules shown are the ones in that served file. No crawl history or search engine report is consulted, so the result reflects what the server returned to this single request.
The robots.txt tester does not tell you whether a named crawler may fetch a specific URL, because it does not simulate any crawler's matching, caching or policy behavior. Robots.txt is a crawl directive, not access control or index removal, so the result says nothing about whether a blocked page is private or absent from search.
A robots.txt tester result proves what the root file contained when it was fetched: its status, the user-agent values, the Allow and Disallow counts, the sitemap declarations and any literal Disallow: / rule. That supports conclusions about what crawlers are told. What a particular crawler then does with those rules cannot be concluded from the summary.
Tải trực tiếp robots.txt. Kết quả xác định nguồn gốc của bằng chứng.
Công cụ tải /robots.txt và đọc các chỉ thị trong đó. robots.txt là chỉ thị thu thập dữ liệu, không phải kiểm soát truy cập hay lệnh gỡ khỏi chỉ mục; công cụ này không mô phỏng chính sách của một trình thu thập cụ thể.
Sử dụng phát hiện để xác minh một vấn đề, sau đó kết nối một không gian làm việc khi bạn cần lịch sử, giám sát hoặc phân tích toàn bộ trang web.
The robots.txt tester applies RFC 9309, the Robots Exclusion Protocol published by the IETF. The specification defines the syntax used to identify User-agent, Allow, Disallow and Sitemap lines, and the tool treats an empty Disallow as permissive. The summary does not claim to implement crawler-specific matching, caching or policy extensions beyond the fields it displays.
Xác định các chỉ thị User-agent, Allow, Disallow và Sitemap đã thu thập, và coi một Disallow trống là cho phép.
Đọc thông số kỹ thuậtVerify a robots.txt tester result by loading the same hostname followed by /robots.txt in a browser and comparing the text with the file shown in the report. Count the Disallow lines by hand for a short file. To confirm the status code, request the file with a command line client and read the first response line.
A typical robots.txt tester finding is a file that returns 200 with a single group for all crawlers, a few Disallow rules for admin and cart paths, and no Sitemap line. The analysis marks the file reachable, adds a warning that no sitemap is declared and suggests a Sitemap line so crawlers discover the sitemap directly.
The robots.txt tester is free and no account is required. You can check any public hostname from the form. A free Novaverb account is needed for the step the file alone cannot answer: crawling the site to see every URL these rules allow or block, keeping the evidence and rechecking after the file changes.
A Novaverb workspace adds a site crawl to the robots.txt tester, so the rules are seen against real URLs and important pages kept out of search by accident become visible. Crawl Explorer is the product that continues the job, letting you inspect every URL captured in the project crawl and turn each supported technical finding into an action.
A free robots.txt checker run is not enough when you need to know which of your actual pages a rule affects, since that takes a crawl of the whole site. One check is also a single moment. A file overwritten by a later deploy is only noticed when the same check is repeated and compared over time.
After running the robots.txt tester, remove any site-wide Disallow: / rule that is not deliberate. If the file returned an error status, publish one at the host root, even a permissive one. Add a Sitemap line with the full sitemap URL. Then run the check again and confirm the status, counts and sitemap list changed.
Related free tools pair with the robots.txt tester. The Robots.txt Generator creates an RFC 9309-aligned file with optional AI crawler controls. The Sitemap Checker follows the Sitemap lines declared in robots.txt and inspects those documents. The Website SEO Checker reads the homepage for a noindex directive alongside its robots.txt and sitemap rows.
People ask what the robots.txt tester checks, what robots.txt is, whether an empty Disallow blocks the whole site, how Allow differs from Disallow, which HTTP status the file should return, whether it should list a sitemap, whether it can protect private content and whether the checker simulates how one named crawler reads the file.
It fetches your /robots.txt file, reports the HTTP status, and lists crawl rules grouped by user-agent, counting every Allow and Disallow directive plus any declared Sitemap lines so you see exactly what crawlers are told.
Robots.txt is a plain-text file at your domain root that follows the Robots Exclusion Protocol (RFC 9309). It tells cooperating crawlers like Googlebot which paths they may or may not request, grouped by user-agent.
No. A line containing Disallow: with no path allows all paths for that group. Disallow: / is the rule that blocks the root and every path beneath it.
No. It lists the groups and directives captured in the file. It does not reproduce a named crawler's complete matching, caching or policy behavior for a submitted URL.
No. The file is public and its rules are voluntary. Protect private paths with authentication and authorization; use robots.txt only to communicate crawl preferences to cooperating crawlers.
A 200 OK means the file was served and its rules apply. A 404 means no file exists, so crawlers assume full access. Persistent 5xx errors can cause crawlers to pause crawling entirely.
Disallow lists paths crawlers should not request; Allow re-permits a sub-path inside a broader Disallow. The most specific matching rule wins, so Allow can carve exceptions out of a blocked directory.
Yes. A Sitemap: directive with the full URL helps crawlers discover your XML sitemap independently of any submission. The checker reports every Sitemap line it finds so you can confirm it is declared.
No. Robots.txt is a public, voluntary instruction for cooperating crawlers, not access control. Anyone can read it, and it cannot protect private content. Use authentication or server rules to actually restrict access.
It parses and reports your directives as written, but it does not replicate any single crawler's full internal matching policy. Treat the grouped rules and counts as an accurate readout, not a crawler-specific simulation.