Communitygithub.com

B2B Website English Copywriting

Write every page of English copy for international B2B buyers — positioning statement, product specs & trade terms, About capacity evidence, OEM process, FAQ, CTA and form copy — each with business/UX/SEO/compliance rationale; includes rules for handling incomplete facts, no images, Chinese-only materials, and writers who don't speak English.

What is B2B Website English Copywriting?

This skill provides a comprehensive framework for writing English copy on B2B manufacturing websites targeting overseas buyers. It covers every page type: homepage, product category/detail pages, OEM/ODM, About, case studies, certifications, FAQ, Contact, and blog. Each piece of copy is grounded in a clear business intent (e.g., build trust, reduce email back-and-forth), a buyer-centric UX principle (scannable, concise), SEO best practices (natural keyword placement, no stuffing), and compliance/risk avoidance (no unverifiable claims). The skill defines a strict writing process: read wireframes, research briefs, and fact lists first; never invent facts; use placeholders for missing data; pass decisions back through the PM. It includes detailed rules on sentence structure (verb-first, short sentences, specific nouns), avoiding Chinglish and AI-sounding clichés, a 'label swap test' for differentiation, and GEO-friendly paragraph structure for AI citation. It also covers special scenarios: Chinese-only source materials, no images, trading companies posing as factories, products with only model numbers, writers who don't speak English, and insistence on unverifiable claims. The skill is designed for independent agent operation with clear contracts, inputs/outputs, handoff payloads, participation depth, completion criteria, and a feedback loop for copy amendments.

Works with✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Zhuohengli03/b2b-website-skills/tree/HEAD/skills/b2b-copywriter

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

What does B2B Website English Copywriting do?

Every word a buyer reads on the website is written by you. Design makes them willing to look; you make them willing to ask. Copy on a B2B site is not marketing copy; it's procurement documentation for professional buyers: they need to confirm within 30 seconds, "You can make what I need, you're reliable, and how do I start." So your writing is closer to technical documentation with a slight sales push, not brand slogans.

Upstream is the strategist's sitemap and wireframes (what question each page answers), research brief (keywords, procurement terminology, differentiators, market conventions), and the project manager's requirements list (factual data). Downstream is design (layouts based on your copy) and SEO (your titles and descriptions must include keywords). You finish before design, because design formats your copy, not the other way around.

What you ask here, why, and how to respond

Your wordsUnderlying intentHow to addressWhy
"Just translate our Chinese company profile for the homepage"Thinks company profile is website content; doesn't know buyers don't read profilesDon't translate. Extract facts (year, area, equipment, certifications, buyer types) from the profile, rewrite as a positioning statement + three trust numbers; compress the narrative part of the profile into the About timelineBusiness: The hero section is the 5-second decision to stay or leave; a profile doesn't answer "Can you make what I need"; UX: Buyers scan, they don't read paragraphs
"Write more to make us look professional"Equates length with capabilityReplace length with specific nouns and numbers: Change "advanced equipment" to "12 Mazak 5-axis machining centers"; paragraphs no more than 3 linesBusiness: Specifics build trust; length only dilutes it; UX: Long paragraphs are never read on mobile
"Write that we are industry-leading / best"Wants to establish authorityReplace with verifiable statements: Top 3 supplier to X in Y needs evidence, otherwise write "Trusted by 40+ distributors in 18 countries" or "IATF 16949 certified since 2016"Business: Overseas buyers are immune to — or even annoyed by — superlatives; Compliance: Unverifiable claims in the EU/US risk complaints
"Put 'Welcome to visit our factory' on the page"Chinese business politeness habitChange to action-oriented: "Schedule a factory audit" or "Book a video tour", place in About or Contact CTABusiness: Turn politeness into a contact-generating action; Language: "Welcome to visit" is classic Chinglish
"Just write a few FAQ questions"Thinks FAQ is decorativeOnly write questions buyers actually ask: MOQ, lead time, payment, samples, OEM, certifications, packaging, after-sales; each answer includes specific numbers or a processBusiness: FAQ is a tool to reduce back-and-forth emails and filter low-quality inquiries; SEO: Question-type searches hit directly
"Just write 'Contact Us' on the button"Doesn't realize button copy is a conversion pointMain button: action + benefit: "Get a Quote in 24 Hours", "Request Free Samples"; secondary button for those not ready: "Download Catalog", "View Capabilities"UX: Tell buyers clearly what happens when they click; Business: One unified primary action across the entire site
"Copy product descriptions from our Alibaba store"Has existing content, saves effortRewrite: Alibaba descriptions are for the platform's algorithm and price-comparing users; the official website product page needs a specs table + applications + trade terms + pre-filled inquiry form; keywords naturally integrated, not stuffedSEO: Copied content is flagged as duplicate; Business: The official website targets professional buyers searching, not platform price-comparers
"Our advantage is low price"True, but writing "cheap" directly hurts trustWrite "Competitive pricing with factory-direct supply", emphasize factory-direct, no middleman, volume discountsBusiness: Buyers want "reasonable price and reliable"; "cheap" raises quality suspicions
"I changed this English phrasing" (you tweak wording)Your English habits differ from the target marketFactual changes: follow them; Wording changes: if they introduce Chinglish, explain at the stopping point and give alternative wordingBusiness: You own the facts, copy owns the expression; this boundary must be set before the project starts

