
A guest post can be ready to read but still be difficult to publish. The writer sends a polished draft, then the editor has to ask which image belongs where, whether the chart is a real result, and what the caption should say. A small image handoff sheet prevents much of that back-and-forth.
This guest post image checklist focuses on preparing useful visuals for an editor. It is not a requirement to add pictures to every article. If an image does not explain something, support a practical example or help the reader navigate the topic, leave it out.
Start with the job, not the decoration
Write one sentence explaining why each proposed image belongs in the article. “Shows where to find the export button” is a useful purpose. “Makes the post look longer” is not. An annotated screenshot may help with software instructions; a simple diagram may explain a handoff; a photograph may clarify a physical detail that words alone cannot describe easily.
Ask the publisher for its image specifications before exporting files. Confirm preferred dimensions, accepted formats, file-size limits and whether the editor wants separate uploads or an accessible shared folder. Keep the editable original, but send an export the publisher can actually use.
Prepare a short record for each visual
Use the following fields in a document next to the draft. One record per image is easier to review than a collection of unexplained attachments.
- Filename: a short, descriptive name such as editorial-handoff-flow.png.
- Placement: the heading and paragraph after which the image belongs.
- Purpose: what the reader should understand from it.
- Caption: context, limitations and any required credit.
- Alt-text suggestion: the useful visual information in the context of this article.
- Source and usage record: who created it, where it came from and the permission or licence information supplied for editorial review.
- Review status: approved, needs a correction, or do not publish.
Do not treat a search-result thumbnail as a reusable asset. If usage rights are unclear, hold the image back and ask the publisher what evidence it needs. This checklist is an editorial workflow, not legal advice about a particular image.
Distinguish examples from evidence
A mock dashboard is useful for teaching, but it should not look like an actual client result. Label invented numbers and interfaces as illustrative. Do not replace real results with a generated screenshot, invent a customer quote inside an image, or imply that a staged scene documents completed work.
For a genuine screenshot, review names, email addresses, account identifiers, customer information and browser tabs before sharing. Crop to the necessary area and obtain the relevant approval. Keep enough context that the crop does not change the meaning. If sensitive information cannot be removed reliably, use a clearly labelled fictional example instead.
Write the caption and alt text separately
A caption explains why the visual matters; alt text conveys its useful information when it cannot be seen. They may overlap, but copying the article title into both fields rarely helps. The W3C guidance on informative images explains that an image’s purpose and context determine the alternative it needs.
For a three-step workflow, an appropriate alternative might be “Writer prepares the image record, editor checks it, and publisher places the approved export.” A caption could add “Illustrative workflow; the publisher’s own requirements take priority.” A decorative background may need an empty alternative rather than a keyword-filled description. Give the editor a recommendation and let them assess the final page context.
Check readability at the size readers will see
Open the export at roughly the intended display width. Can you read the labels without zooming? Does a mobile-sized view hide the important detail? If the diagram contains a long paragraph, move that explanation into the article. Essential instructions and data should not be available only as tiny text inside an image.
Check the crop, contrast and spelling. Compare the compressed export with the original so that compression has not blurred the very detail the reader needs. Avoid a fixed file-size target that makes an instructional screenshot illegible; follow the publisher’s performance requirements while preserving its purpose.
A worked handoff example
Imagine a contribution explaining a three-person editorial workflow. The image is an original diagram, not a screenshot of a real client system. Its record reads: “Place after ‘Who approves the draft’; purpose: show the approval order; caption: illustrative roles, not a promised turnaround; alt text: Writer sends draft to editor, then approved copy goes to publisher; source: original diagram created for this contribution.”
That gives the editor a decision-ready asset. By contrast, sending final-image-v7.png with “please add somewhere” leaves both placement and meaning unresolved.
Before sending the article
Match every filename to its record, remove unused exports and check that the editor can access the files. Include these assets in your guest post submission handoff, and record outstanding image questions in your outreach tracker. Send a replacement with a clear version note if an image changes after review.
The goal is not more images or a higher keyword count. It is a contribution the publisher can understand, verify and present clearly to its readers.