ikigai-test.online

Mostrando los 9 problemas principales. La auditoría completa con correcciones a nivel de código está disponible en el plan gratuito.

• 01
  FAIL · content

  Thin Content

  The page contains almost no text (0 words). This is critically insufficient for search engine indexing. Text-to-HTML ratio: 0%. Such pages may be classified as doorway pages or empty shells and excluded from search results.
  Regístrate para ver cómo corregir esto
• 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.
  Regístrate para ver cómo corregir esto
• 03
  FAIL · onpage

  Content Length

  Only 0 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.
  Regístrate para ver cómo corregir esto
• 04
  FAIL · security

  Email Authentication (SPF / DMARC / DKIM)

  SPF: pass · DMARC: fail · DKIM: info. Missing or broken: DMARC. Without SPF/DKIM/DMARC, your emails are likely flagged as spam by Gmail/Outlook, and your domain can be spoofed by phishers.
  Regístrate para ver cómo corregir esto
• 05
  FAIL · security

  Security Headers Grade (Mozilla Observatory)

  Security grade F (20/100 baseline, Mozilla Observatory rubric). Top issues: Content-Security-Policy header missing (-25); Strict-Transport-Security missing (-20); X-Frame-Options + CSP frame-ancestors both missing (-20)
  Regístrate para ver cómo corregir esto
• 06
  FAIL · ai-readiness

  Knowledge Panel Readiness

  Low knowledge-panel readiness — score 0/100. AI search engines and Google Knowledge Panel cannot confidently identify this brand. The cheapest, fastest fixes are: (1) add Organization JSON-LD with a sameAs chain (Wikipedia, Wikidata, LinkedIn, Crunchbase, GitHub, social), (2) make NAP (Name/Address/Phone) visible in the footer or contact page, (3) create a Wikidata entry (low notability bar), then (4) pursue Wikipedia once notability is established.
  Regístrate para ver cómo corregir esto
• 07
  FAIL · security

  Security Headers

  Only 0 out of 6 modern security headers found. Missing: x-frame-options, x-content-type-options, strict-transport-security, content-security-policy, 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.
  Regístrate para ver cómo corregir esto
• 08
  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.
  Regístrate para ver cómo corregir esto
• 09
  WARN · onpage

  Heading Hierarchy

  No headings (H1–H6) were found on the page. Headings help search engines and users understand the structure of your content.
  Regístrate para ver cómo corregir esto