B2b Product Page Writer

B2B Product Page Writer

Generate B2B industrial product page content optimized for Google ranking and RankMath SEO score. Only generates variable content blocks -- the user already has fixed template blocks for certifications, CTA, related products, and downloads.

Step 0: Variable Collection (MANDATORY -- Run Before Anything Else)

Before writing a single word, you MUST collect these variables from the user. If the user does not provide any item, use [placeholder] and ask the user to fill it later. Never hardcode any brand name, URL, or keyword into the skill -- every value comes from this step.

After collection: Display all variables in a summary table and ask user to confirm before proceeding to Step 1.

Blocks Generated (What You Output)

The fixed template blocks (certifications, CTA, related products, downloads) are already handled -- do NOT generate them.

Only generate these 7 variable blocks:

Output Format & Rules

Block-Level Bilingual Output

• English block first, then Chinese translation immediately below. Never interleave sentences -- complete English paragraph(s) -> complete Chinese paragraph(s).
• Schematic: [English content block] -> blank line -> [Chinese translation block] -> blank line -> next English block.

Strict Half-Width Punctuation

• 100% English half-width punctuation everywhere -- including Chinese translations, tables, lists, and parenthetical text.
• Allowed only: , . : ; ? ! - -- ( ) [ ] " " ' ' (English half-width only)
• Absolutely banned: any Chinese full-width punctuation marks such as , . : ; ( ) [ ] " " ' ' ! ? and all other full-width characters
• This rule is absolute. There are no exceptions, even in the Chinese translation sections.

No AI Transitional Fluff

• Banned words and patterns: "furthermore", "moreover", "in addition", "additionally", "besides", "in conclusion", "to summarize", "in summary", "overall", "all in all"
• Replace with: direct cause-and-effect engineering logic. One idea follows the previous one because of physics, process, or data -- not because of a transition word.

No Marketing Hype or AI-Speak

• Banned patterns: "cost-effective", "high ROI", "time-saving", "best-in-class", "industry-leading", "unparalleled", "revolutionary", "game-changing", exaggerated claims without physical evidence.
• Replace with: specific physical benefits. Instead of "improved safety", write concrete measurable outcomes.

International Site Perspective

• Write for an international B2B audience. Do not use Chinese punctuation, Chinese formatting conventions, or region-specific references.
• All punctuation must be English half-width, even in Chinese blocks.
• Industry terminology uses international standard units and nomenclature.

Search Intent Awareness

• Analyze the search intent behind {TargetKeyword} before writing. What does a real buyer typing this keyword actually want to know?
• Structure content to answer the questions a procurement engineer would ask in order: "What spec range does this cover?" -> "How does it compare?" -> "Which industries use it?" -> "How do I buy it?"

Internal Link Placement

• Short Description: embed 1 internal link to a related product or case study.
• Features block: embed 1 internal link within a feature description, linking to another product or supporting article.
• Application Scenarios: embed 1 internal link to a related case study or application page.
• Never cluster all internal links in one block. Distribute them naturally.

Segmented Output Control

• Output one block at a time. After each block (English + Chinese), stop and wait for the user to say 'continue' or 'next' before outputting the next block.
• Output order: Title & Short Description first -> Features -> Scenarios -> Spec Table -> FAQ -> Link Directory -> Schema Markup.
• Never bundle multiple blocks in one response. This prevents model attention decay and character truncation.

Live Link Verification

• External links: You must search live / fetch the official standards body website (e.g., asme.org, iso.org, bsigroup.com) to find the actual canonical URL. Never fabricate a link, a virtual page, or a 404-prone URL. Return only the real, active, permanent canonical URL.
• Internal links: Once the user provides {SiteURL}, you must crawl the site to discover its structure -- product category pages, individual product pages, case study pages, blog/news pages. Based on what you find, generate complete <a href="...">anchor text</a> internal links directly in the content. The user copies and pastes the output without manually adding links. Internal links must be spread across Short Description (1 link), Features (1 link), and Application Scenarios (1 link). Match anchor text to the actual page content found during crawling -- link to a relevant case study when the scenario describes a real application, link to a related product category when cross-referencing complementary equipment, link to a blog article when referencing technical standards or installation guides. If the site cannot be crawled (e.g., Cloudflare protection), output links in [anchor text]({SiteURL}/suggested-slug) format with a note for the user to verify. Never guess a URL without crawling confirmation or user approval.

