Skip to main content

  1. MIRENA
  2. Compliance
  3. Conflicts and Disclosures

Compliance · Governance standard

Disclose a relationship or conflict before it can distort the claim, comparison, review, or approval.

The standard covers financial, affiliate, employment, ownership, client, personal, provider, review, and self-approval conflicts, together with disclosure placement, mitigation, recusal, and records.

Governance standard

Semantec SEO Conflicts and Material Disclosures Standard

The standard states what must happen, who owns the decision, what evidence is required, and what blocks release.

01 · Identify

What creates a conflict

A conflict exists when a financial, ownership, employment, client, affiliate, sponsorship, provider, personal, competitive, or other relationship could affect—or reasonably appear to affect—the content or decision.

A conflict does not always prohibit the work. It must be identified, disclosed, and managed.

02 · Classify

Material relationships

Common disclosure classes
Relationship Example Required control
Ownership Semantec SEO sells MIRENA State the product ownership on product and comparison pages
Founder or employment Author created or worked for a named entity Disclose when material to the reader's assessment
Affiliate or referral Commission may be earned from a link Disclose near the recommendation before action
Sponsorship or free access Payment, gifted plan, service, travel, or event benefit Label the benefit and preserve editorial independence
Client relationship A case study or testimonial concerns a client Permission, scope, evidence, and limitations
Provider dependency OpenAI, Stripe, or Authflow.ai supports the service State the operational boundary without implying endorsement
Reviewer conflict Reviewer owns the claim or benefit Independent review or recorded second approver
03 · Disclose

Placement and wording

A material disclosure should appear where a reader encounters the related claim, comparison, recommendation, testimonial, or action.

Use direct language that names the relationship and benefit. A generic footer or vague statement that 'some links may be affiliate links' is insufficient when a specific relationship is known.

04 · Protect the decision

Comparison and review independence

A desired commercial result must not determine the comparison question, criteria, evidence, missing values, or verdict.

Disclose product ownership, affiliate relationships, free access, sponsorship, or other incentives. State fit, non-fit, trade-offs, source dates, and unknowns.

05 · Separate authority

Self-review and self-approval

A person may draft or own a claim and still participate in review, but they should not be the only approver where the subject is materially legal, privacy, security, commercial, accessibility, or disputed.

The record should show who provided independent challenge and who had final authority.

06 · Manage

Recusal and mitigation

Mitigation can include visible disclosure, independent source verification, a second reviewer, removal from the verdict, narrower scope, held publication, or recusal.

A conflict that cannot be adequately managed blocks the affected decision.

07 · Protect proof

Case studies, testimonials, and reviews

Identify the relationship, permission, consideration, editing, date, scope, and whether the speaker reviewed the final wording.

Do not fabricate, composite, anonymise without permission, or retain a withdrawn endorsement as though it remains current.

08 · Keep entities separate

Provider and platform references

Use of OpenAI, Stripe, Authflow.ai, Google, WordPress, or another platform does not imply endorsement, partnership, certification, or shared ownership.

A provider security or compliance statement belongs to the provider and must not be converted into a Semantec SEO claim.

09 · Record

Relationship register and changes

Store the related party, relationship, benefit, affected pages, start and end dates, approved disclosure, owner, reviewer, and change trigger.

When the relationship ends or changes, update dependent content and preserve relevant history.

10 · Escalate

Report an undisclosed conflict

Send privacy@semantecseo.com the page, relationship, evidence, date, and requested correction. A challenged disclosure follows the Corrections and Retractions Policy.

Sources

Controlling guidance and first-party records.

The standard uses current source material but does not convert platform guidance into a ranking guarantee.

Semantec SEO
Semantec SEO Disclaimer

First-party no-endorsement and product-relationship boundary.

Open source →

Semantec SEO
Semantec SEO About

First-party founder, company, and product relationship.

Open source →

Google Search Central
Google helpful content guidance

Official trust, authorship, and source questions.

Open source →