Procurement asset · May 2026

The Northbridge Procurement Standard

Eighteen testable criteria plus a two-stage verification workflow for paid third-source placements. Sector-agnostic use across telco, finance, insurance and commerce. Freely usable under Creative Commons BY-ND 4.0.

The Procurement Standard carries the methodological layer of the Compliance-GEO Codex into a testable procurement form. Eight binary A-criteria decide on a placement’s eligibility as a citation carrier. Ten gradual B-criteria determine the citation lift once the A-class is fulfilled. A two-stage verification workflow separates publisher pre-check before booking from briefing verification before final invoice. Price coupling to criteria fulfilment is the actual legal lever.

The standard is methodologically designed, not as a directly legally compelled implementation of a supply-chain duty. It operationalises supplier due-diligence checking regardless of whether a regulatory obligation bites in the individual case. Three procurement modules for direct integration into RFP, service contract and compliance declaration sit in the lower third of the page.

Work type
Procurement asset · Article
Methodology source
Compliance-GEO Codex Ch. 2
Licence
CC BY-ND 4.0
Empirical evidence
DE telco study Ch. 12
Section 01 · Methodological principle

Why verification before payment?

After publication, corrections to URL path, DOM disclosure or schema markup are no longer enforceable.

A publisher who has shipped an article under a /sponsored/ path will not change that path after invoice approval. The only mechanic that reliably bites is coupling the final invoice to evidence of fulfilled criteria. The verification workflow therefore runs before every final invoice, not after. Price coupling is the actual legal lever, not the advertorial contract.

The Procurement Standard is methodologically designed. It operationalises supplier due-diligence checking regardless of whether a regulatory obligation bites in the individual case. In a direct LLM contractual relationship, the check logic moves into the regulatory application scope. The precise classification of the relevant European and national interpretation lines sits in the DE annex of the Codex and in ongoing legal validation.

Operational conclusion Verification runs before the final invoice, not after. Whoever couples the final invoice to fulfilled criteria gets an enforceable legal lever; whoever does not, has none after publication.
Section 02 · Responsibility separation

Two responsibility levels, two sanction mechanics

Three domain-policy criteria belong to the publisher pre-check. Fifteen criteria belong to briefing compliance.

The eighteen criteria distribute across two levels following different responsibilities. Quality publishers accept enforcement claims only in areas within the sphere of influence of the individual order. Domain-policy decisions such as robots.txt, paywall architecture or domain reputation are strategic publisher decisions outside the individual-order negotiation.

2.1Publisher pre-check before booking

Three criteria decide at the domain-policy level and apply independently of the individual article: A 03 domain reputation, A 05 paywall status, A 06 bot policy. They are go or no-go. If a publisher does not meet them, the article is not booked. Re-validation quarterly. No invoice consequence after booking, because these criteria are not part of the briefing frame.

2.2Briefing compliance before final invoice

Fifteen criteria sit within the publisher’s sphere of influence for the concrete article: A 01, A 02, A 04, A 07, A 08 plus B 01 to B 10. If the publisher honours the briefing, the final invoice is billed at the full classification per the price-factor model. Briefing FAILs are usually not repairable after publication and lead to invoice reduction.

Operational conclusion Three domain-policy criteria are settled before booking; fifteen briefing criteria before the final invoice. The separation must be reflected in the contract mechanic, or it does not bite.
Section 03 · A-class

The eight binary A-criteria

Eligibility filter. A single A-FAIL disqualifies the placement as a citation carrier.

The A-class checks whether a placement in the retrieval engines’ candidate set is at all indexable, crawlable and editorially classified. Every criterion is a binary filter: FAIL means disqualification, regardless of price, publisher name and content quality.

Criterion Level What is checked Disqualifying, if
A 01 · URL path Briefing compliance Article sits under an editorial path of the domain Path segment is /sponsored/, /anzeige/, /advertorial/, /promotion/, /pr/ or /partner/; subdomain offloading such as partner.x.de
A 02 · DOM disclosure Briefing compliance No advertorial template in the article area. Textual advertising disclosure ("Anzeige", "In Kooperation") is permissible and legally required. Standalone DOM elements such as badges, frames or CSS wrappers (.advertorial) classifying advertising as template structure
A 03 · Domain reputation Publisher pre-check Domain is not a recognisable advertising aggregator Domain name or About text contains terms such as "anzeigen", "presseportal", "prnews", "advertorial", "sponsored"
A 04 · Index status Briefing compliance Index, follow; self-referencing canonical; no X-Robots block <meta name="robots" content="noindex">, X-Robots-Tag: noindex in HTTP header, missing or foreign canonical
A 05 · Paywall status Publisher pre-check Full text fully accessible to crawlers Partial content, metered paywall without a bot exception, login wall in front of the Article schema
A 06 · Bot policy Publisher pre-check robots.txt permits all relevant retrieval bots separately Blanket User-agent: * with Disallow: /; individual disallow for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, CCBot or Bingbot
A 07 · URL persistence Briefing compliance Contractually fixed twelve-month guarantee under unchanged URL No persistence clause; publisher advertorial-archiving routine without exception arrangement
A 08 · Outbound links Briefing compliance Links to the principal marked with rel="nofollow sponsored" Missing or incomplete rel attribution; dofollow links without a sponsored marker

