contact-page-generator

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Pages: Contact

页面:联系我们页

Guides contact page design and form optimization for conversions.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
为提升转化率提供联系页面设计与表单优化指导。
调用规则首次使用时,如果对用户有帮助,可以先用1-2句话介绍本技能覆盖的范围及其重要性,再提供核心输出内容。后续使用或用户要求跳过介绍时,直接提供核心输出即可。

Initial Assessment

初步评估

Check for product marketing context first: If
.claude/product-marketing-context.md
or
.cursor/product-marketing-context.md
exists, read it for brand voice.
Identify:
  1. Contact types: Sales, support, general, press
  2. Form purpose: Lead capture, support ticket, demo request
  3. Alternative channels: Email, phone, chat, social
首先确认产品营销上下文:如果存在
.claude/product-marketing-context.md
.cursor/product-marketing-context.md
文件,读取文件内容确认品牌调性。
识别以下信息:
  1. 联系类型:销售、支持、通用、媒体问询
  2. 表单用途:获客线索收集、支持工单提交、演示申请
  3. 可选联系渠道:邮箱、电话、在线聊天、社交媒体

Best Practices

最佳实践

Form Design

表单设计

PrincipleGuideline
Short3-5 fields for basic contact; long forms increase abandonment
Single columnVertical layout; works better on mobile
Logical groupingName+email together; address fields together
Required fieldsMark clearly (asterisk); avoid surprises
Progressive disclosureShow relevant fields based on selections
设计原则指导规范
简洁基础联系表单仅保留3-5个字段;长表单会提升用户放弃率
单栏布局垂直布局更适合移动端展示
逻辑分组姓名+邮箱为一组;地址相关字段为一组
必填字段清晰标记(星号);避免用户填写时出现意料之外的要求
渐进式展示根据用户的选择展示对应相关字段

Field Labels

字段标签

  • Clear language: "Email Address" not "Email ID"
  • Conversational: Friendly, welcoming
  • No jargon: Universally understood terms
  • 表述清晰:使用“电子邮箱地址”而非“邮箱ID”
  • 口语化:语气友好、有亲和力
  • 无专业术语:使用所有人都能理解的通用表述

CTA Button

CTA按钮

  • Action verbs: "Send Message," "Get in Touch," "Start a Conversation"
  • Avoid generic: "Submit" ? "Send Message"
  • Stand out: Contrasting color, clear hierarchy
  • 使用动作动词:比如“发送消息”、“取得联系”、“开启对话”
  • 避免通用表述:不要用“提交”,优先用“发送消息”
  • 突出展示:使用对比色,层级清晰

Page-Level

页面层级规范

ElementGuideline
Visibility"Contact" or "Support" in main nav, not just footer
MobileAppropriate input types (tel for phone), large tap targets
ProofreadingNo typos--credibility at conversion moment
AlternativesEmail, phone, chat if form isn't right
页面元素指导规范
可见性主导航栏要设置“联系我们”或“支持”入口,不要仅放在页脚
移动端适配使用合适的输入类型(比如手机号用tel类型),点击区域足够大
内容校对没有拼写错误——转化环节的内容直接影响用户信任度
替代联系方式如果表单无法满足需求,提供邮箱、电话、在线聊天等其他方式

Trust

信任背书

  • Response time: "We reply within 24 hours"
  • Privacy: Link to privacy policy near form
  • Security: HTTPS, visible trust signals
  • 响应时效说明:比如“我们会在24小时内回复”
  • 隐私说明:表单附近放置隐私政策链接
  • 安全保障:使用HTTPS,展示可见的信任标识

Output Format

输出格式

  • Form structure (fields, order)
  • Copy (labels, placeholder, CTA)
  • Page layout and placement
  • SEO metadata
  • Accessibility checklist
  • 表单结构(字段、排列顺序)
  • 文案(标签、占位符、CTA文案)
  • 页面布局与入口位置
  • SEO元数据
  • 可访问性检查清单

Related Skills

相关技能

  • landing-page-generator: Lead capture LP contains contact form; demo request CTA destination
  • about-page-generator: Contact often linked from About
  • legal-page-generator: Privacy policy link near form
  • title-tag, meta-description, page-metadata: Contact page metadata
  • landing-page-generator:线索收集落地页包含联系表单,是演示申请CTA的跳转目标
  • about-page-generator:关于我们页通常会放置联系我们入口
  • legal-page-generator:表单附近需要放置隐私政策链接
  • title-tag, meta-description, page-metadata:联系页面元数据相关技能