sinapse-ai 1.0.0

package/squad-growth/tasks/analyze-conversion-funnel.md

@@ -0,0 +1,98 @@
+---
+task: analyze-conversion-funnel
+responsavel: "@ga-cro-specialist"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Task: Analyze Conversion Funnel
+
+## Metadata
+- **Squad:** squad-growth
+- **Agent:** Convert (ga-cro-specialist)
+- **Complexity:** Standard
+
+## Objetivo
+Analisar funil de conversao — mapear cada etapa, medir drop-offs, segmentar por dimensoes e identificar os maiores gargalos de conversao.
+
+## Entrada
+- Funnel definition (steps)
+- Analytics event data (30+ days)
+- Segmentation dimensions
+
+## Passos
+
+### 1. Funnel Definition
+| Step | Evento | Descricao |
+|------|--------|----------|
+| 1 | page_view (landing) | Visitante chega |
+| 2 | sign_up_start | Inicia registro |
+| 3 | sign_up_complete | Completa registro |
+| 4 | activation_event | Realiza acao de valor |
+| 5 | purchase | Converte para pago |
+
+### 2. Funnel Metrics
+| Step | Users | Conv Rate | Drop-off | Drop-off % |
+|------|-------|----------|---------|-----------|
+| Landing | 10,000 | 100% | — | — |
+| Sign-up start | | | | |
+| Sign-up complete | | | | |
+| Activation | | | | |
+| Purchase | | | | |
+
+### 3. Segmented Funnel Analysis
+| Segmento | Step 1→2 | Step 2→3 | Step 3→4 | Step 4→5 | Total |
+|----------|---------|---------|---------|---------|-------|
+| Desktop | | | | | |
+| Mobile | | | | | |
+| Organic | | | | | |
+| Paid | | | | | |
+| New users | | | | | |
+| Return users | | | | | |
+
+### 4. Drop-off Analysis
+| Biggest Drop-off | De → Para | Taxa | Causa Provavel | Acao |
+|-----------------|---------|------|---------------|------|
+| #1 | | | | |
+| #2 | | | | |
+| #3 | | | | |
+
+### 5. Time Between Steps
+| Step Transition | Median Time | P75 Time | Ideal | Issue? |
+|----------------|------------|---------|-------|--------|
+| Landing → Sign-up | | | < 3 min | |
+| Sign-up → Activation | | | < 24h | |
+| Activation → Purchase | | | < 7d | |
+
+## Saida
+- Funnel analysis report
+- Conversion rates per step
+- Segmented funnel comparison
+- Top 3 drop-off points with root causes
+- Optimization recommendations
+
+## Validacao
+- [ ] Funnel mapeado com todos os steps
+- [ ] Conversion rates calculados
+- [ ] Segmentacao por device, channel, user type
+- [ ] Top drop-offs identificados
+- [ ] Causas provaveis documentadas
+- [ ] Acoes recomendadas por drop-off

package/squad-growth/tasks/analyze-experiment-results.md

