Analytics
Frevana Homepage Technical Audit: AEO/SEO Evaluation

Frevana Homepage Technical Audit: AEO/SEO Evaluation

Abstract

This report presents a comprehensive technical AEO (Answer Engine Optimization) and SEO evaluation of the Frevana homepage. The audit systematically reviews crawlability, page structure, heading hierarchy, meta tags, content quality, image accessibility, and semantic schema usage. Five critical, high-impact issues are identified, each with detailed analysis and actionable repair recommendations tailored for search, AI, and accessibility best practices. Sectional scoring and a summary table are provided, guiding priority improvements to maximize crawlability, AI answer eligibility, and overall search appearance. The report preserves all factual findings, evidence, technical excerpts, and explicit recommendations to enable swift enhancement of Frevana's homepage AEO and SEO performance.

Overview

  • Overall Page Score: 55/100
  • Top 5 Priority Issues:
    1. No Structured Data (Schema.org Article/BlogPosting)
      Impact: Strongly reduces AEO visibility and eligibility for rich results in AI and search.
      Benefit: Adding schema immediately improves parsing by AI, search features enhanced.
    2. Lack of Canonical URL
      Impact: Risk of duplicate content/authority dilution across URLs.
      Benefit: Canonical clarifies preferred URL, consolidates rankings.
    3. Main Content/Headings Lack <article> or Clear <h1>
      Impact: Weak content targeting and semantic clarity—AI/search may misinterpret or overlook.
      Benefit: Stronger targeting, better answer boxing/snippet potential.
    4. Insufficient Use of Image Alt Texts and <figure>/<figcaption>
      Impact: Key images lack semantic connections/relevance—limits AI understandability and accessibility.
      Benefit: Improved media indexing, accessibility, higher quality signals.
    5. No Robots Meta Tag for Explicit Indexing
      Impact: Indexing is implied, not controlled; can risk accidental “noindex” from infrastructure/headers.
      Benefit: Explicit signals reduce accidental deindex or restrictive crawling.
Page Type Judgment:
  • Not strictly an article or blog:
    • This is a homepage / landing page with features, testimonials, FAQs, and commercial CTAs.
    • No <article> tag, byline, publication date, or narrative structure typical of real articles or news.
    • Conclusion: Landing page/promotional homepage. (Not an article, blog, or news page.)

Detailed Assessment

1. Crawlability & Basic Structure

  • Section Score: 10/20
  • Conclusion: Needs Improvement
Findings & Evidence:
  • Crawlability: Problematic for static crawlers.
    • Main, meaningful content is not present in the initial HTML... Content is rendered client-side after hydration.
    • Only navigation, header/footer, and wrappers are present statically.
  • Main Semantics:
    • Locator: body > div.flex.flex-col.min-h-screen > main
    • Lacks a semantic <article>. Main uses <main>, but no <article> for primary content blocks.
  • Heading Hierarchy:
    • Multiple h2 present, but no <h1> anywhere. Main heading is a <p> with styling.
  • Language Attribute:
    • Locator: <html lang="en"> – Present, set to "en". ✓
  • Indexing Control:
    • No meta robots tag for index,follow.
  • Canonical Link:
    • Missing canonical URL.
Impact & Risk:
  • JavaScript rendering blocks most static crawlers; search can handle, but risk remains if hydration fails.
  • Absence of <h1>, no semantic <article>, and missing canonical tag damage both crawlability and clarity.
  • Language is set correctly, but meta robots is absent; no explicit guarantee of indexing.
