1. Confirm the destination accounts
Before preparing captions, verify which Page, channel, or professional account is selected for each platform. Similar account names are a common source of mistakes. If you manage client or brand accounts, compare the displayed profile name and provider identifier where the application makes it available.
2. Check the media itself
Play the final video or inspect the final image, not only the project file. Confirm orientation, duration, audio, captions burned into the media, and safe placement of important text. A title that looks correct on desktop may be cropped in a vertical mobile feed.
3. Adapt copy to the platform
Do not treat every platform caption as an identical text box. Keep the core message consistent while adjusting the title, description, call to action, and hashtag count to the destination. Remove placeholder text and verify that generated suggestions actually describe the media being published.
4. Review privacy and audience settings
Check whether the post will be public, unlisted, private, draft, or otherwise limited. Platform terminology differs, so confirm the setting shown for the selected destination rather than assuming the last-used value will carry over.
5. Schedule in the destination’s intended time
If you schedule content, verify the date, clock time, and target audience location. A schedule displayed in local desktop time may not match the audience’s local time. Keep a written campaign time when several platforms must go live together.
6. Confirm connection health
If an account shows Reconnect, Expired, Permission Required, or another warning, fix the connection before the scheduled time. A queue entry cannot compensate for a provider token that no longer has permission to publish.
7. Review the final queue
Check the media filename, destination, caption, schedule, and post type in the queue. If the same content appears twice for the same destination, remove the duplicate before publishing.
8. Verify after publishing
A successful API response is important, but the user should still open the resulting post or provider link and confirm that the public result is correct. Check the thumbnail, title, privacy, audio, and destination account.
9. Record failures rather than retrying blindly
If a provider returns an error, read the message before pressing Publish again. Repeated retries can create duplicates if the first request actually succeeded but the confirmation response was delayed. Use publishing history and provider links to verify the current state.
Related resources
Wonder Publisher AI documentation →
Basic YouTube channel monitoring →