Facebook supports several very different publishing jobs: a Page update for existing followers, a link or announcement, a set of images, or a short-form Reel. The workflow should choose the format from the communication objective instead of forcing every idea through one template.
Current BlendDuck publishing contract
BlendDuck supports Facebook Page text, single-image, multi-image, and Reel posts. Text can contain up to 63,206 Unicode characters, though readable publishing is usually much shorter. A post can carry up to ten images or one video; mixed image and video batches are not supported.
For video in the current contract, Facebook Reels require a 9:16 aspect ratio, at least 540 by 960 pixels, and a duration from 4 to 60 seconds. Hashtags are supported. The current product contract does not expose additional Facebook-specific post settings.
Match format to the message
Use text when context and conversation matter more than visual demonstration. Use a single image when one proof point or announcement needs recognition. Use multiple images when order, comparison, or event coverage adds value. Use a Reel when movement, demonstration, personality, or transformation is central.
Long character capacity is not permission to bury the point. Put the audience, event, change, or value early. Break long explanations into readable paragraphs and make link expectations explicit. If the post depends on a date, location, price, policy, or availability, assign an owner to confirm it close to publication.
For image sets, define the first image and sequence deliberately. Verify crop and legibility on both desktop and phone. For Reels, keep essential subjects and text inside a safe central area, add accurate captions, and review the 9:16 export at actual phone size.
Review identity, rights, and risk
Confirm the Page identity rather than relying on a familiar display name. Check names, claims, links, offers, dates, locations, customer material, and any regulated or sensitive language. Record rights for music, footage, photographs, testimonials, and user-generated content.
Approval should bind the exact text and media version to the destination. A different image order, edited link, changed offer, or replacement audio track can change meaning and invalidate approval. Use a risk-based path so routine evergreen posts do not wait behind sensitive announcements.
Publish, verify, and recover
Before scheduling, check timezone, campaign dependencies, connected permissions, and whether the Page can publish the selected format. Keep scheduled, sending, accepted, processing, live, failed, and unknown states distinct.
After publication, inspect the public post for text, links, image order, crop, captions, audio, and destination identity. Save the live URL. If status is unknown, check provider evidence before retrying; duplicate Page posts can confuse reporting and community response.
Measure the job of the post
Use metrics tied to the objective: qualified link actions for a resource, event responses for an event, meaningful comments for a community question, or completion and downstream action for a Reel. Compare like formats over the same reporting window.
Include community effort and negative feedback in the learning record. A high-reach announcement that creates avoidable support load may need clearer copy next time. End with a specific next action rather than a generic performance label.
Facebook publishing checklist
- Correct Facebook Page and permissions verified
- Format uses text, up to ten images, or one video
- Reel is 9:16, at least 540 × 960, and 4–60 seconds
- Copy, links, dates, offers, names, and facts checked
- Media order, crop, captions, rights, and accessibility reviewed
- Approved version matches the scheduled destination version
- Timezone and campaign dependencies confirmed
- Public URL and final delivery state recorded
Current product limits were verified on 2026-08-23 against BlendDuck's Facebook platform contract. Meta policies, Page eligibility, and API behavior can change; confirm sensitive requirements in current official documentation.