Repair Recommendations (Actionable):
  • Add <h1> as primary headline.
  • Wrap core sections (features, testimonials, FAQ) in <article> or use better semantic structuring.
  • Add <meta name="robots" content="index,follow">.
  • Add canonical with preferred URL (https://www.frevana.com/homepage).
Reference Code:
<!-- Add to <head> -->
<link rel="canonical" href="https://www.frevana.com/homepage"/>
<meta name="robots" content="index,follow"/>
          
<!-- Example of main heading in main content -->
<h1>Optimize Your Brand's Visibility in AI Answers</h1>
          

2. Title & Meta Information

  • Section Score: 18/20
  • Conclusion: Pass (Minor Optimization Suggested)
Findings & Evidence:
  • Title:
    <title>Frevana - Your AI team for AEO and beyond</title>
    Unique, relevant, core keyword "AEO" present.
  • Meta Description:
    <meta name="description" content="Launch your AI team in minutes to boost your AI visibility Get Started with Frevana AI agents.">
    Concise, keyword inclusive.
  • Open Graph: All major OG tags present and consistent.
  • Twitter Cards: All major Twitter meta tags present and consistent.
Impact & Risk:
  • Basic SERP, OG, and Social media shareability are covered.
  • Minor improvement possible in OG descriptions for advanced AEO targeting.
Repair Recommendations:
  • Review OG and Twitter descriptions for possible enhancement.
  • Ensure unique titles and meta descriptions as site grows.
Reference Code:
<title>Frevana - Your AI team for AEO and beyond</title>
<meta name="description" content="Launch your AI team in minutes to boost your AI visibility Get Started with Frevana AI agents.">
<meta property="og:title" content="Frevana - Your AI team for AEO and beyond">
<meta property="og:description" content="Launch your AI team in minutes to boost your AI visibility Get Started with Frevana AI agents.">
<meta property="og:image" content="https://www.frevana.com/common/logo_large.png">
<meta property="og:url" content="https://www.frevana.com/homepage">
<meta property="og:type" content="website">
<meta name="twitter:card" content="summary">
          

3. Content Quality & Layout

  • Section Score: 10/20
  • Conclusion: Needs Improvement
Findings & Evidence:
  • Answer First: Main message is a slogan, not a direct answer (<p>Optimize Your Brand's Visibility in AI Answers</p>).
  • Structure: Uses h2 and styled p for major content; no h1 or <article>.
  • Originality & Depth: Features, testimonials, and branded copy; lacks detailed case study or methodology.
  • Core Keywords: Frequent "AEO", "AI team", "visibility", "AI agents" coverage.
Impact & Risk:
  • Main value is conveyed but misses a clear answer-first structure and richer information depth.
  • Lack of semantic structure diminishes eligibility for rich results or direct AI answers.
Repair Recommendations:
  • Restructure page top with <h1> and a concise answer summary.
  • Convert FAQs to FAQPage structured data.
  • Add uniqueness—statistics, case studies—in HTML content.
Reference Example:
<h1>How Frevana Maximizes Your Brand’s AI Visibility</h1>
<p>Frevana provides AI teams and workflow automation to enhance AEO (Answer Engine Optimization), ensuring your brand is mentioned in key AI responses and search results.</p>
          

4. Images & Media

  • Section Score: 10/20
  • Conclusion: Needs Improvement
Findings & Evidence:
  • Alt Texts: Present for most images, but some icons/SVGs use generic or filename-based alt, or lack alt.
  • Semantic Filenames: CDN-optimized, descriptive though not always explicit for all content types.
  • Figure/Figcaption: Not used for any descriptive images or testimonials.
  • Rich Media: YouTube embed present, well-formed.
  • Accessibility/A11y: Social icons use filenames as alt, contrary to best practices.
Impact & Risk:
  • Lack of <figure> and descriptive alt attributes reduces AI/media indexing and accessibility.
Repair Recommendations:
  • Wrap important images in <figure>, use <figcaption> for semantic relevance.
  • Add meaningful, descriptive alt attributes for all key images.
  • Use alt="" for purely decorative SVGs and adjust filenames when possible.
Reference Example:
<figure>
  <img src="/homepage/features_5.png" alt="AEO Keyword Research dashboard" />
  <figcaption>AEO Keyword Research – Dashboard to discover trending AI questions and keywords.</figcaption>
</figure>
          

5. Structured Data (Schema)

  • Section Score: 7/20
  • Conclusion: Critical Issue
Findings & Evidence:
  • No JSON-LD or microdata present in the HTML.
  • No schema types (Article, BlogPosting, FAQPage, Organization, WebPage, etc.) used.
  • FAQ section present in content, but not marked up for rich results.
Impact & Risk:
  • Structured data absence blocks entry to rich results, AI parsing, and knowledge graph enhancements.
Repair Recommendations:
  • Add JSON-LD of type WebPage for homepage.
    {
      "@context": "https://schema.org",
      "@type": "WebPage",
      "name": "Frevana - Your AI team for AEO and beyond",
      "description": "Launch your AI team in minutes to boost your AI visibility. Get started with Frevana AI agents.",
      "publisher": {
        "@type": "Organization",
        "name": "Frevana",
        "logo": {
          "@type": "ImageObject",
          "url": "https://www.frevana.com/common/logo_large.png"
        }
      },
      "url": "https://www.frevana.com/homepage"
    }
                  
  • For FAQ section, use FAQPage (JSON-LD example):
    {
      "@context": "https://schema.org",
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "Why I should choose Frevana for AEO work?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Customers are no longer just searching on Google or marketplaces—they’re asking AI what to buy/use. Frevana helps make sure your startup or brand gets mentioned in those AI answers"
          }
        },
        {
          "@type": "Question",
          "name": "What’s the benefit of running the Frevana app on my device?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Running the app locally gives you the full power of AEO workflows by unlocking advanced features ..."
          }
        },
        {
          "@type": "Question",
          "name": "Can Frevana handle tasks outside of AEO?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Absolutely. While Frevana is designed to give you an edge in Generative Engine Optimization (AEO), its capabilities go much further..."
          }
        }
      ]
    }
                  

