OutwizarBot is the name used for automated requests that Outwizar sends to merchant websites. It checks product pages, source images, robots files and sitemap documents associated with products supplied to Outwizar.
This page describes OutwizarBot traffic. It is not an endpoint for starting a check.
How OutwizarBot accesses your site
OutwizarBot may request merchant-owned product pages, source-image URLs, /robots.txt, sitemap documents declared in robots.txt, the conventional /sitemap.xml location and the merchant home page.
- Product-page checks use
HEADand do not retain page bodies. - Robots responses are read for access rules and declared sitemaps. Their bodies are not retained.
- Affiliate click-tracking URLs are not requested.
- OutwizarBot does not browse unrelated pages, submit forms, sign in, add items to a basket or attempt a purchase.
Requests are paced per merchant host and concurrent work is limited. OutwizarBot honours a valid Retry-After response and pauses requests after rate limiting or an unsuccessful home-page check.
Outwizar retains product-page health, image placeholder and dimension evidence, sitemap membership, check timestamps and retry state. Timeouts, rate limits, server errors and access-denied responses are recorded as unknown. Merchant pages and robots response bodies are not retained.
Blocking OutwizarBot from visiting your site
Use the OutwizarBot user-agent token in your robots.txt rules. OutwizarBot fetches /robots.txt once per origin in each probe run and evaluates product and image paths before requesting them.
- A disallowed product or image path is not requested.
- A missing robots file permits access.
- A
401or403robots response denies access. - A robots timeout, rate limit or server error stops product and image requests for that origin during the run.
To ask Outwizar to investigate, reduce or pause checks for your domain, email support@outwizar.co.uk.
Verifying OutwizarBot
OutwizarBot has four request profiles. Every profile sends From: support@outwizar.co.uk and X-Outwizar-Probe-Info: https://outwizar.co.uk/outwizarbot. Redirected requests keep the same identity headers.
OutwizarBot Product URL Health
| User-Agent in HTTP requests | … OutwizarBot/1.0 |
|---|---|
X-Outwizar-Probe | product-url-health |
| User-agent token in robots.txt | OutwizarBot |
| Requests | The merchant home page, /robots.txt and product-page URLs supplied to Outwizar. |
OutwizarBot Image Dimensions
| User-Agent in HTTP requests | … OutwizarBot/1.0 |
|---|---|
X-Outwizar-Probe | image-dimensions |
| User-agent token in robots.txt | OutwizarBot |
| Requests | /robots.txt and allowed source-image URLs supplied to Outwizar. Image reads stop when the dimensions are found or the byte limit is reached. |
OutwizarBot Image Sentinel
| User-Agent in HTTP requests | … OutwizarBot/1.0 |
|---|---|
X-Outwizar-Probe | image-sentinel |
| User-agent token in robots.txt | OutwizarBot |
| Requests | /robots.txt and allowed source-image URLs supplied to Outwizar. Image requests use HEAD and, when needed, GET to complete the placeholder check. |
OutwizarBot Merchant Sitemap
| User-Agent in HTTP requests | … OutwizarBot/1.0 |
|---|---|
X-Outwizar-Probe | merchant-sitemap |
| User-agent token in robots.txt | OutwizarBot |
| Requests | /robots.txt, the conventional /sitemap.xml location and sitemap documents declared or discovered there. |
OutwizarBot does not have a fixed source IP range. These headers identify OutwizarBot traffic but do not authenticate the sender. To ask Outwizar to confirm a request, email support@outwizar.co.uk with the affected domain, request timestamp and header values.