Quick answer
A good Discover checklist covers more than images, but the image block is usually the fastest place to remove preventable errors. Audit size, preview permissions, file weight, and composition before each article goes live.
Why this matters
Discover traffic is volatile enough that teams often chase anecdotes instead of building systems. A checklist changes the conversation: it turns scattered advice into a repeatable release process that writers, editors, and designers can all follow.
Use the checklist as a companion to the complete image optimization guide. The guide explains the why, while this checklist keeps the why from being forgotten on deadline day.
The core Google Discover checklist
These are the checks that catch the majority of preventable visual mistakes for article pages.
- Featured image is at least 1200px wide and composed for a 16:9 card.
- Page metadata allows large previews through max-image-preview:large.
- Final file is compressed, fast to load, and visually sharp on mobile.
- Image context matches the article angle rather than using generic stock filler.
- Internal links connect the article to stronger topical clusters and the main pillar resource.
- The page is free of distracting layout shifts or broken image rendering states.
How to use the checklist in an editorial workflow
A checklist only works when it belongs to a stage owner. Decide who verifies the image, who verifies metadata, and who signs off on the final preview so responsibility does not vanish between teams.
- Writers define the image intent and article angle before asset creation starts.
- Design or content ops produce the featured image using a fixed 16:9 template.
- SEO or editorial QA verifies size, preview permissions, and internal linking.
- The final approver checks the live preview and publishes only after all blockers are cleared.
Common mistakes
Without a checklist, teams typically repeat the same issues: mismatched ratios, oversized files, missing robots directives, or weak editorial visuals that never stood a chance in a mobile discovery feed.
- Publishing a strong article with a recycled thumbnail that does not support the topic.
- Fixing image size but ignoring the metadata needed for large previews.
- Relying on one person to remember every Discover requirement from memory.
- Treating traffic drops as mysterious when the same visual QA failures keep recurring.
Practical implementation note
DiscoverImg works best when it becomes part of the pre-publish checklist instead of an emergency repair tool. Upload the asset, verify score and preview behavior, and close the loop before the article leaves editorial review.
If you need to tighten the image portion of the process further, revisit the size guide and the featured image guide. Then finalize the asset through DiscoverImg Optimizer.
Frequently asked questions
Is there a single Google Discover checklist that guarantees traffic?
No checklist can guarantee traffic, but a disciplined checklist removes many preventable technical and visual mistakes that hurt eligibility and presentation.
What is the most important image check before publishing?
Confirm that the image is at least 1200px wide, visually strong at a 16:9 ratio, and allowed to appear as a large preview.
Who should own Discover QA?
The strongest teams split responsibility clearly across editorial, design, and technical QA instead of leaving all Discover checks to one person.
How often should I audit older posts?
Audit older templates and high-value evergreen posts regularly, especially after site redesigns, CMS changes, or metadata refactors.
Can a tool replace the checklist?
A tool can speed up verification, but the checklist is what keeps the workflow consistent across people and publishing cycles.
