These are shortened previews of frameworks and discussions from inside the library, published here so anyone can see the working style before requesting access.
A strategy deck answers "what should we do." A prioritization model answers "what should we do this week, given that engineering has two sprints free and marketing wants the blog redesign done by Friday." Most in-house SEO frustration doesn't come from lacking ideas. It comes from lacking a defensible way to rank them against everyone else's competing requests.
The framework in the library scores each initiative against three factors: engineering cost, expected visibility gain, and how much internal political capital the request will spend. It isn't complicated. It's meant to be filled out in fifteen minutes before a roadmap meeting, not presented as a twenty-slide argument.
Reviewers see the same gap repeatedly: a redirect map built from the old site's structure instead of the new one's, which quietly breaks internal linking after launch. The fix is a one-line addition to the template most members already use.
One member's live session focused entirely on rewording a technical audit's findings into three sentences a finance leader would actually read. The framework that came out of it now lives in the template vault under stakeholder reporting.
Most content governance advice assumes an editorial team. This framework assumes the opposite: one freelance writer, one SEO owner, and a checklist that catches the recurring quality issues without a formal review layer.
A recurring thread in the private space: how to phrase an internal linking request so it competes fairly against feature work, instead of reading as a nice-to-have that gets deprioritized every sprint.
This page is a preview, not the library itself. Full frameworks, templates, and session recordings are only available to members, and nothing here is written to persuade you either way. It's here so you can judge the working style directly.