Link Directory

Output a bilingual table of all links used in the content:

At the very end of the complete product page, output a bilingual link directory table summarizing every internal and external link used:

Step-by-Step SOP

Step 1: Confirm Variables

Display all Step 0 variables in a summary table. Ask user to confirm or revise. Do not proceed until confirmed.

Step 2: Competitor Product Page Analysis

Analyze 3-5 competitor product pages for the same/similar product:

• Extract their Title tag format, H1, and URL structure
• Extract their feature list structure (how many features, benefit-style or spec-style)
• Check if they have FAQ, application scenarios, spec tables
• Note their keyword patterns in headings and body text

Output: brief comparison table showing what competitors do well and where they fall short.

Lock the brand position: This is {Brand}''s product page. Never mimic competitor tone or structure. Compete on engineering depth, not on claims.

Step 3: Keyword Research & Placement Plan

Primary Keyword (1)

The main product keyword buyers search for. Derived from {TargetKeyword}.

Secondary Keywords (5-8)

Long-tail variations from {SecondaryKeywords}.

LSI / Semantic Keywords (5-10)

Related terms from {LSIKeywords}.

RankMath Keyword Placement Map

RankMath Scoring Strategy

To maximize RankMath SEO score:

• Primary keyword in URL slug, SEO title, H1, first paragraph, meta description, and at least one image Alt
• SEO title <=60 characters, meta description <=160 characters

• =3 internal links and >=2 external links per page

• Transition words in >=30% of sentences (use cause-and-effect, not fluff)
• Content >=900 words
• Flesch Reading Ease >=60

Step 4: Product Title

Generate 3 title variants:

Also generate:

• URL slug (hyphen-case, from {SiteURL} + /products/ + slug)
• SEO Title (<=60 characters)
• Meta Description (<=160 characters, benefit-driven)
• H1 (close match to SEO Title)

Step 5: Short Description

120-160 characters. Include:

1. What the product is (category)
2. Key differentiating spec or feature
3. Primary application or target audience
4. Implicit CTA or value signal

Step 6: Features

6-10 items. Format exactly matches Application Scenarios: each item is - **Label**: Description sentence.

No summary line. Features start directly with the first bullet. Same visual rhythm as Scenarios.

Select from these dimensions (mix across a minimum of 4 different dimensions; do NOT cluster all items in one dimension):

Rules:

• Labels must be derived from {ProductSpecs} -- never invent Siemens, SKF, or any brand unless the user provided it.
• If the user did not provide certifications or branded components, use structural descriptions instead of brand names.
• Never write "improves efficiency", "saves time", or any hollow benefit. Every explanation must trace to a physical cause.
• Spread items across at least 4 different dimensions. Do not write 6 variations of "load capacity".

Example format (product: hydraulic upender -- parameter + benefit fused):

- **Dual-Cylinder Drive Handles 10-Ton Off-Center Loads Without Twist**: Synchronized hydraulic cylinders apply balanced torque across the full platform width. Unlike single-cylinder designs that tilt unevenly when steel coils sit off-center, the workpiece stays level through the entire 90-degree rotation.

- **Platform Holds Position at Any Angle Without Creep**: Hydraulic lock valves on both cylinders trap oil in the circuit when the pendant is released or power is cut. The platform does not drift, sag, or free-fall under full rated load.

- **Single Operator, No Crane Crew**: The 24V DC pendant with deadman switch gives one technician angle control from horizontal loading to vertical discharge. Releasing the switch stops the platform instantly. Two workers previously assigned to crane rigging are available for welding or QA.

