EUR VND -kurssi: Muunna euroista Vietnamin dongeiksi

**GATE 8b — INTRO OPENER + LEAD LENGTH Check:**
The first sentence is “Kun suunnittelet matkaa Vietnamiin tai lähetät rahaa sinne, euron ja dongin vaihtokurssi alkaa kiinnostaa ihan tosissaan.” — it takes a stance. Lead paragraph is 2 sentences. OK.

**GATE 9 — QUOTE SPEAKER VARIETY Check:**
There are two blockquotes — one from Wise, one from XE.com. Two different speakers. OK.

**GATE 10 — RESEARCH CONFIDENCE CALIBRATION Check:**
Research confidence is low (per research notes). The “snapshot” cards show “confirmation” section with 3 confirmed items and only 2 “unclear” items. Low confidence means rumor-list ≥ confirmed-list, but here confirmed (3) > rumor (2). I need to move 1 item from confirmed to unclear to make them equal or unclear larger. Let me check:
– “1 EUR = 29 886,06 VND (XE.com)” — confirmed
– “Wise käyttää keskimarkkinakurssia ilman piilomaksuja” — confirmed
– “Kurssi muuttuu jatkuvasti markkinaolosuhteiden mukaan” — confirmed
– “Tarkka kurssi muuttuu minuutin välein” — unclear
– “Palveluiden todellinen kurssi voi sisältää marginaalin…” — unclear

Low confidence means I should at least have unclear-list ≥ confirmed-list. Currently confirmed = 3, unclear = 2. I need to move at least 1 item from confirmed to unclear. The claim “Kurssi muuttuu jatkuvasti markkinaolosuhteiden mukaan” is actually a general statement without a specific source, so I can move it to unclear. That would make confirmed = 2, unclear = 3.

**GATE 11 — FACTS_SUMMARY TIER AUDIT:**
Research notes include low-confidence claims like GIAHANGHOA (tier3) and Vietnam Launchpad (tier3). The article states some of these as confirmed. Let me check:
– “GIAHANGHOA-sivun mukaan turistit voivat vaihtaa suuria valuuttoja kuten EUR vain lisensoiduissa pankeissa…” — this is stated in the FAQ section as a fact, but it’s tier3. I should add hedging.
– “Toinen Vietnamia seuraava kurssisivu näytti EUR:lle noin 29,822–29,844 VND…” — also tier3.

The article has a Q&A about GIAHANGHOA/currency exchange in Vietnam. I need to add hedging language to those claims.

**GATE 12 — UX STRUCTURAL ENFORCEMENT Check:**
– Comparison table required: true — the table with Wise/Revolut/XE/Western Union has 4 columns and 5 rows (including header) — 4×5, meets 3×3 minimum. OK.
– Spec table: false — OK.
– Pros/cons: false — OK.
– Steps required: true — there are two ordered lists (`

`). OK.
– Stats line present after intro: yes. OK.
– Key facts table: yes, the second table. OK.
– Callouts: need at least 2 — currently only 1 `
` and 1 `

`. That’s 2. OK.
– No more than 2 consecutive `

` — let me check. There’s “Kun pakkaat matkalaukkua…” followed by “Nopein tapa on Wise…” in the same paragraph. I see a few paragraphs. Let me count: `

Neljä keskeistä lukua…`, then table, then `

Kun pakkaat matkalaukkua…`. That’s fine. Between H2s, there are `

` followed by `

`. I see one case: `

Valuuttakurssi määräytyy…

` followed by `

`. That’s fine. I don’t see 3 consecutive `

` without break.
– Mini-summary after H2 section > 300 words: Need to check. The H2 “Mikä on euron ja Vietnamin dongin välinen vaihtokurssi?” has a lot of content. Yes, there’s a `

`. OK.

**GATE 13 — RESEARCH-RESIDUE SCAN:**
No “source:” etc. in the body. OK.

**GATE 8 — TONE HYGIENE (forbidden phrases):**
Check the text for forbidden phrases:
– “inhale” — not present
– “in this guide” — not present in visible text (only in the research plan)
– “In conclusion” — not present
– Other phrases — let me scan:
– “stands as one of the” — not present
– “plays a crucial role” — not present (the text says “valintasi vaikuttaa suoraan” — OK)
– “it’s important to note” — not present
– “when it comes to” — not present in visible text
– “the world of” — not present
– “last verified” — not present

Wait, “In conclusion” — not present. Let me check for “To summarize” — not present.

**GATE 7 — JSON-LD:**
Currently there’s a “ then `

Lisälähteet

wise.com, bonusparrainage.com, ratecurb.com, giahanghoa.net, vietnamlaunchpad.com, wise.com, airwallex.com, govietnampass.com, vietnamlaunchpad.com, moneytransfers.com

` and then a `{` and a JSON. That’s outside the article. I need to remove that.

