RankedContent

RankedContentBot

The page fetcher behind RankedContent’s analyses

RankedContentBot is the fetcher used by RankedContent, a platform that helps site owners optimize their pages for classic search and AI answer engines. If you see it in your server logs, a RankedContent customer asked us to analyze a specific page - most likely on a site they own or manage.

How it identifies itself

Every request carries this User-Agent header:

RankedContentBot/1.0 (+https://www.rankedcontent.ai/bot)

What it does - and what it never does

  • It fetches one page at a time, only when a RankedContent user submits that exact URL for analysis. It does not crawl: it follows no links, discovers no URLs, and never visits a page nobody asked about.
  • It reads the page’s HTML the same way AI answer engines do - without executing JavaScript - to score how well the page can be read and cited.
  • It sends no cookies, submits no forms, and attempts no logins. It reads only publicly served HTML.
  • Requests are infrequent: a page is fetched once per analysis a user requests, with at most one automatic retry.

Allowing RankedContentBot

Some hosting platforms and firewalls block automated visitors by default, which can make a customer’s own site unreadable to their analysis - the symptom is an analysis failing with “We couldn’t read any content from that page” while the page looks fine in a browser. To fix that, allow the User-Agent RankedContentBot in your firewall, bot-protection, or hosting security settings (most managed hosts do this on request).

If your firewall or hosting platform only supports allow rules by IP address, RankedContentBot’s requests come from within this fixed range:

5.60.65.64/26 (5.60.65.64 – 5.60.65.127)

Allowlisting either the User-Agent or that IP range works; together they also let you verify that a request claiming to be RankedContentBot really is - a request with our User-Agent from outside that range is not us.

Known bot-protection layers

When an analysis fails because one of these layers answered instead of your page, the failure message names it. The fix for each:

  • SiteGround (Anti-Bot AI). Serves a CAPTCHA page to automated visitors from cloud networks; browsers pass it invisibly, so the site looks fine to you. Only SiteGround support can allow a visitor: ask them to whitelist the IP range above in the site’s Anti-Bot AI itself, not the separate blocked-traffic list. Solving the CAPTCHA yourself does not help - it allows your own address, not ours.
  • Sucuri firewall. You can do this yourself: in the Sucuri dashboard open Firewall, then Access Control, and allowlist the user agent RankedContentBot.
  • Cloudflare. Add a WAF custom rule with the Skip action for requests whose user agent contains RankedContentBot or that come from the IP range above, so challenges are not applied to them. If a challenge still appears, review the zone’s bot settings.
  • Anything else. A plain 403 or a broken redirect from a layer we do not recognise: ask your host or firewall provider to allow the user agent or the IP range above.

Questions or concerns

If you have questions about RankedContentBot’s behavior, or want to report a problem, reach us through the contact page.