Authority and distribution, control 6 of 12
A-06 Use Preferred Sources only where eligible
Preferred Sources is a documented user-preference feature, not a universal organic ranking boost or mandatory business-site requirement.
- Priority
- Optimisation.
- Hard gate
- No
- Change class
- AUTO_WITH_TEST: A candidate requiring relevant tests.
- Quality bucket
- Authority and distribution readiness
Why it matters
If a site that is not eligible adds the feature, or claims it lifts rankings, users are misled and the team wastes effort on something that does not do what is promised. Preferred Sources is a way for people to choose the sources they see, not a ranking lever. Treating it that way keeps expectations and reporting honest.
Evidence to review
- Eligibility check, implementation test and preference-flow evidence.
How to implement
- Check current eligibility and relevant generative inclusion settings.
- Use the documented button or linking pattern without deceptive prompts.
- Measure voluntary adoption and relevant audience outcomes.
- Record inapplicability when the programme does not fit the site.
How UltimateSEO checks this
Needs your evidence. No automated check covers this control, so it stays UNKNOWN until evidence is supplied.
Evidence needed: whether the site is eligible for Preferred Sources and how it is presented to users.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Myth guards that reference this control
Sources
Part of The UltimateSEO Framework v4.3, catalogue dated 2026-10-14. Evidence states, control states and the publish gate are explained on the hub.