@@ -0,0 +1,131 @@
+---
+task: analyze-experiment-results
+responsavel: "@ga-cro-specialist"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Task: Analyze Experiment Results
+
+## Metadata
+- **Squad:** squad-growth
+- **Agent:** Convert (ga-cro-specialist)
+- **Complexity:** Complex
+
+## Objetivo
+Analisar resultados de experimento — verificar validade estatistica, analisar segmentos, documentar learnings e fazer recomendacao de implementacao.
+
+## Entrada
+- Experiment data (full duration)
+- Experiment brief
+- Sample size requirements met
+- Segmentation dimensions
+
+## Passos
+
+### 1. Data Quality Checks
+| Check | Status | Note |
+|-------|--------|------|
+| Sample Ratio Mismatch (SRM) | | Expected 50/50, actual? |
+| Minimum sample reached | | Per-variant minimum |
+| Full week cycles | | No partial weeks |
+| No external events | | No promotions, PR, outages |
+| Tracking accuracy | | Events firing correctly |
+
+**SRM Check:** If actual split deviates > 1% from expected, investigate before analyzing.
+
+### 2. Overall Results
+| Metric | Control | Variant | Lift | p-value | CI (95%) | Significant? |
+|--------|---------|---------|------|---------|----------|-------------|
+| Primary metric | | | +X% | | [lower, upper] | Yes/No |
+| Secondary 1 | | | | | | |
+| Secondary 2 | | | | | | |
+| Guardrail 1 | | | | | | |
+| Guardrail 2 | | | | | | |
+
+### 3. Segmented Analysis
+| Segment | Control CR | Variant CR | Lift | Significant? |
+|---------|-----------|-----------|------|-------------|
+| Desktop | | | | |
+| Mobile | | | | |
+| New users | | | | |
+| Return users | | | | |
+| Organic traffic | | | | |
+| Paid traffic | | | | |
+
+### 4. Statistical Interpretation
+| Aspecto | Valor | Interpretacao |
+|---------|-------|-------------|
+| p-value | | < 0.05 = significant |
+| Confidence interval | | Range of true effect |
+| Effect size | | Practical significance |
+| Power achieved | | >= 80% adequate |
+| MDE detected | | Within expected range |
+| Bayesian probability | | % chance variant is better |
+
+### 5. Verdict
+| Verdict | Criterio | Acao |
+|---------|---------|------|
+| **WINNER** | p < 0.05, lift > 0, guardrails OK | Implement variant |
+| **LOSER** | p < 0.05, lift < 0 | Keep control, learn |
+| **INCONCLUSIVE** | p >= 0.05 | Extend test, redesign, or accept null |
+| **CONDITIONAL** | Primary wins, guardrail concern | Implement with monitoring |
+
+### 6. Learnings Documentation
+```yaml
+experiment_learning:
+  id: "EXP-{number}"
+  hypothesis: ""
+  result: "Winner/Loser/Inconclusive"
+  primary_lift: "+X%"
+  statistical_significance: "Yes/No"
+
+  key_learnings:
+    - "What we learned"
+    - "Unexpected findings"
+    - "Segment differences"
+
+  implications:
+    - "How this informs future tests"
+    - "Related hypotheses to test"
+    - "Process improvements"
+
+  next_steps:
+    - "Implement winner / Keep control"
+    - "Follow-up experiment ideas"
+    - "Monitoring plan post-implementation"
+```
+
+## Saida
+- Experiment results report
+- Statistical analysis with p-values and CIs
+- Segmented results
+- Verdict and recommendation
+- Learnings document
+
+## Validacao
+- [ ] Data quality checks passados (no SRM)
+- [ ] Significancia estatistica avaliada
+- [ ] Segmented analysis completa
+- [ ] Guardrail metrics verificados
+- [ ] Verdict emitido com evidencia
+- [ ] Learnings documentados
+- [ ] Knowledge base atualizada

package/squad-growth/tasks/analyze-funnel-segmented.md

