Getting Your Writing Seen Beyond Your Own Site

Part one of this series covered your own site: llms.txt, structured data, machine-readable feeds, the eight layers that make your pages legible to humans and to the AI agents that increasingly read on their behalf. This piece is about everywhere else.

The mental model is simple. Your site is the canonical home. Everywhere else is a spoke that points back to it. Spokes get you seen. The hub gets the credit. If you mix that up, you spend a year writing for someone else's audience and ranking for someone else's domain.

I just finished wiring this distribution stack on Promptway, the site you are reading. Here is what I built, in the order I would build it again, and why each layer matters.

Start with full content feeds

Most blogs ship a summary-only RSS feed by default. That is fine if RSS is just an archive ping for a few Feedly subscribers. It is a real problem the moment you want to syndicate.

Every downstream channel that consumes your feed reads from it directly. dev.to's RSS importer, Flipboard magazines, Feedly previews, AI ingestion bots, every one of them pulls the article body out of the feed. If your feed has a summary, that is all they get. They cannot republish a full article from a 200 character teaser, so they either skip you or post a fragment that is useless to anyone who finds it.

The fix is one feed change. In RSS, add <content:encoded> with the full rendered HTML of the article wrapped in CDATA. In JSON Feed, populate content_html. Keep the short description or summary field for clients that want a preview. While you are in there, add <atom:link rel="self"> so the feed is self-aware, a <link rel="hub"> pointing at a WebSub hub, and a <media:content> block with your hero image so cards render with art.

This is the foundation. Nothing else in this article works as well if the feed is summary-only.

Push, do not wait to be pulled

Crawlers used to be the only way new URLs got noticed. That is no longer true. There is a faster path for everything except Google, and it costs you one HTTP POST.

IndexNow is a small open protocol that lets you tell search engines about a new or updated URL the instant it ships. You generate a key, serve it from your domain as a static file, and POST your URLs to https://api.indexnow.org/indexnow. One submission propagates to Bing, Yandex, Seznam, and Naver. Google is not a participant.

Bing matters double. Seer Interactive's analysis found that roughly 87% of ChatGPT search citations overlap with Bing's top ten results. The fastest path into ChatGPT citations is being indexed by Bing the moment you publish, not three weeks later when its crawler eventually wanders in.

WebSub does the same thing for feed readers. Add a <link rel="hub"> to your RSS, then POST to the hub when you publish. Feedly, Inoreader, and similar readers subscribed to the hub get notified in seconds instead of on their normal polling interval. Google retired its hosted hub but Superfeedr's free hub still works fine for low volume publishers.

Both of these belong in your publish pipeline as one or two function calls. They are the highest-return two minutes of distribution work you will ever do.

Syndicate with canonicals, always

The standard objection to cross-posting is duplicate content. The fix is older than the problem. Every copy of your article on someone else's domain declares a rel="canonical" link back to your version, plus a visible "originally published at" line for human readers. Google has said for years that canonical syndication is fine, and dev.to, Medium, and Hashnode all support it natively.

The targets worth the effort, in roughly this order:

• dev.to has an open API. Create an organization page, generate an API key, and POST /api/articles with canonical_url set to your version and organization_id set to your org. Their RSS importer also works if you would rather skip the code path. Dev.to's audience reads new posts, and the engagement signals roll up to your domain via the canonical.
• Hashnode has an RSS importer that respects canonicals. Their free GraphQL API reportedly went paid in May 2026, so prefer the RSS path unless you are already on a paid plan.
• Flipboard has been courting indie publishers in 2026, but the self-serve RSS pipe into magazines is gone, the help article for it now returns a 404. What works today: create a magazine, flip your own articles into it by URL, mix in third-party links so it reads like a magazine instead of a billboard, and email [e-mail] with your feed URL if you want true source-level ingestion.
• Medium has an import flow per article that sets the canonical automatically. Their write API has been closed to new tokens since early 2025, so this is a manual step. Code blocks import poorly. Use it opportunistically for essay-style pieces.

The rule across all of them: never let a syndicated copy live without a canonical pointing home. If a partner's CMS does not support rel="canonical", do not syndicate there.

Social, with realistic expectations

The honest truth about social in 2026 is that the only platform where automation is a clear win for indie publishers is Bluesky. The rest are either too expensive, too restricted, or too judgment-heavy to automate.

Bluesky lets you claim a domain handle for free by adding a DNS TXT record. Claim your domain as the handle, @promptway.com in our case, for the same reason browsers show a padlock: the domain is the verification. The AT Protocol API is free and open, so a publish-time post is a few lines of code with an app password. EchoFeed at about $25 a year will do it for you from your RSS if you do not want to write the code.

