Every one of those 1 sits in a single category, markets. Of the tracked stories, 1 of 1 also mention YieldMax, the most common co-covered peer. The 5 average consequence score is below the beat benchmark of 6.3 in the same window.
Recent coverage · YieldMax AI & Tech Portfolio Option Income ETF
1story
avg impact
0%positive
0%negative
100% neutral
Figures are computed live from our source-verified story record
— see our methodology for how impact and
sentiment are derived.
What the coverage shows about YieldMax AI & Tech Portfolio Option Income ETF
Every one of those 1 sits in a single category, markets. Of the tracked stories, 1 of 1 also mention YieldMax, the most common co-covered peer. The 5 average consequence score is below the beat benchmark of 6.3 in the same window. Source depth averages 3 original sources per story, versus 2.5 across the same-window beat baseline. YieldMax AI & Tech Portfolio Option Income ETF appears in 1 tracked Finance story from March 10, 2026.
Stories tracked
1
Sources per story
3
Computed from the 1 stories linked to this entity, with beat comparisons drawn from all 88 Finance stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.
Coverage cohort
Appears alongside
Other entities that clear the same relevance threshold in stories also covering YieldMax AI & Tech Portfolio Option Income ETF. Shared-story counts are live from our verified record — not editorial picks.
YieldMax has announced its March 2026 dividend distributions for its thematic tech portfolios, led by a robust $0.4384 payout from its semiconductor-focused fund. These declarations reflect the ongoing high-volatility environment in the AI, crypto, and chip sectors, which continues to fuel the firm’s synthetic covered call strategies.
YieldMax AI & Tech Portfolio Option Income ETF is linked from 1 story on this site, each scored at or above our 35% relevance threshold — see how these pages are built.
See something wrong on this page — a misattributed entity, a wrong stat, a broken source
link? Report a data issue.