Skip to content

Hierarchical publish gate · The UltimateSEO Framework

The publish gate: hard gates first, then the quality score

The gate is not a ranking formula. Eight hard gates are decided first and are never scored: if any one fails, the page is rejected or fixed before anything else. Only when the gates pass does the 100-point quality score apply, and it is always reported together with its evidence coverage.

1. Hard gates (not scored)

If any of the following fails, the decision is reject or fix first, whatever the total score.

  1. No spam, deception, fake reviews or authors, cloaking or scaled abuse. G-01 G-02 G-03 G-04 G-05 G-06
  2. The target URL is reachable, has the correct canonical, renders and is indexable. T-01 T-02 T-03 T-05 T-09
  3. Critical facts are verified and an evidence chain exists. Q-05 Q-06
  4. Author, business and entity information is real. E-01 E-02 E-06 E-08
  5. Structured data does not contradict visible reality. R-14
  6. Local pages do not claim coverage outside the real service area. I-08
  7. If the topic is YMYL, the required expert and source standard has been applied. E-05
  8. Transactional facts such as price, stock and availability agree with the source of truth. E-09

The 21 controls that act as hard gates

2. Quality score, only when the hard gates pass

Main purposeWeight
Intent and user-task fit15
Accuracy and evidence chain15
Original, non-commodity value15
Technical eligibility12
Retrievability and UX10
Entity and trust10
Business usefulness and conversion readiness8
Authority and distribution readiness5
Freshness and maintenance plan5
Measurement and experiment readiness5
Total100

How UltimateSEO computes it

  • Only controls in state PASS or FAIL count. UNKNOWN, NOT_APPLICABLE and BLOCKED controls are excluded, never assumed.
  • Per bucket: score = pass ÷ (pass + fail) × weight. Buckets with no evidenced control are left out.
  • The total is shown with its evidence coverage (evidenced controls ÷ 100) so a high score on thin evidence cannot pass for a verified one.
  • If a hard gate fails the decision is gate failed: the score is still shown, labelled "fix gates first".

3. Decision bands

ScoreDecision
90–100Publish
80–89Publish with minor fixes
70–79Rework
0–69Reject
Any hard gate FAILReject: fix the gate first

4. Page-level dependency order

An agent or a reviewer assesses a page in this order. Each question is only worth asking once the one before it has a satisfactory answer.

  1. G Is there a policy or spam problem?
  2. T Is the URL technically eligible?
  3. I Is it the right user, intent and page type?
  4. Q Is the information accurate, sufficient and original?
  5. R Can people and retrieval systems understand it easily?
  6. E Are the author, brand and entity trustworthy?
  7. A Is there an authority or distribution opportunity?
  8. M How will the result be measured and kept up to date?

5. Change classes used in findings

Every recommended change in a report carries one of these classes so you know what can be applied safely and what needs evidence or approval first.

  • AUTO_SAFE: Reversible changes that create no new business claim: an obvious broken link, accidental duplicate metadata, a verified canonical inconsistency, missing semantic HTML.
  • AUTO_WITH_TEST: Changes that must be measured after release: title and meta, internal linking, layout order, image optimisation, schema clean-up, copy clarity.
  • EVIDENCE_REQUIRED: Changes that need a source of truth before they are made: price, product features, 'tested' or 'best' claims, legal claims, service area, author bio, case study, review, availability.
  • APPROVAL_RECOMMENDED: Changes with a wide blast radius that a named owner should approve: deleting or merging high-traffic URLs, sitewide navigation rewrite, brand positioning change, pricing or offer change, robots or crawler policy change, large redirect map.
  • DO_NOT_DO: Never: spam, fake authority, fake reviews or personas, cloaking, hidden ranking copy, doorway pages, fabricated evidence, manipulative link schemes.

Framework hub · Agent runtime, phase K uses this gate