Distribution·Guide

What leaves your site

Every way of sharing your work sends something out of your site, and no two channels send the same thing. One carries a blog excerpt. One carries a link. One carries an image. Knowing which is which is what makes the switches easy to set.

Four channels

What each one carries

  1. RSS

    Blog posts, as an excerpt or roughly the first 500 characters of HTML, plus a link. It's a feed of writing, not a photo feed.

  2. Link previews and embeds

    A card (title, short text, one image) from Open Graph, or an embed where the other site reads oEmbed. Hiding a page from search doesn't remove either.

  3. Share buttons

    Your URL and nothing else. A visitor opens Facebook, X, or LinkedIn with the link filled in, and the network builds its own preview from your page.

  4. Open Web Distribution

    The only channel that sends a copy of the image: a public JPEG up to 2048 px with copyright metadata, the caption, and a link home.

Four payloads, one table

ChannelWhat travelsWhere a copy livesWhat you can pull back
RSSExcerpt and linkFeed readers and aggregatorsEdit or delete on your site. A reader may keep what it already fetched
Link previews and embedsA card (title, short text, one image), or an embed where the other site reads oEmbedThe app or site that fetched itFix the page, then each platform refreshes on its own schedule
Share buttonsA URLNothing from youSame as link previews and embeds
Open Web DistributionImage, caption, linkEvery server that received the postA Delete is sent. Removal elsewhere isn't guaranteed

Each channel is its own switch

ArtInStack keeps these separate on purpose. Turning on RSS doesn't turn on Open Web Distribution, and neither changes what a pasted link looks like. Sharing buttons are off until you want a collection to travel, and stay off when it should feel like a quiet viewing room. Each channel does one job, so you can match the channel to how your audience already behaves.

Email Center campaigns are a separate channel again: a list you chose, on a schedule you set. They are not RSS, Open Graph, or Open Web Distribution. See Built-in email or a separate tool.

Previews and embeds are fetched, not sent

You never push a preview or an embed anywhere. When someone pastes your public URL, the chat app or editor fetches the page: Open Graph for a card, oEmbed when the host wants a richer embed. That's why either can lag behind a fix: each platform holds its own copy and refreshes it on its own schedule. The docs page on link previews has the refresh steps. Search visibility is a separate system, which is why hide from search leaves the card and the embed path intact. See Hide from search, noindex, and private.

What stays home, in every channel

Vault links and private-portfolio files are kept out of these channels on purpose. RAW files and originals never go out, only the public web derivative. Nothing is published outward unless you chose it.

What none of this controls

These channels describe what you send. They don't stop anyone from saving a public image, and they don't govern crawlers. The site's robots.txt today allows crawling and points to your sitemap; there are no AI-crawler controls. Treat anything you make public as copyable, and let that decide what goes on a public page.

Know what travels before you switch it on

Four channels, four payloads. Only one sends a copy.

Also in Guides: Open Web Distribution, honestly · Built-in email or a separate tool · Hide from search, noindex, and private · Public vs private work

All Distribution guides · Guides home