Text us!
X
Hi there, have a question?
Send us a text!

PluseBot

The web crawler that powers SEO intelligence inside the NEXEO platform — built and operated by Ready2Ride.

What is PulseBot?

PulseBot is the dedicated web crawler operated by Ready2Ride as part of the NEXEO SEO Intelligence Platform. It crawls websites that have been explicitly added by their owners to NEXEO, analysing page structure, technical SEO health, content quality, and on-page signals.

PulseBot is not a general-purpose search engine crawler. It only visits domains that have been enrolled in NEXEO by an authorized account holder — your website will never be crawled without a registered project in the platform.

Crawl behaviour

5 s

Minimum delay between requests

100

Max pages per domain per 24 hours

1

Concurrent request per host at any time

30 s

Per-request timeout before moving on

PulseBot reads each site’s sitemap.xml first to discover pages efficiently, falling back to link-following only when a sitemap is unavailable. It skips binary and static assets entirely, and aborts a crawl session automatically if its error rate exceeds 20% — protecting your server from repeated failed requests.

File types never fetched

PulseBot skips the following extensions on every request:

.pdf .jpg .jpeg .png .gif .webp .svg .css .js .ico .xml .txt .zip .mp4 .mp3 .woff .woff2 .ttf

robots.txt compliance

PulseBot fully respects robots.txt directives — including Disallow rules, Crawl-delay directives, and sitemap declarations. When a Crawl-delay is specified, PulseBot honours whichever value is larger — its own minimum or the one you declared.

To block PulseBot entirely, add the following to your robots.txt:

Changes to robots.txt are picked up on every new crawl session — there is no delay or cache period to wait for.

CRAWL MODES

Mode Triggered by robots.txt Max pages Data retention
Client Audit Site owner via NEXEO dashboard Respected by default. Owner may authorise an override for their own domain. Up to 100 pages Retained for SEO reporting
Prospect Prospecting workflow inside NEXEO Always respected — blocked if / is disallowed Up to 10 pages Purged after 24 hours
Competitor Competitor analysis inside NEXEO Always respected — blocked if / is disallowed Up to 10 pages Purged after 30 days

What data PulseBot collects

PulseBot reads publicly accessible HTML pages only. For each page it analyses:

Signal Why it's read
<title> tag Title tag optimisation scoring
<meta name="description"> Meta description analysis
<h1><h6> headings Heading structure and keyword usage
<img alt> attributes Image accessibility and alt-text coverage
<link rel="canonical"> Canonical tag validation
<meta robots> Indexability checks
Open Graph & Twitter Card tags Social sharing metadata quality
Schema.org structured data Rich result eligibility
Internal link structure Internal linking health
HTTP response status codes Broken page detection
Viewport meta tag Mobile-friendliness check
Favicon presence Brand completeness signal

PulseBot does not collect personal data, form inputs, session cookies, login-protected content, or any user-generated information.

Verifying a PulseBot request

Check the User-Agent string

Every request from PulseBot carries this exact User-Agent header:

PulseBot/1.0 (+https://www.ready2ridemobile.com/pulsebot; contact:support@ready2ridemobile.com)

If you see requests claiming to be PulseBot from a different string, it is not from Ready2Ride. Please report spoofing to support@ready2ridemobile.com.

Contact

Questions about PulseBot?

If you have questions, concerns, or need to report unexpected crawl behaviour, contact the Ready2Ride platform team directly.