Fig. 01 — Who runs this

A working team, not an editorial board

Lajobo Xahuro is maintained by people who have held the exact seat this community is built for: sole in-house SEO owner at a company where nobody else understands the job.

Fig. 02 — Core team

Two people, one review queue, and a rotating panel of members

The library is small on purpose. A small team keeps the frameworks specific instead of generic, and keeps the peer review queue readable instead of automated.

Founder of Lajobo Xahuro, a woman in her mid-forties, standing in a modern office with city skyline visible through floor-to-ceiling windows

Program Lead, Frameworks & Review

Former in-house SEO lead, B2B software and logistics

Spent nine years as the only SEO hire at two mid-sized companies before building the first version of this library for personal use. Oversees the framework catalog and reads the first pass of every peer review submission.

Community and sessions lead, a man in his late forties, seated at a desk in a glass-walled office reviewing documents

Sessions & Community Lead

Former in-house SEO manager, retail and marketplace platforms

Runs the monthly live sessions and moderates the private discussion space. Spends most of a working week reading member questions and matching them to the right framework or a past session recording.

Fig. 03 — Editorial approach

Why this isn't run like an agency blog

Most SEO content published online is written to generate leads for a service business. That's a reasonable business model, but it shapes the advice: broad, generic, and cautious about naming real constraints.

Everything in this library is written from the opposite direction. A framework exists because a member needed it for an actual project, tested it, and then it got cleaned up and added to the catalog. Nobody on the team sells SEO services outside of this community, and members are never pitched consulting work.

01

Every framework is dated and attributed to the project context it came from.

02

Peer reviewers are current or former in-house practitioners, not contracted consultants.

03

Live sessions are built from member-submitted topics, not a fixed curriculum.

04

Membership terms and what's included are described plainly on the Services page.

Fig. 04 — How the team supports members

Two things the team does every single week

Reads every review submission

Documents submitted to the peer review queue are read by a team member before being routed to the right reviewer, so submissions never sit unanswered in a generic inbox.

Prepares the monthly session

Topic requests from members are grouped, prioritized, and turned into a working agenda for the next live session, then archived afterward with notes.