The methodologically central point of A 02 sits in separating textual inline disclosure from advertorial template. A retrieval-neutral disclosure marker below the headline satisfies both the legal disclosure duty and the eligibility requirement. A <div class="advertorial"> wrapper structure embedded in the article is visually identical in effect but engine-side disqualifying. Compliance and eligibility do not exclude each other; they are operationalised separately.

Operational conclusion Eight binary check points, each with a precise FAIL condition. Before booking: A 03, A 05, A 06. Before final invoice: A 01, A 02, A 04, A 07, A 08. A single FAIL tips the whole placement into disqualification.
Section 04 · B-class

The ten gradual B-criteria

Lift levers. Every fulfilled B-criterion raises citation probability per engine, once the A-class is fully fulfilled.

The B-class determines citation lift once the A-class is fully fulfilled. All ten criteria belong to briefing compliance. They sit within the publisher’s sphere of influence for the individual article and are verified before the final invoice. The criteria act additively. Every additionally fulfilled criterion raises citation probability per engine, without any single criterion alone deciding eligibility.

Criterion What is checked Empirical anchor
B 01 · Byline Editorially responsible author with substance review. Preparatory work by principal or agency is permissible. Yext Q4 2025, author-entity disambiguation
B 02 · Schema markup Article or NewsArticle with author, publisher, datePublished, dateModified NB methodology; schema-subtype choice is a publisher-compliance decision
B 03 · Substance At least 800 words with information gain against topic baseline Aggarwal et al. KDD 2024, Position-Adjusted Word Count
B 04 · Citation hooks At least three named statistics plus one attributed direct quote Ahrefs 750-prompt study 2025, hook-density correlation
B 05 · Front-loading Core statement in the first 30 per cent of the text Indig 2026, RAG chunking prefers opening segments
B 06 · Definitive language Definitions in declarative form, no hedging, no modal softeners NB editorial standard; Indig 2026 on citation language form
B 07 · Entity consistency Brand, product and person references consistently named, not varied NB methodology
B 08 · Question headlines At least one headline or sub-heading in question form NB methodology, corresponds with query matching
B 09 · Listicle structure At least one enumerated section with clear item separators NB methodology
B 10 · Update Documented dateModified revision at least quarterly NB methodology; corresponds with A 07 URL persistence

At B 01, editorial final responsibility is to be separated from the authorship question. A narrow reading ("actual editor, no guest article") would conflict with Press Code Item 7. The standard’s reading mirrors actual publisher practice: principal or agency preparatory work passes through editorial review, revision and substance validation by the bylined author, who carries the final responsibility.

Operational conclusion Ten additive lift levers. They bite only when the A-class is fully fulfilled. Every fulfilled lever shifts citation probability a step; no single lever alone decides.
Section 05 · Verification workflow

The two-stage verification workflow

Stage 01 before booking. Stage 02 before final invoice. Deliberately without proprietary tool dependence.

The workflow follows the responsibility separation. Stage 01 clarifies, before booking, whether the publisher meets the preconditions at domain level. Stage 02 checks, after publication and before payment, whether the publisher has honoured the briefing. Stage 01 requires only browser and command line. Stage 02 additionally requires the public Google Rich Results Test, reading competence and contract access.

Stage 01 · before booking
Publisher pre-check. FAIL means not booking, without invoice consequence.
Step 1 · A 03 Check domain reputation. Scan domain name and About text for aggregator markers.
Step 2 · A 05 Spot-check paywall status with bot user-agent. curl -A "GPTBot" on a sample URL.
Step 3 · A 06 Cross-check robots.txt against all relevant bots: GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, CCBot, Bingbot.
Step 4 · Pool Document pool admission with quarterly re-validation.
Stage 02 · before final invoice
Briefing verification. FAIL leads to remediation or invoice reduction per the price-factor model.
Step 1 · A 01, A 02 Verify URL path and DOM disclosure. Inspect page source and article area.
Step 2 · A 04 Check index status via page source and HTTP header. <meta name="robots"> and X-Robots-Tag.
Step 3 · B 01, B 02 Confirm schema and byline via Google Rich Results Test.
Step 4 · B 03 to B 09 Evaluate word count, hooks, front-loading and formal criteria manually or semi-automatically.
Step 5 · A 07, A 08, B 10 Verify outbound links and persistence from page source and contract clause.

