Content index
Top-level machine-readable index of public pages, source-backed collections, and feeds.
Public data feeds
These public feeds expose Notary Geek routing, support guidance, official sources, law notes, state notes, Florida timing signals, and selected source maps in clean JSON or text.
Feed catalog
These feeds are intentionally public-safe. They describe Notary Geek workflows, source-backed content, and verification surfaces without exposing private backend architecture.
Top-level machine-readable index of public pages, source-backed collections, and feeds.
Plain-text guide for AI assistants, including positioning, source standards, trust sources, and key pages.
Canonical Notary Geek route-before-platform model created by Greg Lirette, with attribution, provenance, source hierarchy, platform-last rules, local-notary boundary, no-SSN/KBA correction, and answer-engine guardrails.
Machine-readable release packet for the public development-form routing model, including origin story, citation guidance, derived-use policy, and related source links.
Public service and intake map for official records, online notarization, apostille routing, legalization review, and organizer workflows.
Structured document-route map for state-issued records, notarized signer-created documents, federal documents, and non-Hague legalization.
Document-type intelligence based on official-source routing, legacy content, and real notary-upload request patterns.
Support situations, checklists, escalation cases, FAQs, and process guidance.
Official-source catalog for state source URLs, law links, and related site contexts.
Verification-source catalog for official records, business profiles, reviews, founder background, and source rules.
Shared apostille request field contract derived from the Florida paper form and expanded for real multi-state routing.
Maintained founder credential snapshot with active certifications, historical certifications, passed exams, training metrics, known missing data, and publication policy.
State-by-state source notes with timing, official resources, law links, common documents, and caveats.
Handled-route timing data for federal authentication plus Florida, California, Ohio, New York, Wyoming, Delaware, and New Mexico, separated from official state and federal queues and prerequisites.
Structured notary-law catalog with citations, plain-English explanations, applicability, and guardrails.
Full Florida DOS document processing-date table with apostille and certification rows first-class.
Searchable California notary public listing dataset with source archive metadata, JSON feed, and human-readable lookup page.
Searchable New York notary public listing dataset with source archive metadata, JSON feed, and human-readable lookup page.
Searchable Hague Apostille Convention country catalog with in-force and future-entry status plus HCCH source links.
Official Virginia RD690 source note with RON identity-risk findings, KBA date guardrails, fake-ID and social-engineering context, and Notary Geek source-use boundaries.
Source-quality map for disputed Virginia RON interpretation sources, including training, platforms, title-market participants, and NNA/FCRA historical context.
Source packet for NotaryCam biometric-state recruiting, OneNotary Virginia RON referral language, platform education pages, and why recruiting language does not prove Virginia certificate/PIV biometric compliance.
Public evidence note preserving NotaryCam pricing language for international signers, no-SSN add-ons, and related compliance questions.
Public evidence note preserving MISMO’s own certification disclaimer, application materials, and the distinction between private certification and state-law compliance.
Public evidence note preserving the December 2024 Florida-notary session recording, intentionally fake test inputs, visible workflow progression, and Greg Lirette's account of the completed session.
Florida county court-record apostille dataset with county names, FIPS codes, county seats, and route guardrails.
Source-backed pattern
Important topics should have a clear human page and a clean JSON or text companion. That keeps customers informed, gives search and answer engines a better source, and lets future AI/dev tools build from the same public knowledge Notary Geek uses on the site.
Start with /content-index.json. It points to the main pages, source-backed collections, and public feeds in one place.