pSEO数据库用两个YAML文件(产品维度+场景维度)+一个组合映射文件(过滤无意义组合)。场景YAML需包含:场景描述、主要挑战、关键技术要求、相关行业标准、推荐产品列表。用AI辅助填写每个场景的技术细节,比手工快10倍。
数据库设计:品类 × 场景的组合矩阵构建
pSEO 的质量上限由数据质量决定。数据越细致,生成的页面越有价值;数据越通用,生成的内容就只是换了关键词的复读机。
文件结构
src/data/
├── products.yaml # 产品品类维度
├── applications.yaml # 应用场景维度
├── combinations.yaml # 有效组合列表(过滤无意义组合)
└── certifications.yaml # 认证标准数据(可选)
products.yaml:产品维度
# src/data/products.yaml
- id: centrifugal
name: "Centrifugal Pump"
namePlural: "Centrifugal Pumps"
slug: "centrifugal-pump"
pillarSlug: "/products/centrifugal-pumps/"
shortDescription: "Single-stage end-suction design for high-flow, low-to-medium viscosity applications"
keyAdvantages:
- "High flow rate capability (up to 500 m³/h)"
- "Simple construction with fewer wear parts"
- "Wide material options (CI, SS316, Duplex Steel)"
notSuitableFor:
- "High-viscosity media (>500 cP)"
- "Precise metering requirements"
- "Very high pressure (>40 bar)"
- id: magnetic_drive
name: "Magnetic Drive Pump"
namePlural: "Magnetic Drive Pumps"
slug: "magnetic-drive-pump"
pillarSlug: "/products/magnetic-drive-pumps/"
shortDescription: "Sealless design eliminates shaft seal leakage for toxic and volatile media"
keyAdvantages:
- "Zero leakage by design (no mechanical seal)"
- "Ideal for toxic, flammable or precious chemicals"
- "Low maintenance (no seal replacement)"
notSuitableFor:
- "Abrasive slurries (bearing wear)"
- "Very high temperature (>200°C standard)"
- id: gear
name: "Gear Pump"
namePlural: "Gear Pumps"
slug: "gear-pump"
pillarSlug: "/products/gear-pumps/"
shortDescription: "Positive displacement pump for precise metering of high-viscosity fluids"
keyAdvantages:
- "Handles high viscosity fluids (up to 100,000 cP)"
- "Precise, consistent flow rate"
- "Self-priming capability"
notSuitableFor:
- "Abrasive particles"
- "Very large flow rates (>50 m³/h typically)"
applications.yaml:场景维度
这是数据质量最关键的地方。每个场景需要足够的技术细节,才能让生成的页面有实质性内容。
# src/data/applications.yaml
- id: chemical_transfer
name: "Chemical Transfer"
nameFull: "Industrial Chemical Transfer"
slug: "chemical-transfer"
industry: "Chemical Processing"
shortDescription: "Transfer of acids, alkalis, solvents and other process chemicals"
challenges:
- "Corrosion resistance to media with pH 1–13"
- "Seal integrity for hazardous chemical containment"
- "Material compatibility with specific chemicals"
- "ATEX compliance for explosive atmosphere zones"
keySelectionCriteria:
- parameter: "Casing Material"
recommendation: "SS316, Hastelloy C-276, or PVDF depending on chemical"
- parameter: "Seal Type"
recommendation: "Mechanical seal (standard) or magnetic drive (zero leakage)"
- parameter: "Temperature Rating"
recommendation: "Up to 120°C standard; 180°C for high-temp version"
- parameter: "Certification"
recommendation: "CE + ATEX (Zone 1/2) for hazardous areas"
industryStandards:
- "API 685 (sealless pumps)"
- "NACE MR0175 (sour service material selection)"
- "ATEX Directive 2014/34/EU"
compatibleProducts:
- centrifugal
- magnetic_drive
incompatibleProducts:
- gear # 通常不用于化工,齿轮泵更适合高黏度
- id: water_treatment
name: "Water Treatment"
nameFull: "Municipal and Industrial Water Treatment"
slug: "water-treatment"
industry: "Water & Wastewater"
shortDescription: "Clean water circulation, chemical dosing, and wastewater transfer"
challenges:
- "Large flow rates with low head requirements"
- "Energy efficiency for 24/7 operation"
- "Corrosion resistance to chlorinated water"
- "Low maintenance for remote installations"
keySelectionCriteria:
- parameter: "Flow Rate"
recommendation: "50–500 m³/h typical for municipal plants"
- parameter: "Material"
recommendation: "Cast iron (standard water) or SS316 (chlorinated)"
- parameter: "Efficiency"
recommendation: "IE3 motor minimum; IE4/IE5 for energy savings"
industryStandards:
- "NSF/ANSI 61 (drinking water contact materials)"
- "ISO 9906 (pump hydraulic performance testing)"
- "EN 733 / ISO 2858 (dimensional standards)"
compatibleProducts:
- centrifugal
- submersible
incompatibleProducts:
- gear
- id: food_processing
name: "Food Processing"
nameFull: "Food and Beverage Processing"
slug: "food-processing"
industry: "Food & Beverage"
shortDescription: "Hygienic transfer of food products, beverages, and cleaning solutions"
challenges:
- "Hygienic design (no dead zones, fully drainable)"
- "FDA/EU food contact material compliance"
- "CIP (Clean-in-Place) compatibility"
- "Gentle handling of shear-sensitive products"
keySelectionCriteria:
- parameter: "Material"
recommendation: "SS316L with Ra ≤ 0.8 μm surface finish"
- parameter: "Seal"
recommendation: "FDA-approved EPDM or PTFE seal materials"
- parameter: "Design"
recommendation: "EHEDG or 3-A Sanitary Standards certified"
industryStandards:
- "3-A Sanitary Standards"
- "EHEDG (European Hygienic Engineering)"
- "FDA 21 CFR (food contact materials)"
- "EU Regulation 1935/2004"
compatibleProducts:
- centrifugal
- gear
incompatibleProducts:
- submersible
combinations.yaml:过滤无效组合
不是每个“产品 × 场景”的组合都有意义。这个文件明确声明哪些组合值得生成页面:
# src/data/combinations.yaml
# 格式:productId + applicationId → 是否生成页面
- product: centrifugal
application: chemical_transfer
generate: true
priority: 5 # 高优先级,先生成
- product: centrifugal
application: water_treatment
generate: true
priority: 5
- product: centrifugal
application: food_processing
generate: true
priority: 4
- product: magnetic_drive
application: chemical_transfer
generate: true
priority: 5
- product: gear
application: food_processing
generate: true
priority: 4
# 不生成的组合
- product: gear
application: water_treatment
generate: false # 齿轮泵不用于水处理,跳过
在 Astro 的 getStaticPaths() 里读取这个文件,只为 generate: true 的组合生成页面。
用 AI 批量填写场景数据
填写 applications.yaml 的技术细节是工作量最大的部分。用 AI 加速:
我在建一个工业泵制造商的 B2B 外贸站,使用 pSEO 批量生成应用场景页面。
请为以下应用场景填写 YAML 数据(符合工业泵行业的真实技术信息):
应用场景:Oil & Gas Upstream Production(油气上游开采)
需要填写以下字段:
- shortDescription(1句话描述该场景的泵应用)
- challenges(3–5个主要技术挑战,工程视角)
- keySelectionCriteria(3–4个选型参数,含具体推荐值)
- industryStandards(2–4个相关行业标准,如 API、ISO)
要求:信息必须准确,使用行业标准术语,不要泛泛而谈。
用这个提示词,1分钟可以填写一个场景的完整数据。20个场景也只需要20分钟——而不是手工研究每个场景的2–4小时。
→ 用 AI 批量生成应用选型 Cluster 页(完整流程)
RELATED / 相关推荐
接着读这些
按同一分类、系列与标签为你挑选。
从供应商资料到网站产品页:这条链上的顺序为什么不能换
从供应商发来一份 PDF 到产品页上线,中间有五个环节,顺序不能换。跳过关键词登记这一步,新页面会和自己站上已有页面抢同一个词;把核对挪到最后,审核必然退化成走过场。这篇逐段讲清每个"为什么必须是这个顺序"。
Pillar 与产品页开发:基于注册表意图的页面结构实现
把注册表字段转化为真实的 Astro 页面——这篇讲 Pillar 页和 SKU/Application/Resource 三种 Cluster 页的代码层实现:内容集合(Content Collections)配置、模板组件结构、注册表字段如何映射到 HTML 元素,以及 SEO 关键点的代码实现。
事实与表达分离:为什么产品资料要单独存一层
改一个参数要翻好几个页面,根源是事实和表达混在一起了。这篇讲怎么把"型号存在吗、参数多少、谁能供"这类事实单独存成一层,让页面、报价单、询盘回复全部从它派生——以及一个能立刻看清你有没有真的建立事实源的判断标准。