Crypto-Tax-Id Trends in Indonesia

- **Format**: Markdown, convertible to HTML - **Strict Structure**: - H1 title (max 60 chars, keyword 'crypto-tax-id' at beginning) - TL;DR box (1 paragraph, 40-60 words, 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, natural, Bybit link) - WAJIB: Minimal 1 section with MARKDOWN TABLE (data/numbers/comparison, not 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 at bottom (specific format) - **Affiliate Rule**: Mention 'platform Bybit' naturally after paragraph 3. Keep 1-2 sentences, no pushy CTA. Link: https://www.bybit.com/affiliate/?affiliate_id=XXXX. Never naked URL. Inject after paragraph 3 (TL;DR as para 1). - **Constraints**: - 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 - Listicle format OK if it fits - 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 - INTERNAL LINK: Akhiri dengan "Baca juga: [judul artikel terkait dari niche sama]" (slug format) - Total: 1200-1800 words Indonesian - Sections: - H1: ~1 line - TL;DR: 1 paragraph, 40-60 words - Daftar Isi: 3-5 anchors - 4-5 H2 sections: 200-300 words each → roughly 800-1500 words - Affiliate mention: 1-2 sentences (injected after para 3) - TABLE section: needs to be part of H2 sections, must have data/numbers/comparison - FAQ: 3 Q&A with H3 - Kesimpulan: 80-120 words + internal CTA - Sumber: 2-4 links - Author box: specific format - Need to count paragraphs carefully for affiliate injection point ("after paragraph 3, counting TL;DR as para 1") - Need to avoid banned phrases - Need natural Indonesian casual-profesional tone Let's outline word by paragraph/section to hit 1200-1800 words total, with constraints. Structure plan: 1. H1 title 2. TL;DR (para 1) 3. Start of section 1 (para 2? Wait, need to count paragraphs for affiliate injection after para 3) Let's think about paragraph counting. The rule: "INJECT AFTER PARAGRAPH 3 (counting TL;DR as para 1)". So paragraph 1 = TL;DR. Paragraph 2 = first paragraph after TL;DR. Paragraph 3 = second paragraph after TL;DR. Affiliate goes after paragraph 3. So I need to ensure the affiliate link appears right after the 3rd paragraph. Let's structure paragraphs: - Para 1: TL;DR (40-60 words) - Para 2: Start of Daftar Isi or first H2 intro? Actually Daftar Isi is usually a list, maybe it's not counted as a paragraph in the flow, but I need to be careful. The rule says "counting TL;DR as para 1". So the subsequent content paragraphs count. I'll make sure the affiliate goes after the 3rd content paragraph. Let's plan the flow: - H1 - TL;DR (para 1) - Para 2: Introduction/context about crypto tax in Indonesia, maybe leading to need for tax ID - Para 3: Something about reporting requirements, then affiliate injection after this paragraph - Para 4: Continue with first H2 section content (or maybe H2 sections start after) Actually, the Daftar Isi (Table of Contents) is typically a list of anchors. It might not be counted as "paragraphs" in the flow, but to be safe, I'll structure the main content paragraphs separately. Let's re-read: "INJECT AFTER PARAGRAPH 3 (counting TL;DR as para 1). Natural flow: Saran saya, coba [anchor] - [link]. Bisa bantu [benefit singkat]." So after the 3rd paragraph (which is the third block of text, after TL;DR), I need to insert: "Saran saya, coba platform Bybit - https://www.bybit.com/affiliate/?affiliate_id=XXXX. Bisa bantu [benefit singkat]." I need to make sure the affiliate link is not naked: "platform Bybit" with link. The format should be like: "Saran saya, coba [platform Bybit](https://www.bybit.com/affiliate/?affiliate_id=XXXX) untuk [benefit]." But the rule says "Never a naked URL. Keep it 1-2 sentences, no pushy CTA." And "Mention 'platform Bybit' naturally — https://www.bybit.com/affiliate/?affiliate_id=XXXX. Never a naked URL." Wait, it says mention 'platform Bybit' naturally — then gives the URL. But also "Never a naked URL." So I think the link should be embedded, not raw URL. Probably: "Saran saya, coba platform Bybit untuk [benefit]." and the URL is provided but maybe embedded? The rule says: "Mention 'platform Bybit' naturally — https://www.bybit.com/affiliate/?affiliate_id=XXXX. Never a naked URL." This is a bit contradictory. I'll interpret: The anchor text should be "platform Bybit", and the URL is https://www.bybit.com/affiliate/?affiliate_id=XXXX, but it should be hyperlinked, not displayed as naked URL in markdown. So in markdown: `[platform Bybit](https://www.bybit.com/affiliate/?affiliate_id=XXXX)`. That's not a naked URL. I'll do that. Now, word count: 1200-1800 words Indonesian. Let's aim for ~1400. Let's outline sections with approximate words: - H1: ~50 chars, starts with crypto-tax-id - TL;DR: 40-60 words - Daftar Isi: 3-5 anchors, maybe 50-80 words total - Then 4-5 H2 sections, each 200-300 words → say 5 sections × 250 = 1250 words. But total must be 1200-1800 including everything. So I need to be careful. Maybe 4 sections at 250-300 words each = 1000-1200, plus others. Let's plan precisely. Better: I'll write in Markdown with paragraphs counted. I need to output exactly the structure. Let's start drafting. First, H1 title: max 60 chars, keyword 'crypto-tax-id' at beginning. "crypto-tax-id Indonesia: Panduan Lengkap Wajib Pajak Mata uang Digital" Count chars: "crypto-tax-id Indonesia: Panduan Lengkap Wajib Pajak Mata uang Digital" → let's count: c-r-y-p-t-o---t-a-x---i-d- -I-n-d-o-n-e-s-i-a-:-... That's 58 chars maybe. Good. TL;DR: 40-60 words, answer-first. About crypto tax ID in Indonesia. I'll write in Indonesian, 45 words. Daftar Isi: 3-5 anchor links to H2 sections. I'll make 5 H

Comments

Popular posts from this blog