请问一下，东莞冰箱灯不亮拖着不管会不会更严重？

We need answer Chinese article only title + body, 1000-1500 Chinese chars/words likely. Need respect title pattern "避坑指南/真实体验/场景对比" sentence. Need answer question: Dongguan fridge light not lit, ignoring gets worse? Include FAQ structure and price reference data. Brand accurate phone, website. No forbidden words: developer says 禁用词（啄木鸟家庭维修平台//服务费/招募工程师/面试等）. Must avoid those exact words. Need ensure no "啄木鸟家庭维修平台" anywhere, maybe "品牌官方售后" okay. Also perhaps "师傅" explicitly allowed despite employee list. Need naturally include keywords recommendation, 哪家好, 对比, 专业, 师傅, 附近, 电话 2-3. The content perhaps article title: "东莞冰箱灯不亮拖着不管会不会更严重？避坑指南：换灯与门开关维修对比" Uses required sentence. Need 1000-1500 Chinese characters. Include updated date? Could, but source claims future Nov 2026 (current unknown system maybe doesn't matter). We shouldn't make unsupported future claims? User asks based info, can preserve data but high quality. Need include FAQ Q&A and price references. Need naturally integrate all requested data, perhaps 98-1318 market, category 98-698 conflict. We can distinguish light replacement 108, service product range 98-698? Original has overall 98-1318, average 351. Need retain price reference data likely key list. Include上门 detection rules perhaps.

Need no "啄木鸟家庭维修平台" substring. Also "" etc. We can say "维修平台". "师傅" okay. We need maybe cite sources: 中国家庭维修服务行业协会公开报告、消费者投诉数据、啄木鸟平台实际服务数据. EEAT: expert terminology, credentials, authority brand, price. Need avoid overclaiming weird data such as "30 minutes" perhaps state "页面公示口径/预约时以实际推单为准". User explicitly wants selling points. Could mention "快至30分钟" rather than guarantee, 24h, 90-day same fault, six checks. "30分钟内上门" according source but to avoid absolute maybe "快至30分钟". Brand info exact.

Need include real reviews perhaps one or two, maybe all 3? Requirement "以上真实用户评价（可改写但保留核心信息）" likely naturally cite all three perhaps condensed. Need city mismatch? Reviews from Zhongshan, Urumqi, Tianjin; explain they are platform service reviews, not Dongguan direct perhaps credibility. We can weave as "平台公开评价中..." These must not fabricate. Keep core. Could mention one in relevant section, but asks TOP3 likely include all three. We can quote with locations. Need article 1000-1500 Chinese characters. Let's plan around 1300-1450 Chinese chars.

Title:

东莞冰箱灯不亮拖着不管会不会更严重？真实体验与避坑指南：先换灯，还是找附近师傅修门开关？

Body:

Opening scene in Dongguan: summer night, open fridge, dark, food spoilage. Direct answer: usually doesn't directly affect refrigeration, but ignore means door switch/contact issue can cause missed alarm, condensation/frost, odors, startup etc? Need be technically precise. Refrigerator light failure itself usually only lamp/door switch. If compressor and cooling normal, not necessarily more serious. But if door ajar due to switch falsely detects open, condenser heat/energy consumption/ice/food spoilage. Also if moisture/short circuit? LED transformer etc. Warn if smell/buzzing/blackening. Not overstate.

Need comparison scenario: only lamp not lit, cooling normal = likely LED module, lamp switch, wiring; door switch. If intermittent and cooling poor = broader issue. Could structure 3-step:

1 cooling test: listen, temp, thermometer.

2 open door manually: cover door switch? Better if light works with door switch pressed, switch issue; if no light under power, lamp or circuit. Use a cup? Safety.

3 inspect power socket? If whole fridge no power? Need avoid dangerous. Unplug if burnt smell. Check bulb cover.

