FeedTheJoeTHATDEVELOPERGUY LLC Search everything Explore
THE LIBRARYFind your wayTap a place to move there
You are hereEntrance
Open the book · read a library volume
Select a cabinet to look closer
The librarySEO · AEO · AIO · GEO knowledge baseSwipe to explore · Tap a cabinet to step closer
The library

178 volumes. 8 shelves. Knowledge you can open, read, cross-reference and put to work.

Explore the room

Choose your next discovery

Enter this section
The library The library

The knowledge collection

The library

The SEO / AIO 26-Discipline Library: 178 volumes across 8 shelves. Open a volume, follow its references and check its review stamp. Release 2026.09.12-g40.

Answers: What is in the SEO / AIO 26-Discipline Library and how is it organised?

  • 91 current
  • 41 researched
  • 9 reference
  • 2 baseline
  • 35 workbench

Review labels distinguish current guidance, researched designs, reference documents, historical baselines and workbench drafts. A researched design is not evidence that a system is deployed.

Operating model

How the 26 disciplines work as one accountable system: routing, handoffs, acceptance, integration, decision ownership.

19 volumes — browse this shelf
  1. 01Instructions for AI-assisted use of this library
  2. 02Change log
  3. 03Operating model — separate expertise, one accountable system
  4. 04Master routing protocol — choose the right specialist before acting
  5. 05Handoff contracts — preserve evidence across specialties
  6. 06Acceptance and independence — what a pass actually means
  7. 07Build public expertise from the internal discipline library
  8. 08Integrate the discipline library into an actual AI coding project
  9. 09Decision ownership and conflicting-repair matrix
  10. 10Full-audit coverage without launching 26 uncontrolled agents
  11. 11The 26-discipline operating library
  12. 12SEO / AIO Library — 26-Discipline Edition
  13. 1326-discipline validation — actual local results
  14. 1426-Discipline Expansion — Research and Delivery Report
  15. 15Discipline gap map
  16. 16Discipline expansion — primary-source register
  17. 17Discipline-library integration snippet
  18. 18Discipline templates
  19. 19Discipline utilities — executable scope and limitations
Open the full shelf

Role charters

The 26 specialist charters — accountable responsibility, activation, diagnostic sequence, evidence, acceptance, failure modes.

26 volumes — browse this shelf
  1. 01R01 — Site Reliability Engineer
  2. 02R02 — Network/DNS Engineer
  3. 03R03 — Backend Web Engineer
  4. 04R04 — Frontend Web Engineer
  5. 05R05 — Browser Compatibility Engineer
  6. 06R06 — Web Performance Engineer
  7. 07R07 — Accessibility Specialist
  8. 08R08 — Technical SEO Engineer
  9. 09R09 — Information Architect
  10. 10R10 — Search Relevance/IR Engineer
  11. 11R11 — Structured Data/Knowledge Graph Engineer
  12. 12R12 — AEO/AIO/GEO Engineer
  13. 13R13 — Content Strategist/SEO Editor
  14. 14R14 — Fact-Checker/Claims Auditor
  15. 15R15 — Conversion-Rate Optimization Specialist
  16. 16R16 — Analytics/Measurement Engineer
  17. 17R17 — Email Deliverability Engineer
  18. 18R18 — Local SEO/GBP Specialist
  19. 19R19 — Digital PR/Authority Specialist
  20. 20R20 — Application Security/Privacy Engineer
  21. 21R21 — QA/SDET Engineer
  22. 22R22 — Adversarial/Red-Team Reviewer
  23. 23R23 — Product Marketing/Market Researcher
  24. 24R24 — Solutions Architect/Integrator
  25. 25R25 — Release/Change Manager
  26. 26R26 — Independent Acceptance Engineer
Open the full shelf

Cross-discipline playbooks

End-to-end procedures that cross several charters, with the evidence each step must leave behind.

9 volumes — browse this shelf
  1. 01Bubbles: outside-in availability and public reachability
  2. 02Contact form to actual mailbox: an end-to-end evidence chain
  3. 03From public delivery to useful answers and observed AI citations
  4. 04Browser and accessibility regressions across a complete task
  5. 05Improve measured performance without damaging the website
  6. 06Turn verified work into a public expertise asset
  7. 07Coordinate hostname, URL and content migrations
  8. 08Preflight, controlled release and fresh acceptance
  9. 09Cross-discipline playbooks