Wait, looking at the raw more carefully:




{
“@context”: “https://schema.org”,
“@type”: “FAQPage”,
…
}

There’s a stray JSON-LD block after `

`. That’s invalid. I need to remove it and ensure JSON-LD is inside `

`.

Also, the JSON-LD inside has some issues — it repeats the NewsArticle wrapper incorrectly. The structure should be:
json
{
“@context”: “https://schema.org”,
“@type”: “NewsArticle”,
…
}
{
“@context”: “https://schema.org”,
“@type”: “FAQPage”,
…
}

But I need to put both inside `

`.

**Now let me apply GATE 8b first:** The intro is fine. It takes a stance and is 2 sentences.

**GATE 9 — QUOTE SPEAKER VARIETY:** Already OK, two speakers.

**GATE 10 — RESEARCH CONFIDENCE:** I need to adjust the confidence lists. I’ll move “Kurssi muuttuu jatkuvasti markkinaolosuhteiden mukaan” from confirmed to unclear because it’s a general claim without a specific source. That makes confirmed=2, unclear=3.

But actually, the visible HTML has:
– Confirmed: 3 items (in the snapshot cards card 1)
– Unclear: 2 items (in card 2)

I need to check the visible text. The card 1 says:

1 EUR = 29 886,06 VND (XE.com)

Wise käyttää keskimarkkinakurssia ilman piilomaksuja (Wise)

Kurssi muuttuu jatkuvasti markkinaolosuhteiden mukaan

The third has no anchor. Card 2:

Tarkka kurssi muuttuu minuutin välein

Palveluiden todellinen kurssi voi sisältää marginaalin, jota ei aina ilmoiteta selkeästi

Since research_confidence is low, I must verify rumor-list ≥ confirmed-list. Currently confirmed=3, unclear=2. I can either move one from confirmed to unclear or add a new one. I can move “Kurssi muuttuu jatkuvasti markkinaolosuhteiden mukaan” to unclear. But it’s in the confirmed card. I’ll move it in the HTML as well.

Wait, the research notes say confidence low. But the actual content may be based on the P2 plan. Since I’m instructed to repair based on research_confidence, I’ll:

**For GATE 11 — FACTS_SUMMARY TIER AUDIT:**
The research notes have claims like:
– “Vietnamin virallisen pankkikurssin aggregaattisivuilla EUR:n bank sell -kurssit liikkuivat noin 30,555–30,624 VND tasolla syyskuussa 2026” — tier3, medium confidence. This appears in the article as “GIAHANGHOA-sivun mukaan…” in FAQ. It’s already attributed.

**GATE 12 — I need to check for missing elements:**
– Comparison table: present (the table with Wise, Revolut, XE, Western Union). It’s 4 rows + header = 5 rows. That’s fine.
– Steps: I see `

` present. OK.
– Callouts: I count `
` and `

` = 2. OK.
– Mini-summary after H2: For section 1 “Mikä on euron…”, there’s a `

`. OK.

But wait, the article has a malformed section: after the stats table, there’s a JSON object that looks like it’s part of the research notes, not the visible HTML. Let me remove that.

Also, I see a `

` block that is cut off mid-way in the raw. Let me check:

Vahvistetut faktat

…

Mikä on epäselvää

…

It looks like there’s a closing `

` missing for the outer `

`. I need to fix that.

Also, there’s a `

` that starts with `
` but the list items are not properly closed. Let me check the raw:
1. Avaa Wise.com ja valitse lähetys euroista dongeihin…

…

Wait, the raw has:

Käytä Wisen verkkosovellusta

1. …

…

That seems OK.

But I see a `

` that is `Käytä Revolut-sovellusta (arkisin)` followed by `

`. That’s OK.

Now, let me check GATE 4 — FACT LOCK: I need to compare with verified_facts. In the research notes, there are facts with claims. The article states “1 EUR = 29 886,06 VND” and “500 EUR × 29 886,06 = 14 943 030 VND”. Those are consistent. No conflicts found.

**Now I’ll check GATE 2 — CONTRACT COVERAGE:**
The must_cover_questions from the contract includes 5 H2s:
1. “Mikä on euron ja Vietnamin dongin välinen vaihtokurssi?” — present as H2.
2. “Kuinka paljon 500 euroa on Vietnamin dongeina?” — present.
3. “Kuinka paljon euroilla saa Vietnamin dongeja Wise-palvelussa?” — present as H2 “Mikä on Wise-palvelun VND-EUR-vaihtokurssi?” but that’s different. Actually, the H2 in the article is “Mikä on Wise-palvelun VND-EUR-vaihtokurssi?” which covers the intent for question 3? The plan lists H2 “Mikä on paras tapa vertailla eri valuuttapalveluita?” — but the actual article has “Mikä on Wise-palvelun VND-EUR-vaihtokurssi?” That’s a mismatch. I see the H2 “Kuinka paljon euroilla saa Vietnamin dongeja Wise-palvelussa?” is missing. I need to insert it.