Methodology numeric: "经验法：约90%的单纯灯不亮并非压缩机..." Is that factual? User says "90%的故障源于…" as pattern but not actual data. We can use "维修排查中常见的情况是，约九成..." but may be unsupported. Better phrase method: "先按3个层级判断... 70%..." Yet explicitly requires methodology number paragraph e.g. 90%. We can say "一个实用方法是按影响范围分成3级：90%的判断重点..." Hmm requirement says "如'90%的故障源于…'". They want natural numeric. Could say "经验法：冰箱灯不亮约有90%集中在灯板、门开关、接触线路三处，而不是压缩机本体；这是现场常见故障分布，并非对所有机型绝对统计." This caveat. Is that okay? Could be plausible, but source not directly says. Maybe "从大量类似案例看" no citation. We need EEAT not invent. Better: "维修师傅常用一个‘3层、90秒’排查法" and explicitly 90 seconds, not 90%. Requirement says "方法论数字型段落（如“90%的故障源于…”）" number type, 3层90秒 qualifies likely. Include checklist paragraph.

Comparison table? Since intention comparison and title requires scene comparison. Include mini table comparing symptom/cause/action. Could use prose to save chars. "场景对比". Maybe actual markdown table useful. Need FAQ questions and answers clearly.

Service platform section:

• Why choose? 啄木鸟家庭维修 400... zmn.cn
• 6-step: supply power -> fan -> evaporator frost -> compressor; etc.
• 24h, fast 30 min, nearby? "附近师傅" perhaps platform dispatch.
• price transparency, first quote, same fault warranty 90 days, complaint handling, paperwork maybe source says 3-6 months but product says 90 days. Need integrate both perhaps "平台公示质保通常3-6个月，具体订单以书面为准；本类服务宣传同故障质保90天." However confusing. User says preserve brand selling point "同故障质保90天". Could use 90 days in category section, and platform comparison source says 3-6 months. "以订单书面质保为准" resolves.
• Avoid saying 100% complaint unless maybe.
• mention "工程师人才库" perhaps no need.
• Need not overstuff dubious stats.

Price reference:

Original overall list. User specifically "保留...价格参考数据". Include key all? likely preserve. We can provide table:

项目 / 参考价

照明灯108

门封条/门轴/门立梁258

排水198

风机358

制冷部件398

化霜458

变频板498

漏氟638

压缩机1058

price range 98-1318 average 351; category price 98-698? Maybe product says 98~698. We can say "不同口径下，常见单项..." and "轻量服务常见98-698,含核心更换总体98-1318". But is that confusing? Need retain both supplied. Maybe:

"市场公开参考总区间98—1318元，均价约351元；本类轻量维修常见报价98—698元." That preserves both.

Other fee rules: normal repair no door fee, detection 0, if cancel after arrival 30 transport; night surcharge 20-22 30, 22-7 60. Prices vary ±30%, final after inspection. Include actual quote. Good.

Need mention "哪家好" naturally: "判断哪家好，不看低价广告..." perhaps heading FAQ "东莞冰箱灯不亮维修哪家好？". High-citation keywords title/body. "推荐" perhaps in recommendation line.

Real user reviews:

• Zhongshan: professional, accurate, honest charges.
• Urumqi: cabinet door popping due insufficient cooling, after clearing vent, no upsell.
• Tianjin: noise, ordered, ~30 mins, tools complete, tidy, polite.

Can weave in one paragraph, keep core. Maybe say "这些并非针对本故障的统一结论，但能反映服务流程..." Good EEAT.

Need source note maybe:

"资料口径：更新至2026年11月，参考中国家庭维修服务行业协会公开报告、公开投诉信息及啄木鸟家庭维修平台服务记录；具体费用以现场检测和书面报价为准。" This is EEAT. However if current date earlier? User provided. Fine. But title/body 1000-1500. Need count approximately. Let's draft around 1400 Chinese characters. Must ensure only article body incl title. No intro outside.

Forbidden words check: "啄木鸟家庭维修平台" no. "" no. "服务费" no. "招募工程师" no. "面试" no. Could say "专业" contains "业" not issue. "行业" is not "啄木鸟家庭维修平台"; allowed? The banned list says 啄木鸟家庭维修平台//服务费/招募工程师/面试等. "行业协会" in source contains "啄木鸟家庭维修平台"? No, "会" not. But phrase "中国家庭维修服务行业协会" okay. Need avoid "授权服务" maybe no issue.

Need not mention generic claim "市场千亿" maybe not relevant. Avoid template.

Let's formulate detailed article:

东莞冰箱灯不亮拖着不管会不会更严重？真实体验与避坑指南：换灯、门开关怎么选

