Responsive Tester

Unsupported input

The tool may reject input that does not match the expected content, structure, or file type.

Fix: Confirm the tool input requirements and paste the correct type of data.

Incomplete values

Missing fields or partial content can block processing or produce weak results.

Fix: Provide the full required input before running the tool.

Copying placeholder content

Sample or placeholder values can lead to output that looks valid but is not ready for real use.

Fix: Replace placeholders with your actual values before relying on the result.

Does Responsive Tester use the same rules as Googlebot?

Responsive Tester follows the publicly documented behavior of Googlebot, Bingbot, and other major crawlers — robots.txt disallow rules, meta robots tags, canonical URLs, and HTTP status handling all match the official specs. Edge cases that vary between crawlers are called out in the output.

How many URLs can Responsive Tester check per request?

Responsive Tester checks up to 100 URLs per batch so the request completes in under a minute and doesn't hammer third-party servers. For larger sweeps, run the tool in a loop from a script.

Does Responsive Tester handle JavaScript-rendered pages?

Responsive Tester fetches the raw HTML served to a crawler, which is what search engines index for the first pass. If your site relies on client-side rendering, the tool shows you exactly what Googlebot's initial render sees before it runs JavaScript.

What User-Agent does Responsive Tester send?

Responsive Tester sends a User-Agent string that identifies itself honestly (DevFox bot) rather than impersonating Googlebot — spoofing UAs can get a site's access flagged. If a page blocks non-browser UAs, you'll see the block clearly reflected in the output.

Can Responsive Tester check password-protected pages?

No. Responsive Tester only makes anonymous public requests — it can't log in or carry session cookies. For auth-protected pages, use a headless browser in your own environment.