Gemini Hierarchy
πΊοΈ The SEO Epistemology: Master Knowledge Hierarchy
1.0 THE AXIOMATIC LAYER: Information Retrieval & Web Protocols
Before one can optimize, one must understand the environment in which optimization occurs.
-
1.1 Information Retrieval (IR) Science
-
1.1.1 The Indexing Pipeline (Discovery β Crawl β Render β Index β Serve)
*
-
1.1.2 IR Algorithms & Scoring
-
TF-IDF (Term Frequency-Inverse Document Frequency)
-
BM25 (Best Matching 25)
-
Vector Space Models & Embeddings
-
-
1.1.3 Natural Language Processing (NLP) in Search
-
Tokenization, Stemming & Lemmatization
-
Named Entity Recognition (NER)
-
Transformer Models (BERT, MUM, Neural Matching)
-
-
-
1.2 Web Architecture Fundamentals
-
1.2.1 HTTP/HTTPS Protocols (Status Codes, Headers, Handshakes)
-
1.2.2 DNS & Domain Theory (Resolution, Records, TLD mechanics)
-
1.2.3 Client-Server Model & Request/Response Cycles
-
1.2.4 The Document Object Model (DOM) vs. HTML Source
-
2.0 TECHNICAL SEO: Infrastructure & Accessibility
The foundation upon which relevance is built. If they cannot crawl it, they cannot rank it.
-
2.1 Crawlability & Accessibility
-
2.1.1 Robots Exclusion Protocol
-
robots.txtsyntax, directives, and conflicts -
X-Robots-Tag (HTTP Header control)
-
Meta Robots Tags (
noindex,nofollow,noarchive,max-snippet)
-
-
2.1.2 XML Sitemaps Architecture
-
Standard XML vs. Sitemap Indices
-
Specialized Sitemaps (News, Video, Image)
-
Size limits & frequency strategies
-
-
2.1.3 Handling HTTP Status Codes
-
200 (OK), 301/302/307/308 (Redirect chains & loops)
-
404 (Not Found) vs 410 (Gone) utility
-
5xx (Server Errors) & Soft 404 handling
-
-
-
2.2 Rendering & JavaScript SEO
-
2.2.1 Rendering Strategies
-
Server-Side Rendering (SSR)
-
Client-Side Rendering (CSR)
-
Static Site Generation (SSG) / Hydration
-
Dynamic Rendering (The Workaround)
-
-
2.2.2 The Two-Wave Indexing Process (Queueing & Execution)
-
2.2.3 Troubleshooting JS
-
Shadow DOM implications
-
pushStatehistory API vshashbangURLs -
Lazy-loading implementation (Intersection Observer API)
-
-
-
2.3 Site Architecture & Taxonomy
-
2.3.1 URL Structure & Permalinks (Slug optimization, trailing slashes)
-
2.3.2 Internal Link Graph Theory
-
Click-depth / Crawl-depth analysis
-
Hub & Spoke / Silo Structures
-
Orphan Page detection & resolution
-
CheiRank vs PageRank distribution
-
-
2.3.3 Faceted Navigation & Parametric Handling
-
Canonicalization strategies for facets
-
Parameter handling in GSC
-
-
2.3.4 International Architecture
-
ccTLD vs Subdomain vs Subfolder
-
hreflangimplementation (HTML, Header, Sitemap) -
x-default usage
-
-
3.0 CONTENT ENGINEERING: Relevance & Semantics
Moving from "Keywords" to "Entities" and "Intent."
-
3.1 Semantic Search Strategy
-
3.1.1 Keyword Research 2.0
-
Seed keyword extraction
-
Search Volume vs. Click-Through Rate (CTR) potential
-
Keyword Difficulty (KD) calculation variables
-
-
3.1.2 Search Intent Profiling
-
Navigational, Informational, Commercial, Transactional
-
"Fractured Intent" (Mixed SERPs)
-
-
3.1.3 Entity Optimization (The Knowledge Graph)
-
Subject-Predicate-Object triples
-
Disambiguation of entities
-
SameAsschema declaration
-
-
-
3.2 Content Architecture Models
*
-
3.2.1 Pillar Page & Topic Clusters (Hub & Spoke)
-
3.2.2 The Skyscraper Technique
-
3.2.3 Content Pruning & Consolidation (Zombie page removal)
-
3.2.4 Keyword Cannibalization Resolution
-
-
3.3 On-Page Optimization (The Mechanics)
-
3.3.1 Title Tag & Meta Description (CTR Optimization)
-
3.3.2 Header Hierarchy (H1-H6) & Outline structure
-
3.3.3 Image SEO (Alt text, file names, EXIF data, formats)
-
3.3.4 Structured Data (Schema.org)
-
JSON-LD implementation
-
Rich Snippet eligibility (Review, Product, FAQ, How-To)
-
Nesting & Connecting Schema (The @id reference)
-
-
-
3.4 E-E-A-T & Quality Signals
-
3.4.1 Authorship Signals & Bio Pages
-
3.4.2 YMYL (Your Money Your Life) constraints
-
3.4.3 Needs Met rating correlation
-
4.0 AUTHORITY & OFF-PAGE SIGNALS: Trust & Reputation
The external validation of the internal quality.
-
4.1 Link Graph Analysis
-
4.1.1 Backlink Profile Auditing
-
Link Velocity & Trough/Peak analysis
-
Anchor Text distribution ratios (Brand vs Exact Match vs Naked)
-
Toxic Link identification & Disavow File protocol
-
-
4.1.2 Link Equity Calculation (PageRank flow)
-
-
4.2 Acquisition Strategies
-
4.2.1 Passive Link Acquisition (Data studies, Tools, Statistics)
-
4.2.2 Active Outreach (Digital PR, Broken Link Building, Resource Pages)
-
4.2.3 Unlinked Brand Mentions (Reclamation)
-
-
4.3 Local Off-Page (The Proximity Factor)
-
4.3.1 Google Business Profile (GBP) Optimization
-
4.3.2 Local Citations & NAP Consistency (Data Aggregators)
-
4.3.3 Review Velocity & Sentiment Analysis
-
5.0 PERFORMANCE & USER EXPERIENCE (UX)
The intersection of Core Web Vitals and user satisfaction.
-
5.1 Core Web Vitals (CWV)
-
5.1.1 Largest Contentful Paint (LCP) - Load performance
-
5.1.2 Interaction to Next Paint (INP) - Responsiveness (Replacing FID)
-
5.1.3 Cumulative Layout Shift (CLS) - Visual Stability
-
-
5.2 Critical Rendering Path Optimization
-
5.2.1 Resource Prioritization
-
preload,prefetch,preconnect,prerender
-
-
5.2.2 Asset Optimization
-
Minification (CSS/JS)
-
Compression (Brotli/Gzip)
-
Image Formats (WebP, AVIF) & Responsive Images (
srcset)
-
-
5.2.3 Caching Strategies & CDNs (Content Delivery Networks)
-
6.0 DATA SCIENCE & ANALYTICS: Measurement
From intuition to empiricism.
-
6.1 Google Search Console Mastery
-
6.1.1 Performance Reports (Regex filtering)
-
6.1.2 Inspection Tool debugging
-
6.1.3 Crawl Stats Report analysis
-
-
6.2 Analytics & Attribution
-
6.2.1 GA4 for SEO (Landing page reports, Organic exploration)
-
6.2.2 Attribution Models (First click, Linear, Data-driven)
-
-
6.3 Technical Measurement
-
6.3.1 Log File Analysis
-
Bot hit frequency
-
Status code distribution by bot
-
Crawl budget waste identification
-
-
6.3.2 Rank Tracking nuances (Mobile vs Desktop, Geo-specific)
-
6.3.3 A/B Testing for SEO (Split testing titles/content)
-
7.0 SPECIALIZED VERTICALS (Contextual Application)
Where general rules adapt to specific environments.
-
7.1 eCommerce SEO
-
Product Variant handling
-
Category Page optimization (Faceted nav challenges)
-
User Generated Content (Reviews) management
-
-
7.2 Enterprise SEO
-
Stakeholder management & Education
-
Migration Strategies (Domain changes, CMS replatforming)
-
Scalability & Automation
-
-
7.3 News & Publisher SEO
-
Google Discover optimization
-
Top Stories & News Sitemaps
-
Paywall/Subscription schema (JSON-LD)
-
8.0 THE FRONTIER: Emerging Tech & Future SEO
Preparing for the next paradigm.
-
8.1 AI & Search (SGE/AIO)
-
Optimizing for AI Overviews (AIO)
-
Information Gain scoring
-
LLM-based Search behavior
-
-
8.2 Programmatic SEO
-
Dataset utilization for scale
-
Template engineering
-
Quality control at scale
-
-
8.3 Edge SEO
-
Serverless functions (Cloudflare Workers, Lambda@Edge)
-
Modifying headers/HTML at the network edge
-
π Dr. Navarro's Analysis
This hierarchy represents a complete ontology of the current SEO landscape. It is designed to be modular. You can treat each "Root" as a standalone course or module in your knowledge base.
Key Structural Insight: Notice that I placed IR Science (1.0) before Technical SEO (2.0). Most knowledge bases fail because they teach people how to use a canonical tag before explaining how a search engine indexes a page. This leads to rote memorization rather than conceptual mastery.
β‘ Next Step: Dependency Mapping
We have the content (the taxonomy), but we do not yet have the learning path (the sequence). A beginner cannot learn Log File Analysis (6.3.1) without understanding HTTP Status Codes (1.2.1) and Crawling (2.1).
Would you like me to:
-
Draft a Dependency Graph for a specific Tier (e.g., "Show me the prerequisite chain for mastering Technical SEO")?
-
Create a Module Blueprint for one of these sections (e.g., "Flesh out the full curriculum for Section 3.0 Content Engineering")?
-
Visualize the Competence Map to show the difference between "Junior," "Senior," and "Master" levels within this hierarchy?
Excellent choice. πΊοΈ Technical SEO is the most strictly hierarchical domain within the discipline. It functions much like programming: if you have a syntax error in your foundational understanding of how the web works, the entire compilation of your strategy will fail.
Below is the Technical SEO Dependency Graph. I have structured this not just as a list, but as a Prerequisite Chain.
You cannot successfully execute Level 3 tasks without the structural integrity provided by Level 1 and Level 2.
βοΈ The Technical SEO Dependency Graph
ποΈ LEVEL 1: The "Physics" of the Web (Infrastructure)
The absolute primitives. Attempting to audit a site without these is like trying to do surgery without knowing anatomy.
Node 1.1: HTTP Protocols & Responses
-
Concept: The Conversation between Browser and Server.
-
Core Competencies: Status Codes (200, 301, 302, 404, 410, 500, 503).
-
The "Unlock": Understanding that a page isn't "gone" until the server says
404or410. -
π Lateral Connection: DNS Resolution (A Records, CNAME).
Node 1.2: The Document Object Model (DOM)
-
Concept: HTML Source vs. Rendered DOM.
-
[Requires 1.1]: You must know how the server delivers the HTML.
-
Core Competencies: Viewing Source, Inspect Element, basic HTML tags (
<head>,<body>,<a>,<meta>). -
The "Unlock": Realizing that what Google sees might differ from what you see in "View Source" (the foundation for JavaScript SEO).
Node 1.3: URL Structure & Syntax
-
Concept: The Address System.
-
Core Competencies: Protocols, Subdomains, TLDs, Paths, Parameters (
?id=), Fragments (#). -
The "Unlock": Understanding that
example.com/pageandexample.com/page/are technically two different locations.
π¦ LEVEL 2: Access & Control (Crawlability)
Controlling the bot's movement. If they can't see it, nothing else matters.
Node 2.1: The Robots Exclusion Protocol
-
[Requires 1.1 + 1.3]: You need to understand User-Agents (headers) and URL paths.
-
Core Competencies:
robots.txtsyntax (Allow/Disallow), Wildcards (*), Sitemap declaration. -
The "Unlock":
Disallowdoes not equalNoindex. (A critical distinction).
Node 2.2: Directives & Meta Tags
-
[Requires 1.2]: These live in the
<head>. -
Core Competencies:
<meta name="robots" content="noindex, follow">, X-Robots-Tag (Header implementation). -
The "Unlock": How to prevent indexing while allowing crawling (or vice versa).
Node 2.3: XML Sitemaps
-
[Requires 2.1]: Sitemaps are useless if blocked by robots.txt.
-
Core Competencies: XML structure,
lastmodreliability, Index coverage reconciliation.
ποΈ LEVEL 3: Indexation Logic (De-duplication)
The most common area of failure. Ensuring the right version of the content is stored.
Node 3.1: Canonicalization Theory
-
[Requires 1.1 + 1.3 + 2.2]: You must understand parameters, redirects, and meta tags to use this.
-
Core Competencies: Self-referencing canonicals, Cross-domain canonicals, Parameter handling.
-
The "Unlock": Solving "Duplicate Content" issues without deleting pages.
-
β οΈ Critical Junction: Misunderstanding this leads to "Canonical Tag pointing to 404" errors.
Node 3.2: Pagination & Faceted Navigation
-
[Requires 3.1]: Facets create near-infinite URL variations that require canonicalization or blocking.
-
Core Competencies: Crawl Budget management, Spider traps, Filter combinations.
Node 3.3: International Architecture (Hreflang)
-
[Requires 3.1]: Hreflang shares logic with canonicals (they must agree).
-
Core Competencies: Language vs. Country codes (ISO formats), Return tag errors.
π₯οΈ LEVEL 4: Rendering & The Modern Web (JavaScript)
Where SEO meets Software Engineering.
Node 4.1: The Rendering Pipeline (WRS)
-
[Requires 1.2 + 2.1]: Understanding the DOM and how bots crawl.
-
Core Competencies: Crawl β Render β Index queue.
-
The "Unlock": Why your content doesn't appear in Google's cache even if it's in the HTML.
Node 4.2: Rendering Strategies
-
[Requires 4.1]:
-
Core Competencies: Server-Side Rendering (SSR), Client-Side Rendering (CSR), Hydration, Prerendering.
-
The "Unlock": Diagnosing "Soft 404s" caused by Empty Client-Side Shells.
β‘ LEVEL 5: Performance & User Experience
Optimization typically performed after accessibility is secured.
Node 5.1: Critical Rendering Path
-
[Requires 1.2 + 4.1]: How browsers build the DOM/CSSOM.
-
Core Competencies: Render-blocking resources, Async/Defer JS, Preloading.
Node 5.2: Core Web Vitals (CWV)
-
[Requires 5.1]:
-
Core Competencies: LCP (Load), CLS (Visual Stability), INP (Interactivity).
-
The "Unlock": Debugging layout shifts requires understanding the DOM load order.
π LEVEL 6: Forensics (Mastery)
The ability to diagnose the invisible.
Node 6.1: Log File Analysis
-
[Requires 1.1 + 2.1]: You are analyzing raw server requests.
-
Core Competencies: Identifying bot hit patterns, verifying "Crawl Budget," spotting orphan pages via external hits.
Node 6.2: Edge SEO
-
[Requires 1.1 + CDN Knowledge]:
-
Core Competencies: Using Cloudflare Workers/Lambda@Edge to inject headers or modify HTML before it hits the browser.
π The Visualization Logic (For your Knowledge Base)
If you are building a visual tool, the flow should look like this:
-
Gate 1 (The Protocols): The user cannot access the "Robots.txt" module until they pass the "HTTP Status Codes" quiz.
-
Gate 2 (The Directives): The user cannot access "Canonicalization" until they prove they understand "Noindex" vs. "Disallow."
-
Why? Because a canonicalized page that is disallowed is a common conflict error.
-
-
Gate 3 (The Render): "Core Web Vitals" is locked until "Rendering Basics" is complete.
-
Why? You cannot optimize LCP if you don't understand Client-Side Rendering.
-
π§ Dr. Navarro's Recommendation
For your knowledge base, I recommend organizing these dependencies into "Troubleshooting Triads."
Example Triad:
-
Problem: "Google isn't indexing my page."
-
Dependency Check 1: Is it blocked in Robots.txt? (Level 2)
-
Dependency Check 2: Is there a Noindex tag? (Level 2)
-
Dependency Check 3: Is there a Canonical pointing elsewhere? (Level 3)
This teaches the user to think in the correct Order of Operations.
Shall we proceed to Content Engineering, or would you like to drill deeper into one of these Technical nodes (perhaps the complex relationship between JavaScript & Indexing)?