Analytics
AEO and SEO Evaluation of Mokahr.io Homepage

AEO and SEO Evaluation of Mokahr.io Homepage

Abstract

This report presents a comprehensive evaluation of the AEO (Answer Engine Optimization) and SEO (Search Engine Optimization) aspects of the https://www.mokahr.io homepage. The assessment considers technical, structural, and semantic features affecting crawlability, indexability, structured data, heading hierarchy, media accessibility, and eligibility for rich search results. A detailed breakdown of audit scores, priority technical issues, and actionable remediation suggestions is provided, alongside suitability recommendations for structured data strategy and content markup improvements. Findings are organized by major SEO/AEO area, providing prioritized action steps and acceptance criteria for measurable improvement.

Evaluation Overview

  • Overall Page Score: 73/100

Top 5 Priority Issues

  1. Missing JSON-LD (Structured Data/Schema.org)
    • Impact: Search engines cannot fully understand or feature the page as an “Article” or “Product”; limits eligibility for rich results.
    • Benefit: Enhances eligibility for result enhancements (e.g., carousels, snippet cards).
  2. No Visible <article> Element or Explicit Article Semantics
    • Impact: Reduces semantic clarity for crawlers and accessibility tools, may limit recognition as an "article" or main content block.
    • Benefit: Improves SEO structure and can boost trust signals.
  3. Main Content Not in Visible Headings (<h1> etc.)
    • Impact: Main title and sections are in a .sr-only container; reduces keyword prominence for standard browsers/crawlers.
    • Benefit: Improving heading visibility would increase on-page SEO scoring and answer extraction for AEO.
  4. Partial Image Semantics
    • Impact: Some images well described; others (likely decorative) have empty or non-descriptive alt text—opportunity for richer results via more <figure>/<figcaption>.
    • Benefit: Better image search ranking, accessibility, and AEO trust signals.
  5. No Indexing (robots) Meta Present
    • Impact: Indexing control is undefined; default is index, but explicit control is best for large-scale AEO/SEO.
    • Benefit: Reduces accidental de-indexing and enables fine-grained control.

Page Type Judgment: Landing/Marketing Page (not pure Article/Blog/News)
Reason: The content is product-focused, not classic news/blog article, lacking schema, author/date, or explicit article format. Headings and content style are promotional, not chronological or news-style.

1. Crawlability & Basic Structure

  • Section Score: 15/20
  • Conclusion: Needs Improvement

Findings & Evidence

  • HTML Language Attribute
    Locator: <html lang="en-US">
    Snippet: <html lang="en-US"> Pass
  • Canonical Link
    Locator: <head> > link[rel="canonical"]
    Snippet: <link rel="canonical" href="https://www.mokahr.io/"> Pass, unique
  • Meta Robots
    Locator: <head>
    Not found: No <meta name="robots"> found.
    Should be explicit for indexability.
  • Main Content Semantics
    Locator: <main>, inside: .sr-only h1, but actual visible content in styled divs.
    Snippet: <main><div class="sr-only"><h1>AI-Powered Hiring Trusted by 1,000,000 HR Professionals</h1>...
    Issue: Main headline is “sr-only” (screen-reader only), not visible for users/crawlers using rendered DOM; no explicit <article> element.
  • Heading Hierarchy
    Locator: .sr-only h1 (unique), multiple .sr-only h2, .sr-only h3
    Pass on uniqueness but issue on visibility.
  • Page Structure
    Uses <main>, <header>, <footer>, and nav HTML5 sections.
    No <article> tag.

Impact & Risk: Crawlers will index core meta, canonical, and see accessibility titles, but main semantic points are visually hidden. This may hamper AEO/SEO for question-answer, SERP snippets, and reduce topical confidence. Lack of robots meta can cause accidental noindexing or issues for scaled deployments.

Repair Recommendations (Actionable)

  • Move main <h1> out of .sr-only into a visible element.
  • Add meta name="robots" with proper value (index,follow) to <head>.
  • Wrap main visible content with an <article> tag where appropriate.
  • Optionally supplement with ARIA roles for improved screen reader and crawler clarity.

Reference Code

<!-- Add to <head> -->
<meta name="robots" content="index,follow">
          
<!-- Example: move h1 to visible, semantic context -->
<main>
  <article>
    <h1>AI-Powered Hiring Trusted by 1,000,000 HR Professionals</h1>
    <!-- ...rest of the content... -->
  </article>
</main>

2. Title & Meta Information

  • Section Score: 19/20
  • Conclusion: Pass

Findings & Evidence

  • Title Tag
    Locator: <title>
    Snippet: <title>AI-Powered HR and Recruitment Software with ATS | Moka</title>
    Unique, clear, length ~55 chars, main keywords present.
  • Meta Description
    Locator: <meta name="description">
    Snippet: content="MokaHR is the most trusted AI-powered Applicant Tracking System and HR software, helping 2,000+ global brands automate recruiting and HR workflows."
    Length: ~146 chars, clear summary, keywords present.
  • Open Graph
    og:title, og:description, og:image, og:url all mapped to core content.
    <meta property="og:image" content="https://www.mokahr.io/wp-content/uploads/2026/09/Moka_logo.png?v=2.0">
    <meta property="og:url" content="https://www.mokahr.io/">
  • Twitter Cards
    All required twitter:card meta present and mapped.

