ETF Trends
Answered with HTTP 200 and parsed as RSS 2.0 when we last looked.
https://www.etftrends.com/feed/Check it live- Format
- RSS 2.0
- Items in the feed
- 50
- Newest item
- 17 Nov 2026
- New items
- about every 2 hours
- Language
- en-US
What was in the feed when we checked
- Top Performing Leveraged/Inverse ETFs: 11/15/2026
- Esports & Natural Resources Led NTHM Performance in Q3
- Risks Beyond the Midterms: Tackle Inflation & AI With Value
- American Century’s Bartolini on Midterms, Data Centers, and Bonds
- BlackRock Files for Exchange-Traded Interval Funds
- A New King of Dividend ETFs
At that moment the newest item was 15 hours old, and items were appearing about every 2 hours. The address above is the one to paste into a feed reader. Everything on this page comes from fetching the feed ourselves on 18 November 2026, not from a list that was typed once and never looked at again.
How to subscribe
- Copy the feed address above.
- Paste it into the "add feed" or "follow" box of your reader. Feedly, Inoreader, NetNewsWire, Thunderbird, Reeder and every other reader take a plain address.
- The reader fetches the feed on its own from then on. Nothing is sent to ETF Trends about you, and there is no account to make.
If your reader refuses the address, run it through the feed checker. It repeats the fetch live and says what came back.
Questions
Is this address official?
It is the address ETF Trends itself serves. We found it at the address the site publishes for it on https://etftrends.com/ and then fetched it to make sure it works. We do not host or mirror the feed.
How current is the information on this page?
It was all measured on 18 November 2026. Feeds move and get retired, so the generator reruns the checks and the page is rebuilt from the new results. If you want the state of the feed right now, the checker fetches it while you wait.
The feed stopped updating in my reader. Whose fault is it?
Check the feed here first. If it loads and shows recent items, the feed is fine and your reader is the problem, usually because the publisher is refusing its requests. Our guide on feeds that stop working runs through the rest.