Blog images, alt text and infographics
Blog images prove the business is real: your own photos and charts show work only you could have done, and generic pictures prove the opposite. Use your own material first, and make every image fast, described and unique.
Files and performance
- Every page image is WebP, with its real width and height, a responsive srcset, and lazy loading except for the hero. The hero loads eagerly with high fetch priority and is preloaded. The favicon and the Open Graph PNG are the exceptions.
- A blog cover is WebP at 1600 × 900.
- Every post and every linkable page has its own social sharing image: 1200 × 630, in the brand's colours and fonts, with the page title on it. It is generated at build time for every new post, in every language, and served publicly even when the page itself is gated, so a shared link always shows a preview.
- File names are descriptive keyword slugs, in the site's own naming style ("what and where", "material and part").

Alt text
- Alt text says what the image shows, in plain words a person who can't see it would understand: "a 150-litre boiler on a kitchen wall in a 1970s flat", not "boiler image". It never repeats or contradicts the copy, and no two images share one.
- Write it as a sentence in the page's language, 70 to 140 characters, with a figure first where it fits.
Sources and realism
- Real photos first: the business's own work photos. Never stock photos of people, never images from other businesses, and every picture your own, never copied from another site.
- Photograph the people, premises and finished work. A generated picture never stands in for staff, an office or a job you did; readers and search engines both learn to spot it.
- A phone is enough for your own photos: good daylight, the whole job in frame, people at work rather than posing, a tidy site and no other company's logos in shot.
- Not every image needs a person. Take the before and after photos from the same spot.
- Capture real screens for real interfaces. When the post discusses a search result, a business profile or a test score, show a real capture of it, taken on the day you write and dated in the caption. Never draw a screen the reader can check for themselves.
What counts as your own picture changes with the business.
- For an online store: product images come from the catalogue (the same photos as the product page, with alt text written for the post's context), plus photos of the product in use.
- For a software or B2B company: real screenshots of the product interface, cropped to the part the text discusses, with any customer data replaced.
Infographics and charts
- Beside the photos, every post that teaches something carries visual explainers: infographics, charts and graphs, and diagrams of how the job works.
- Make them linkable. Each one holds a finding other sites want to cite, with its own descriptive file name, alt text and a caption naming where its data comes from.
- Every language gets its own version, with the text written natively in that language.
- They use the site's own colours and fonts, so your graphics look like your site and no other.
- The facts in a graphic also appear in the text.
- In-house data in a graphic comes from your own records; outside data is sourced in the caption.
Draw infographics with code
An infographic drawn by code from the same data as the text stays correct in every language and costs nothing to update.
- Keep the figure's words and numbers in a data file per language, and let one template draw every language's version, so a changed figure changes every image at once.
- Save charts as WebP or PNG, at least twice the width the page shows them at, so the smallest label stays sharp on a phone.
- Give every image its class: a photo (no text) is compressed hard; an image with text, a chart or a screenshot is lossless and never squeezed.
- Every post carries at least one image.
- Write the caption on the page, not in the picture: the finding in one sentence and the source of its data, in the page's language.
- Load images below the first screen lazily, with their width and height set, so the page never jumps while they arrive.

Image search and sharing
An image that answers a question on its own gets found in image search and shared in chats, and every share carries your name with it.
- Give each infographic a caption that states its finding, so the picture makes sense when it travels without the post.
- Put your brand's colours and fonts in every chart, so a copied image still looks like yours.
- Offer the best charts as linkable assets: each one at its own address, with a line of code a writer can paste to embed it with a credit link back to the post.
- Check how a shared link previews in a chat app and on a social network before the post goes out; the sharing image carries the title in the page's language.
What to show
- Prefer a real interface fragment to an abstract diagram (a search result row, a business profile card, a test result) and make the number the hero.
- Drawings beat photos for hidden work (pipe routes, valve schemes, data flows) and can be a site's signature proof object.
- Key facts never live only in images, PDFs or script-driven widgets.
Edited by Andres LepikCo-founder & Head of Growth
Fact-checked by Siim SaarHead of SEO
Post by Rasmus Kivi
Co-founder & CEO
Co-founded REND and still reads every client's monthly report himself before it goes out.