@@ -0,0 +1,155 @@
+---
+task: analyze-funnel-segmented
+responsavel: "@ga-data-analyst"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Task: Analyze Funnel Segmented
+
+## Metadata
+- **Squad:** squad-growth
+- **Agent:** Insight (ga-data-analyst)
+- **Complexity:** Standard
+
+## Objetivo
+Analisar funis segmentados — decompor conversion funnels por dimensoes (canal, device, regiao, cohort) para identificar onde e por que usuarios abandonam em cada segmento.
+
+## Entrada
+- Funnel definition (stages and events)
+- Segmentation dimensions
+- Date range
+- Baseline conversion rates
+
+## Passos
+
+### 1. Funnel Definition
+| Stage | Evento GA4 | Descricao |
+|-------|-----------|----------|
+| Awareness | page_view (landing) | Primeiro contato |
+| Interest | scroll > 50% OR time > 30s | Engajamento inicial |
+| Consideration | add_to_cart OR sign_up_start | Intent signal |
+| Intent | begin_checkout OR form_start | Alta intencao |
+| Conversion | purchase OR sign_up_complete | Conversao |
+| Retention | return_visit (D7+) | Retorno |
+
+### 2. Segmented Funnel Matrix
+| Stage | Overall | Organic | Paid | Social | Email | Direct |
+|-------|---------|---------|------|--------|-------|--------|
+| Awareness | 100% | 100% | 100% | 100% | 100% | 100% |
+| Interest | | | | | | |
+| Consideration | | | | | | |
+| Intent | | | | | | |
+| Conversion | | | | | | |
+| Drop-off total | | | | | | |
+
+### 3. Drop-off Analysis
+| De → Para | Rate | Top Motivo | Acao |
+|-----------|------|-----------|------|
+| Awareness → Interest | | Bounce alto | Melhorar landing page |
+| Interest → Consideration | | Falta de CTA claro | CRO na pagina |
+| Consideration → Intent | | Friction no processo | Simplificar form |
+| Intent → Conversion | | Custo/trust | Otimizar checkout |
+
+### 4. SQL Query Pattern
+```sql
+-- Segmented funnel analysis
+WITH funnel_events AS (
+  SELECT
+    user_pseudo_id,
+    event_name,
+    event_timestamp,
+    -- Segmentation dimensions
+    traffic_source.medium AS channel,
+    device.category AS device_type,
+    geo.country AS country,
+    -- Funnel stage mapping
+    CASE
+      WHEN event_name = 'page_view' THEN 1
+      WHEN event_name IN ('scroll', 'user_engagement') THEN 2
+      WHEN event_name IN ('add_to_cart', 'sign_up_start') THEN 3
+      WHEN event_name IN ('begin_checkout', 'form_start') THEN 4
+      WHEN event_name IN ('purchase', 'sign_up_complete') THEN 5
+    END AS stage_number
+  FROM `project.dataset.events_*`
+  WHERE _TABLE_SUFFIX BETWEEN '20260101' AND '20260331'
+    AND event_name IN (
+      'page_view', 'scroll', 'user_engagement',
+      'add_to_cart', 'sign_up_start',
+      'begin_checkout', 'form_start',
+      'purchase', 'sign_up_complete'
+    )
+),
+user_max_stage AS (
+  SELECT
+    user_pseudo_id,
+    channel,
+    device_type,
+    country,
+    MAX(stage_number) AS max_stage_reached
+  FROM funnel_events
+  GROUP BY user_pseudo_id, channel, device_type, country
+)
+SELECT
+  channel,
+  device_type,
+  COUNT(DISTINCT CASE WHEN max_stage_reached >= 1 THEN user_pseudo_id END) AS stage_1_awareness,
+  COUNT(DISTINCT CASE WHEN max_stage_reached >= 2 THEN user_pseudo_id END) AS stage_2_interest,
+  COUNT(DISTINCT CASE WHEN max_stage_reached >= 3 THEN user_pseudo_id END) AS stage_3_consideration,
+  COUNT(DISTINCT CASE WHEN max_stage_reached >= 4 THEN user_pseudo_id END) AS stage_4_intent,
+  COUNT(DISTINCT CASE WHEN max_stage_reached >= 5 THEN user_pseudo_id END) AS stage_5_conversion
+FROM user_max_stage
+GROUP BY channel, device_type
+ORDER BY channel, device_type;
+```
+
+### 5. Key Segmentation Dimensions
+| Dimensao | Segmentos | Por que Segmentar |
+|----------|----------|------------------|
+| Channel | organic, paid, social, email, direct | Diferentes intencoes e expectativas |
+| Device | mobile, desktop, tablet | UX e friction variam |
+| New vs Returning | first visit, returning | Familiaridade com o produto |
+| Geography | pais, estado, cidade | Preferencias regionais |
+| Landing page | homepage, product, blog, LP | Contexto de entrada |
+| Time of day | morning, afternoon, evening, night | Comportamento temporal |
+
+### 6. Statistical Comparison
+| Comparacao | Metodo | Significancia |
+|-----------|--------|-------------|
+| Segment A vs B conversion | Chi-squared test | p < 0.05 |
+| Drop-off rate difference | Z-test for proportions | p < 0.05 |
+| Trend over time | Linear regression | R² > 0.7 |
+| Segment contribution | Weighted average | By volume |
+
+## Saida
+- Segmented funnel analysis report
+- Drop-off analysis por segmento
+- Statistical comparisons
+- Opportunity sizing (revenue impact)
+- Prioritized recommendations
+
+## Validacao
+- [ ] Funnel stages definidos e mapeados para eventos
+- [ ] Pelo menos 3 dimensoes de segmentacao analisadas
+- [ ] Drop-off points identificados por segmento
+- [ ] Significancia estatistica verificada
+- [ ] Oportunidades quantificadas (impacto em revenue)
+- [ ] Acoes priorizadas por impacto

package/squad-growth/tasks/analyze-retention-churn.md

