substack.com

Mostrando os 10 principais problemas. Auditoria completa com correções no nível do código disponível no plano grátis.

• 01
  FAIL · content

  Thin Content

  The page contains almost no text (26 words). This is critically insufficient for search engine indexing. Text-to-HTML ratio: 0.3%. Such pages may be classified as doorway pages or empty shells and excluded from search results.
  Cadastre-se para ver como corrigir isto
• 02
  FAIL · onpage

  H1 Heading

  The H1 heading is missing. Google + Bing + Yandex use H1 as a secondary ranking signal (after <title>) to confirm page topic. ChatGPT / Claude / Perplexity also lean on H1 when extracting page summaries for citation — a missing H1 forces them to infer the topic from <title> and body text, often less accurately. Accessibility screen readers also rely on H1 for page-level navigation.
  Cadastre-se para ver como corrigir isto
• 03
  FAIL · onpage

  Content Length

  Only 26 words were found on the page. This is extremely low for proper indexing. Pages with minimal text content (fewer than 100 words) are considered "thin content" by search engines and rank poorly.
  Cadastre-se para ver como corrigir isto
• 04
  FAIL · performance

  HTTP Requests Count

  The page loads 164 external resources — this is too many (14 CSS, 146 JS, 0 images). A high number of HTTP requests critically slows down page loading, as browsers are limited to 6 simultaneous connections per domain. This negatively affects all performance metrics.
  Cadastre-se para ver como corrigir isto
• 05
  FAIL · security

  Security Headers

  Only 2 out of 6 modern security headers found. Missing: x-frame-options, x-content-type-options, referrer-policy, permissions-policy. The site is exposed to XSS (no CSP), clickjacking (no X-Frame-Options / CSP frame-ancestors), MIME-sniffing (no X-Content-Type-Options), and HTTPS-stripping MITM (no HSTS). Mozilla Observatory grades sites with <4 headers as D or F.
  Cadastre-se para ver como corrigir isto
• 06
  FAIL · security

  Server Signature

  The Server header contains a generic name: "cloudflare". This is acceptable — the specific version is not exposed. The X-Powered-By header reveals the framework in use: "Express". This is a significant security risk — attackers gain information about the technology stack for targeted attacks.
  Cadastre-se para ver como corrigir isto
• 07
  FAIL · ai-readiness

  Structured Data Completeness

  No structured data (JSON-LD / Schema.org) found. AI search engines rely heavily on structured data to understand and cite content. Without it, your pages are much less likely to appear in AI-generated answers.
  Cadastre-se para ver como corrigir isto
• 08
  WARN · ai-readiness

  Knowledge Panel Readiness

  Partial knowledge-panel readiness — score 50/100. Missing components: Organization JSON-LD with ≥5 sameAs anchors, visible NAP (name/address/phone). Each missing piece reduces the chance of appearing in Google Knowledge Panel and AI-search citation anchors.
  Cadastre-se para ver como corrigir isto
• 09
  WARN · technical

  Viewport Meta Tag

  The viewport meta tag restricts user zoom capability (user-scalable=no). This creates accessibility issues — users with visual impairments will not be able to enlarge the content. Google may consider this a degraded user experience.
  Cadastre-se para ver como corrigir isto
• 10
  FAIL · performance

  Browser Caching

  Only 1 out of 4 caching headers found (Cache-Control). Missing: Expires, ETag, Last-Modified. Caching is virtually unconfigured, causing resources to be reloaded on every visit.
  Cadastre-se para ver como corrigir isto