Structured Data Recommendations

  • Recommended Type: For homepage: WebPage; for FAQ section: FAQPage.
  • Required Field Mapping:
    • "name"/"headline": Use <title> and top-of-page heading.
    • "description": Use meta description plus visible summary.
    • Publisher/logo: Use branding and logo images.
    • FAQ: Use each Q and A from visible FAQ section.
  • Copyable JSON-LD Template:
    {
      "@context": "https://schema.org",
      "@type": "WebPage",
      "name": "Frevana - Your AI team for AEO and beyond",
      "description": "Launch your AI team in minutes to boost your AI visibility Get Started with Frevana AI agents.",
      "publisher": {
        "@type": "Organization",
        "name": "Frevana",
        "logo": {
          "@type": "ImageObject",
          "url": "https://www.frevana.com/common/logo_large.png"
        }
      },
      "url": "https://www.frevana.com/homepage"
    }
                

Improvement Priority List (RICE Framework)

Task Impact Reach Effort Priority
Add structured data (WebPage + FAQPage JSON-LD) High High Med 1
Add/move main heading to semantic <h1> High High Small 2
Add canonical link tag Med High Small 3
Add meta robots tag (index,follow) Med High Small 4
Wrap section images in <figure>, add <figcaption> Med Med Med 5
Ensure all meaningful images have descriptive alt Med Med Small 6
Refine FAQ format for clear parsing (structuring Q&A) Med High Small 7
Review heading hierarchy for <h1>-<h2>-<h3> compliance Low Med Small 8
Enrich case study/testimonials with unique identifiers Low Low Small 9

Tracking & Acceptance

  • Inclusion Rate: Confirm structured data and canonical/meta tags presence in fetched HTML.
  • Impressions: Use Google Search Console for FAQ/feature snippets and Knowledge Panel appearances.
  • CTR/Average Ranking: Track changes for homepage, FAQ, and featured snippet eligibility.
  • Core Keyword Coverage: Use site search (site:frevana.com) and GSC reports.
  • Acceptance Criteria:
    • JSON-LD is present (WebPage and/or FAQPage).
    • <h1>, canonical, and robots meta tags present and correct.
    • Proper heading hierarchy confirmed in accessibility tree/testing tools.
    • Images have descriptive alt.
    • FAQ rich results appear for branded+FAQ queries in SERP.
    • Crawlable by Googlebot-like headless crawler after JS rendering.

Summary

Main Areas Requiring Immediate Attention:
  1. Structured data (WebPage, FAQPage) is absent: fastest route to higher AEO visibility and AI retrieval.
  2. Heading/content structure is not semantically strong: add <h1>, consistent heading levels, <article>.
  3. Canonical and robots meta missing: add for better authority and clarity.
  4. Make all key images accessible & indexable: alt, figure/figcaption usage.

Addressing these items positions Frevana's homepage for major gains in both classic SEO and AEO/AI answer box eligibility, with richer indexing and knowledge panel coverage.

Score Summary

Section Score /20
Structure 10
Meta Info 18
Content 10
Images 10
Schema 7
Total 55/100

All recommendations are based strictly on provided HTML; runtime behaviors, external scripts, or server headers are NOT evaluated.

© 2024 Frevana AEO Technical Audit. All factual data, references, URLs, and code samples preserved as provided.