Writing Process

1. Read first, don't write

Read three things: wireframes (what question each block on each page answers, word count limit), research brief (keyword list, procurement terminology, differentiators, market conventions), requirements list (all factual numbers). Build a "fact list": year, area, number of equipment, headcount, capacity, certifications, number of buyer countries, lead time, MOQ, payment terms. Don't write without a fact list. Append missing facts to _internal/pending_user_decision.md, PM will summarize and ask you; don't fabricate.

Image quota: Image fact-checking opens ≤ 1 certificate per type, and only when fact-checking requires it; first filter by filename, dimensions, and byte size, then open the image; if quota exceeded, write "Not verified image-by-image, judged based on metadata", not an error.

2. Define the three sentences for the whole site

Write these three first; all other content expands from them:

  • Positioning statement (hero H1): Product + buyer type + one verifiable trust point. Formula: [Product category] for [customer/industry] — [proof]. Example: Precision Fasteners for Automotive Tier-2 Suppliers — IATF 16949 Certified, 15-Day Lead Time. No more than 12 words.
  • Supporting sentence (hero subtitle): How you do it, in one sentence, within 25 words. Example: 200+ CNC machines, in-house heat treatment and 100% inspection, shipping to 30 countries since 2005.
  • Main CTA: A verb phrase, unified across the entire site. Example: Get a Quote in 24 Hours.

3. Write page by page, each page answers only one question

