agente.diy

• Clear signalStructure

  Classic AI-builder template: Hero → 3-feature cards → FAQ → CTA, with uniform H2 lengths and numbered step lists

  Evidence

  • “H2: Não é só responder perguntas. H2: Parece uma conversa. H2: Da sua ideia ao agente publicado”×3page
  • “01 Criar sua aplicação / 02 Montar o agente / 03 Definir acesso”body
  Try this

  Vary section structure: break the numbered-step pattern, combine related sections, rewrite H2s as full sentences to reduce template uniformity.

• Clear signalContent

  Repetitive 'seu agente' and 'você decide' phrasing across multiple sections creates flat cadence

  Evidence

  • “Seu agente pode receber quem acabou de te descobrir, entregar uma amostra do seu repertório, qualificar interessados”body
  • “Você decide se aquilo vira conexão, lista, comunidade ou venda”body
  Try this

  Replace repeated phrases with specific use cases: instead of 'seu agente pode fazer', show concrete examples (e.g. 'A Mariana usou para captar 200 leads em duas semanas').

• Worth notingImagery

  Zero images present despite layout structure indicating image placements; unusual for modern SaaS landing pages

  Evidence

  • “Images: 0”page
  Try this

  Add custom product screenshots, creator testimonial photos, or workflow diagrams to break text monotony and demonstrate product UI.

Observations of human authorship the page is doing well.

• Tone

  Authentic Brazilian Portuguese voice with creator-specific slang ('refém da parte técnica', 'fit', 'DM') and direct address—not translated marketing copy.

• Content

  Grounded in specific product features and use cases ('Semana 1 128 conversas abertas', real FAQ scenarios) rather than generic benefit claims.

• Words1,007
• Images0
• Alt coverage100%
• Internal links8
• External links0
• Schema blocks0
• HTML size20 KB

• Meta tags

  Missing canonical

  Why this matters

  Why it matters. Title and description are the two strings Google shows in search results — they decide whether anyone clicks. A canonical tag tells Google which URL is the source of truth when the same content lives at multiple paths.

  Passing looks like. A non-empty title under 60 characters, a meta description under 160, and a self-referencing canonical link.

  Fix. Add the missing tags inside the page head. Treat the title as a headline you'd want to read in a SERP, not a brand slogan.

• Heading structure

  1 H1, 8 H2

  Why this matters

  Why it matters. Headings are how crawlers and assistive tech understand a page's outline. One H1 names the page; H2s break it into sections. Skipped levels and missing H1s confuse both.

  Passing looks like. Exactly one H1, at least one H2, and no skipped levels (no H1 → H3 jumps).

  Fix. Replace the missing or duplicate H1 with a single, descriptive heading. Promote section titles to H2; demote sub-points to H3.

• Mobile readiness

  Responsive

  Why this matters

  Why it matters. Google indexes mobile-first. A page without a responsive viewport renders zoomed-out on phones, fails Core Web Vitals on touch, and loses its mobile ranking.

  Passing looks like. A meta viewport tag with width=device-width and a layout that reflows under 600px.

  Fix. Add a viewport meta tag set to width=device-width and initial-scale=1, then audit your largest blocks at mobile widths.

• Page speed signals

  0.4s · 20 KB

  Why this matters

  Why it matters. Page weight and response time directly feed Core Web Vitals. Slow LCP and oversized HTML hurt rankings more than people expect.

  Passing looks like. First-byte under 1.5s, HTML payload under 500 KB, fewer than 30 images on the initial render.

  Fix. Trim render-blocking scripts, defer non-critical CSS, and serve compressed images sized to the viewport. Move heavy components below the fold.

• Schema markup

  No JSON-LD

  Why this matters

  Why it matters. JSON-LD structured data is how you earn rich results — review stars, FAQ accordions, breadcrumbs, article cards. Without it you're competing with one hand tied.

  Passing looks like. At least one valid JSON-LD block matching schema.org types relevant to the page (Article, Product, FAQPage, Organization).

  Fix. Add an application/ld+json script block describing the page. Validate with Google's Rich Results Test before deploying.

• Broken links

  No outbound paths

  Why this matters

  Why it matters. Broken internal links waste crawl budget, degrade UX, and signal to Google that the site isn't well-maintained. They also cap how deep crawlers reach.

  Passing looks like. Every internal link in the sample returns 2xx or 3xx. No dead anchors, no stale paths.

  Fix. Use the link list above to spot the broken paths. Either restore the missing pages or update the links to point at live URLs.

• Image alt text

  No images

  Why this matters

  Why it matters. Alt text is how screen readers describe images and how Google understands what's in them. Missing alts hurt accessibility, image search, and on-page relevance.

  Passing looks like. Every meaningful image has a descriptive alt attribute. Decorative images can use alt="" to be skipped intentionally.

  Fix. Audit images in /assets and CMS uploads — write alts that describe what's in the image, not what it links to.

Every H1, H2, and H3 we found on the page, in document order.