Tweet Hunter is a popular tool among indie hackers and creators for sourcing tweet ideas, queueing content, and analyzing what is working on X. The product overlaps with Hypefury and Typefully on the scheduling side, with a stronger lean on idea discovery and inspiration libraries. What Tweet Hunter is not is a card renderer for the WordPress post your tweet links to. The image attached to the queued tweet is whatever was uploaded inside Tweet Hunter, and the link preview is whatever the WordPress post happens to expose through og:image.

For creators who treat X as the entry point to a longer article, that creates a mismatch. The tweet hooks someone, the link drops them into a WordPress post, and the share preview shown when a third party retweets the link is the default WordPress image, not the templated card the original creator was using. The first share looks polished and the downstream shares look generic.

SleekPixel fixes the downstream half by rendering the card from the WordPress post on save. og:image and twitter:image meta point at a 1200x675 PNG using the post fields. Tweet Hunter keeps doing what it is good at (idea sourcing, scheduling, analytics), and the WordPress post produces its own consistent card that every reshare picks up automatically.

Idea libraries and queue analytics are upstream concerns. They help the creator decide what to write and when to post. The rendered card is a downstream concern.

It decides whether the click happens once the tweet is in front of a reader. Treating both as one product is what leads to images uploaded into queue entries that then go stale. Splitting the upstream tool (Tweet Hunter) from the downstream renderer (SleekPixel) gives each one a clear job.

Tweet Hunter keeps making it easier to find ideas and queue them. SleekPixel makes sure the rendered card on the post is correct no matter who shares it. Over time, that downstream consistency is what compounds, because reshares of evergreen posts can outnumber the original share by orders of magnitude.