RoaringShiftsBot

How to recognise it

Every request carries this User-Agent:

RoaringShiftsBot/1.0 (+https://roaringshifts.com/bot)

Its robots.txt token is RoaringShiftsBot.

The rules it follows

• robots.txt first. It reads your robots.txt before anything else (cached for a day) and obeys the rules for RoaringShiftsBot, or for * when there are none for it. If your robots.txt can't be read because of a server error, it treats the whole site as off-limits and tries again later.
• Slow and small. It waits at least 10 seconds between requests to the same site, and longer if your robots.txt sets a Crawl-delay. It makes only a few dozen requests to a site a day at most, usually your events page once a day plus the event pages it links to.
• Conditional requests. It sends If-None-Match / If-Modified-Since, so an unchanged page costs you a 304 and nothing more.
• Backs off. A 429 or 503 response pauses it for that site, honouring Retry-After.
• Public pages only. It never logs in, never fills in forms, and never reads past a login wall or a paywall.
• Organizers' own sites only. It does not crawl ticket resellers, event aggregators or social networks.
• Car events only. It reads schema.org Event data (JSON-LD or microdata) and keeps only automotive events. Everything else on the page is ignored.

What happens to what it finds

An event it finds goes into a review queue. A RoaringShifts staff member checks it before it is published. A published meet credits the real organizer by name, links back to the organizer's own site, and keeps the event's own name. RoaringShifts does not sell tickets to events it lists this way.

Opting out

To keep RoaringShiftsBot off your whole site, add this to your robots.txt:

User-agent: RoaringShiftsBot
Disallow: /

To have a listing changed or taken down, or if you think the bot misbehaved, email help@roaringshifts.com with the page address, or see our takedown policy.