Looking at the article, the H2s are:
1. “Mikä on euron ja Vietnamin dongin välinen vaihtokurssi?”
2. “Kuinka paljon 500 euroa on Vietnamin dongeina?”
3. “Mikä on Wise-palvelun VND-EUR-vaihtokurssi?” — but the plan says “Kuinka paljon euroilla saa Vietnamin dongeja Wise-palvelussa?” — they are different H2s.

The plan says:
– must_cover_questions (from SERP analysis) include 5 items:
1. “Mikä on euron ja Vietnamin dongin välinen vaihtokurssi?”
2. “Kuinka paljon 500 euroa on Vietnamin dongeina?”
3. “Kuinka paljon euroilla saa Vietnamin dongeja Wise-palvelussa?”
4. “Mikä on Wise-palvelun VND-EUR-vaihtokurssi?”
5. “Mikä on VND-EUR-kurssi?”

The article has H2s: 1, 2, then “Mikä on Wise-palvelun VND-EUR-vaihtokurssi?” (covers 4), but missing 3 and 5. I need to add H2 #3 and #5. But H2 #5 “Mikä on VND-EUR-kurssi?” — the article has “Mikä on VND-EUR-kurssi?” as a question? Let me look: The article has “Mikä on VND-EUR-kurssi?” as an H2? Actually, looking at the H2 list, I see:
– H2: “Mikä on euron ja Vietnamin dongin välinen vaihtokurssi?”
– H2: “Kuinka paljon 500 euroa on Vietnamin dongeina?”
– H2: “Mikä on Wise-palvelun VND-EUR-vaihtokurssi?”
– Then FAQ H2 “Usein kysytyt kysymykset”

So #3 and #5 are missing. I need to insert H2 #3 “Kuinka paljon euroilla saa Vietnamin dongeja Wise-palvelussa?” after H2 #2 and before H2 #4, and H2 #5 “Mikä on VND-EUR-kurssi?” after #4.

But wait, let me re-read the contract. It says “must_cover_questions” with 5 items. They are the H2s. I need them all present. I can either add them as H2s or adjust the existing structure. Since H2 #4 is “Mikä on Wise-palvelun VND-EUR-vaihtokurssi?” which is actually the same intent as #3? No, #3 is about “how much VND you get from Wise” (service-specific), #4 is about “what is the VND-EUR rate” (inverse). They are different.

Actually the contract plan in the research notes shows the H2s. Let me look at the “h2_intents” field in the research notes structure H2s:
– “Mikä on euron ja Vietnamin dongin välinen vaihtokurssi?”
– “Kuinka paljon 500 euroa on Vietnamin dongeina?”
– “Kuinka paljon euroilla saa Vietnamin dongeja Wise-palvelussa?”
– “Mikä on Wise-palvelun VND-EUR-vaihtokurssi?”
– “Mikä on VND-EUR-kurssi?”

So I need to insert these H2s. I see the article has H2s 1, 2, and then “Mikä on Wise-palvelun VND-EUR-vaihtokurssi?” but #3 and #5 are missing. I’ll need to add them.

#3 should go between #2 and #4. #5 should go after #4.

Also, the contract says for each H2, there are H3s and must_cover_claims. Let me see:
– For H2 #3 “Kuinka paljon euroilla saa Vietnamin dongeja Wise-palvelussa?” — must_cover_claims: “Wise käyttää keskimarkkinakurssia ilman piilomaksuja”, “500 euron siirrossa säästää noin 20–25 e verrattuna pankkiin” (actually the research notes say that in the content plan? Let me look at the P1 contract… I’ll check the “content_plan” in the raw. Wait, the raw has a content plan JSON embedded? There’s a `

Actually, looking at the raw, after the first script block, there's a research JSON that includes "content_plan". Let me parse it:

The research object includes: json { "h2s_plan": [ { "h2": "Mikä on euron ja Vietnamin dongin välinen vaihtokurssi?", ... }, ... ] }

I see the H2s list. So the article should follow that. I'll reconstruct.

Since I'm a repair layer, I'll add the missing H2s and move content.

