Used Car Listing Accident History Badge

WHAT IT DOES

This userscript helps used car buyers quickly identify vehicles with accident history or title problems. It scans listing pages—Autotrader, Cars.com, Craigslist, Facebook Marketplace, eBay Motors, and similar sites—for keywords indicating accident history, damage, title issues, or repair records. It detects phrases like "accident", "damage", "rebuilt", "salvage", "flood", "frame damage", "airbag deployed", "clean title", "salvage title", and "rebuilt title". The script displays a visual badge or panel showing the accident history status—Clean History, Minor Accident Reported, Major Accident Reported, Salvage Title, or Rebuilt Title—with color-coded indicators. It also provides a summary of disclosed issues, flags listings with missing or vague accident disclosures, and suggests questions to ask the seller to uncover hidden problems.

WHERE IT RUNS

The script works on used car listing pages—Autotrader, Cars.com, Craigslist, Facebook Marketplace, eBay Motors, and similar classified sites. It runs entirely within your browser, reading only the visible content of the current page. It does not track your browsing history, access other tabs, or send any data externally. All analysis is performed locally using built-in keyword detection.

HOW TO USE

After installation, open the panel by clicking the tool's icon in the BotGentz sidebar. The script auto-scans car listing pages on load (toggle this on/off). Choose your display mode—"Badge only" shows a floating badge in the corner, "Panel only" shows details in the panel, or "Both" shows both. Toggle "Show seller questions" to display a list of questions to ask the seller about the vehicle's history. Click "Scan for accident history" to manually analyze the page. The badge displays the status with a colored border. The panel shows the status, a list of detected indicators, and seller questions. Use "Clear analysis" to remove all overlays.

THE TECHNICAL MECHANISM

This script uses keyword-based detection to analyze accident history from page text. It maintains a curated list of keywords organized into four categories: major accidents (salvage, rebuilt, flood, frame damage, airbag deployed, total loss), minor accidents (minor damage, fender bender, scratches, dents), title issues (salvage title, rebuilt title, branded title, odometer discrepancy), and repairs (repair, body work, replaced parts). The script scans the page using common selectors for listing descriptions and details—.description, .details, .vehicle-description, and [class*="description"]. It compiles a list of detected keywords and determines the overall severity based on the presence of major vs. minor indicators. Clean title mentions are detected as positive signals. The status is then categorized: Clean History (green), Minor Accident (yellow), Major Accident (red), Salvage Title (red), Rebuilt Title (orange), or Unknown (gray). Seller questions are displayed based on detected issues.

THE PANEL

The panel is draggable anywhere on the screen and remembers its position between sessions. It can be collapsed to a small floating bubble to minimize distraction, and expanded again with a single click. The panel's width can be adjusted, and pressing the Escape key closes it instantly. All settings—display mode, show questions, and auto-scan—are persisted locally using GM_setValue, so your preferences remain intact across page reloads and browser restarts.

PLEASE NOTE

This userscript requires the free BotGentz extension to function. The script is designed for used car listing sites; it may work on other classified sites but is not guaranteed. The accident detection relies on the current text patterns on each site—if a site updates its UI or wording, the script may need to be updated. The analysis is based on keyword detection and may miss accidents that are not mentioned in the text. Always verify the vehicle's history through a professional vehicle history report (e.g., Carfax, AutoCheck) and have the vehicle inspected by a mechanic before purchasing. The script does not access your account or API; it only reads what is visible on the page. No data from your browsing is stored or transmitted anywhere—all processing occurs entirely in your browser.