Grouped image inventory
Review each discovered image source with its usage and source-page counts instead of treating every repeated occurrence as a separate file.
Image SEO Analysis Tool
Group the image sources used across your website, filter missing alt text, dimensions, broken responses, and responsive delivery, then trace each finding to the pages and shared components that need review.
TL;DR
Too Long; Didn't Read
Show summary Hide summary
TL;DR
Too Long; Didn't Read
What Is Image SEO Analysis?
Screpy Image SEO Analysis groups the image sources discovered in a completed website crawl and connects each source with its technical signals and source pages. Use the report to investigate accessibility, dimensions, response health, loading, responsive delivery, and repeated implementation patterns before deciding what to change.
Build the image inventory
- Group each discovered source with its total uses and crawled source-page count.
- Use All Images for coverage and All Issues as the first investigation queue.
- Search within the selected crawl instead of mixing evidence from different snapshots.
- Keep the preview and source URL beside the recorded image signals.
Review accessibility in context
- Compare Missing Alt and Has Alt instead of assuming any non-empty value is useful.
- Open every relevant Source Page before writing or changing alternative text.
- Distinguish informative, functional, complex, and decorative image purposes.
- Treat an intentionally empty alt value differently from a missing decision.
Inspect delivery and markup
- Separate successful, redirected, client-error, server-error, and broken responses.
- Find image uses without recorded width or height dimensions.
- Compare sources with and without srcset before planning responsive delivery.
- Review loading behavior, response time, external sources, SVGs, and data URIs.
Fix and verify the shared cause
- Use source-page counts to prioritize patterns repeated across important templates.
- Find the CMS field, component, template, stylesheet, asset, or URL that owns the issue.
- Validate the published page and image response at representative viewport sizes.
- Run a comparable crawl to confirm that the intended queue changed.
Review each image source together with every page that uses it.
Turn a completed crawl into a grouped image inventory with a preview, source URL, total uses, source-page count, recorded issues, and direct access to the pages where the asset appears.
Learn more about grouped inventory- Separate one image source from its repeated page occurrences
- Move between All Images and focused issue queues
- Trace shared assets back to the component or content that owns them
Decide what the alternative should say from the page purpose.
Compare missing and present alt values, then inspect representative source pages. The same image can be informative, functional, complex, or decorative depending on how the page uses it.
Learn more about alt text context- Use Missing Alt as an investigation queue rather than a quality score
- Keep deliberately empty decorative alternatives distinct from mistakes
- Review repeated uses before applying one description everywhere
Separate unavailable sources from incomplete layout markup.
Filter successful, redirected, client-error, server-error, and broken responses independently from missing dimensions. Each signal leads to a different technical investigation and verification step.
Learn more about response and dimensions- Test failed source URLs and inspect every affected page
- Review missing width or height without assuming the image caused CLS
- Keep response time and loading evidence in its measured context
Review responsive delivery and source type without forcing one rule.
Compare sources with and without srcset alongside loading behavior, external ownership, SVG, and data-URI signals. Use the asset role and rendered layout to decide which delivery pattern is appropriate.
Learn more about responsive sources- Find raster-image uses that may need responsive candidates
- Keep a crawlable fallback source when implementing srcset
- Evaluate external, SVG, and data-URI sources by their actual use
See the image, the issue, and every page that uses it.
Screpy turns a completed crawl into a grouped image inventory. The report keeps source URLs, usage, source pages, alt text, dimensions, response health, loading, and responsive signals connected for investigation.
Issue presets and counts
Move from All Images to focused queues for alt text, dimensions, response codes, source types, formats, and responsive delivery.
Alt text and page context
Compare missing and present alt values, then open the source pages before deciding whether an image is informative, functional, complex, or decorative.
Image dimensions
Find image uses without width or height data and review the affected page before changing markup, CSS, aspect ratio, or the underlying asset.
Response health
Separate successful, redirected, client-error, server-error, and broken image responses so unavailable assets can be traced to the pages requesting them.
Loading and response context
Keep the recorded loading behavior and fetch response time beside the image and page evidence without presenting either value as a Core Web Vitals diagnosis.
Responsive source coverage
Compare images with and without a recorded srcset, then decide whether the page and asset actually need responsive candidates for their layout.
Source-page drilldown
Open every crawled page using the same source to find the CMS field, component, template, stylesheet, or content entry where the fix belongs.
Turn an image finding into a verified website fix.
Begin with representative crawl coverage, interpret the issue in page context, repair the shared cause, and verify the public result in a comparable crawl.
- 01
Start with a completed, representative crawl
Choose a crawl whose scope and rendering settings cover the templates you need to review. A partial crawl produces a partial image inventory.
- 02
Use All Issues as a queue, not a verdict
Review the grouped counts for missing alt text, missing dimensions, unsuccessful responses, and missing srcset, then select the category tied to the current goal.
- 03
Open representative source pages
Inspect the image in its visible page context. The same source can be decorative on one page, informative on another, or the only content inside a link.
- 04
Fix the shared cause at the right layer
Update the asset, URL, CMS field, component, template, CSS, or delivery rule that created the repeated pattern instead of patching each occurrence independently.
- 05
Verify the public result and crawl again
Check representative mobile and desktop pages, confirm the image response and markup, then run a comparable crawl to see whether the intended queue changed.
Use Image SEO Analysis where one asset can affect many pages.
Grouped image evidence is especially useful for publishing libraries, ecommerce catalogues, redesigns, migrations, and repeatable agency audits.
Publishing and content libraries
Find repeated editorial images, missing contextual alternatives, and shared content patterns across articles, guides, and landing pages.
- Editorial context
- Repeated assets
- Accessible alternatives
Ecommerce catalogues
Trace product and category image problems across templates where one unavailable source or markup pattern can affect many shopping journeys.
- Product templates
- Shared sources
- Broken variants
Redesigns and migrations
Create a pre-release inventory, then look for moved sources, missing attributes, or responsive-delivery changes after a template or platform migration.
- Before-and-after crawl
- Moved sources
- Template regressions
Agency and multi-site reviews
Turn grouped image evidence into a focused implementation queue while keeping each recommendation attached to the pages and purpose it affects.
- Scoped evidence
- Source-page examples
- Verified recrawl
Interpret image findings before turning them into tasks.
A crawler can reveal missing or unsuccessful signals, but the image purpose, rendered layout, delivery strategy, and source-page context determine the correct fix.
Empty alt text can be correct
The Missing Alt queue includes empty values, but a deliberately empty alt attribute is appropriate for a decorative image. Decide from the page context, not the count alone.
Missing dimensions do not prove poor CLS
Width and height attributes help reserve space, but CSS and containers can also control layout. Validate the rendered page and measured layout shifts before assigning a cause.
Missing srcset is not always a defect
Responsive candidates are useful for many raster images, but not every icon, vector, tiny asset, or fixed-size use needs the same delivery pattern.
The report audits; it does not edit assets
Screpy records crawl evidence and source-page relationships. It does not automatically compress files, rewrite alt text, change markup, or guarantee image-search rankings.
Choose the image analysis that matches the scope.
Audit images across a completed crawl, investigate them inside the wider crawler workflow, or check the image signals on one public page for free.
Group crawled image sources, filter technical and accessibility findings, and trace repeated assets to every source page.
Review images together with pages, links, responses, crawl scope, and the wider technical SEO inventory.
Check one public URL for image, accessibility, metadata, link, structured-data, and technical page signals without an account.
Screpy documentation
Learn how to audit website images
Use the Screpy images guide to interpret issue queues, inspect each asset in its source-page context, choose the correct fix, and verify the result with a comparable crawl.
Related SEO guides
Learn the concepts behind this workflow and apply them with practical SEO guidance.
SEO
What Is Image SEO? How Is It Done?
Learn image SEO basics, from choosing relevant visuals and file formats to alt text, compression, indexability, page speed, and user experience.
Read article Content Marketing
SEO Strategy for Blog Sites: How To Optimize Your Blog Website
Build a stronger blog SEO strategy with better design, image optimization, keyword research, content planning, internal links, and technical checks.
Read article SEO
Hold Your Website Rankings Back: 6 Tips!
Avoid SEO mistakes that hold back rankings, including low-quality content, clickbait, duplicate pages, hard-to-read text, and poor user experience.
Read article SEO
How Does an AI Technical SEO Audit Find Website Issues?
An AI technical SEO audit analyzes crawl and performance data to flag indexation, redirects, broken links, and schema issues, then prioritizes fixes by impact.
Read articleImage SEO Analysis FAQ
Understand alt-text context, dimensions, responsive sources, response failures, crawl scope, source pages, and what the report does not change automatically.
What does Screpy Image SEO Analysis check?
It groups images discovered in a website crawl and provides focused views for alt text, dimensions, response codes, broken images, external sources, SVGs, data URIs, srcset coverage, loading behavior, and source pages. Available evidence depends on the selected crawl and what it could discover.
Does every image need descriptive alt text?
No. Informative images need useful contextual alternatives, functional images should describe their action or destination, and complex images may need nearby explanation. Purely decorative images normally use an intentionally empty alt attribute. Review the image on each source page before changing it.
Does Screpy generate or rewrite alt text automatically?
No. The report identifies missing and present alt values and shows where an image is used. A person who understands the page purpose should decide whether the alternative needs to be descriptive, empty, or supported by a longer explanation.
Does a Missing Dimensions finding mean the page has poor Core Web Vitals?
No. Missing width or height is a useful markup signal, not proof that an image caused layout shift. Inspect the rendered layout and compare measured performance because CSS, containers, fonts, banners, and injected content can also affect CLS.
Does every image need a srcset?
No. Responsive source candidates can reduce unnecessary downloads for many raster images, but the right choice depends on the asset, rendered size, layout, browser support, and delivery workflow. Keep a usable src fallback when implementing responsive images.
What counts as a broken image in the report?
The report separates successful and redirected responses from client and server errors. The Broken view combines unsuccessful image responses so you can test the source URL, inspect every source page, and repair the URL, asset, template, or delivery rule responsible.
Does Image SEO Analysis compress or resize image files?
No. The current workflow is a crawl-based audit, not an image editor or compression service. Use the source-page, response, dimensions, loading, and format evidence to decide what should change in your CMS, code, asset pipeline, or delivery setup.
How do I verify an image SEO fix?
Publish the change, inspect representative pages at mobile and desktop widths, test the image URL and rendered markup, then run a comparable crawl. Confirm that the intended issue count and source-page uses changed without introducing a new accessibility or delivery problem.