F1 Data Embeds for Journalists & Bloggers
F1 data embeds for newsrooms, blogs, and Substacks — race pace, long runs, telemetry, qualifying. Free tier covers a single domain. Higher tiers in development.
It's Sunday, 9:47 PM. The race ended four hours ago. Your editor wants 800 words on the McLaren strategy call by midnight. You want one chart. Maybe a long-run pace plot. Something that shows readers why this race actually mattered, instead of just telling them.
Your options are all bad. Screenshot something off Twitter and hope nobody notices the watermark. Spend 90 minutes wiring up a Python toolchain. Pay for a charting tool. Or just skip the visual and pad with another paragraph nobody will read.
I built F1 data embeds for that exact moment. Copy-paste into WordPress, Ghost, or a custom CMS. Preview first, publish when ready.
If you're new to how F1 prediction data ties into race analysis, F1 Predictions for Beginners covers the basics. This post is for people who already know what FP2 long runs are and just need to put one in an article tonight.
What the embeds cover
Browse the gallery at /embeds. Each entry is a session-bound iframe — pick a season, a round, a session, and the chart renders. Each embed auto-updates after every session. Each one carries a small attribution footer back to Podium Prophets. That's the whole deal.
The catalog covers the angles a working journalist actually needs:
- Pace and stints — race-pace scatter, long-run strip plots, stint-level box plots. The "why was this race actually decided in FP2" angle.
- Qualifying and one-lap pace — qualifying breakdowns, sector deltas, top-speed comparisons. The "0.4s gap that decided Saturday" angle.
- Team and field structure — team-pace hierarchy, fuel-corrected deltas, midfield gap visualizations. The "the real story is between P5 and P9" angle.
- Telemetry and on-track behavior — speed/throttle/brake traces, track-dominance overlays. The "Hamilton found the lap time in Turn 12" angle.
I'm being deliberately vague about the exact catalog because we're still adding more, and a list locks me into a count that's already wrong by next race weekend. If you want the exact set live today, the gallery at /embeds is the source of truth.
If you want a primer on what any of this data means before you publish, How to Read F1 Practice Data walks through it.
How to embed — three steps
The whole thing was designed to be publish-ready before you paste a line of code.
Step 1: Pick a session at /embeds
Go to /embeds, pick an embed type, then pick the season, round, and session. The page renders a live preview right there. If it looks wrong, change the session and try again. No sign-in needed to browse.
Step 2: Copy the iframe code
Below the preview, there's a code block with the iframe snippet. One click to copy. The snippet is standard HTML with sandboxing already set, sized for typical article widths (100% width, fixed height that suits the chart type).
Step 3: Paste into your CMS
WordPress: open your post, add a Custom HTML block, paste, publish. Self-hosted WordPress and WordPress.com Business plans handle this fine. Lower-tier WordPress.com strips iframes for security, so heads up if that's you.
Ghost: hit the plus icon, type /html, paste into the HTML card, publish.
Squarespace: drop in a Code Block, paste, toggle off Display Source.
Wix: Add Elements, Embed Code, Embed HTML, Code mode, paste.
Static sites (Hugo, Jekyll, Astro, Next.js): paste the iframe directly into your markdown or template. Standard HTML, works everywhere raw HTML renders.
Substack and Medium are the holdouts. They strip custom HTML across the board, not just for these widgets. If that's where you publish, you can either link to the live widget URL or use a screenshot with a link back to the interactive version. Annoying, but it's a platform constraint, not a Podium Prophets one.
What it looks like in your article
The widgets are lazy-loaded, so a chart embedded halfway down your post doesn't slow your initial page render. The iframe is sandboxed with sandbox="allow-scripts allow-popups", which means it can render itself and let the attribution link open in a new tab, but it can't touch your cookies, your DOM, or your readers' data. You can verify that in the snippet before you paste.
Themes ship in dark, light, and auto. Auto reads your reader's system preference and matches. Most blogs run dark or light, so the auto presets save you the trouble of picking. You can also pick a custom accent color, write your own chart title, and add a caption — small touches that make the embed feel like part of your article instead of someone else's chart parachuted in.
Attribution is a small text footer at the bottom of the chart. Says "Data by Podium Prophets" with a dofollow link back. It's small enough to not visually compete with your article. Big enough that readers know where the data comes from.
Four use cases with hypothetical headlines
To make this concrete, here are four article shapes that map cleanly onto the embeds.
"How Hamilton Found 0.4s in FP2" → race-pace scatter. Driver-improvement stories live or die on whether readers can see the pace shift themselves. The scatter plot lets them hover and find the lap range where the gap closed. You write the narrative. The chart is the proof.
"Why Ferrari's Long Runs Don't Match Their Qualifying" → long-run strip plot. The classic Saturday-afternoon pace mystery. Strip plot shows compound-by-compound stints, side by side. Readers can see the degradation pattern that explains the qualifying-vs-race-pace divergence. If the topic interests you, F1 Tyre Strategy Guide goes into more depth on the underlying mechanics.
"The Midfield Battle in Imola" → team-pace hierarchy. Midfield stories are about deltas, not absolutes. The hierarchy widget shows the gap from the leader, fuel-corrected if you toggle it. Six teams within four tenths reads as one chart, not a 600-word digression.
"Sprint Weekend Rookie Watch" → long-run analysis. Box plots are the right shape for showing consistency. Toggle individual stints on and off, compare a rookie's median lap to the regular driver in the same car, write the piece around the gap.
If you cover the full prediction landscape too, Best F1 Prediction Games 2026 is the comparison post that surfaces in those queries.
How tiers will work (the plan)
Going forward, the embed product is going to be tiered. Here's the model in plain language. None of this is final, prices haven't been set, and the exact split between tiers is still being worked out — so treat what follows as direction, not commitment.
Free tier. A single publishing domain. Embed across one site. Covers the core embed types — the ones a working journalist needs to fire off a Sunday-night race recap with one supporting chart. Standard customization controls (theme, density, attribution style, accent color, custom title and caption).
Higher tier(s). Multiple publishing domains, useful if you write for several outlets, syndicate across regional publications, or run a network of sites. Plus heavier customization: more configurable layouts, configurable data dimensions on the same chart, the ability to draw on or annotate the chart with your own markers, and access to the more interactive and data-heavy embed shapes that are still in active development.
Today, in practice. Billing isn't live yet. The full tier system, the upgrade flow, and the exact paywall split are all in development alongside more flexible sizing and layout work that has to land first. While that's true, all embed types and customization controls are open on every account. The free-vs-pro line activates once the subscription system goes live.
If you start using embeds today, nothing you publish breaks when tiers go live. Existing publications are grandfathered.
Why it's free for the journalist
Backlinks. That's the whole answer for the free tier.
Each embed carries a dofollow attribution link. When a working journalist writes a race recap and embeds a chart, that's one inbound link from a real publication, in a real article, with real editorial context. Search engines like that. I like that. You get a chart you didn't have to build. I get a link from a domain that has actual authority. The math works for both of us.
The only rule is that the attribution stays visible. Don't hide the footer with CSS, don't crop it out of a screenshot. Higher tiers (when they ship) will keep attribution mandatory — gating customization and domains, not the link.
Open /embeds, pick a session, paste the code into your next race recap. That's the whole product surface. Everything else is just attribution and the tier model that hasn't fully landed yet.