Open the full shelf

Reference modules

Researched guidance and preserved baseline material; each document states its own review status.

47 volumes — browse this shelf
  1. 01Agent access, MCP and security boundaries
  2. 02AI answer observation and controlled evaluation
  3. 03AI referrals, analytics channels and qualified outcomes
  4. 04AI citation engineering — controllable inputs and observable outcomes
  5. 05Google AI Overviews and AI Mode — eligibility, controls and measurement
  6. 06Bing AI Performance and citation-share interpretation
  7. 07Client scope, tier applicability and acceptance
  8. 08Commerce data consistency across page, feed and structured data
  9. 09Content delivery first — without false crawler absolutes
  10. 10Crawl payload budgets and content delivery
  11. 11Crawler identity, logs and safe edge access
  12. 12Engine-specific discovery, training and user-access controls
  13. 13Evidence governance and claim authorization
  14. 14Faceted navigation and crawl-space control
  15. 15Field performance and interaction acceptance
  16. 16GA4 implementation — current AI channels, scopes and outcome quality
  17. 17Google generative AI performance: current reporting contract
  18. 18Search Console analysis — current reports and defensible diagnostics
  19. 19Titles, descriptions and preview copy without false limits
  20. 20Location-page evidence and genuine local utility
  21. 21SEO library — canonical master index
  22. 22Migration contract, checkpoints and rollback
  23. 23Next.js metadata, streaming and rendering validation
  24. 24Next.js SEO implementation — versioned route contracts
  25. 25Preferred Sources and publisher relationship design
  26. 26Regional Search eligibility and policy differences
  27. 27Research maintenance and documentation drift control
  28. 28Structured-data lifecycle and feature eligibility
  29. 29Schema types in 2026 — semantic validity versus search features
  30. 30ChatGPT Search — publisher access and measured referrals
  31. 31SEO release contracts and reproducible acceptance tests
  32. 32Social and video platform properties in Search Console
  33. 33First-party facts, provenance and reusable evidence
  34. 34Search spam policy — scoped interpretation and operational controls
  35. 35URL lifecycle, canonical decisions and safe retirement
  36. 36SEO build reference: intake to production evidence
  37. 37Universal Search Delivery Framework — not a ranking formula
  38. 38Executed validation — 2026.09.09
  39. 39SEO library audit and research update
  40. 40Coverage matrix — every unique original
  41. 41Findings and dispositions
  42. 42Remaining review queue and explicit limits
  43. 43Primary-source register
  44. 44Tier applicability and deliverable map
  45. 45Schema examples — fictional, not deployable as supplied
  46. 46Implementation templates
  47. 47Offline tools and test scope
Open the full shelf

Graph systems

Forty selected graph types, representations and practical views over one source-linked data model — a researched expansion (2026-09-12) with its source register; designs, not deployed systems.

43 volumes — browse this shelf
  1. 01Graph systems — research and implementation expansion
  2. 02G01 — Personal identity and profile graph
  3. 03G02 — Organization, business, and brand graph
  4. 04G03 — Cross-domain operating and ownership graph
  5. 05G04 — Entity resolution and reconciliation graph
  6. 06G05 — Local business, place, and service-area graph
  7. 07G06 — Product, offer, merchant, and inventory graph
  8. 08G07 — Authorship and editorial contribution graph
  9. 09G08 — Topic, ontology, and taxonomy graph
  10. 10G09 — Document, passage, and entity graph
  11. 11G10 — Claim, evidence, and provenance graph
  12. 12G11 — E-E-A-T evidence graph
  13. 13G12 — Reputation, review, and corroboration graph
  14. 14G13 — Internal link and navigation graph
  15. 15G14 — External web-link graph
  16. 16G15 — Citation, co-citation, and bibliographic-coupling graph
  17. 17G16 — Canonical and duplicate-document graph
  18. 18G17 — Redirect and migration graph
  19. 19G18 — Hreflang and locale-alternative graph
  20. 20G19 — Crawl, rendering, and resource-dependency graph
  21. 21G20 — Structured-data consistency graph
  22. 22G21 — Query, intent, and page-relevance graph
  23. 23G22 — SERP observation and competitor-overlap graph
  24. 24G23 — Question, task, and query-fan-out map
  25. 25G24 — Entity-mention and co-occurrence graph
  26. 26G25 — AI answer, grounding, and citation graph
  27. 27G26 — Search-to-lead and customer-journey graph
  28. 28G27 — GraphRAG and owned-corpus retrieval graph
  29. 29G28 — Embedding-similarity and nearest-neighbor graph
  30. 30G29 — Temporal, version, and supersession graph
  31. 31G30 — Contradiction, uncertainty, and dispute graph
  32. 32G31 — Source-dependency and change-impact graph
  33. 33G32 — Instruction, capability, and workflow dependency graph
  34. 34G33 — Requirement, test, evidence, and acceptance graph
  35. 35G34 — Permissions, consent, and disclosure graph
  36. 36G35 — Multimedia, transcript, and rights graph
  37. 37G36 — Open Graph social-preview metadata
  38. 38G37 — Social, professional, and interaction graphs
  39. 39G38 — Scholarly and research graph
  40. 40G39 — Event, venue, organizer, and time graph
  41. 41G40 — Learning prerequisite and curriculum graph
  42. 42Primary source register (S01–S49)
  43. 43Synthetic public JSON-LD example and claim record template — not production
