I Built an RSS Feed So HackerNoon Could Auto-Import My Blog Posts. Here's How.

I publish blog posts on my own site. I also want those posts on HackerNoon, Medium, Dev.to, Hashnode, and CoderLegion. But I do not want to copy-paste every article five times.

So I built an RSS feed into my Next.js static site, pointed HackerNoon at it, and now every post I publish shows up there automatically. The whole thing took about 30 minutes. Here is exactly how I did it and why it matters more than most developers think.

Why RSS Still Matters in 2026

RSS feels like a relic from the Google Reader era. But for content distribution and SEO, it is one of the most underrated tools available.

Here is what an RSS feed gives you:

Automatic cross-posting. Platforms like HackerNoon, Medium, and Dev.to can import directly from your feed. You publish once on your own domain, and the content propagates everywhere.

Backlinks on autopilot. Every platform that imports your content links back to the canonical URL on your site. That is free domain authority from high-DA sites like HackerNoon without any manual outreach.

Canonical URL control. When you set the canonical URL in your RSS feed, Google knows your site is the original source. The cross-posted versions do not compete with you — they point back to you.

Podcast and newsletter compatibility. RSS is the backbone of podcast distribution and many email newsletter tools. Building the feed now means you are ready for those channels later.

The Architecture

My site is built with Next.js 16 using static export. No server. No API routes at runtime. Everything is pre-rendered at build time and served from a CDN via AWS Amplify.

The blog posts live in a TypeScript array in a single data file. Each post has a slug, title, description, date, author, tags, and the full content as a markdown string. Adding a new post means adding an object to the array and pushing to main.

For the RSS feed, I created a route handler at /feed.xml that generates valid RSS 2.0 XML at build time. Since the site uses static export, Next.js pre-renders this route into a static XML file — no server needed.

The feed includes both a short description and the full article content using the content:encoded namespace. This is important because platforms like HackerNoon need the full content to import, not just a summary.

I also convert the markdown content to basic HTML inline — headings, bold text, links, and paragraphs. Nothing fancy. Just enough for the imported version to be readable.

What I Changed

Four files:

feed.xml/route.ts — The RSS route handler. It loops through all blog posts, converts markdown to HTML, and outputs valid RSS 2.0 with the dc, content, and atom namespaces.

layout.tsx — Added a link rel alternate tag pointing to the feed so browsers and crawlers can auto-discover it.

sitemap.ts — Updated to include individual blog post URLs. Previously it only listed the /blog index page.

robots.txt — Added a Feed directive pointing to /feed.xml.

That is it. Four files, maybe 50 lines of code total. The feed auto-generates from the same data source as the blog, so there is zero maintenance.

The HackerNoon Import

HackerNoon has an RSS import feature in their story editor. You paste your feed URL, it finds all the articles, and you select which ones to import. They go into your drafts for review, then you submit them for editorial approval.

The key insight: HackerNoon requires the content:encoded field in your RSS items. If you only include a short description, the importer says "No articles found." I hit this exact issue on my first attempt. Adding the full article content as HTML inside content:encoded fixed it immediately.

The SEO Play

This is really about backlinks. Every article I publish on my own domain now automatically becomes available for import on platforms with domain authority scores of 70 or higher. Each imported article links back to my canonical URL.

Over time, this compounds. Ten blog posts cross-posted to three platforms is 30 backlinks from high-authority domains. That is the kind of link profile that moves the needle on organic rankings.

And I did not have to email a single person, submit a single guest post pitch, or pay for a single link.

How to Build This Yourself

If you have a Next.js site with static export, here is the short version:

Create a route handler at src/app/feed.xml/route.ts that exports a GET function. Loop through your posts, generate RSS XML, and return it as a Response with content type application/rss+xml. Add the content:encoded namespace and include full article content as HTML inside CDATA blocks.

Add a link rel alternate tag in your root layout head. Update your sitemap to include individual post URLs. Add a Feed line to robots.txt.

Build, push, deploy. Your feed is live. Point HackerNoon, Medium, or any RSS-compatible platform at it and you are distributing content everywhere from a single source of truth.

The whole thing is maybe 50 lines of code and it will generate backlinks for as long as your blog exists.

Try It

My RSS feed is live at axiondeepdigital.com/feed.xml. If you want to see what your site is missing from an SEO perspective, run a free audit at axiondeepdigital.com/free-seo-audit. It checks 60+ factors including whether you have an RSS feed, structured data, and proper canonical URLs.