How to block the Ryte crawler (botLogen)
Ryte is a technical-SEO platform (the rebrand of OnPage.org) whose crawler fetches pages to evaluate site quality and crawlability. This page shows the robots.txt token to target, notes the historical OnPage relationship, and explains why a Disallow steers only compliant fetchers.
What the Ryte crawler is
Ryte is a technical-SEO and content-quality platform, formed from the rebrand of OnPage.org. Its crawler fetches public pages to assess structure, crawlability, and on-page factors. Because the company evolved from OnPage.org, both the historical OnPage token and Ryte's own token may appear in older and newer logs.
Match on the documented Ryte user-agent token rather than a version string, and check your logs for the exact self-identifying string.
- Ryte is the rebrand of OnPage.org
- Purpose: technical-SEO and content auditing
- Both Ryte and historical OnPage tokens may appear
robots.txt rule
To ask the Ryte crawler to stay off your site, target its documented token with a site-wide Disallow:
User-agent: Ryte Disallow: /
Confirm the exact token from the self-identifying user agent before relying on the rule, and add the OnPage token too if you see it. robots.txt is honoured by compliant crawlers and is not enforcement.
How it appears in analytics and logs
Requests carrying the Ryte crawler token are SEO-audit events, not human visits. If you did not commission the audit, a third party may be analysing your site; classify the hits as bot traffic.
Diagnostic use case
Stop a technical-SEO audit crawler from fetching your pages when the audit is not authorised by you, and confirm the rule reached the correct token.
What WebmasterID can help detect
WebmasterID classifies the Ryte crawler server-side and shows whether it keeps reaching your pages after a robots.txt rule, helping you tell authorised audits from uninvited ones.
Common mistakes
- Blocking only Ryte and missing the historical OnPage token (or vice versa).
- Guessing the token instead of confirming it from the self-identifying user agent.
- Expecting robots.txt to enforce the block rather than request compliance.
Privacy and accuracy notes
Blocking the Ryte crawler uses only the request user-agent token. No visitor identity is involved, and WebmasterID records the crawl as a bot event separate from human analytics.
Related pages
- Ryte crawler (BotLogen)
Ryte is a website-quality and SEO auditing platform, and its crawler has been observed identifying with the BotLogen token. It fetches a customer's pages to run technical and content audits. As a tool crawler it does not serve a consumer search engine. Token and self-identifying URL are observable; some specifics are not exhaustively published, so this entry is partially verified.
- How to block the OnPage.org / Ryte crawler
OnPage.org was an SEO site-audit platform that later became Ryte; its crawler fetches your pages to analyse technical SEO. This page shows the robots.txt token to target, notes the relationship to Ryte's crawler, and explains why a Disallow steers only compliant fetchers.
- How to block SEOkicks
SEOkicks is a backlink-index service whose crawler fetches public pages to build a link database. This page shows the robots.txt token to target, explains what the crawler collects, and why a Disallow steers only compliant fetchers.
- Bot intelligence
Categorise SEO-audit crawlers reaching your site.
Sources and verification notes
- Ryte — crawler informationRyte (formerly OnPage.org) crawler; token matched on the self-identifying user agent.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.