Open the full shelf

Publication briefs

Public-content briefs for each discipline — a reader question, a distinct contribution, and the proof required before publishing.

26 volumes — browse this shelf
  1. 01R01 public-content brief — Why can a website be running on the server but unavailable to customers?
  2. 02R02 public-content brief — Why does my website work through Tailscale but not on the public internet?
  3. 03R03 public-content brief — What does a contact form success message actually prove?
  4. 04R04 public-content brief — How do you build a website that remains usable when JavaScript fails?
  5. 05R05 public-content brief — Is a Playwright WebKit test the same as testing Safari on an iPhone?
  6. 06R06 public-content brief — Why does a good Lighthouse score not prove that real visitors have a fast website?
  7. 07R07 public-content brief — What must an accessibility audit test beyond an automated score?
  8. 08R08 public-content brief — How do you distinguish a crawlability problem from an indexing or relevance problem?
  9. 09R09 public-content brief — How do you organize a service website without creating duplicate or orphan pages?
  10. 10R10 public-content brief — What makes a page relevant to a customer question rather than merely keyword-rich?
  11. 11R11 public-content brief — How do you connect an author, business and technical article without inventing authority?
  12. 12R12 public-content brief — How can a business measure AI search visibility without confusing crawler visits with customers?
  13. 13R13 public-content brief — How do you turn technical troubleshooting into useful evidence-led content?
  14. 14R14 public-content brief — What evidence should support a website performance or marketing claim?
  15. 15R15 public-content brief — How do you improve a service inquiry path without mistaking clicks for leads?
  16. 16R16 public-content brief — How do you reconcile search visibility, AI referrals and qualified website inquiries?
  17. 17R17 public-content brief — How do you prove that a website inquiry reached your mailbox?
  18. 18R18 public-content brief — How do you improve local visibility without inventing locations or duplicating city pages?
  19. 19R19 public-content brief — What makes a backlink or publication mention meaningful evidence of expertise?
  20. 20R20 public-content brief — How do you harden a business website without breaking its forms or tracking?
  21. 21R21 public-content brief — What should a website regression suite prove before deployment?
  22. 22R22 public-content brief — How does an adversarial website review challenge a clean audit report?
  23. 23R23 public-content brief — How do you choose technical website topics that attract the right service inquiries?
  24. 24R24 public-content brief — Who resolves conflicting fixes when SEO, performance and security disagree?
  25. 25R25 public-content brief — What should a website release plan include beyond clicking deploy?
  26. 26R26 public-content brief — What makes website acceptance testing genuinely independent?
Open the full shelf

Article drafts

Six drafts from the public workbench. Not approved as published fact until reviewed with evidence.

6 volumes — browse this shelf
  1. 01Why SEO cannot repair a broken inquiry pipeline
  2. 02A public website needs a public test
  3. 03Sent is not the same as received
  4. 04Browser coverage without overclaiming
  5. 05Measure AI visibility without inventing attribution
  6. 06Independent acceptance is more than another green check
Open the full shelf

Publishing

How verified work becomes a public expertise asset.

2 volumes — browse this shelf
  1. 01Author, business and publication identity plan
  2. 02Public expertise layer — briefs and reviewable drafts
Open the full shelf
Open the complete record

Opening the volume…