Working with Wichita Eagle Obituary Archives
I spend a lot of time going through old obituary databases for family history work and local journalism projects. The Wichita Eagle's collection is reasonably thorough but not exactly user-friendly if you don't know where to look. Most people hit a wall within ten minutes and give up, which is unfortunate because the records themselves contain genuinely useful detail when you can actually retrieve them. The Kansas City Star and the Wichita Eagle share some back-end systems through their parent company, GateHouse Media, which now operates under Gannett. This matters because it means the search interface isn't purely local. When you go to the Wichita Eagle's obituary page and type in a name, you're running against a national Gannett search schema that sometimes throws out results from other states or merges separate people with the same name. I found this out the hard way when researching a grandmother's death in 2003 and got thirty-seven hits for "Margaret Johnson" before I realized half of them were from Arizona and Michigan. The actual search works best when you narrow the date range first, then add the full name. The default date filter is set to "All Time" which returns thousands of results and effectively useless page two of pagination. Setting the range to the specific five-year window around the expected death date cuts the result set down to something manageable. From there you can layer in additional filters like city or cemetery name. The cemetery field is especially useful because it often catches people the name search misses, particularly for older records where last names were misspelled or Anglicized at publication.
Here's a practical note about download access. The Wichita Eagle doesn't offer a bulk export or API for obituary data. Each record has to be viewed individually or printed through the browser. I wrote a Python script that uses Selenium to scrape the public pages and save them as plain text files. It runs reliably for batches of under two hundred names. Beyond that, the site starts throttling requests and you'll hit CAPTCHAs. I usually split larger queries into groups of one hundred and stagger the runs by about fifteen minutes between batches. This has saved me somewhere around forty hours of manual copying over the past few years compared to reading and transcribing each one by hand. The obits themselves are structured inconsistently, which is the main technical headache. Pre-2010 records tend to be shorter and more formulaic: birth date, death date, surviving family list, service location. Post-2010 notices get longer and include more biographical content, sometimes up to a thousand words. The inconsistency makes automated parsing tricky if you're trying to extract structured data. I built a simple regex-based parser that looks for standard patterns like "born," "died," "survived by," and "service" and pulls out those segments into separate fields. It gets roughly seventy-five percent accuracy on older records and about ninety percent on newer ones. The gap exists because family members sometimes write obits that deliberately avoid chronological markers or bury dates in narrative paragraphs rather than listing them plainly. One thing nobody warns you about: the Eagle retains obituaries indefinitely on their site, but the URL structure changed around 2018. Older links from the pre-change era often return 404 errors now. The Wayback Machine has most of them, but not all. If a direct link is broken, searching by the person's full name plus the city of Wichita and the approximate year will usually surface the archived version under the new URL format. I keep a local spreadsheet that cross-references the old and new URLs so I'm not constantly chasing dead links.
If you need a raw dataset rather than individual pages, your options are limited. The Wichita Public Library has microfilm copies of the newspaper going back to the 1870s, but those require an in-person visit and a reader-printer. Some genealogy sites like Ancestry and Newspapers.com have licensed portions of the Eagle's archive, but the coverage is selective and lags behind the live site by several years. For anyone doing serious research on Wichita-area deaths, the most reliable approach combines direct Eagle searches with a parallel check against the library microfilm for anything predating 2000. The microfilm catches records that were digitized incompletely or removed during website migrations. The main limitation of this whole process is that obituary content is self-reported and frequently contains errors. I've seen correct birth years off by a decade, wrong spouse names, and funeral home listings that don't match the actual service. The records are valuable but they should never be treated as authoritative without cross-referencing with death certificates or Social Security death index records. I usually verify any critical dates against the Kansas Historical Society's death certificate database, which is publicly accessible online. That extra step adds maybe twenty minutes per person but it prevents you from building a family tree on incorrect information. For people who want to just browse without writing scripts, the Eagle's own obituary search at their website is the starting point. Go to kansas.com, navigate to obituaries, and use the advanced filters. If you hit rate limits or broken links, the workarounds I described above handle most of the common friction points. The data is there. It just requires a bit of patience to pull it out cleanly.
Get the Full Details
