When Something Looks Off, Start Here.

Two common causes. First, you may be at your monthly generation limit - check the counter near the top of the screen. Second, a browser extension or stale cache can hide the button. A hard refresh usually fixes the second one.

Try this in order:

1. Hard refresh the page (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac).
2. Check your generation counter - if you're at the cap, the button hides until next month or until you add more credits.
3. Disable ad blockers or content blockers for posthelp.ai and reload.
4. If the button is still missing, email hello@posthelp.ai with your browser and platform.

Generic captions almost always trace back to a thin profile or no save history. PostHelp leans on three signals to write in your voice: your tone selections, your Rules / Guidelines field, and the rolling window of your last 20 saved posts.

Fix it at the source:

1. Open your profile and pick at least two or three tone pills. One tone alone gives the AI very little to work with.
2. Add concrete instructions to the Rules field. "Always end with a question." "Never use the word 'amazing.'" "Mention we're family-owned when it fits." Specific beats general.
3. Save the captions you love. Voice learning kicks in after a handful of saves and gets stronger from there. The AI mimics how YOU write while avoiding repetition.

GBP is the one platform that does not accept a photo embedded in the paste. The caption pastes fine, but the photo has to be uploaded separately through the GBP "Add update" interface.

The flow: copy the caption from PostHelp, click Add Update in your Google Business Profile, attach your photo using GBP's photo picker, then paste the caption into the text field. PostHelp's GBP captions are also tuned to be hashtag-light by default - GBP rewards plain text over hashtag-heavy posts.

Each click of Generate counts as one generation - including Redo. If you Redo a post twice for the same photo, that's three generations against your cap, not one. Editing inline is free; Redo is not.

Two ways to stretch your cap:

1. Edit captions inline instead of using Redo. Most small fixes (a different opener, a swapped hashtag) are faster as inline edits.
2. Add the +10 add-on credits when you're close to the cap. They're applied automatically the next time you Generate, no upgrade or contract change required.

If you're consistently running out, the next plan up is usually the right move - email hello@posthelp.ai and we'll talk it through.

Most fetch failures are pages behind a login, paywall, or hard redirect. Some are pages that hide their text behind heavy JavaScript. PostHelp returns gracefully without consuming a generation when this happens, so you don't lose anything.

Try one of these:

1. Use a different public URL from the same site - usually a deeper article or product page works when a homepage doesn't.
2. Switch to Photo mode and write the caption from a screenshot of the page.
3. If it's a page you own, make sure it's published, not behind a maintenance redirect, and not blocking server fetches via robots.

The link image waterfall tries three sources in order: the page's social share image (og:image), then the favicon, then a bundled PostHelp logo as a final fallback. If you got the logo, the page didn't have a usable share image OR favicon.

If it's your own page: add an og:image tag in the page head - that's the standard social-share image tag every social platform reads. Most modern themes have a setting for it. Once added, regenerate and the image picks up automatically.

If it's someone else's page: you can't fix the source, but you can switch to Photo mode and use your own image with the same caption intent.

Link posts auto-detect category from the page's structured data (Schema.org markers for BlogPosting, NewsArticle, Product, WebPage). The detection is helpful but not always right - a recipe page tagged as Article might land somewhere generic.

Two options: regenerate with a different URL on the same site that has clearer markup, or switch to Photo mode where you pick the category yourself from the seven options. Photo mode is the only path that gives you full manual control over category.

Some phone photos carry orientation metadata that browsers handle inconsistently. PostHelp shows the photo as the browser interpreted it. There is a rotate button in the upload preview - tap it before clicking Generate. The AI sees the rotated version, not the sideways one.

Tip: rotate before you generate. Rotating after means the AI's caption was written based on the original orientation, which is rarely what you want.

History filters might be hiding it. Above your saved posts list there's an All / Photos / Links toggle - if it's set to Photos and your missing post is a link post (or vice versa), the filter is doing exactly what it's supposed to. Switch the filter to All to see everything.

Also worth knowing: copying a caption auto-saves it to history if your "Copy saves to history" toggle is on. If that toggle is off, posts you copied but didn't explicitly save are not stored anywhere. Saved or not, posts never delete on their own - the rolling 20-post voice-learning window is a separate read; saved posts older than 20 still count as saved, they just don't feed voice learning anymore.

If you set a per-platform hashtag count and posts before April 28, 2026 ignored it, that's the v2.5.1 hashtag-count fix. Older posts were generated before the fix shipped. Generate a new post and the count is honored.

If new posts still don't match, double-check: each profile has its own per-platform hashtag toggle and count. The setting is on the profile, not on the account, so if you switch profiles the hashtag rules switch with it.

That's the free-tier organic-marketing tag. Every free-trial post on a hashtag-enabled platform gets #PostHelp prepended as the first hashtag. It's how we keep the free tier sustainable without making it ad-supported. Paid plans (Basic, Pro, Elite) get nothing added - your hashtags are entirely yours.

Platforms with hashtags disabled (Google Business Profile by default, or any platform you've turned off) are untouched on every plan.

Email hello@posthelp.ai. Bug reports go straight to the developer. Feature requests get logged and reviewed against the roadmap. PostHelp is built and maintained by a real person, not a support team that filters everything - you'll get a real answer, not a ticket number.