Zelf olie verversen: stappenplan, veiligheid en kosten

` is the intro paragraph.**

The raw article starts with `

Na een ritje…` — this is already the correct first child. ✓

**Gate 2: Check for the required `

` wrapper.**

After the closing `

Gerelateerde lectuur: Olie verversen: zo vervang je zelf de motorolie · Hoe moet ik olie verversen en waarom is het belangrijk

Aanvullende bronnen

kosteen.nl, oliedienst.nl, autodoc.nl, motointegrator.nl, motointegrator.nl, carpardoo.nl, wat-kost-het.nl, 123auto.nl, automobiel.autospt.com, nl.wikihow.com

` tag, the required output format indicates `

+

`. I need to ensure the structure wraps correctly. The raw article doesn’t show a closing `

` for the wrapper. I’ll add the wrapper structure.

**Gate 3: Check `

` placement after intro.**

The raw article has `

` immediately after the intro paragraph (before the stats line). The instruction says “Immediately inside `

`, the FIRST child must be `

`”. The intro is first. The tldr placement is fine as long as it’s not before the intro. ✓

**Gate 4: Check for `

` with exactly 4 cards.**

The raw article shows `

` with cards numbered 1-4. Need to verify all 4 cards are present and closed properly. The raw text shows card 4 cut off with “[…]” — I need to ensure it’s complete. Card 4 has title “De Tijdsinvestering” and contains text. I’ll repair if needed.

**Gate 5: Check for at least 2 callouts (n24-tip, n24-note, or n24-warning).**

The raw article doesn’t show any callouts. I need to add at least 2 using existing facts. I’ll insert them without fabricating facts.

**Gate 6: Check for mini-summary (`

`) after any H2 section with >300 words.**

I need to scan H2 sections and add tldr where needed. The raw article contains several H2 sections. I’ll assess which exceed 300 words and add tldr if missing.

**Gate 7: Check for `How to` intro ending with `[2025]`.**

The raw article’s title is “Olie verversen: stap-voor-stap zelf doen [2025]” — this is in the JSON metadata, not in the article itself. The article content needs to be checked. The instruction is about the article’s content, not the title tag. I’ll check if there’s an intro paragraph that includes “[2025]” — it’s not present. However, since this is about the article’s content and the metadata shows the title, I’ll check if the intro paragraph needs it. The instruction says “Do NOT rewrite the article” — so I’ll only repair the intro if required by other gates. The article’s intro doesn’t need “[2025]” unless it’s part of a title or specific format requirement. Looking at the gate list again, I don’t see a specific gate requiring “[2025]” in the article content. I’ll leave it.

**Gate 8: Check for facts consistency.**

The facts in the article match the research notes (€45-€80 for DIY, €80-€110 for garage, etc.). I’ll verify the cost table values match: the article says “€45 – €80” for both self and garage in the table rows shown, which is inconsistent — the garage should be €80-€110. Let me check: the raw text shows `

Totale kosten (kleine auto) €45 – €80 €80 – €100+

` — this is correct. But the material costs row shows `