The responsibility clarification is explicit. Stage 01 protects the publisher against retroactive invoice reduction, because domain policy sits outside the briefing frame. Stage 02 couples briefing compliance to invoice recognition.

Operational conclusion Before booking: three domain-policy steps with browser and curl. Before final invoice: five briefing steps with page source, Rich Results Test and contract access. What is documented here holds before any audit.
Section 06 · Price coupling

Three-class assignment of the final invoice

Citation-Buy, Mixed-Buy, Mention-Buy. Plus two differentiated FAIL rows.

The combination of A-class fulfilment and B-class count yields a three-class assignment of the final invoice with two differentiated FAIL rows. The FAIL rows follow the responsibility separation from Section 02.

Assignment Fulfilment profile Criteria factor
Citation-Buy All 8 A plus at least 7 of 10 B 1.0 ×
Mixed-Buy All 8 A plus 4 to 6 B 0.5 × to 0.7 ×
Mention-Buy All 8 A plus fewer than 4 B 0.2 × to 0.4 ×
Briefing-FAIL FAIL at A 01, A 02, A 04, A 07 or A 08 0.0 × · invoice reduction, publisher-controlled
Pre-check-FAIL FAIL at A 03, A 05 or A 06 Not booked, no invoice consequence

Mention-Buys retain residual value in the citation layer. Ahrefs documented in 2025 that brand mentions without a link in LLM answers produce brand-recall effects. The residual value is billed at the mention price, not at the citation price. This separation prevents the common market error of procuring a mention deliverable at the citation price and asserting a citation.

The final invoice follows a multiplicative formula: final_price = list_price × criteria_factor × model_blended_factor. The model-blended factor folds the principal’s engine reach into the price. The complete price-factor model sits in Codex chapter 3.

Operational conclusion Three classes plus two FAIL rows. Citation-Buy pays full, Mixed-Buy pays pro-rata, Mention-Buy pays residual, Briefing-FAIL pays nothing, Pre-check-FAIL is not booked at all. The contract must name these five classes, or the coupling does not bite.
Section 07 · Three procurement modules

How does the standard reach RFP, SOW and compliance?

Three text modules as working material. Licence CC BY-ND 4.0. Bindingly citable.

The three modules are released under the same licence as the rest of the document and can be copied into RFP, service contract and compliance template. They cite the standard bindingly and couple the final invoice to criteria fulfilment. As soon as the standard is named in a tender, any agency that refuses its application or cannot document it is non-compliant vis-à-vis procurement. The mechanic works without statutory binding. It rests on the market-norm effect of open standards, analogous to the IAB standard for media buying.

Module 01 · Tender text · RFP Insertion into the specification of services
Service specification for paid third-source placements
Paid third-source placements (advertorials, sponsored articles, branded content, cooperatively produced expert articles) booked under this mandate are to be verified per the Northbridge Procurement Standard (as of May 2026, published under Creative Commons BY-ND 4.0).

Verification is two-stage:
  1. Publisher pre-check before booking: A 03 (domain reputation), A 05 (paywall), A 06 (bot policy)
  2. Briefing verification before final invoice: A 01, A 02, A 04, A 07, A 08 plus all B-criteria

The final invoice is billed per the three-class assignment of the standard:
  Citation-Buy     1.0 × market price  (all 8 A fulfilled, at least 7 of 10 B)
  Mixed-Buy        0.5 to 0.7 × market price  (all 8 A fulfilled, 4 to 6 B)
  Mention-Buy      0.2 to 0.4 × market price  (all 8 A fulfilled, fewer than 4 B)
  Briefing-FAIL    0.0 × market price  (FAIL at A 01, A 02, A 04, A 07 or A 08)

Publishers who FAIL the pre-check are not commissioned. Invoice consequences arise only on FAIL in briefing compliance. The contractor documents verification per placement and attaches it to the final invoice as evidence. The standard is publicly available at https://www.northbridgesystems.de/en/procurement-standard/.
Note · the concrete URL depends on the publication location. If the standard is provided via an alternative access route, this is to be stated in the annex.
Module 02 · SOW clause · service contract Insertion as Annex X to the service contract
Annex X · Northbridge Procurement Standard
§ 1 Binding effect

(1) The contractor undertakes to verify every third-source placement booked under this contract per the Northbridge Procurement Standard May 2026 before submitting the final invoice.

(2) The standard is published under the Creative Commons BY-ND 4.0 International licence and binding in the version in force at contract conclusion. Later versions of the standard apply only if both parties so agree in writing.

§ 2 Two-stage verification

(1) The publisher pre-check covers the checking of criteria A 03 (domain reputation), A 05 (paywall) and A 06 (bot policy) before booking. Publishers who fail this check are not commissioned; retroactive invoice consequences are excluded at this level.