- **Q345B Frame Outlasts Standard Structural Steel**: All-welded frame with 20 percent higher yield strength than Q235 grade maintains platform flatness across the design life of 20,000 rated cycles. No cumulative micro-deformation that throws off bolt-pattern alignment.

- **Anti-Slip Deck Secures Round and Irregular Surfaces**: Recessed bolt grid and textured steel decking hold cylindrical pipe sections and asymmetrical weldments without ratchet straps. Custom fixturing bolts into the grid for repeat production runs.

- **CE + ISO 9001, Factory Load-Tested at 125 Percent**: Every unit runs a static overload proof test at 12,500 kg and a full-cycle functional test before crating. The test certificate ships with the machine.

Step 7: Application Scenarios

3-5 scenarios. Each: Industry/Use Case + 1-sentence description of how the product fits.

Format:

- **Industry/Use Case**: Concrete description of how this product operates in that environment.

Step 8: Technical Specification Table

Translation rule: When outputting the Chinese version of the Spec Table, keep the Parameter and Unit column headers in English. The Parameter names and Unit symbols are international standards and must not be translated. Example: "Rated Load Capacity" stays in English in both versions.

Generate as a Markdown table. Format: Parameter | Value | Unit.

Rules:

• Sort rows logically: capacity/dimensions first -> performance -> materials -> electrical -> certifications
• Use consistent units throughout (metric preferred for B2B)
• Include safety and certification rows at the bottom

Step 9: FAQ

6-8 questions. 50% product questions, 50% purchase/delivery questions.

Product questions (3-4):

• Technical capability questions specific to this product type
• Safety and compliance questions
• Installation and maintenance questions

Purchase questions (3-4):

• MOQ, lead time, customization capability
• Shipping, warranty, after-sales support

Each Q&A: 2-4 sentences. Factual, no marketing fluff.

Step 10: Link Directory + Schema Markup + Quality Check

Output order: Link Directory first (human-readable bilingual table) -> blank line -> Schema Markup (JSON-LD, machine-readable) -> blank line -> Quality Check Checklist.

Link Directory

Output a bilingual table of all links used in the content:

Schema Markup

Generate JSON-LD blocks using {Brand}, {BrandFull}, {SiteURL}, {ProductName}, {ProductCategory} variables:

Product Schema:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "{ProductName}",
  "description": "[Short Description]",
  "sku": "[SKU]",
  "brand": { "@type": "Brand", "name": "{BrandFull}" },
  "category": "{ProductCategory}",
  "offers": {
    "@type": "Offer",
    "availability": "https://schema.org/InStock",
    "priceValidUntil": "[Date]"
  }
}

FAQ Schema (from Step 9).

BreadcrumbList Schema:

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "{SiteURL}/" },
    { "@type": "ListItem", "position": 2, "name": "Products", "item": "{SiteURL}/products/" },
    { "@type": "ListItem", "position": 3, "name": "{ProductName}", "item": "{SiteURL}/products/[slug]/" }
  ]
}

Quality Check Checklist

• All keywords placed per RankMath map (Step 3)
• URL slug <=75 characters, hyphen-case, primary keyword present
• Meta Title <=60 characters, primary keyword at front
• Meta Description <=160 characters
• H1 contains primary keyword
• Primary keyword in first 100 words of description
• Image file names follow keyword-descriptor.jpg format
• Image Alt text on every image with keyword context
• Spec table is MD-formatted with consistent units
• FAQ has 6-8 Q&As, balanced product/purchase split
• No AI cliche openings or exaggerated claims
• No marketing hype words (cost-effective, high ROI, best-in-class, etc.)
• No fabricated numbers -- [placeholder] used where data is unavailable
• All external links verified as active (no 404)
• Flesch Reading Ease >=60
• Content >=900 words (RankMath minimum)

• =3 internal links with descriptive anchors to related products, case studies, or blog posts

• =2 external links to authoritative sources

• English punctuation only throughout
• English -> Chinese block delivery respected
• All {Variable} placeholders resolved before final output