I-95 Accidents

Constraint

After a highway crash, people search for what happened, often from a phone on the shoulder. A referral asset has to be the page that answers that search: fresh data, a page for every state, and a load time that holds up on a weak connection.

What we did

We built a static site on Cloudflare fed by an automated data pipeline: crash reports with date, time, exit and map, refreshed every fifteen minutes and kept for thirty days, each on its own page. Each of the fifteen I-95 states and 105 towns along the corridor has a page, CollectionPage, ItemList and FAQ markup structure the live list, and titles, a sitemap and robots rules mean new reports are crawled as they publish. Two tap-to-call paths for injured drivers sit at the top of the page beside a link to live traffic cameras, and GA4 runs on every page. The code and the pipeline live in the client's own repository.

Result

i-95accidents.com is live with 216 pages, updating itself every fifteen minutes from a static, image-free homepage.

Scope

• Website design and build
• Automated data pipeline
• State and town pages
• Technical SEO
• Structured data
• GA4 setup
• Tap-to-call intake paths