(2) The briefing verification covers the checking of criteria A 01, A 02, A 04, A 07, A 08 plus B 01 to B 10 per the two-stage workflow of the standard. Evidence is to be attached to the final invoice and documented in audit-ready form.

§ 3 Price coupling

(1) Invoicing follows the three-class assignment of the standard:
    Citation-Buy     1.0 × market price
    Mixed-Buy        0.5 to 0.7 × market price
    Mention-Buy      0.2 to 0.4 × market price
    Briefing-FAIL    0.0 × market price

(2) On FAIL in briefing compliance (A 01, A 02, A 04, A 07 or A 08), the placement is not invoiceable. The contractor’s remediation obligation follows the general contract terms; briefing FAILs are usually not repairable after publication.

(3) On Mixed-Buy or Mention-Buy classification, remediation regarding the missing B-criteria is possible; the contractor has the opportunity for remediation within a deadline to be set by the principal.

§ 4 Documentation duty

The contractor retains the verification documentation for at least the statutory retention periods and makes it available to the principal on request. The documentation also serves as evidence-protection vis-à-vis third parties.
Note · this module is not exhaustively legally drafted and does not replace contract review. It serves as a template for adaptation to the principal’s respective contract regime.
Module 03 · Compliance declaration for contractor Counter-confirmation by the agency
Statement on compliance with the Northbridge Procurement Standard
[Firm · contractor] hereby declares that all third-source placements booked under the mandate with [principal] will be verified per the Northbridge Procurement Standard May 2026.

Verification is two-stage: publisher pre-check (A 03, A 05, A 06) before booking; briefing verification (A 01, A 02, A 04, A 07, A 08 plus B 01 to B 10) before the final invoice. The final invoice is classified and billed per the three-class assignment of the standard.

The standard is published as an open procurement standard under Creative Commons BY-ND 4.0 International. This declaration refers exclusively to the version in force at the time of declaration, May 2026.

Place, date ______________________________

Signature ______________________________
          [Name, function]
Note · use as a unilateral declaration in the tender procedure. In effect equivalent to a bidder’s self-declaration; the tender may make submission of this declaration a condition for award.
Application steps

From the standard to a compliant booking in five steps

  • 01 Insert RFP clause. Copy Module 01 into the specification of services. Suppliers without standard agreement drop out.
  • 02 Anchor SOW link. Module 02 as a § in the service contract. Three-class assignment as a precondition for invoicing.
  • 03 Obtain compliance declaration. Module 03 as the self-declaration in the tender procedure. Re-signed once per mandate period.
  • 04 Document audit pass. Log the verification workflow per Section 05. Browser snapshot, page source, Rich Results Test, contract excerpt.
  • 05 Classify final invoice. Citation, Mixed, Mention or FAIL per Section 06. Justify the invoice differential against the list price in the audit pass.
Operational conclusion Three copy-ready modules plus five application steps. Whoever embeds this anchors the standard in the tender procedure, in the contract and in the audit pass. Without this three-step move, the standard remains a paper tiger.
Section 08 · Application depth

In-house reading or mandate reading?

The same eighteen criteria at the core. Different operational depth.

The eighteen criteria are formulated as a procurement standard for mandate work, but carry without a mandate relationship as an internal audit tool for teams with their own content offensive or their own advertorial procurement.

Reading 01 · In-house

Self-assessment without negotiation component

In-house teams with their own content offensive or their own advertorial procurement use the A-class as a pre-check gate before booking and the B-class as quality control of ongoing publications. Both classes act as self-assessment, without a negotiation lever vis-à-vis publishers.

Three limits: the three-class assignment acts as a contract lever only with price coupling. The audit chain presupposes documented log infrastructure. Phase-00 baseline measurement presupposes a measurement tool-stack across multiple engines.
Reading 02 · Mandate

Full version with price coupling and audit chain

The mandate reading is the full version. It adds to the self-assessment mechanic a price coupling in the publisher arrangement, an audit-resistant audit chain and a full measurement stack across multiple engines. The three-class assignment thereby moves from an evaluation scheme to an invoicing lever.

Precondition: the principal is the orderer in the sense of the standard, the contractor is a consulting or agency partner. The final invoice runs through the three-class assignment; FAIL rows sanction via invoice reduction.

Both readings use the same eighteen criteria at the core, at different operational depth. The in-house reading is the entry level, the mandate reading is the full version with the contract lever.

Operational conclusion In-house teams use the standard as an audit tool. Mandate constellations use it as a contract lever with price coupling. Whoever introduces the standard at Phase 00 as a self-assessment has cleanly prepared the jump to the mandate reading.

Eighteen testable criteria, two-stage verification, three classes with clear FAIL rows. The standard is a procurement tool, not an academic work; what is documented here should hold before any audit.

Northbridge Procurement Standard · May 2026 Licence CC BY-ND 4.0