No article field sets the ownership disclosure; the build decides when

ON THIS PAGE

1. Key findings
2. What actually triggers the paragraph
3. The same rule enforced a second way
4. What the FTC's own standard actually requires
5. Why a prior affiliation is disclosed rather than resolved by silence
6. What a reader can transfer to any other directory
7. Limitations and open questions
8. Sources

A few pages on this site open with a paragraph that most articles never carry: a notice that this publication and one named supplier, Banana Peppers, were formerly under common ownership. Nothing in the article decides whether that paragraph appears. The build does, by reading the finished page itself.

What actually triggers the paragraph

This site's build script assembles every article from a template that carries a fixed slot for the disclosure, present on every article whether or not the disclosure ever fills it. Before that slot is filled, the build runs two checks against a fixed pattern matching the formerly affiliated supplier's name or its domain: one against each entry in the article's own retailers list, and a second against the composed page's own text, with the slot itself removed so the check cannot trigger on its own output, combined with the article's title, description, summary, and deck fields. If either check matches, the approved disclosure sentence is inserted into the slot. If neither matches, the slot is replaced with nothing and the page carries no disclosure at all. There is no dedicated field that simply switches the disclosure on or off; naming the supplier, whether in the retailers list or anywhere in the piece's own text, is what turns it on, which is also why this piece itself will carry one.

The same rule enforced a second way

A second mechanism enforces the identical rule against this publication's own supplier ledger rather than against an article. A function checks each ledger record for whether it names the formerly affiliated supplier; if it does, and that specific record does not also carry a disclosure field set to true, the build refuses outright rather than publishing an undisclosed record. The two mechanisms check different things, an article's finished text against one pattern, a ledger record's own field against the same underlying fact, but both exist so that naming the supplier without disclosing the history is not something either surface can do quietly.

What the FTC's own standard actually requires

The FTC's endorsement guidance, read 2026-09-19, defines the kind of connection that requires disclosure in plain terms: one where "there's a connection between an endorser and the marketer that a significant minority of consumers wouldn't expect and it would affect how they evaluate the endorsement." A prior common ownership between a publication and a supplier it now covers is exactly that kind of fact, one a reader would reasonably want to know before weighing what the publication says about that supplier. The same guidance is specific about placement, not just content: a disclosure "should be placed where it easily catches consumers' attention and is difficult to miss," and applies wherever the underlying claim appears rather than once, buried, somewhere else on the site. On an article page here, the disclosure sits immediately after the headline, above the first line of body text, for the same reason. The homepage is a documented exception, carrying a compact version of the line inside one directory card rather than the full paragraph at the top, by a separate design decision the build script records as an owner decision dated 2026-09-05.

Why a prior affiliation is disclosed rather than resolved by silence

The disclosure this site prints does not merely name the past relationship. It states plainly that current ownership is separate, that no personnel from the formerly affiliated supplier hold any editorial role here, and that the supplier is held to the same evaluation criteria as every other supplier this publication covers, nothing more favorable. A publication could choose instead to simply stop mentioning a supplier it was once tied to, which would avoid the disclosure question by avoiding the coverage. This site's own stated approach is the opposite: the history is disclosed, and the coverage continues under the same criteria, so a reader can judge for themselves whether the coverage holds up rather than having the question resolved by the publication's own silence.

What a reader can transfer to any other directory

The mechanism this piece describes is specific to this site's own build. The test it demonstrates is not. Reading any vendor-comparison site or review directory, a reader can ask the same two questions this site's own mechanism answers automatically: what does the site actually disclose about its own relationships to what it covers, and does that disclosure sit where a reader will see it before reading the content, or somewhere a reader has to go looking for it. A site that discloses nothing has not necessarily hidden something, since it may have nothing to disclose. A site that discloses a relationship only in a footer, a terms page, or an about page a reader never opens has made a choice about visibility that the FTC's own placement standard treats as a real difference, not a technicality.

Limitations and open questions

This piece describes a mechanism read directly from this site's own build script on 2026-09-19; the underlying code could change after that date, and a reader checking this claim later should verify it against the current source rather than this description. This piece takes no position on whether a disclosure like this one actually changes what readers do once they see it, which is not something this publication has measured about itself and is not a question a description of the mechanism can answer on its own.

An article here cannot choose whether it carries this disclosure. What it can do is name the supplier honestly when the coverage calls for it, and let the build decide the rest.

Sources

This publication's own build script, read directly on 2026-09-19, for the disclosure-triggering mechanism and the separate ledger-side enforcement function described above; both are located in the source by their function names rather than by line number, since line numbers move as the codebase changes. FTC, endorsement guidance materials published at ftc.gov, read 2026-09-19, for the material-connection definition and the placement standard quoted above.