Ryan Perez · SEO operating system

A truthful answer to a distinct condition.

Every search page is built as a technically accessible, honest answer to one user condition — then connected to the funnel transition it should produce, and measured on whether the visitor made real progress. Traffic is not the outcome. This is the same LAKA change model, applied to discovery.

The failure it prevents A hundred industry pages where only the industry name changed. Scale without value is a policy violation, not a strategy.
The object

Ten LAKA components, in SEO terms

{{ l.a }} {{ l.b }}
The pipeline

Six stages. Any one of them can be the whole problem.

Search is an automated pipeline. A page that ranks badly is failing at exactly one of these, and the diagnosis is always “which stage”, never “more content”.
{{ p.t }}
{{ c.a }} {{ c.b }}
Meta-variables

Twenty dials, low to high

{{ v.a }} {{ v.b }} {{ v.c }}
Middle · the question Right · the states
Escalation

Ten states of SEO change

{{ e.a }} {{ e.b }}
Minimum conditions

Eight things, all required

Miss one and nothing downstream matters. Content quality cannot rescue a page a crawler cannot reach.
{{ e.t }}
The confusion that costs most

robots.txt is not noindex

{{ r.a }} {{ r.b }}
A page blocked in robots.txt can still be indexed from external links, because the crawler never gets to read the noindex it was never allowed to fetch.
Status codes

One condition, one honest response

Condition Response Failure mode
{{ s.a }} {{ s.b }} {{ s.c }}
Never redirect every removed URL to the homepage. It is a soft 404 with extra steps, and it destroys the signal that the content is gone.
Canonicalisation

Signals, ranked by strength

{{ c.a }} {{ c.b }}
When signals conflict, the fix is consistency — not adding another signal on top.
Indexing control

Desired outcome selects the technique

{{ i.a }} {{ i.b }}
Rendering

Ten JavaScript rules

{{ r.a }} {{ r.b }}
Page experience

Three vitals, at the 75th percentile

{{ v.k }} {{ v.target }} {{ v.what }}
{{ r.t }}
If a perfect score requires removing useful content, optimise the experience and let the score be imperfect.
Intent → funnel

Eleven queries, eleven landings

Search traffic arrives mid-thought. The landing continues that thought rather than restarting everyone at the top of one generic funnel.
Query type Funnel entry What the page must do first
{{ i.a }} {{ i.b }} {{ i.c }}
If several intents are materially different, that is several pages. One overloaded page serving four intents serves none of them.
Page anatomy

Fourteen elements a primary page may need

{{ a.t }}
Blue are non-negotiable on any indexable page. The rest are earned by the specific page.
Heading rules {{ r.t }}
Retired tactics

Six things not to optimise for

Each of these is either explicitly unused, explicitly against policy, or explicitly not a thing Google has a rule about.
{{ r.a }} {{ r.b }}
Internal architecture

Eleven page roles, each with one job

{{ p.a }}{{ p.b }}
{{ r.a }} {{ r.b }}
Media

Image and video rules

{{ r.a }} {{ r.b }}
Helpful content

Eleven elements, and the AI clause

{{ h.t }}
{{ r.t }}
Structured data

Page condition selects the type

JSON-LD, describing content that is visible on the page. Validation means eligibility for a rich result — never a guarantee it displays.
{{ s.a }}{{ s.b }}
{{ r.a }} {{ r.b }}
{{ c.eyebrow }}

{{ c.t }}

{{ i.t }}
{{ r.t }}
The one that gets a site penalised

A hundred pages where only the name changed

Scaled content abuse is about added value, not about automation Using a template is fine. Using AI to draft is fine. Generating many pages that exist mainly to catch queries, without page-specific substance, is the violation — whoever or whatever wrote them. The test is not “was this automated”, it is “would a person in this situation be better off for having landed here”.
{{ g.label }} {{ g.t }}
Programmatic rules

Seven, for the industry repository

{{ r.a }} {{ r.b }}
Publication gate

Nine checks, then publish

The engine runs in order. The first failing condition decides the action, and the page does not ship until it clears.
{{ l.t }}
Blocked outright

Eight things that stop publication

{{ p.t }}
Validation, before and after
{{ v.t }}
Repository layout

Where the rules live

{{ l.t }}
Agent contract

The page spec an agent reads

{{ l.t }}
The bridge

Every SEO measure has a business counterpart

This is the same funnel bridge as the analytics layer, entered from search. If organic traffic does not produce qualified progress, the SEO is not working — whatever the impressions say.
SEO measure Business counterpart Event
{{ b.a }} {{ b.b }} {{ b.c }}
Search Console

Twelve-item setup

{{ c.t }}
Diagnosis

Symptom selects where to look

{{ d.a }} {{ d.b }}
Governing principle Build every search page as a truthful, technically accessible answer to a distinct user condition. Connect that answer to the correct funnel transition. Then measure whether the visitor achieved meaningful progress — not whether the page received traffic.