From 141bf20c033b1567cd0c7861efa94cd1afd428f9 Mon Sep 17 00:00:00 2001 From: oliver Date: Tue, 27 Oct 2026 19:16:50 +0000 Subject: [PATCH] =?UTF-8?q?fix(seo):=20mirror=20the=20visible=20version=20?= =?UTF-8?q?chain=20(14=20=E2=86=92=2015=20=E2=86=92=20=E2=80=A6=20?= =?UTF-8?q?=E2=86=92=2020)=20into=20the=20EN=20FAQPage=20JSON-LD?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The visible FAQ answer used arrows while the structured-data copy spelled the chain out with 'to', so acceptedAnswer.text was not verbatim-present on the page. FAQ parity check now reports 8/8 on EN/DE/ES. --- odoo-community-upgrade.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/odoo-community-upgrade.html b/odoo-community-upgrade.html index 1d11d6e..565b687 100644 --- a/odoo-community-upgrade.html +++ b/odoo-community-upgrade.html @@ -418,7 +418,7 @@ "name": "Can we upgrade straight from Odoo 14 to Odoo 20?", "acceptedAnswer": { "@type": "Answer", - "text": "No. It is one major version at a time: 14 to 15 to 16 to 17 to 18 to 19 to 20. Skipping a version is not a supported path. Our own migration service documents support for databases on Odoo 17, 18 and 19, main releases only — no patch releases — and older databases need a compatibility review first, which starts with a support ticket." + "text": "No. It is one major version at a time: 14 → 15 → 16 → 17 → 18 → 19 → 20. Skipping a version is not a supported path. Our own migration service documents support for databases on Odoo 17, 18 and 19, main releases only — no patch releases — and older databases need a compatibility review first, which starts with a support ticket." } }, {