OnPage.org / Ryte audit crawler heritage
OnPage.org was a German SEO and website-quality platform that rebranded to Ryte. Its audit crawler fetched a customer's site to run technical and content checks. Older log entries may reference OnPage-era tokens. This entry documents the lineage and audit-crawler behaviour; exact historic UA strings are not asserted, so it is partially verified.
What this means
OnPage.org was an SEO and website-quality platform that ran an audit crawler to fetch customer sites for technical and content analysis. The company rebranded to Ryte, so current audit crawling is under the Ryte brand and its crawler.
Knowing this lineage helps when older logs show OnPage-era references: they describe the same audit-crawler purpose, now continued by Ryte.
How it identifies itself
Historically OnPage.org's crawler used a self-identifying token and URL; today Ryte's crawler (observed as BotLogen) performs the audit role. Match on the token present in your logs and treat it as commissioned audit traffic.
Because exact historic user-agent strings are not asserted here, confirm by the self-identifying URL and behaviour rather than guessing a precise legacy string.
- OnPage.org rebranded to Ryte
- Purpose: commissioned technical/content SEO audits
- Current audit crawler observed as Ryte's BotLogen
How it appears in analytics and logs
A reference to an OnPage-era audit crawler indicates a commissioned SEO-audit fetch, historically from OnPage.org and now under the Ryte brand. It is tool traffic, not search indexing, and should be counted as bot.
Diagnostic use case
Interpret OnPage-era audit-crawler references in older logs, and understand the platform is now Ryte, so current audit traffic follows Ryte's crawler.
What WebmasterID can help detect
WebmasterID classifies OnPage/Ryte audit crawlers as SEO/audit crawlers distinct from search bots, so historic and current audit traffic is visible separately from human analytics.
Common mistakes
- Assuming OnPage and Ryte are unrelated when they share lineage.
- Treating an audit crawler as a search-engine indexer.
- Inventing an exact legacy OnPage user-agent string.
Privacy and accuracy notes
OnPage/Ryte audit crawlers are identified by user-agent token only. They are crawlers, not people; WebmasterID records them as bot events with no visitor identity.
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.
- Screaming Frog SEO Spider
Screaming Frog SEO Spider is a desktop application that site owners and SEO professionals run themselves to audit a site. It is not a public, continuously operating crawler like Googlebot; its user agent is user-controlled and its crawling is initiated by whoever runs the tool.
- Managing third-party SEO crawler load
Third-party SEO crawlers such as AhrefsBot and SemrushBot can generate significant request volume without contributing to search visibility. You can manage their load by targeting their tokens in robots.txt, using crawl-delay where the crawler supports it, and blocking those that bring no value to you.
- Bot intelligence
Tracks audit-crawler lineage and current tokens.
Sources and verification notes
- Ryte — formerly OnPage.orgOnPage.org rebranded to Ryte; legacy UA specifics not asserted.
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.