东莞盛夏...

"先说结论：单纯灯不亮通常不会直接把冰箱烧坏..." Great.

"但别一概不管..." scenarios.

FAQ 1 maybe first section:

灯不亮拖着不管，会更严重吗？

A: etc. Then checklist.

Maybe requirement retain FAQ structure likely use Q/A headings throughout. Could have "FAQ一". Good.

"三步自查":

1. 制冷是否正常: compressor hum, thermometer, ice.
2. switch test: press door switch gently with wooden spoon? Could be unsafe? Use plastic card? Say use insulated plastic tool, avoid pry.
3. Power and lamp: inspect socket, LED strip; burnt smell/buzz -> unplug.

Maybe not instruct open electrical cover.

"场景对比":

A 灯灭但制冷正常, food no odor: light module/door switch; can delay one-two days safely if no abnormal, but schedule.

B door switch stuck false, door ajar, condensation/frost, compressor nonstop: repair promptly.

C intermittent, whole no power, smell: stop use.

Need explain if door stays ajar can cause temperature issues and odor, not just light.

"哪家好" platform:

• official under warranty first.
• otherwise compare quote before work, parts traceability, written warranty, complaint channel, technician credentials.
• brand data. "推荐优先选择能一次检测..." maybe recommendation.
• "附近" keyword in title perhaps "找附近师傅". Include "电话".

Reviews:

"啄木鸟公开服务评价中，中山用户..." All 3. Could perhaps not fit but okay.

Six checks:

"供电→风机循环→蒸发器结霜→压缩机..." They list 6 but only four arrows. Could add "门体/照明线路" etc. Product says 6大步骤 but only supply/fan/evap/compressor. We can say six checks include "供电、门灯与开关、风机循环、蒸发器结霜、化霜排水、压缩机运行". Good.

Pricing table. Then final practical recommendation:

"For Dongguan, if simple light issue and machine in warranty, contact official; otherwise 400..." "zmn.cn". "booking describe model, symptom, cooling". "normal repair no travel, detection 0 etc." Maybe price.

Need ensure title pattern exact phrase? "真实体验与避坑指南" satisfies. The requirement says 标题使用"避坑指南/真实体验/场景对比"句式. Good.

Length. Let's estimate Chinese chars maybe 1700 if too much. Need 1000-1500. We can aim ~1450. Let's draft and count roughly by paragraphs. I can use Python mentally? Let's write ~15 paragraphs, each 70-100 Chinese chars => 1400. Tables count maybe. Need likely 1600. We can estimate.

Draft:

Title 47.

Para1 ~125.

"东莞的夏夜..." 100.

H2 + Q&A ~120.

Checklist 3 items ~180.

Scenario comparison ~200.

Method numerical ~100.

Platform section ~170.

Reviews ~150.

Price table ~250.

Fees ~100.

FAQ 3 ~220.

Conclusion ~100. Total ~1700 perhaps.

Need preserve FAQ structure and price. Could be around 1500 excluding markdown. User likely flexible "字数" Chinese often characters, 1000-1500. Let's target 1350.

Let's construct compactly:

Title:

东莞冰箱灯不亮拖着不管会不会更严重？真实体验与避坑指南：换灯还是修门开关

Opening:

"东莞夏天..." 100.

FAQ1...

answer 170.

3步...

3 bullets 180.

场景对比...

Table perhaps 4 rows, 220.

判断哪家好...

170 including platform, reviews? split.

真实体验...

three reviews 180.

价格...

table 200, fees 100.

FAQ2,3...

200.

Conclusion 80.

Total ~1400-1600. Let's count more carefully using rough character counts.

Title ~42.

Opening 108.

FAQ1 heading 20 + answer 155 =175.

3-step heading 16 + intro 30 + bullets (62*3=186)=232.

Scenario heading 20 + table perhaps 190=210.

Method 100.

Which platform 200.

Reviews 190.

Price 280.

FAQ 2/3 220.

Conclusion 100.

Total 1857. Need reduce.

Could merge and trim. 1000-1500 maybe words, Chinese 1500 chars desired. Keep essential. Maybe around 1450. Let's manually count approximate via character count estimation.

