Does QA.tech respect robots.txt?

Yes. QA.tech says requests that perform discovery or policy checks identify as QATechBot/1.0 and respect normal robots rules for the configured URLs.

Why does the documented identity differ from this page's token?

This page retains QA.tech as its catalog token. The operator's current documentation says automated browser traffic carries a QATechBot/1.0 suffix, which is the more precise value to match in live logs.

Can I verify that a QATechBot request is genuine?

Check the source against QA.tech's published IPv4 prefixes and confirm reverse and forward DNS for bot.qa.tech. Some top-level navigations also carry HTTP Message Signatures, but subresource requests are usually unsigned.

Does QA.tech collect content for AI search or training?

QA.tech documents this bot as a testing browser, not a search crawler or content harvester. Its use of AI for test execution does not make the visited pages part of a documented search index or training dataset.

QA.tech: AI Crawler Guide & robots.txt

What is QA.tech?

QA.tech uses an automated browser to test web applications. A customer adds an application or environment to QA.tech, defines a test goal, and sends the agent through that configured site. The agent can also identify possible test cases before it runs them.

During a test, the browser navigates pages, clicks controls, fills forms, and checks outcomes. These are real application interactions, not a background scan of every public URL on a domain. They may reach login screens, staging hosts, or other routes that the QA.tech customer has deliberately made available to the test.

QA.tech describes this traffic as authorized functional and regression testing. It does not use the bot to index the public web or bulk-scrape arbitrary sites. Although AI helps decide how a test is executed, QA.tech does not document this bot as collecting material for model training or an AI search product. Allowing it has no direct effect on search inclusion or citations in AI answers.

Current QA.tech bot documentation says browser requests append QATechBot/1.0 (+https://docs.qa.tech/bot) to a normal Chromium user agent. A standalone request, including a request for robots.txt, can use that value by itself. This page retains QA.tech as its catalog token, so log and firewall checks should account for the operator's more specific current suffix.

A user agent alone is easy to copy. QA.tech publishes its current IPv4 prefixes at https://app.qa.tech/.well-known/qatech-ips.json, and its documented egress addresses resolve to bot.qa.tech with matching forward DNS. Top-level navigations may also carry HTTP Message Signatures. Images, scripts, and stylesheets are usually unsigned, so signature checks cannot cover every request in a browser session.

QA.tech says its policy checks use the QATechBot/1.0 identity and honor normal robots rules for customer-configured URLs. Access controls still matter. If the application sits behind a WAF, CAPTCHA, or IP restriction, an approved test may fail until the QA.tech addresses or verified bot traffic are allowed through.

Relevant for AI search

Is QA.tech relevant for AI search?

Yes. QA.tech collects pages for an AI product, so what it can crawl influences how AI systems describe your brand.

QA.tech fetches, indexes, or retrieves pages for an AI product, so the pages it can reach shape how that system describes your brand and products.

How to handle QA.tech

Allow QA.tech on an application only when your team or an authorized partner has configured tests for it. For protected test environments, use QA.tech's published IP data or DNS checks in addition to the user agent. A rule that trusts any request containing QATechBot can be spoofed.

QA.tech documents QATechBot as the robots identity. To stop its policy-compliant test traffic across the site, use:

User-agent: QATechBot
Disallow: /

The operator says this identity respects standard robots rules. A robots block can cause an expected test run to fail, so coordinate the change with whoever owns the QA.tech project. If traffic is not authorized, block it at the access-control layer as well and investigate which account or integration targeted the environment.

Examples

A pull request test opens a staging checkout, adds an item to the cart, and confirms that payment validation appears without submitting a real order.
A security engineer sees the QATechBot suffix on a login request and checks the source against QA.tech's published IPv4 prefixes before adding a WAF exception.
A test starts loading HTML but its scripts are blocked. The team allows the verified QA.tech browser session to fetch those subresources so the test can run.

Frequently asked questions about QA.tech

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

A QA.tech customer configures the target application or environment and runs an automated test. QA.tech says QATechBot is not used to crawl or index arbitrary public sites.