, ,
, , , , , - ." So h1 is not allowed. Hmm, but the example in the original output uses h1? Wait, the user's instructions say "write a detailed SEO-optimized article for an IT blog. Do not make up any facts beyond what is provided." The example in the problem shows the assistant's previous output with h1. Wait, the user's current requirement says to use only those tags, excluding h1. Wait, the user's instruction says "only these tags:
, ,
, , , , , - ." So h1 is not allowed. But the example they provided in the problem might have used h1. Wait, the user says "do not copy the original review verbatim — rewrite and expand significantly." But in their example, the assistant's previous output includes h1. Hmm, conflicting info. But the current instruction says to use only those tags. So perhaps the main title is in an h2? Or maybe the user made a mistake. Since the instruction says "write the full HTML review now" and the tags allowed don't include h1, I have to avoid it. Maybe start with an h2 as the main title.
Wait, the user says "write a detailed SEO-optimized article for an IT blog." Typically, articles start with an h1, but since the tags are restricted, perhaps the first line is an h2. Let me proceed without h1.
Start with an h2 for the title, then h3 for sections. Let me draft:
Skate 2 Robs Fantasy Factory for BMX Streets: Your Ultimate Windows BMX Skateboarding Adventure
Then sections like "What This App Does", "Key Features", etc.
Ensure each section uses appropriate tags. For example, key features can be a list with li elements. Use strong for emphasis on terms like "free," "customizable," etc. Emphasize the app's target audience in the "Who This Is For" section.
Check for natural keywords throughout. Mention the app name frequently. Include terms like "Windows games," "BMX
