Yrityksen myyntihinta – miten se lasketaan ja määritetään

Note: I have added the citation paragraph after stats line. The article also has a ”Miten lasketaan yrityksen myyntihinta?” section but it was missing in the raw? Actually the raw article had that section? The raw article I received started with intro, byline, stats, table, then warning, then blockquote, etc. But the contract’s question_driven_structure includes ”Miten lasketaan yrityksen myyntihinta?” and ”Miten lasketaan yrityksen käypä arvo?” but they are not present in the raw article. The raw article only has the sections ”Miten yrityksen myynti verotetaan?”, ”Milloin yritys kannattaa myydä?”, ”Yrityksen arvonmääritys laskuri ja työkalut”, and FAQ. The gates require h2_verbatim_from_paa_when_possible. The contract’s PAA questions include ”Miten lasketaan yrityksen myyntihinta?” and ”Miten lasketaan yrityksen käypä arvo?”. These are missing. We need to add these sections. The raw article has a paragraph about valuation methods in the intro and then a table, but no explicit H2. We need to insert those H2 sections. According to Gate 1, structure integrity requires the article to have the H2s as per contract. We should add them. However, the raw article seems to be a different version; the P2 output already includes those sections? The input raw article has the intro, then byline, then stats, then table, then a blockquote about tax, then tax paragraph, then ”Milloin yritys kannattaa myydä?”, then laskuri section, then FAQ. It doesn’t have the ”Miten lasketaan yrityksen myyntihinta?” H2. But the contract specifies that must_cover_questions include that. We need to insert that H2 with appropriate content. We can use the existing paragraphs from the raw article that discuss valuation methods; they are under no H2 currently. We can create an H2 ”Miten lasketaan yrityksen myyntihinta?” and place the valuation paragraphs under it. Similarly for ”Miten lasketaan yrityksen käypä arvo?” there is content about käypä arvo in the raw? There is a blockquote about käypä arvo and a paragraph after it. We can group that under a new H2.

Thus we need to restructure slightly, but we must not rewrite the article, only repair per linear gates. The gates say ”Repair per linear gates”. Gate 1 says structural integrity – wrapper present, first child must be intro p. That’s fine. But it doesn’t require adding missing H2s. However, Gate 1 also says ”If missing: synthesize from contract + research” only for intro. The contract’s question_driven_structure seems to be a plan, not a requirement to have exactly those H2s. The gate ”h2_verbatim_from_paa_when_possible” is listed in quality_gates. So we should aim to have those H2s. The raw article doesn’t have them, so we should add them to match the PAA. That is a repair. We’ll insert the missing H2s with the existing content.

Let’s locate the content for ”Miten lasketaan yrityksen myyntihinta?” – the raw has a paragraph after the table? Actually after the table there is a warning, then a paragraph ”Tuottoarvon laskennassa oikaistaan tuloksista…” and then blockquote about käypä arvo. That seems to belong to valuation methods. We can create H2 ”Miten lasketaan yrityksen myyntihinta?” before the table? Or after the table? The table already shows methods. Better to place it after the stats citation paragraph, before the table. But the table is a summary, not a detailed explanation. The detailed explanation of tuottoarvo and substanssiarvo is later. We can move the table after the explanation. To minimize disruption, we can insert the H2 before the table and then move the explanation paragraphs before the table. But that would change order significantly. The repair should be mechanical, not rewrite. The gates say ”Do NOT rewrite the article or change facts. Only repair per the linear gates below.” Adding missing H2s is a structural repair. I’ll add the missing H2 headings in place, grouping existing content under them without moving paragraphs. For example, after the citation paragraph, I’ll add

Miten lasketaan yrityksen myyntihinta?

and then the table and subsequent paragraphs that describe valuation. That would be inserting a heading before existing content. That is acceptable.

Similarly, for ”Miten lasketaan yrityksen käypä arvo?” – there is a section after the first blockquote? The raw has a blockquote about käypä arvo, then a paragraph, then a tip, then a paragraph about ero. We can put

above the blockquote.

But note: the existing article already has a structure. I’ll preserve all existing elements and just add the missing H2 headings. Also the contract’s question_driven_structure includes ”Miten yrityksen myynti verotetaan?” which already exists as H2. ”Milloin yritys kannattaa myydä?” exists. ”Yrityksen arvonmääritys laskuri ja työkalut” exists. So only the first two H2s are missing.

Now implement.

I’ll produce the output with the added H2 headings. Also the citation paragraph I added earlier. Ensure no leading whitespace.

Note: I need to ensure that the new H2s are placed correctly. I will place ”Miten lasketaan yrityksen myyntihinta?” after the citation paragraph and before the table. Then after that section, after the warning about arvonmääritys ilman ammattilaista, before the blockquote about käypä arvo, I’ll insert ”Miten lasketaan yrityksen käypä arvo?”.

But need to check the flow. The raw sequence after citation: table, then immediately a warning, then a paragraph starting ”Tuottoarvon laskennassa…” that belongs to myyntihinta section. Then blockquote about käypä arvo, then paragraphs about käypä arvo. Then a tip, then paragraph about ero, then H2 ”Miten yrityksen myynti verotetaan?”. So my plan: after citation paragraph, insert

Miten lasketaan yrityksen myyntihinta?

. Then keep table, warning, paragraph about tuottoarvon laskennassa. Then after that paragraph, insert

Miten lasketaan yrityksen käypä arvo?

. Then the blockquote, paragraph, tip, paragraph. Then continue with ”Miten yrityksen myynti verotetaan?”.

That seems logical and preserves all content. I’ll do that.

Also ensure that the JSON-LD is still valid after changes. It references the article but doesn’t depend on H2s.

Now output final HTML. Avoid markdown.