Impact & Risk: Excellent for SERP enhancement and social sharing. Passes core AEO/SEO meta checks. Risk: None.

Repair Recommendations

No critical fixes, but confirm ongoing maintenance for title/meta as product offering evolves.

3. Content Quality & Layout (Answer Priority)

  • Section Score: 14/20
  • Conclusion: Needs Improvement

Findings & Evidence

  • Answer First / Direct Answer Structure
    Actual heading is hidden (.sr-only h1); above-the-fold banner text provides intent.
  • Clear Structure
    Subheadings, lists, testimonials present but mainly styled div/span, not semantic headings.
  • Originality & Depth
    Includes unique testimonials, metrics ("Reduced manual resume review time by 70%"), and benchmarks ("40% faster time-to-hire").
  • Keyword Presence
    Core phrases are included; no evidence of keyword stuffing.

Impact & Risk: Lacks visible semantic headings, which can reduce answer extraction, featured snippet eligibility, and clarity for search engines.

Repair Recommendations

  • Use visible <h2>, <h3> tags for all key article/product sections.
  • Move unique claims and metrics into structured formats (e.g., <dl> for value propositions).
  • Consider FAQPage schema for customer Q&A if applicable.

4. Images & Media

  • Section Score: 13/20
  • Conclusion: Needs Improvement

Findings & Evidence

  • alt Texts
    Most feature screenshots, avatars, logos have descriptive alt; some images have empty or overly generic alt attributes.
  • Semantic Filenames
    Filenames are descriptive and contextually meaningful ("header_image_01.png", "Client_logo_01.png").
  • Image-Text Relationship
    No use of <figure>/<figcaption> for testimonials or standout graphics.

Impact & Risk: Images provide some SEO/AEO benefits via alt and filenames, but semantic grouping (figure/caption) and more descriptive alt text would improve accessibility and rich result eligibility.

Repair Recommendations

  • Use <figure> and <figcaption> for key testimonials, graphics, or data visualizations.
  • Expand all meaningful image alt text; use alt="" for decorative images.

Reference Code

<figure>
  <img src="/wp-content/uploads/2026/09/card_header_image/Avatar.png" alt="Sarah Collins, Talent Acquisition Director, Global E-commerce Company">
  <figcaption>"Moka HR's AI screening reduced our manual resume review time by 70%..."</figcaption>
</figure>

5. Structured Data (Schema)

  • Section Score: 12/20
  • Conclusion: Needs Improvement

Findings & Evidence

  • JSON-LD Presence: Not found.
  • Type & Completeness: No schema types (Article, Product, FAQPage, etc.) provided.
  • Field Coverage: Headline, meta, image, and publisher can be mapped from visible page content; no explicit author or date present.

Impact & Risk: Absence of schema reduces eligibility for enhanced search results and structured answer extraction.

Repair Recommendations (Actionable)

  • Add JSON-LD using at least @type: WebPage or Product.
  • Map key fields: headline, publisher, image, canonical URL; supply author/date if possible.
  • Add FAQPage schema when clear Q&A content is available.

Reference Code

{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "headline": "AI-Powered HR and Recruitment Software with ATS | Moka",
  "image": ["https://www.mokahr.io/wp-content/uploads/2026/09/Moka_logo.png?v=2.0"],
  "publisher": {
    "@type": "Organization",
    "name": "MokaHR",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.mokahr.io/wp-content/uploads/2026/09/Moka_logo.png?v=2.0"
    }
  },
  "mainEntityOfPage": "https://www.mokahr.io/"
}

If author and publication date are available, they should be mapped in the schema. For FAQPage or HowTo, provide when content supports it.

Improvement Priority List (RICE Framework)

Task Impact Reach Effort Priority
Add JSON-LD structured data (WebPage/Product/Article type) High High Small 1
Move main <h1> heading out of .sr-only into visible flow High High Small 2
Add explicit <meta name="robots" content="index,follow"> High High Small 3
Add <article> around main readable content Medium High Small 4
Use visible <h2>/<h3> tags for main sections Medium Medium Small 5
Add <figure>/<figcaption> for testimonials/images Medium Medium Small 6
Expand image alt text for context, use blanks for decor. Low Medium Small 7
Add or map datePublished, author fields (if applicable) Medium Low Medium 8
Periodic review of title/OG/meta length/content Low Medium Small 9

Tracking & Acceptance

Item Indicator Acceptance Criteria
JSON-LD added Google Rich Results Test, code presence Passes test, info accurate and discoverable
h1 visible h1 shown outside .sr-only, visible in DOM Headline appears in viewport, not hidden
robots meta present <meta name="robots"> in HTML Tag present with "index,follow"
<article> present <article> wraps main content Article tag visible in DOM, contains primary content
Heading structure <h2>/<h3> used for visible sections Each major block starts with semantic heading
Images semantically grouped <figure>/<figcaption> in HTML Key images/testimonials grouped, captions shown
Image alt improvements Descriptive alt attributes for main images No critical image has missing/empty alt
Author/date present (if applicable) Schema.org/visible text Fields filled and mapped to page footer or byline

Expected Change: Improved site eligibility for Google/Bing rich results and answer box; improved AEO (Answer Engine Optimization) signals; increased click-through rate on branded/product queries.