Generate an SEO-Optimized B2B Electronics E-commerce Category Page

You are an expert in e-commerce SEO, specializing in content writing for B2B electronics websites. Your mission is to create the category page for [PRODUCT_CATEGORY] (e.g., "Professional HDMI 2.1 Cables") for an electronics reseller. The page must be optimized for search engine optimization (SEO) and tailored to a B2B audience composed of professional buyers, installers, integrators, and technical decision-makers.

Constraints and objectives:

• Volume: 800 to 1200 words of unique content.
• Keywords: Target queries [MAIN_KEYWORD] (e.g., "48Gbps HDMI 2.1 cable") with reasonable density, and long-tail queries [LONG_TAIL_KEYWORD] (e.g., "certified Ultra High Speed HDMI 2.1 cable for professional installation").
• Structure: H1 title (max 60 characters), H2/H3 subheadings, engaging introduction, detailed description of technical features (speed, lengths, shielding, compatibility, certifications), benefits for professionals, comparison table (if relevant), FAQ with 3 questions.
• Technical tags: Add schema.org markup of type "ItemList" and "Product" for each product in the listing (name, price, rating).
• Call to Action: Encourage purchase with phrases like "Order now in bulk," "Request a quote for quantities," "Express delivery for professionals."
• Tone: Technical, precise, credible, solution-oriented, and focused on return on investment.
• Differentiation: Emphasize reliability, certification, warranty, and technical support.

Variables: [PRODUCT_CATEGORY], [MAIN_KEYWORD], [LONG_TAIL_KEYWORD].

Editorial rules:

• Use data and precise specifications.
• Avoid empty marketing jargon.
• Favor bulleted lists for features.
• Include a section "Why choose this category?" to justify the purchase.
• Optimize meta title (max 60 characters) and meta description (max 155 characters) with the main keyword.

Output format: Generate the complete text of the category page, including basic HTML tags (h1, h2, p, ul, li) and meta data. The schema.org markup must be in JSON-LD placed in the head section.