LinkedIn is where the operator audience actually reads, especially for AEO and stack-of-tools pieces. Skip their API, which has a restricted approval process you will not pass as an indie. Post manually, or pipe through a tool like Typefully or Buffer. LinkedIn newsletters push to subscribers via email and notifications, which sidesteps the feed algorithm. Worth setting up once you are publishing weekly.

X is a poor investment in 2026. The free API tier is closed to new developers, and in April 2026 URL-containing posts were repriced to roughly $0.20 each on the paid tiers. Keep the account, post important pieces by hand, and put the automation budget anywhere else.

Email is the channel you actually own

Every platform above can change its rules, throttle your reach, or close its API tomorrow. Email cannot. It is the only channel where you own the list and the delivery mechanism.

Two practical pieces. First, you need a transactional sender that can do broadcasts. I use Resend because the API is good, the React Email integration is good, and the dashboard is sane. Postmark and AWS SES work fine too. Second, on every publish, send a broadcast to your audience. This is the closest thing you have to a guaranteed reader.

Do not skip RFC 8058 one-click unsubscribe. Gmail and Yahoo require it for any sender with a meaningful list, and inbox placement gets worse fast without it. Resend handles the headers if you use their broadcasts API; if you roll your own, add List-Unsubscribe and List-Unsubscribe-Post headers and honor the POST.

A welcome email on signup is a nice touch and roughly doubles the chance a subscriber remembers who you are by the time the next broadcast arrives.

The channels that cannot be automated

Some of the highest-value surfaces are also the ones where automation will get you banned, downranked, or quietly ignored. They are worth doing, but they are human work.

Reddit is the biggest of these. Research from ZipTie found Reddit is the most cited domain in Perplexity, near the top in ChatGPT search, and a dominant source in Google's AI Overviews. The dynamic is straightforward: AI engines treat Reddit as a corpus of authentic human discussion, and they pull from it heavily. A single relevant comment with a link to your piece can drive more AI citations than a month of feed syndication.

The catch is that Reddit kills self-promotion on sight. Two to four weeks of genuine participation in a subreddit before you ever post a link is the floor. Read the rules of each sub, the old sitewide 90/10 self-promo rule is retired and each subreddit governs itself now. Text posts that lead with the insight and link out as a citation tend to do better than link posts.

Hacker News is the other one. It rewards founder-bylined essays with plain factual titles and punishes anything that smells like marketing or AI prose. If you have personas writing on your site, post only the pieces under your own name and from an account that comments on other people's submissions too. Do not submit your own work every week.

These are slow channels. They are also where the citation flywheel actually spins.

Automate the mechanical, keep judgment human

The split is the whole game. The mechanical work (indexing, syndication, broadcast, the Bluesky post) belongs in a script that runs on publish. The judgment work (which subreddit, when to post to HN, which LinkedIn comment to respond to) stays with you.

My setup is a single distribute.ts script that GitHub Actions runs after the deploy succeeds. It hits IndexNow, pings the WebSub hub, posts to dev.to via API, sends the Resend broadcast, and posts to Bluesky and Mastodon with the hero art, an author tag, and hashtags. It writes a row to a committed ledger file so re-runs are idempotent. Total code, about a thousand lines, and most of that is per-channel error handling so one flaky API never blocks the rest.

The matching human side is a 15 minute per-article checklist: request indexing in Google Search Console, share-rail posts, one relevant subreddit if it genuinely fits, Medium import. Fifteen minutes is short enough that I actually do it.

Measure what is actually working

The headline number to track is not pageviews. It is AI referrals.

In GA4, build a custom channel group that captures the referrers worth knowing about: chatgpt.com, perplexity.ai, claude.ai, gemini.google.com. Industry data puts AI referrals around 1% of pageviews for most publishers, but they convert at multiples of organic search traffic. They are small, high-intent visits from people whose AI assistant has already vouched for you.

The other dashboards: Google Search Console for indexed pages and impressions, Bing Webmaster Tools for the IndexNow side, Resend for audience growth per broadcast, dev.to organization analytics for the syndicated reach. Look weekly, not daily. None of this moves fast.

The shape of it

The whole stack, in one breath: ship full content feeds, fire IndexNow and WebSub on publish, syndicate with canonicals, post to Bluesky and LinkedIn, email your list, participate honestly on Reddit and Hacker News, and watch the AI referrer channel quietly grow.

Most of it is one-time setup. The publish pipeline runs itself once it is wired. The human channels stay human. The site stays canonical.

The point is not to be everywhere. It is to make sure that when a human or an AI engine wants to find your work, every spoke they touch sends them back to the same place: your domain, your byline, your archive.

That is what gets your writing seen.