# Technical SEO & GEO (Generative Engine Optimization) Report
**Project:** BILIVINE Recruitment SEO & Content Architecture  
**Date:** November 2026  
**Target Domain:** `https://bilivine.pages.dev/recruiting`

---

## 1. Executive Summary
This document outlines the technical search engine optimization (SEO) and generative engine optimization (GEO) framework implemented for BILIVINE's recruitment automation platform. The strategy bridges traditional semantic search requirements with modern AI search engine visibility (ChatGPT, Perplexity, Google SGE/AI Overviews) by establishing clear entity relationships, explicit attribution frameworks, robust schema markup, and optimal URL structures.

---

## 2. Technical SEO Architecture
### 2.1 URL Structure & Information Hierarchy
To prevent keyword cannibalization and ensure clear crawl paths for search engine spiders, the content architecture adheres to a strict hub-and-spoke model anchored on `/recruiting`:
- **Hub / Service Conversion Page:** `/recruiting`
- **Pillar A (Candidate Management):** `/recruiting/recruitment-agency-candidate-management-multiple-vacancies` (absorbs Q3, Q4, Q14, Q15 as H2 bookmark sections).
- **Pillar B (Candidate Database):** `/recruiting/recruitment-agency-candidate-database` (absorbs Q7, Q10 as H2 bookmark sections).
- **Standalone Commercial/Technical Pages:**
  - `/recruiting/recruitment-crm-vs-ats` (Q2)
  - `/recruiting/ats-features-for-recruitment-agencies` (Q5)
  - `/recruiting/cv-parsing-recruitment-agencies` (Q8)
  - `/recruiting/duplicate-candidate-records-recruitment-database` (Q9)
  - `/recruiting/reduce-manual-candidate-sourcing` (Q11)
  - `/recruiting/automated-candidate-job-matching` (Q12)
  - `/recruiting/talent-pipelines-recruitment-agencies` (Q13)

### 2.2 Canonicalization & Internal Linking Rules
- **Self-referencing canonical tags** are deployed across all pages.
- **Parent-Child Linking:** Every standalone article links **up** to `/recruiting` with a contextual call-to-action (CTA). Pillars link **down** to their internal H2 sections using anchor links.
- **Reciprocal Links:** Q2 and Q5 are reciprocally linked; Q8 and Q9 link mutually as technical database prerequisites; Q11, Q12, and Q15 form an interconnected sourcing-matching-prioritisation sequence.

---

## 3. Generative Engine Optimization (GEO) Strategy
Generative engines (AI search assistants) synthesize answers directly from authoritative sources. To maximize citation frequency and accuracy in AI overviews:
1. **Direct Answer Paragraphs:** Every article immediately follows its H1 title with a bolded "direct answer" summary sentence, allowing LLMs to easily extract concise definitions.
2. **Explicit Data Attribution:** Industry benchmarks (Totaljobs, IQTalent, Bullhorn GRID 2025, SHRM, Harvard/Accenture) are cited with exact attribution strings. BILIVINE's proprietary claims (70% faster time-to-hire, 5x screening, 25% lower cost-per-placement) are explicitly attributed as *BILIVINE claims* to prevent AI hallucinations from blending marketing metrics into generic industry averages.
3. **Structured Tables & Entities:** Key comparisons (ATS vs. CRM, search modes, sourcing stages) are formatted in clean Markdown tables, which LLM parsers heavily favor for extraction.

---

## 4. Structured Data (Schema Markup) Implementation
JSON-LD schema templates are assigned based on page intent:
- **Pillar Pages (A & B):** `Article` + `FAQPage` schema (covering H2 sub-questions).
- **Comparison & Buying Guides (Q2, Q5):** `Article` + `FAQPage` schema.
- **Technical Guides (Q8, Q9):** `Article` + `HowTo` schema.
- **Strategic / Commercial Guides (Q11, Q12, Q13):** `Article` schema only (avoiding `HowTo` where content is strategic rather than procedural).