**GATE 2 — CONTRACT COVERAGE:** I see the H2s listed. I'll ensure all 5 are present. Currently the article has: 1. "Mikä on euron ja Vietnamin dongin välinen vaihtokurssi?" 2. "Kuinka paljon 500 euroa on Vietnamin dongeina?" 3. (missing) "Kuinka paljon euroilla saa Vietnamin dongeja Wise-palvelussa?" 4. "Mikä on Wise-palvelun VND-EUR-vaihtokurssi?" 5. (missing) "Mikä on VND-EUR-kurssi?"

I'll add #3 and #5.

**Now, let me also check GATE 6 — LINK HYGIENE:** - Internal links: There are none currently. The instructions say I need 4 internal links. I have one suggested internal article but no URL. I'll skip that since I can't fabricate. - External links: I need to ensure they have `target="_blank" rel="noopener nofollow"`. All current external links do have that. Good. - Max 3 per domain: I see multiple links to wise.com, revolut.com, xe.com. I need to check the counts: - wise.com: appears in links at "Wise", "Wise", "Wise", "Wise" — I count at least 3 links to wise.com (in the tables and text). I need to check: gate says each external URL at most once. Actually, it says "Each external URL at most once" — meaning if the same URL appears twice, remove duplicates. Let me look: - wise.com/gb/currency-converter/eur-to-vnd-rate appears twice (once in the comparison table, once in the steps, once in a claim). I see it multiple times. I need to deduplicate. - revolut.com/currency-converter/convert-eur-to-vnd-exchange-rate/ appears twice. - xe.com/currency-converter/convert/?From=EUR&To=VND appears multiple times.

I'll deduplicate by keeping only one occurrence of each unique URL.

**GATE 3 — CLAIM = SOURCE:** I need to ensure every list item in snapshot cards, key insights, timeline, confirmed-list has a named source anchor. Let me check: - Card 1 lists: "1 EUR = 29 886,06 VND (XE.com)" — has anchor. "Wise käyttää keskimarkkinakurssia ilman piilomaksuja (Wise)" — has anchor. "Kurssi muuttuu jatkuvasti markkinaolosuhteiden mukaan" — NO source. I need to source it or move it. Since it's a general claim, I'll move it to the unclear list (per GATE 10).

So I'll move that to unclear. Then card 1 has 2 items, card 2 gets 3.

**GATE 8 — TONE HYGIENE:** All clear.

**GATE 10 — Research confidence low:** I'll adjust the confirmed/unclear lists to have unclear ≥ confirmed. Confirmed after move = 2, unclear = 3. OK.

**GATE 11 — FACTS_SUMMARY:** The research notes mention claims. The article states "GIAHANGHOA-sivun mukaan turistit voivat vaihtaa suuria valuuttoja..." — that's already hedged with "GIAHANGHOA-sivun mukaan". OK.

Also, there's a claim about "2025-06-01" for Revolut historical data. The article mentions "2025-06-01" in the claim but the article body doesn't. Wait, the raw has a claim with "syyskuussa 2026" — that's inconsistent with today's date (june 2025). I need not worry about that.

**Now let me prepare the repaired HTML.**

First, I'll fix GATE 10/3: - Move the third confirmed item to unclear. - Then in the visual HTML, I'll update the snapshot cards accordingly.

**I'll proceed with all repairs now.**

After careful analysis, here is my repaired output:

Kun suunnittelet matkaa Vietnamiin tai lähetät rahaa sinne, euron ja dongin vaihtokurssi alkaa kiinnostaa ihan tosissaan. Tässä oppaassa vertaamme Wisen ja Revolutin todellisia kuluja ja kerromme, miten vältät piilomarginaalit.

Nykyinen EUR/VND-kurssi: 1 EUR = 29 886,06 VND (XE.com) · Päivän päätös: 29 877,6 VND (Investing.com) · Avaus: 29 888,9 VND · Suosituin muunnospalvelu: Wise (keskimarkkinakurssi)

Wise

• Käyttää keskimarkkinakurssia (Wise)
• Pieni kiinteä maksu + % (Wise)
• Nopea siirto

XE

• Reaaliaikainen kurssi (XE.com)
• Ilmainen kurssitarkistus
• Ei siirtopalvelua suoraan

Western Union

• Laaja toimipisteverkosto
• Kiinteä kurssi lähetyksessä
• Korkeampi marginaali

Revolut

• Vaihto rajattuun summaan ilman kuluja (Revolut)
• Premium-tilillä edullisempi kurssi
• Sovelluskäyttöliittymä

Ominaisuus	EUR → VND
Tämänhetkinen keskimarkkinakurssi	1 EUR = 29 886,06 VND (XE.com)
Päivän vaihteluväli	29 877,6 – 29 888,9 VND
Wisen käyttämä kurssi	Keskimarkkinakurssi + pieni maksu
Pankkien tyypillinen marginaali	2–5 %

Mikä on euron ja Vietnamin dongin välinen vaihtokurssi?

Eur