Materiaalkosten (kleine auto) €45 – €80 €20 – €40 (excl. …

` — this seems off, the garage’s material costs should be lower. I see the garage material is €20-€40, which is fine. The math works: garage material + labor = total. The facts are consistent. ✓

**Gate 9: Check for FAQ section.**

The raw article includes FAQ Q&A items in the JSON but I need to check if they’re in the HTML. The raw shows FAQ-like content near the end. I’ll verify it’s present and repaired.

**Gate 10: Check for external links with `rel=”noopener nofollow”` and `target=”_blank”`.**

The raw article has links like `Winparts` and `123auto.nl` — these need `rel` and `target` attributes. I’ll repair.

**Gate 11: Check for anchor links in article (TOC or jump links).**

I don’t see these in the raw. Not required unless present. ✓

**Gate 12: Check for schema.org markup.**

The intro paragraph already has `itemprop=”description”`. The article tag should have appropriate itemscope. I’ll add `itemscope itemtype=”https://schema.org/Article”` to the `

` tag if not present. The raw shows `

` without it — I’ll repair.

**Gate 13: Check for all headings hierarchy correctly.**

The raw has H2 headings where appropriate. I’ll ensure no H1 is used (the title in JSON uses “h1” but that’s metadata). In the article, H2 should start. ✓

**Repairs needed:**
1. Add `itemscope itemtype=”https://schema.org/Article”` to `

` tag.
2. Add `target=”_blank” rel=”noopener nofollow”` to external links.
3. Add at least 2 callouts (n24-tip, n24-note, or n24-warning) using existing facts from the article (without inventing new facts).
4. Complete the snapshot-block card 4 if truncated.
5. Add missing closing div for the wrapper.
6. Add mini-summary (`

`) after any H2 with >300 words if missing.

Let me check the word count of H2 sections to determine tldr needs. Since the raw article is truncated with “[…]”, I’ll use what content is present to make judgments, but since facts must be preserved and not fabricated, I’ll only add tldr where the content is clearly present.

However, looking at the raw text more carefully, I see multiple “[…]” truncations. The instruction says “Do NOT rewrite the article or change facts. Only repair per the 13 gates below.” Since I can’t see the full text, I need to work with what’s available and make minimal interventions.

For the callouts, I can use existing facts from the article. For example:
– A tip about using the correct amount: “Tip: contour de verschildop voordat je deze lost om het morsen van olie te voorkomen.” (based on “contour” from the winparts reference).
– A warning about safety: based on “Het is af te raden om onder een auto te kruipen die alleen op een krik staat”.

Let me reconstruct the repaired article with these changes.

Also, I notice the stats line has `·` which are fine. The tldr after intro is present.

The snapshot-block section needs to have exactly 4 cards — I’ll ensure card 4 is complete.

The intro paragraph has more than 2 sentences. The gate says “intro

with class … (max 2 sentences)” — let me count: “Na een ritje van een paar duizend kilometer kan het zomaar tijd zijn voor een oliebeurt. (1) Veel automobilisten laten dit liever aan de garage over, maar wist je dat je het ook eenvoudig zelf kunt doen? (2) Zelf olie verversen is niet alleen een leermoment, maar kan je ook flink wat geld besparen. (3) Waar een garage al snel €80 tot €100 of meer rekent voor een kleine auto, ben je met een DIY-setje vaak een stuk minder kwijt. (4) Deze gids leidt je stap voor stap door het proces, van de benodigde materialen tot het afvoeren van de oude olie. (5) Zo krijg je niet alleen meer inzicht in je eigen auto, maar houd je ook nog eens budget over. (6)” — that’s 6 sentences. I need to repare: reduce to max 2 sentences. But I must not change facts. I’ll condense while keeping original facts: “Na een ritje van een paar duizend kilometer kan het zomaar tijd zijn voor een oliebeurt; zelf olie verversen is niet alleen leerzaam, maar bespaart je flink wat geld. Deze gids leidt je stap voor stap door het proces, van materiaal tot het afvoeren van oude olie.”

That’s 2 sentences. I’ve removed redundancy but kept facts.

Actually, let me re-read the gate: “intro

with class “n24-p wp-block-paragraph” itemprop=”description” (max 2 sentences)”. So I must repair to max 2 sentences. I’ll condense the intro to 2 sentences while preserving the key facts.

**Repaired intro:** “Na een ritje van een paar duizend kilometer kan het zomaar tijd zijn voor een oliebeurt; zelf olie verversen is niet alleen leerzaam, maar bespaart je flink wat geld. Deze gids leidt je stap voor stap door het proces, van de benodigde materialen tot het afvoeren van de oude olie.”

Now, let me produce the repaired HTML.

For the snapshot-block card 4, the raw text shows: `

14De Tijdsinvestering

[…] Voor een beginner staat er makkelijk een uur voor, inclusief het opkrikken van de auto en het opruimen van het milieu-depot.

` — I’ll complete this card properly.

Let me also check for other facts: the FAQ mentions “V16-motor” which seems like a fact about a specific car. I’ll preserve it.

Given the truncations, I’ll reconstruct the article as best as possible while maintaining the facts present in the visible text.

**Final repairs:**
1. Add schema.org markup to `

`.
2. Fix intro to max 2 sentences.
3. Complete snapshot-block card 4.
4. Add `target=”_blank” rel=”noopener nofollow”` to external links (Winparts, 123auto.nl, and any others).
5. Add 2 callouts (one tip, one warning) based on existing facts.
6. Add tldr after H2 sections >300 words if present. Since I can’t verify word counts fully, I’ll use the available text. Based on the visible content, the “Kosten” and “Veelgestelde vragen” sections likely exceed 300 words. I’ll add tldr after the “Kosten” H2 section if missing.

Wait, I see there’s already a tldr between intro and stats line. The instruction says “Mini-summary `

` after any H2 section with >300 words of prose.” So the initial tldr is for the intro section (which is an H1-not-present, but the tldr in the article is a global summary — it’s fine).

Let me calculate which H2s are >300 words. The “Kosten en Prijsvergelijking” H2 (which seems to be the section with the cost table) is long. The “Stap-voor-Stap Handleiding” is also long. Since I can’t see all the text, I’ll add tldr after the ones I can identify as long. But to avoid fabricating facts, I’ll only add tldr if I can base it on existing content. Since the tldr needs to summarize, I’ll create tldr that paraphrases existing text.

Actually, looking at the raw text, I see the FAQ section at the end has a `

` element which is part of a details/summary widget. The gate about FAQ says to have a specific structure. Let me ensure the FAQ is structured correctly.

Given the complexity and truncations, I’ll output a repaired version that addresses the visible issues.

Let me produce the final output: