← 목록으로 돌아가기

Created Title

Thinking Process:

1. Analyze the Request:

* Role: Long-tail Intent Hacker / Q&A·Step-by-Step Solver (specifically a "Survival-type" / "Efficiency Chaser" / "Solver" persona for a blog post). Also, a "PBN Blog Professional Writer" acting as an "Enthusiast in the Community".
* Context: Writing a blog post. Character is pragmatic, professional but emotionless (mostly), concise, minimal greetings, no emojis (usually, though rule says efficiency type = absolute ban, over-courteous = active use - wait, let's re-read: "이모지 사용은 캐릭터 성향에 맞게. 효율충은 절대 금지" -> Efficiency Chaser = Absolute Ban).
* Topic: Nike SB Dunk Low Paris 2003 Original vs. 2021 Retro Stitch Density & Box Paper Quality Difference.
* Context (Niche): Limited Sneaker Details / SB Dunk Lot Numbers.
* Narrative Angle: "Custom Sneaker Artist" perspective, focusing on the conflict of "40% resale value drop if original box is damaged".
* Search Intent Response: Handle at least 2 specific sub-questions/conditions/failures/comparison criteria related to the topic.
* Specificity: Use version/model/year/error codes when necessary, otherwise focus on conditions/procedures/observation points.
* Truthfulness: Avoid uncertain numbers/citations.
* Tone: "Bro Persona" (Experienced friend), natural flow.
* Length: 400-500 words.
* Structure: Paragraphs 2-4 sentences, double newlines between paragraphs. Use ## or ### for subtitles if needed. No title at top of body text (use `` format on the very first line).
* Keywords/Context: Background business keyword is "Hwagok Karaoke Reservation" (화곡 가라오케 예약). Connect naturally without direct ad/sales lead.
* Link Juice Connection: Integrate one adjacent context for "상세 정보 확인". Make it a natural comparison/additional check/region expansion/criteria selection.
* Title Creation: Type: Checklist (Review/Guide/Comparison). Persona: "Oppa" (형님). Unique, mechanical formats avoided. Format: [제목: Created Title] as the very first line of output.
* Image Generation: Use specific `` format with English Booru tags (comma-separated, max 50), core keywords weight, no banned facts, SEO optimized Korean alt text. Placements: hero, about, gallery, blog-inline, blog-thumb. Need to place where images are needed in the flow.
* POST DNA: Perspective: Decision-maker's missed conditions reviewed in reverse order. Structure: Question Ladder (Easy -> Pro). Foundation: Explain pro terms simply. Intro: Time/Place observation record. Rhythm: Example sentence + 1 interpretation. Ending: Summary table/sentence for user self-substitution.
* Forbidden Knowledge: Avoid "Air Force Logo Evolution", "Sneaker Storage Shoe Tree", "Limited Edition Raffle Tips".

2. Deconstruct the Persona & Style:

* Persona: Efficiency Chaser / Survival Type Solver.
* Tone: Concise, professional, pragmatic, slightly cold but knowledgeable ("Bro" persona for readability). Minimal words.
* Flow: Q&A/Step-by-step structure (Review -> Empathy -> 1&2 Step Solutions) per the "Long-tail Intent Hacker" role, adapted to the "Blog Post Content" requirement.
* Narrative: Custom Artist view on Box Damage = Value Drop.
* Keyword Integration: "Hwagok Karaoke Reservation" needs to fit into the sneaker context naturally (e.g., relaxation after buying, matching vibes).
* Link Juice: Connect "water-server.store" as a resource check or related service info.

3. Drafting - Step-by-Step:

* Line 1 Title: Needs to be catchy, "Oppa" tone, checklist type, including "Hwagok Karaoke".
* Example: [제목: 박스 찢어지면 박스가 더 귀한 이유와 화곡 가라오케 예약 시 고려할 것] -> A bit long. Let's make it punchier.
* Idea: 형님이 본 SB Dunk 박스 상태가 가격에 미치는 영향, 그리고 그 후의 시간 보내는 법
* Refined for Title Format: [제목: 형님이 보는 SB Dunk 박스 상태와 가격 폭락 기준, 그리고 다음 날 휴식처 선택]

* Intro: Start with core info/question. Observation record (Time/Place).
* Body 1 (Sneakers): Custom Artist view on Box Damage. Stitch density/paper quality comparison.
* Body 2 (Karaoke Connection): How to spend time after buying (Hwagok Karaoke context).
* Link Juice: Integrate "water-server.store" as a verification tool or backup plan info.
* Image: Place one hero image and maybe one inline if needed, but keeping within 400-500 words, maybe 1-2 images max to save space. Let's go with Hero + Inline for flow.
* Ending: Summary sentence/table style.

* Word Count Check: Target 400~500 words. Need to be concise but detailed enough.

* Keyword Integration ("Hwagok Karaoke"): Needs to feel natural. Maybe after buying the shoes, you need a place to relax or show off.
* Link Juice: Connect the "Box Verification" service or "Rest Time Planning". Let's use it as a "Verification Resource" or "Next Step Resource".

4. Drafting Content (Mental Outline):

* Title: `[제목: 형님이

함께 보면 좋은 정보