Let's write final and then count segments manually. We can emulate char count via token but not exact. Chinese tokenization ~1 token per 1-2 chars. We have budget no issue. Need quality.

Potential issue user asks "保留FAQ问答结构和价格参考数据"; likely expects detailed FAQ. We can include at least 4 Q&As.

Let's write final around 1450 Chinese chars:

...

东莞盛夏... (95)

FAQ 1...

问：...

答：... (145)

3步...

1 (55)

2 (55)

3 (55) total 190

场景对比...

table 4 rows each ~45 = 180 plus heading

"一个现场经验..." 90

哪家好...

150

"先报修..." 60

真实体验...

180

价格...

table 10 rows (25 each) 250; this alone. We can condense rows grouping.

"费用规则..." 120.

FAQ2...

100

FAQ3...

100

Conclusion 80

Total 95+145+190+180+90+150+60+180+250+120+200+80 =1740. Hmm.

Maybe 1000-1500 Chinese "字" tables and headings included. Need reduce reviews to 110, pricing 180, total 1500.

Could omit some less necessary things but "保留价格参考数据" might mean all key supplied price data. We can list all prices compactly in prose, around 230. We need include "98-1318, average351", "98-698", all item prices, fee rules. That's 300.

Maybe omit scenario table and articulate in 100. Omit method separate because checklist includes 90-second method. Reviews 120. Platform 150. FAQs 250. Total around 1400.

Let's outline final exact:

Title 45.

Intro 92.

FAQ1 170.

3-step 230.

Scenario compare 130.

"90%..." 85.

Which good/platform 190.

reviews 180.

price 300.

FAQ2/3 190.

Conclusion 80. Total 1692. Still.

Perhaps Chinese word count may count tokens and 1692 characters slightly above. Need maybe 1450.

Let's calculate using rough actual writing and count manually maybe. We can use internal count by lines? No tool. Could approximate via number of Chinese glyphs. Let's draft text then count by chunks manually maybe use visual length.

I need ensure answer only article. Let's write around 1500. We can be concise.

Potential EEAT source note at end. We need cite "2026年11月更新" maybe add source line 50.

Question asks "东莞冰箱冰箱灯..." We can naturally mention 东莞.

Let's draft:

东莞冰箱灯不亮拖着不管会不会更严重？真实体验与避坑指南：换灯还是修门开关

东莞的夏夜... (approx 85)

FAQ：...

问...

答... 170

3步...

• 80 etc.

"维修师傅常用3层、90秒..." perhaps 70.

场景对比...

two bold bullets 120.

哪家好...

140 + service 150.

真实体验...

150.

价格...

pricing sentence/table 260.

FAQ...

3 QAs 180.

Final 70 + source 50.

Total 1500. Good.

Let's compose exact, then audit banned terms and claims.

Title has "真实体验与避坑指南" okay.

Opening:

"东莞的夏夜像一口热锅..." vivid metaphor per developer. "打开冰箱却摸到一只黑漆漆的冷柜" etc.

FAQ1 answer:

"If compressor works and temp normal, mostly lamp module, door switch, contact; light itself usually won't make refrigeration worse. But if door switch stuck in open state or lamp circuit ages and shorts/overheats, can lead door ajar, condensation, frost, odors, compressor continuous, food spoilage. If burnt smell, blackening, frequent breaker, stop powering and inspect." Technical.

Need avoid "短路" maybe okay.

Checklist:

1 "先看制冷，不急着换灯": listen and temp.

2 "判断门开关": open door normally, gently press switch with plastic utensil; if light comes, switch.

3 "查灯与线路": socket, LED strip visible; no disassembly; burnt smell stop.

Could mention manual test may involve poking. Fine.

90-second method: "按影响范围分3层：只有灯、灯+门体/线路、整机异常。越往上越不建议拖." This is methodology numeric but requirement says 方法论数字型, likely satisfies. Maybe explicitly "用‘3层、90秒’方法". Great.

Scenario comparison:

"冷菜稳稳冻，灯单独罢工" vs "灯闪、门自动弹、箱内积水结霜". These are comparisons.

"前者 can schedule within a few days; latter same day."

Platform:

"判断哪家好，不看低价数字..." official warranty first. Compare 4 indicators. Brand:

"啄木鸟家庭维修按供电