Free · without registration
Do browsers and bots get the same response?
Get the same URL with two profiles and compare status, redirects, SEO information, and content. In this way, possible differences through user agents, language or cache become visible.
Compare two request profiles
Their results
Example: Browser receives content, bot profile a lock
The two fictitious answers clarify the comparison columns. For your own test, select two profiles for the same URL. A Googlebot string merely simulates a header and does not confirm a real Googlebot origin.
Profil A: HTTP 200 · Title: Beratung
Profil B: HTTP 403 · Title: Zugriff verweigert
Gleiche Ziel-URL: https://example.org/beratungExpected result
The comparison shows different HTTP status values and titles. First, check security rules, WAF, and cache behavior before you derive an intentional content disadvantage from bots.
What the Example Does Not Prove
Dynamic content, tests, language or session can change responses. The comparison is a snapshot and not an automatic proof of cloaking or the actual response to verified search engine bots.
Limiting differences based on concrete signals
The comparison shows HTTP status, final URL, title, canonical, robots and selected response headers. Additionally, you’ll see response size, content hash, text clippings, and a word set similarity of the static main content. Another hash alone can be created by timestamps or dynamic IDs.
Test User Agent and Header Separately
First, just change the user agent and leave the headers the same. After that, for example, test Accept-Language separately. This makes it easier to narrow down whether language, cache or a bot rule is involved. The header Vary can indicate an intended distinction.
What this comparison does not prove
Both requests come from the Seitenreport server and do not run JavaScript. IP-based bot sharing, geolocation, cookies, A/B testing and time changes can affect the outcome. Repeat eye-catching checks and compare them to server logs and Search Console before changing any rules.
Frequent questions
Is a Googlebot user agent a real Googlebot?
No. Only the HTTP identifier is simulated. The retrieval comes from Seitenreport and does not have a verified Googlebot IP.
Which headers can I compare?
Accept, Accept Language and Cache Control. Sensitive or routing-relevant headers such as Cookie, Authorization, Host and X-For are excluded.
Does different content automatically mean cloaking?
No. Language, device customization, protection systems, testing, and dynamic content can cause differences. The tool shows evidence for further checks.