@@ -0,0 +1,165 @@
+---
+task: analyze-retention-churn
+responsavel: "@ga-data-analyst"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Task: Analyze Retention & Churn
+
+## Metadata
+- **Squad:** squad-growth
+- **Agent:** Insight (ga-data-analyst)
+- **Complexity:** Advanced
+
+## Objetivo
+Analisar retencao e churn — diagnosticar padroes de retencao, identificar leading indicators de churn e construir framework preditivo para intervencao proativa.
+
+## Entrada
+- User activity data (sessions, events, transactions)
+- Subscription/account data
+- Support ticket data
+- Feature usage data
+
+## Passos
+
+### 1. Retention Metrics Framework
+| Metrica | Formula | Tipo |
+|---------|---------|------|
+| Gross Retention | (Start - Churned) / Start × 100 | Logo retention |
+| Net Retention | (Start - Churned + Expanded) / Start × 100 | Revenue retention |
+| DAU/MAU Ratio | Daily Active / Monthly Active | Stickiness |
+| WAU/MAU Ratio | Weekly Active / Monthly Active | Engagement frequency |
+| Resurrection Rate | Reactivated / Total Churned × 100 | Win-back success |
+| Time to Value | Days from signup to "aha moment" | Activation speed |
+
+### 2. Churn Types & Detection
+| Tipo | Definicao | Detection Signal | Window |
+|------|----------|-----------------|--------|
+| Voluntary churn | User cancela ativamente | Cancel event | Immediate |
+| Involuntary churn | Falha de pagamento | Payment failed | 3-7 days grace |
+| Silent churn | User para de usar | No activity | 30-60 days |
+| Downgrade churn | Reduz plano/spend | Plan change | Immediate |
+| Competitive churn | Migra para concorrente | Survey/exit interview | Post-churn |
+
+### 3. Churn Prediction Signals
+| Signal | Tipo | Peso | Threshold |
+|--------|------|------|----------|
+| Login frequency decrease | Behavioral | Alto | -50% vs 30d avg |
+| Feature usage decline | Behavioral | Alto | -40% weekly |
+| Support tickets increase | Service | Medio | > 3 in 30 days |
+| NPS/CSAT drop | Sentiment | Alto | NPS < 6 |
+| Payment failure | Financial | Alto | > 1 failed |
+| Contract approaching end | Temporal | Medio | < 30 days |
+| Key user departure | Organizational | Alto | Admin/power user left |
+| Competitor page visits | Intent | Alto | Pricing/competitor pages |
+
+### 4. SQL — Churn Risk Scoring
+```sql
+-- Churn risk score calculation
+WITH user_activity AS (
+  SELECT
+    user_id,
+    -- Activity recency
+    DATE_DIFF('day', MAX(event_date), CURRENT_DATE) AS days_since_last_activity,
+    -- Activity frequency (last 30 days vs prior 30 days)
+    COUNT(CASE WHEN event_date >= CURRENT_DATE - 30 THEN 1 END) AS events_last_30d,
+    COUNT(CASE WHEN event_date BETWEEN CURRENT_DATE - 60 AND CURRENT_DATE - 31 THEN 1 END) AS events_prior_30d,
+    -- Feature breadth
+    COUNT(DISTINCT CASE WHEN event_date >= CURRENT_DATE - 30 THEN event_name END) AS features_used_30d,
+    -- Session depth
+    AVG(CASE WHEN event_date >= CURRENT_DATE - 30 THEN session_duration END) AS avg_session_duration_30d
+  FROM events
+  GROUP BY user_id
+),
+risk_scores AS (
+  SELECT
+    user_id,
+    days_since_last_activity,
+    events_last_30d,
+    events_prior_30d,
+    -- Recency score (0-100, higher = more risk)
+    LEAST(100, days_since_last_activity * 3) AS recency_risk,
+    -- Frequency decline score
+    CASE
+      WHEN events_prior_30d = 0 THEN 50
+      ELSE LEAST(100, GREATEST(0,
+        (1 - events_last_30d::FLOAT / events_prior_30d) * 100
+      ))
+    END AS frequency_decline_risk,
+    -- Feature breadth score
+    CASE
+      WHEN features_used_30d >= 5 THEN 0
+      WHEN features_used_30d >= 3 THEN 30
+      WHEN features_used_30d >= 1 THEN 60
+      ELSE 100
+    END AS feature_breadth_risk
+  FROM user_activity
+)
+SELECT
+  user_id,
+  ROUND((recency_risk * 0.4 + frequency_decline_risk * 0.4 + feature_breadth_risk * 0.2), 1) AS churn_risk_score,
+  CASE
+    WHEN churn_risk_score >= 75 THEN 'Critical'
+    WHEN churn_risk_score >= 50 THEN 'High'
+    WHEN churn_risk_score >= 25 THEN 'Medium'
+    ELSE 'Low'
+  END AS risk_tier
+FROM risk_scores
+ORDER BY churn_risk_score DESC;
+```
+
+### 5. Retention Improvement Levers
+| Lever | Impacto | Custo | Timeframe |
+|-------|--------|-------|----------|
+| Onboarding optimization | Alto | Medio | 1-2 months |
+| Proactive outreach (at-risk) | Alto | Baixo | Immediate |
+| Feature education emails | Medio | Baixo | 2-4 weeks |
+| Loyalty/rewards program | Alto | Alto | 2-3 months |
+| Product improvements (top requests) | Alto | Alto | 1-3 months |
+| Customer success touchpoints | Alto | Medio | Ongoing |
+| Payment recovery automation | Medio | Baixo | 1-2 weeks |
+| Win-back campaigns | Medio | Baixo | 2-4 weeks |
+
+### 6. Churn Post-Mortem
+| Dimensao | Analise |
+|----------|--------|
+| When | Em qual ponto do lifecycle churnam mais? |
+| Who | Quais segmentos churnam mais? |
+| Why | Motivos declarados (survey) vs comportamentais |
+| What | Ultima acao antes do churn |
+| Where | Em qual feature/pagina a jornada termina |
+| How much | Revenue impact per churn segment |
+
+## Saida
+- Retention analysis report
+- Churn risk scoring model
+- Leading indicators identificados
+- Retention improvement roadmap
+- Win-back strategy
+
+## Validacao
+- [ ] Retention metrics calculados (gross e net)
+- [ ] Churn types definidos e quantificados
+- [ ] Churn risk score implementado
+- [ ] Leading indicators validados
+- [ ] Retention levers priorizados por impacto
+- [ ] Win-back strategy definida