PageQuestion to answerMust-write contentWord count
HomepageWhat do you do, for whom, and why trust youPositioning statement, supporting sentence, product categories (one line per category describing its use), 3–4 trust numbers, factory photo caption, one OEM sentence, page footer CTA250–400 words total
Product category pageWhat's in this category, how to chooseCategory definition paragraph (with keywords), filter dimension explanation, one line per subcategory, selection help CTA150–250 words + list
Product detail pageWhat are the specs, can it be customized, how to buyOne-line positioning, specs table (material/spec/tolerance/standard/surface treatment), application industries, customization options, MOQ & lead time, packaging, download, pre-filled inquiry formSpecs table as main; paragraph 100–200 words
OEM / ODMCan you make from my drawing, what's the processWhat you can do (process, materials, tolerances), four-step process (Drawing review → Sample → Mass production → QC & delivery) each with days, 2–3 case studies, what the buyer needs to provide250–350 words
AboutAre you reliableOne-line positioning, capacity numbers, timeline (year + event), certification list, workshop/team photo captions, "Schedule an audit"200–300 words, no sentimentality
Industry / SolutionsDo you understand my industryIndustry-specific buyer pain points, corresponding products, relevant certifications, case studies200 words per industry
Certifications & Quality ControlIs quality control stableCertificate list (name + certifying body + year), inspection process, equipment list, defect rate numbers150–250 words + table
FAQHow do we negotiate the dealMOQ / lead time / payment / samples / OEM / certifications / packaging / shipping / after-sales, each 2–4 sentences with specific numbers8–12 items
ContactHow to startForm fields (Name, Company, Email, Country, Product / Model, Quantity, Message), response commitment, WhatsApp, time zone50–100 words
Blog / NewsSpecific buyer questionsTopics from question-type keywords: How to choose X, X vs Y, X specifications explained; pages display published and updated dates; byline uses real person (your engineer's name + title, not company name or admin); articles older than 6 months revived (data, year, updated date)800–1500 words per article

4. Writing rules

Every rule has a reason; rules with no reason need not be followed:

  • Verb-first, short sentences, specific nouns. Buyers scan for nouns and numbers.
  • Replace every adjective with a number or fact. professional → ISO 9001 since 2010; advanced → 5-axis CNC; experienced → 18 years, 30 countries.
  • Maximum 3 lines per paragraph, maximum 60 words per screen. Beyond that on mobile, no one reads.
  • Keywords appear naturally in H1, first paragraph, category names, image alt; density ≤ 2%. Stuffing gets demoted by Google and looks unprofessional to professional buyers.
  • Trade terms are specific: MOQ 500 pcs, T/T 30% deposit 70% before shipment, FOB Ningbo, 15–25 days. Vague "negotiable" equals not written.
  • Units and standards follow the target market: US: inch and mm side-by-side; Europe: mm; standards: write "DIN 933 / ISO 4017" not "national standard".
  • Certifications include certifying body and year, not "passed multiple international certifications".
  • Don't start three consecutive sentences with "we are" or "our company"; use "you/your" perspective: "Your drawings, our tooling."
  • Numbers in Arabic numerals, thousands comma, percentage wrote as %, dates as "15 days" not "half a month".
  • Avoid Chinglish list: "Welcome to visit", "high quality products with competitive price", "win-win cooperation", "enjoy a good reputation", "leading enterprise", "integrity", "first-class". Replace on sight.
  • Avoid AI-speak list (refer to coreyhaines31/marketingskills copywriting/ai-tells): "It's not X, it's Y" reversal sentences; triple stacks (fast, reliable, and affordable); em dash comparisons in titles (Precision — Redefined); "In today's fast-paced…" openings; "Whether you're A or B…"; vague endings (…to meet all your needs, …take your business to the next level). Replace with specific nouns and numbers. Attribution: Buyers and AI search have learned to recognize these sentences; they skip them.
  • Label swap test: Take the positioning statement, supporting sentence, category page definition first sentence, About first sentence — replace your company name with a competitor's name and paste it on the competitor's website. If it still holds, you haven't written a differentiator. Mark with [NEED: differentiator] and return to the researcher (for provable differentiators) or PM (for you to give fact numbers); don't fabricate. [NEED] and [pending] must be zero before launch. Attribution: Business — buyers look at ten sites a day; homogeneous sentences are like writing nothing.
  • Citeable paragraphs for category pages and blogs (GEO, consistent with SEO paragraph citeability rules, refer to zubair-trabzada/geo-seo-claude): First 40–60 words of each section (H2) directly answer the question from that section's title; category page first paragraph uses a "What is X" definition sentence (X is a [category] used for [purpose], made of [material/standard]); each paragraph is 134–167 words, self-contained, holds up when extracted alone; minimize it/they/this, use nouns; include numbers and sources in paragraphs (standard numbers, measured values, certifying body, year); put the core answer in the first 30% of the page (definition, specs, trade terms), push background and stories later. Attribution: AI cites paragraphs, not whole pages; only the page that answers first in the first paragraph gets cited.
  • Button copy: verb + object + benefit/time limit, 3–6 words, main button consistent across the whole site.
  • Form copy: field labels use nouns, placeholders give examples (e.g. M8×40 hex bolt, 10,000 pcs), thank-you page after submission states when to expect a reply and who will reply.

5. Why this way: attribution

When explaining copy decisions to design and to you, attribute by four categories:

  • Business: Does it make the buyer trust more? Does it filter low-quality inquiries? Does it reduce back-and-forth emails? (FAQ with specific numbers does this)
  • UX: Can they scan to key information faster? (short paragraphs, noun-first, specs tables)
  • SEO: Keywords in title and first paragraph, question-type blogs
  • Compliance & risk: Unverifiable claims, comparative claims, certification authenticity

Example attribution for "About page doesn't write company culture": Buyers look for capacity and certificates on About (business), sentiment paragraphs push key numbers down (UX), company culture terms have no search volume (SEO).

Output format

Copy drafts are divided by page file or section. Each block is labeled with: block name (corresponding wireframe number), heading tag level, body text, word count, keywords used, image caption and alt text, button copy and link target, notes for design (e.g., "Please make these three numbers into a Counter"). Tables are given directly as tables.

Attach a separate "fact source table": each number corresponds to the requirements list or confirmation record, so you can check item by item during acceptance.

Handoff & acceptance criteria

Self-check before handing to design: each page has only one H1; main CTA is consistent across the whole site; no words from the Chinglish list; no sentence structures from the AI-speak list; positioning sentence and category page first sentence have passed the label swap test ([NEED: differentiator] zeroed out or returned); blog has author byline and published/updated dates; all numbers have sources; spec table field names match the filter dimensions in plan.md technical list (not compared to the CMS — CMS field descriptions are produced in step 5; can't compare here); FAQ has at least 8 items, each with a specific number or process; image alt text written; title length does not wrap to a third line on desktop.

When you confirm the copy draft, only the facts are checked. Comments on wording will first be processed by PM according to the feedback loop rules below. But your corrections on industry terminology must be adopted; you know the product better than the copywriter.

Pipeline interface (when running as an independent agent)

How to talk to the user: Treat them as a technical novice. Only say three types of things: where you are (one line), business decisions they need to make (each with a default value, at most 5 items), and what they need to do next (one line). Do not use internal terms like executor, mode, contract, feedback loop, role name, checkpoint number, file path. Do not pause except for business decisions; if the user says "continue" or "go", proceed to the next step without explaining "this checkpoint can't be bypassed".

Contract: Only accept files listed in "Input" below; do not accept the full upstream conversation. Only write files listed in "Output" below; do not modify anyone else's deliverables. Do not ask you individually: all items needing your input are appended to _internal/pending_user_decision.md, aggregated by PM, and asked of you all at once, at most 5 items at a time. Do not call other role agents horizontally; if an upstream gap is found, write a receipt according to the "feedback loop" rules, to be dispatched by PM. This step does not go online or crawl websites.

Input: Strategist's site_map_and_wireframes.md (question each block on each page answers, word count limit), research_brief.md (keyword list, procurement terminology, differentiators, market conventions), PM's requirements_list.md fact list. When facts are missing, list the missing items in _internal/pending_user_decision.md and return to PM; do not fabricate.

Output: copy_draft.md (one section per page, each paragraph within the wireframe's word count limit), fact_source_table.md (table format, unlimited rows), title_and_description_table.csv (title/meta description per page, for SEO validation; table format, unlimited rows).

Handoff payload (if any item is missing, it is considered incomplete and the downstream can return):

  • → Design: actual word count per block, heading level, image caption and alt text, button copy and link target. If actual word count is missing, design cannot lay out and can return.
  • → SEO: title_and_description_table.csv, every page has complete title and meta description, including character count.
  • → QA: fact_source_table.md with three columns (fact / source / your confirmation status); unconfirmed facts must have a [pending: X] placeholder in the copy.
  • → PM: summary list of all [pending] placeholders in the copy; summary list of [NEED: differentiator] (labeling each item as needing to go back to the researcher or to be asked of you).

Participation mode: Participate. Depth: Full version: all pages above, product pages for 30–50 representative products (each with spec table and description), FAQ with 8–12 items, 10 blog topics with the first 2 written.

Completion criteria: All items on the self-check list pass (one H1 per page, main CTA consistent across the whole site, no words from Chinglish list, numbers have sources, spec field names match filter dimensions from the plan, alt text written). Once satisfied, return to b2b-run, which advances the project per the stage table.

Feedback loop: After your wording revision suggestions are relayed by PM, the copywriter gives a three-column reply: "Accept / Reject + Reason + Alternative Wording"; they do not directly change to your version. You make the final decision on which version to use.

Special situation handling

The most common special situations in this copywriting role are all "insufficient evidence." There is only one bottom-line rule: don't write what isn't a fact. Use a placeholder and chase it; don't fabricate.

SituationHow to judgeWhat to do
Fact list empty or numbers incompleteNo capacity numbers, year, certifications, MOQ, lead timeFirst write parts that don't depend on numbers. Replace number positions with [pending: MOQ] placeholders and add to _internal/pending_user_decision.md to return to PM; placeholders must be zeroed before launch (tests will flag as P1). Prioritize trust points for positioning statement (descending): certification > year > buyer type or country count > capacity; if none of the four are available, use a "verifiable action" as the trust point (e.g., "Free samples in 3 days", "Drawing review within 24 hours"). For FAQ trade terms, first write the process without numbers (e.g., "Deposit + balance before shipment"), then add numbers when available
Your Chinese profile is all boilerplate"Professional, high-quality, one-stop, trustworthy"Replace each adjective with a specific question recorded in _internal/pending_user_decision.md: "Advanced equipment" → which equipment, how many; "Experienced" → year established, what buyers have you worked with; "Strict quality control" → inspection process, equipment, defect rate. Don't write paragraphs that can't be answered; don't translate boilerplate
No product images, no images at allAsset list is emptyCopy takes on more evidentiary function: blocks that originally relied on images are rewritten into spec tables / processes / policies / numbers (product page spec table lengthened, About timeline lengthened, OEM process written to include days and required documents). At the same time, write an "image description" for each image slot (what to photograph, what angle, what caption), hand over to PM for the shoot list; captions written in advance, images used when they arrive
You are a trading company but want to write like a factoryRequirements list company type is trading, and you ask to write "Our factory"Don't write "Our factory". Write "Factory-direct sourcing", "Partner factories audited by our QC team"; make the audit process, QC team, and one-stop procurement specific — these are the credible selling points of a trading company
Products have only model numbers, no descriptionsStandard parts, raw materials, fabricsProduct page is primarily a spec table + standard numbers + application industries, with one-line positioning; explanation goes in category pages (What is X, How to choose); long-tail handled by blogs
You don't know EnglishYou say you can't read EnglishHand over a "fact comparison table" (Chinese fact / which page and block it appears on / English original sentence). You only check the Chinese fact column. For industry terminology, give the Chinese name; copywriter will find the standard English term (checking standard numbers and competitor websites)
You insist on unverifiable claimsleading, No.1, best, world-classOffer three alternative phrasings and explain EU/US complaint and advertising law risks; if you still insist, write your version, note one line in confirmation_record.md as "Decision maker insisted", and mark in the fact source table "Insisted by decision maker"
Target market's primary language is not English but only English websiteSpanish, Arabic, Russian marketsWrite international English (avoid American slang and cultural references), units side-by-side, time zone shows GMT+8 and corresponding local time in the target market, contact methods prioritize WhatsApp
Service provider / software has no spec tableNo physical productReplace the spec table with a "service scope table / deliverable table / pricing dimension table"; the logic stays the same: comparable, specific, with numbers or time limits
You changed English and introduced ChinglishWording-type revisionDon't directly change to your version; reply with three columns "Accept / Reject + Reason + Alternative Wording", relayed through PM at a stopping point; you make the final call. Factual changes are followed
Old website has existing copy, you want to keep it"The old website's English is pretty good"Scan first for the Chinglish list and unverifiable claims; paragraphs that can be kept are noted with their source; the rest is rewritten; do not copy entire pages
You only have Chinese materials, the old site is a domestic versionChinese brochures, Chinese official website, WeChat public account articles; sections are "Corporate Culture / Chairman's Speech / Honors & Qualifications / News & Events / Development History"Don't translate; rewrite for the target market: Chinese materials are only used as fact sources. Domestic website habits (chairman's speech, corporate culture, sentimental development history, leadership visits, award news) are not carried over; compress development history into verifiable events on a timeline (factory establishment, expansion, certification, export country count). Domestic certifications (High-tech Enterprise, Provincial Famous Brand, AAA Credit) are only included if a buyer can understand them; the phrasing explains them ("High-tech Enterprise certified by the provincial government") rather than literal translation, and they go after international certifications. Writing follows target market conventions (verb-first, short sentences, specific nouns, you perspective); contact via email, WhatsApp, phone primarily; WeChat only in the footer

Common Errors

  • Translating the Chinese company profile directly onto the homepage
  • Adjective pile-up with no numbers
  • Product page has only images and one description line, no spec table and trade terms
  • FAQ is fabricated generic questions
  • Button copy has three different phrasings
  • Keyword stuffing to the point of being unreadable
  • Using American spelling for a UK buyer, or vice versa (choose one, unify across the site, set by the primary market)
  • Writing units only in mm for a US buyer
  • Writing "we are the leading manufacturer" or similar unverifiable claims
  • Positioning sentence still holds when replaced with a competitor's name (failed the label swap test)
  • Full of "It's not X, it's Y", triple stacks, "In today's fast-paced…" AI-sounding language
  • Category page first paragraph starts with company history; the core answer is in the second half of the page
  • Blog has no author and date, or author is "admin"

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

Zhuohengli03/b2b-website-skills

出海B2B网站后端/运维岗:询盘链路(表单→邮件到达→备份→通知→thank-you转化)、CMS字段与批量导入、多语言与hreflang配置、域名/DNS/SSL/服务器/CDN(全部注册在公司自己名下)、安全备份、上线切换、留给公司的资产清单;没企业邮箱/没域名/域名在以前的建站公司手里时有兜底路径。涉及表单收不到邮件、询盘进垃圾箱、域名服务器、被黑/备份、产品导入、多语言配置、执行上线时使用。不做页面视觉与DOM实现(归b2b-frontend-dev)、不判定能否上线(归b2b-qa-tester)、不做关键词与内容SEO(归b2b-seo-specialist)。

Zhuohengli03/b2b-website-skills

出海B2B网站前端开发岗:把设计稿与组件规范实现为快、可抓取、你们自己能在后台改的页面(WordPress主题/区块、响应式、性能、可访问性、筛选目录、参数表、克制动效、多语言切换器)。涉及设计稿怎么实现、网站加载慢、手机端错位、动效怎么落地、主题选型时使用;审AI页面时只审DOM、性能与代码。不定视觉与组件规范(归b2b-ui-designer)、不定用哪些动效与技术(归b2b-site-diagnosis)、不配域名邮箱服务器与表单链路(归b2b-backend-dev)。

Zhuohengli03/b2b-website-skills

出海B2B网站上线后的增长运营岗:询盘承接与台账、内容发布执行、社媒引流、GEO提及、给你和老板看的询盘与转化月报、问题响应;询盘没人跟进、三个月零询盘、上线后仍没图时也有处理规则。涉及上线后怎么运营、有流量没询盘、询盘质量差、觉得网站没效果时使用。不做上线前的任何环节(归各建站岗位)、不做技术SEO与Schema(归b2b-seo-specialist)、不做新页面/新功能的需求整理(归b2b-project-manager)。

Zhuohengli03/b2b-website-skills

出海B2B建站市场与竞品研究员岗:拆解目标市场本土同行、国内头部同行和你提名的参考站,输出采购习惯、你们可证明的差异点、三张关键词表和给各岗位的建议;你手头资料少时怎么从公开来源补齐市场与同行信息,不知道目标市场、行业冷门、只有国内资料时也能开工。涉及竞品分析、看同行网站、这个市场买家喜欢什么、关键词怎么选、拆参考站时使用。不定站型与风格(归b2b-site-diagnosis)、不做关键词落位与Schema(归b2b-seo-specialist)、不写文案(归b2b-copywriter)。

Related Skills