Screenshots
Choose how article images are captured, and upload real product screenshots to the Image library.
Articles need images, and AgenticSEO gets them in two ways. The writer can ask for a screenshot of any public page, which your screenshot service captures. And you can upload real screenshots of your product to the Image library, which the writer uses when it shows your own app. QA checks that images are present and have alt text.
Choose a screenshot service
Open Settings > Integrations, card Screenshots (article images).
| Service | Cost | Notes |
|---|---|---|
| Built-in (free) | Free | Chromium with Playwright on the app server. No key, no monthly limit. Hides most cookie banners and chat widgets |
| Microlink | Free for about 50 screenshots a day with no key | Add an API key for more |
| ScreenshotOne | Paid service (100 free a month) | Strong blocking of ads and cookie banners |
| No screenshots | Free | Articles get no images. QA does not require images |
The default is Built-in (free).
| Setting | What it does | Default |
|---|---|---|
| Service | Which screenshot service to use | Built-in (free) |
| Microlink API key (optional) | Leave empty to use the free plan (about 50 screenshots a day) | Empty |
| ScreenshotOne access key | Needed for ScreenshotOne | Empty |
Use Test to see a sample image before you save.
Note: Built-in screenshots need Chromium on the app server. If the test shows that the built-in browser could not start, choose Microlink or ScreenshotOne.
How screenshots get into an article
- The writer adds an image line that names a real, public URL and describes what the image shows.
- The app captures that URL with your service.
- The image is stored and placed in the draft. The description becomes the alt text.
Rules:
- Up to 6 new screenshots per draft.
- A screenshot of the same URL from the last 30 days is reused, so rewrites do not pay again.
- If a capture fails, the image is removed and the reason goes into the writer notes, for example "Screenshot failed for ...".
The Image library
Automatic screenshots show public pages. They cannot show your app in use behind a login. For that, upload your own screenshots.
- Open Image library in the site menu.
- Under Add screenshots, choose up to 5 images (PNG, JPG, WebP or GIF, 5 MB each).
- In What the image shows, describe each one in detail.
- Click Upload.
Be specific in the description. The writer reads it to choose the right image, and it becomes the alt text. A good description:
Dashboard: a revenue-by-region bar chart with the follow-up question "Compare with last year" beside it.
Tip: Upload 5 to 10 screenshots of your key screens: the main dashboard, a settings page, a report, and one image per main feature. QA fails product articles that use none of your library images.
Removing an image from the library does not break published articles that use it.
Images and QA
| QA check | Rule |
|---|---|
| Images | At least Min images (default 1). Critical when a screenshot service is set up |
| Image alt text | Every image needs useful alt text |
| Uses an approved product screenshot | Articles about your product must use a library image, when your library has images |
With No screenshots, the images check does not block publishing.
Images when you publish
| Target | What happens to images |
|---|---|
| WordPress, Ghost | Uploaded to your CMS media library |
| GitHub | Committed to your image folder |
| Webflow, Shopify, webhook | Linked from the app, so the app must be on a public URL |
| Manual | Download each image from the ticket and upload it yourself |
See CMS.
Fix common errors
| Message | Fix |
|---|---|
| The built-in screenshot browser could not start | The server is missing Chromium. Choose Microlink or ScreenshotOne |
| Microlink free limit reached (about 50 a day). | Add a Microlink API key or use the built-in service |
| ... answered HTTP 404. Use a page that exists. | The writer named a missing page. The image is skipped |
| No ScreenshotOne access key. | Add the key or pick another service |
Each screenshot counts on the AI usage page.
Did this page help? Tell us at support@agenticseo.com.