package/squad-growth/tasks/audit-sitemap-robots.md

@@ -0,0 +1,129 @@
+---
+task: audit-sitemap-robots
+responsavel: "@ga-seo-strategist"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Task: Audit Sitemap & Robots.txt
+
+## Metadata
+- **Squad:** squad-growth
+- **Agent:** Rank (ga-seo-strategist)
+- **Complexity:** Standard
+
+## Objetivo
+Auditar e otimizar sitemap.xml e robots.txt — garantir que search engines podem descobrir e indexar todo conteudo relevante eficientemente.
+
+## Entrada
+- Current sitemap.xml
+- Current robots.txt
+- Page inventory
+- Index coverage report (Search Console)
+
+## Passos
+
+### 1. Sitemap Audit
+| Check | Status | Issue |
+|-------|--------|-------|
+| Sitemap exists and accessible | | |
+| Submitted to Search Console | | |
+| All important URLs included | | |
+| No noindex pages in sitemap | | |
+| No 4xx/5xx URLs in sitemap | | |
+| No redirect URLs in sitemap | | |
+| Lastmod dates accurate | | |
+| Sitemap < 50,000 URLs | | |
+| Sitemap < 50MB uncompressed | | |
+| Sitemap index if needed | | |
+| Image/video sitemaps (if applicable) | | |
+
+### 2. Robots.txt Audit
+| Check | Status | Issue |
+|-------|--------|-------|
+| robots.txt accessible at /robots.txt | | |
+| Not blocking important resources | | |
+| Sitemap URL referenced | | |
+| No accidental Disallow: / | | |
+| CSS/JS not blocked | | |
+| Admin/private paths blocked | | |
+| API endpoints appropriately handled | | |
+| Crawl-delay appropriate (if used) | | |
+
+### 3. Optimized robots.txt Template
+```
+User-agent: *
+Allow: /
+
+# Block admin and private paths
+Disallow: /admin/
+Disallow: /api/
+Disallow: /internal/
+Disallow: /_next/data/
+
+# Block search results and filtered pages
+Disallow: /search?
+Disallow: /*?sort=
+Disallow: /*?filter=
+
+# Sitemap
+Sitemap: https://example.com/sitemap.xml
+```
+
+### 4. Next.js Sitemap Generation
+```typescript
+// app/sitemap.ts
+export default async function sitemap(): Promise<MetadataRoute.Sitemap> {
+  const pages = await getPages();
+  const posts = await getPosts();
+
+  return [
+    { url: 'https://example.com', lastModified: new Date(), changeFrequency: 'daily', priority: 1 },
+    ...pages.map(page => ({
+      url: `https://example.com/${page.slug}`,
+      lastModified: page.updatedAt,
+      changeFrequency: 'weekly' as const,
+      priority: 0.8,
+    })),
+    ...posts.map(post => ({
+      url: `https://example.com/blog/${post.slug}`,
+      lastModified: post.updatedAt,
+      changeFrequency: 'monthly' as const,
+      priority: 0.6,
+    })),
+  ];
+}
+```
+
+## Saida
+- Sitemap audit report
+- Robots.txt audit report
+- Optimized sitemap configuration
+- Optimized robots.txt
+- Implementation guide
+
+## Validacao
+- [ ] Sitemap contem todas as paginas importantes
+- [ ] Nenhuma pagina noindex no sitemap
+- [ ] Nenhuma pagina 4xx/5xx no sitemap
+- [ ] robots.txt nao bloqueia conteudo importante
+- [ ] Sitemap referenciado no robots.txt
+- [ ] Sitemap submitted no Search Console