Crypto-Tax-Id Trends in Indonesia

- Write a blog post about "crypto-tax-id" for an Indonesia audience - Strict format requirements (Markdown, convertible to HTML) - Specific structure: H1, TL;DR, Daftar Isi, 4-5 H2 sections, affiliate mention, markdown table, FAQ, conclusion, sources, author box - Word count: 1200-1800 words - Language: Indonesian, casual-professional - No banned phrases - No AI markers - Affiliate link injection after paragraph 3 - Internal link at the end - Specific constraints around YAGNI, stdlib, etc. (but those seem like a persona prompt, I need to follow the blog post format) Wait, the prompt starts with "You are a lazy senior developer. Lazy means efficient...". This is a system persona/instruction style. But the actual task is to write a blog post about crypto-tax-id for Indonesia. The "lazy developer" part seems like a meta-instruction or maybe it's mixed in. Let me re-read carefully. Actually, the prompt combines two things: - A system prompt about being a "lazy senior developer" with specific coding principles (YAGNI, etc.) - A task to write a blog post with very strict formatting rules I need to produce the blog post. The "lazy developer" persona might influence me to be concise, but the blog post has strict word count (1200-1800 words) and structure. I'll focus on fulfilling the blog post requirements. The lazy developer principles might be a distraction or maybe I need to apply efficiency to the writing, but the constraints are clear. Let me list the blog post requirements: - H1 title - max 60 chars, keyword 'crypto-tax-id' at the beginning - TL;DR box - 1 paragraph, 40-60 words, direct answer (answer-first) - Daftar Isi - 3-5 anchor links to H2 sections - 4-5 H2 sections, each 200-300 words - Tepat 1 affiliate mention mid-article (after paragraph 3, counting TL;DR as para 1). Mention 'platform Bybit' naturally — https://www.bybit.com/affiliate/?affiliate_id=XXXX. Never a naked URL. Keep it 1-2 sentences, no pushy CTA. - WAJIB: Minimal 1 section pakai MARKDOWN TABLE dengan data/angka/komparasi (bukan list) - FAQ section - 3 Q&A with H3 - Kesimpulan - 80-120 words + internal CTA - Sumber - 2-4 source links (E-E-A-T signal) - Author box di paling bawah: Penulis, Diterbitkan, Diperbarui, Topik - AFFILIATE: Inject after paragraph 3 (counting TL;DR as para 1). Natural flow: Saran saya, coba [anchor] - [link]. Bisa bantu [benefit singkat]. - Total: 1200-1800 words - Bahasa Indonesia, casual-profesional tone - No absolute claims without sources - Max 4 sentences per paragraph - Use H2 for main sections, H3 for FAQ - BANNED PHRASES: In today's digital age, In conclusion, As mentioned earlier, In this article we will, Let's dive into, Delve into, Tapestry, Elevate, Leverage, Unlock, Seamless, Holistic, Paradigm, Game-changer - NO AI MARKERS: Jangan sebut "artikel ini dibuat AI", "sebagai AI", "generated", "model bahasa" - INTERNAL LINK: Akhiri dengan "Baca juga: [judul artikel terkait dari niche sama]" (slug format) Additional: The "lazy developer" part at the top might be a system prompt that I should ignore or internalize, but the task is clear. I'll produce the blog post markdown. Let me structure this step by step. First, H1 title: max 60 chars, keyword 'crypto-tax-id' at the beginning. In Indonesian context, maybe "Crypto Tax ID: Panduan Lengkap Wajib Paham untuk Pelaku Crypto Indonesia". Count chars: "Crypto Tax ID: Panduan Lengkap Wajib Paham untuk Pelaku Crypto Indonesia" - let's count: C-r-y-p-t-o- -T-a-x- -I-D-:-... Actually, the keyword must be at the beginning. So H1 should start with "crypto-tax-id". Maybe: "crypto-tax-id: Panduan Lengkap Pelaku Crypto Indonesia". Count: "crypto-tax-id: Panduan Lengkap Pelaku Crypto Indonesia" - that's 57 chars including colon and space? Let's count properly later. TL;DR box: 1 paragraph, 40-60 words, direct answer (answer-first). About crypto tax ID in Indonesia. Need 40-60 words. Indonesian. Answer-first: maybe "Wajib pajak crypto di Indonesia harus melaporkan identitas melalui form tertentu setiap tahun." Count words. Daftar Isi: 3-5 anchor links to H2 sections. 4-5 H2 sections, each 200-300 words. Need to cover topics related to crypto tax ID in Indonesia. Each H2 200-300 words. That's 800-1500 words for sections, plus other parts, total 1200-1800. So sections should be substantial. Affiliate mention: after paragraph 3 (TL;DR as para 1, then paragraphs). I need to structure paragraphs carefully. TL;DR is para 1. Then daftar isi might be considered separate, but usually daftar isi is not a paragraph. I'll treat TL;DR as para 1, then paragraph 2, paragraph 3, then after paragraph 3 insert affiliate. Need to count paragraphs. Markdown table with data/angka/komparasi, minimal 1 section. FAQ section - 3 Q&A with H3. Kesimpulan - 80-120 words + internal CTA. Sumber - 2-4 source links. Author box at bottom. Banned phrases must be avoided. Max 4 sentences per paragraph. Indonesian casual-professional tone. Let me start drafting. First, H1: "crypto-tax-id: panduan lengkap wajib paham untuk pelaku crypto Indonesia". Need max 60 chars. Let's count: "crypto-tax-id: panduan lengkap wajib paham untuk pelaku crypto indonesia". Char count: c(1)r2y3p4t5o6 -7 8t9a10x11 -12 i13d14:15 16p17a18n19d20u21a22 23l24e25n26g27k28 29w30a31j32i33b34 35p36a37h38a39m40 41p42e43r4445 46t47u48r49 50p51e52l53a54k55u56 57c58r59y60 61n62e63w6465. That's 65 chars. Need max 60. Shorten: "crypto-tax-id: panduan pelaku crypto Indonesia". Count: c1r2y3p4t5o6 -7 i8d9:10 p11a12n13d14u15 16l17e18 19p120? Let's do properly later. Maybe: "crypto-tax-id: panduan cepat pelaku crypto Indonesia". I'll craft carefully. Actually, H1 text will be in markdown: # crypto-tax-id: ... Let me think about the structure in Indonesian. I'll write the post step by step in markdown. Important: The affiliate link must be https://www.bybit.com/affiliate/?affiliate_id=XXXX. I need to use a placeholder or actual? The prompt says "Never a naked URL." and gives format. I'll use the exact URL but maybe with a placeholder ID, or just as given. It says "https://www.bybit.com/affiliate/?affiliate_id=XXXX". I'll keep it as is, but ensure it's not naked, it'll be within text. "Saran saya, coba platform Bybit - https://www.bybit.com/affiliate

Comments

Popular posts from this blog