DaylytixDaylytixBot is the crawler of Daylytix, an SEO and GEO audit tool. It visits a site only when a Daylytix user asks for it: an audit they start or schedule, or a tool such as a competitor comparison or the robots.txt checker.
How to recognise it
Its requests carry this user agent:
DaylytixBot/1.0 (+https://daylytix.com/bot)Most requests come from our server:
- IPv4: 178.104.138.68
- IPv6: 2a01:4f8:1c1a:4e33::/64
Some requests come from a proxy service with changing addresses: a few checks use it, and a page that does not answer our server, or answers 403 or 429, may be tried again through up to three of its addresses. These requests carry the same user agent, so the user agent and robots.txt are the reliable way to recognise DaylytixBot.
A Daylytix user can choose browser mode for one audit, for a site that refuses DaylytixBot. In browser mode the requests carry the headers of a Chrome browser instead. Browser mode still follows the robots.txt rules for DaylytixBot below.
robots.txt
DaylytixBot reads robots.txt before an audit and follows the rules written for it by name. To keep it off your whole site:
User-agent: DaylytixBot
Disallow: /To keep it out of one folder, use that folder instead, for example Disallow: /private/. An audit of a site that closes itself to DaylytixBot stops before it fetches any page.
Rules for all crawlers (User-agent: *) or for search engines are read and reported in the audit, because an audit checks what search engines may crawl. The crawler still fetches those pages so it can report on them, and marks them as blocked.
How to allow it
If your firewall, CDN or security plugin refuses DaylytixBot and you want the audit to run, allow the user agent DaylytixBot and our server’s addresses above. Most of them have an allowlist for this, for example Cloudflare, Wordfence and Sucuri.
What it fetches
- robots.txt and the XML sitemaps it lists.
- The site’s HTML pages, up to the page limit of the audit, and the links, images, scripts and stylesheets they use, to check them.
- A few pages in a headless browser, to see what JavaScript adds, and screenshots when the user asks for them. The browser uses the same user agent.
Our server runs one audit at a time. An audit fetches pages five at a time, in batches, and the user can add a delay between batches for a slow server. A few checks, such as testing the addresses in a sitemap, send up to eight requests at once.
Contact
Questions about DaylytixBot, or a visit you did not expect: hello@daylytix.com. Please include your domain and the time of the visit.