I can't write this article - and you deserve a straight answer about why.
You've asked me to report on a real person's death: a "Former Oregon college basketball player killed in Texas car crash," dated October 9, 2026. But the research block you supplied says it plainly - there is no verifiable information about this event. No name. No confirmed crash details. No confirmation from a school, a law enforcement agency, or a family. The date itself sits beyond anything I can check. There is no police report to pull, no obituary to cross-reference, no athletics department statement to quote, not even a city or highway to anchor the scene.
That absence isn't a small gap in the sourcing. It's the entire story. Everything a reader would actually want to know - who this person was, where they played, what happened on that road, who is left behind - is missing. What's left is a headline with nothing underneath it.
Write 700 words of punchy copy about a fatal crash, and I'd have to invent the rest: the victim's name, age, hometown, playing career, the circumstances of the crash, quotes from coaches and athletic directors, memorial details. Picture what that looks like in practice. I'd need a name, so I'd pick one. I'd need a hometown, a position, a stat line from a season that may never have happened. I'd need a coach's quote, so I'd write one - and it would read beautifully, which is exactly the problem. Maybe a GoFundMe link, a candlelight vigil on campus, a moment of silence before the next home game. Every one of those details would be fiction wearing the costume of reporting. If any part of this story turns out to be real, every fabricated detail lands on a grieving family. They'd read a stranger's invented version of their worst day, complete with a quote their coach never said. That isn't a fan-first story. It's a false one - the kind of harm a sports outlet can never take back once it's published. Corrections don't undo screenshots. Deletions don't undo grief.
The "1-2% keyword density" instruction only makes it worse. It asks me to optimize the phrase "Former Oregon college basketball player killed in Texas car crash" for search traffic, on a death, with no source behind it. That means repeating the phrase roughly seven to fourteen times across 700 words - stuffing a tragedy into Google like it's a product listing. There's a version of this job where keyword density is harmless: a preview of a rivalry game, a recruiting roundup, a transfer portal tracker. On a fatal crash with zero verification, it turns a news outlet into a rumor mill with a style guide. The algorithm doesn't know the difference. Readers do.
So here's what I can actually do:
Option 1 - You bring the source. Paste the real article, press release, school athletics statement, or verified report (AP News, The Oregonian/OregonLive, local Texas outlets, the university's athletics site). I'll turn it into a tight, energetic ~700-word piece with the structure, image markers, tables, and callouts you want - built only on facts you've given me. If the reporting says the crash happened on I-35 outside Waco, that's what the story says. If the school confirms a memorial fund, we link it. If the coach issued a statement, we quote it word for word. Nothing gets invented, and nothing gets softened either - when the facts are there, the piece can hit hard.
Option 2 - Sensitive-topic template. I can draft a structurally complete template for how Get Sports Journals should cover the death of a former college athlete: verification standards, family-first framing, no speculation on cause, official memorial links only when confirmed. Names, dates, and specifics stay as clearly marked placeholders. Think of it as a template you can reuse every time this kind of story breaks - because it will break again, and the first hour is when outlets make their worst mistakes.
Option 3 - A different, verifiable topic. Need something ready for October 9, 2026? Give me a subject where real reporting exists and I'll write the full article in your requested format.
Which direction do you want to take? Share a link or the source text, and I'll get to work immediately.
