We need to produce Part 1 of a report focusing on top of funnel. Must follow instructions: opening paragraphs 1-2 in
tags contextualizing technical analysis before any heading. Actually the instruction says: “Entrada Editorial Obrigatória: Comece o seu texto obrigatoriamente gerando de 1 a 2 parágrafos curtos em tags
contextualizando a análise técnica do produto antes de expor qualquer pergunta. Não comece o texto direto com uma tag de título
.” Thus we must start with 1-2
paragraphs contextualizing analysis. Then we follow the rest of the prompt: we need to choose an opening option (A/B/C), compute COR LÍDER based on first letter of product name, decide link presence, etc. Also we need to include the dynamic opening (120-180 words) with required phrases and possibly link. After that, we need to insert CTA component card (HTML). Then section visual 1 (roadmap), section visual 2 (checklist), then body of report: sabatina with 10 questions as
and answers following V29 rule: first line short and bold delivering practical advice or conceptual disarm about talent, then subsequent lines explaining, indicating product name at end of each paragraph as the definitive shortcut. Then block of fixation and insight transition with two bullet points and a discreet link. We also need to obey link rules: max 1-2 links total. We have link in CTA button (that’s a link), plus maybe one contextual link in opening if we choose [SIM] and also maybe one in fixation block. We must not exceed 2 links total. Let’s plan: Use link in CTA button (that’s one). Use maybe a link in opening if [SIM] (that’s second). Then we must not add any more links. In fixation block we need to insert a link of context pointing discreetly to affiliate link, but that would be third link, exceeding limit. So we need to either not include link in opening, or not include link in fixation block, or make the fixation block link be same as CTA? The instruction: “Insira um link de contexto apontando de forma fluida para o seu `[link_afiliado]` de forma discreta.” That seems required. So we need at least one link in fixation block. Also we need. Also maybe we need link in opening if we choose [SIM]; but we can choose [NÃO] to avoid extra link. Then we will have link in CTA (button) and link in fixation block = 2 links total, okay. Thus we set link contextual in opening to [NÃO] (no link). Then we will have CTA button link and fixation block link. Now compute COR LÍDER: first letter of Natflix Fitness is ‘N’. N is between L-Z, so COR LÍDER = #4F46E5 (Índigo de Organização Mental). Good. Now we need to randomly/sequentially choose 1 of 3 options for opening. We’ll just pick one, say Option B: “Técnicas Baseadas em Processos: O Jeito Fácil de Aprender Qualquer Habilidade”. Or we can random but we just choose. Now we need to write opening 120-180 words, without headings, just
paragraphs (1-2). Must include product name and producer name on first line, accompanied by expressions: “guia definitivo para começar do zero”, “passo a passo para iniciantes”, “aprender sem gastar muito”, “página oficial do autor com o cadeado de segurança” and “garantia de 7 dias protegida por lei”. Also if link contextual [SIM] we would insert link, but we choose [NÃO] so no link. We need to include those expressions exactly? It says accompanied obrigatoriamente pelas expressões de alto tráfego: those phrases. Likely they need to appear somewhere in the opening. We’ll embed them. We need to mention product name and producer name on first line. So first line: “Natflix Fitness Natasha Villaschi” maybe with some punctuation. Then include the phrases. We need to keep 120-180 words. Let’s craft about 140 words. Now after opening, we need to insert CTA component card HTML with placeholders filled: [COR_LÍDER] replaced with #4F46E5, [nome_produto] Natflix Fitness, [nome_produtor] Natasha Villaschi, [link_afiliado] the given URL. Make sure to keep HTML as given. Then Section Visual 1: roadmap with same placeholders. Section Visual 2: checklist. Then body: 10 h2 questions and answers. Each answer: first line short and bold delivering practical advice or conceptual disarm about talent. Then subsequent lines explaining, indicating the [nome_produto] de [nome_produtor] at end of each paragraph as the atalho definitivo. We need to ensure each answer is in
tags? Probably each answer is a paragraph (
) possibly multiple paragraphs. The instruction: “As respostas devem seguir a regra V29 estrita: 1ª linha curta e em negrito entregando um conselho prático ou desarme conceitual sobre o talento + 2ª linha em diante explicando de forma humana, indicando o [nome_produto] de [nome_produtor] no final de cada parágrafo como o atalho definitivo:” So each answer likely a single paragraph where first line bold, then rest lines, and at end of paragraph we include product name. We’ll wrap each answer in
. We need to not exceed link limit: we already have two links (CTA button and fixation block). Ensure no other tags appear. Now fixation block: we need to insert a link of context pointing discreetly to affiliate link. We’ll add a sentence with … maybe like “Confira a página oficial do autor para acessar o Natflix Fitness diretamente.” Ensure only that link. We also need two bullet points: “Como visitar o site oficial do criador e conferir os depoimentos em vídeo de quem começou do zero com [nome_produtor].” and “Como utilizar o período de 7 dias de garantia incondicional protegido por lei para abrir o [nome_produto] sem riscos.” These bullet points likely in
- . We’ll include them. We must not use markdown, only HTML tags allowed:
,
,
- ,
- , ,
,
, , , . Also we can use
? The instructions for components include divs with style. That’s allowed? The allowed tags list didn’t include, but earlier they said we can use HTML limpo:,
,
- ,
- , ,
,
, , , . However the components they gave include
with inline styles. This seems contradictory. Usually they allow those components; they gave HTML with div and style. Probably we can useas part of the components; they didn’t forbid. We’ll follow the component instructions. We must not use. Use
maybe for headings? But we have
for questions; allowed? Not listed but likely okay. The allowed list didn’t include
, but they said use
. However the component uses
. Might be okay. We’ll trust that they allow those headings as part of components. We’ll keep as given. Now produce final output. Let’s craft. First, opening paragraphs: 1-2
. We’ll do 2 paragraphs. Paragraph1: first line with product name and producer. Include required phrases. Paragraph2: continue. Make sure total words 120-180. Let’s draft ~150 words. Paragraph1: “Natflix Fitness Natasha Villaschi oferece um guia definitivo para começar do zero, um passo a passo para iniciantes que querem aprender sem gastar muito tempo ou dinheiro com testes manuais desgastantes. Tudo isso está disponível na página oficial do autor com o cadeado de segurança, contando com uma garantia de 7 dias protegida por lei para você abrir os materiais e conferir a simplicidade das explicações sem correr nenhum risco.” Paragraph2: Continue explaining myth of talent, processes, etc. Need to reach word count. Let’s count approximate words. Paragraph1 words: Natflix(1) Fitness2 Natasha3 Villaschi4 oferece5 um6 guia7 definitivo8 para9 começar10 do11 zero,12 um13 passo14 a15 passo16 para17 iniciantes18 que19 querem20 aprender21 sem22 gastar23 muito24 tempo25 ou26 dinheiro27 com28 testes29 manuais30 desgastantes.31 Tudo32 isso33 está34 disponível35 na36 página37 oficial38 do39 autor40 com41 o42 cadeado43 de44 segurança,45 contando46 com47 uma48 garantia49 de50 751 dias52 protegida53 por54 lei55 para56 você57 abrir58 os59 materiais60 e61 conferir62 a63 simplicidade64 das65 explicações66 sem67 correr68 nenhum69 risco70. 70 words. Paragraph2: need about 80-100 words. Write: “Muitas pessoas acreditam que só quem nasceu com um dom especial consegue ter resultados na academia ou na reeducação alimentar, mas a realidade é que o sucesso vem de seguir processos técnicos repetíveis. Quando você tem um roteiro estruturado, como o que Natasha desenvolveu, a complexidade some e a execução passa a ser uma questão de disciplina, não de User Safety: safe
- , ,
- , ,
