# Top Chicago Bears position battles to watch in 2026: No. 3 top wide receiver

Page: https://stenobird.com/podcast/shaw-local-s-bears-insider-podcast-4534/top-chicago-bears-position-battles-to-watch-in-2026-no-3-top-wide-receiver
Text version: https://stenobird.com/podcast/shaw-local-s-bears-insider-podcast-4534/top-chicago-bears-position-battles-to-watch-in-2026-no-3-top-wide-receiver.md
Podcast: [Shaw Local's Bears Insider Podcast](https://stenobird.com/podcast/shaw-local-s-bears-insider-podcast-4534)
Published: 2026-07-01T11:00:06+00:00
Episode link: https://www.spreaker.com/episode/top-chicago-bears-position-battles-to-watch-in-2026-no-3-top-wide-receiver--72770196
Audio file: https://dts.podtrac.com/redirect.mp3/api.spreaker.com/download/episode/72770196/019f1d60b57c_019f1d60_b57c_7ee2_b1e5_7791d05f06a8.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/shaw-local-s-bears-insider-podcast-4534/episodes/top-chicago-bears-position-battles-to-watch-in-2026-no-3-top-wide-receiver
Duration seconds: 253

## Resource

Rome Odunze became the Chicago Bears' and Caleb Williams' No. 1 wide receiver last season before injuries derailed his year. But after showing some flashes last year and in the spring, Luther Burden III will compete with Odunze for the top wide receiver spot. Become a supporter of this podcast: https://www.spreaker.com/podcast/shaw-local-s-bears-insider-podcast--3098936/support .

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/shaw-local-s-bears-insider-podcast-4534/episodes/top-chicago-bears-position-battles-to-watch-in-2026-no-3-top-wide-receiver/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/shaw-local-s-bears-insider-podcast-4534/top-chicago-bears-position-battles-to-watch-in-2026-no-3-top-wide-receiver.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.