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.
Too Long; Didn't Read
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.
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 inventoryCompare 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 contextFilter 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 dimensionsCompare 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 sourcesScrepy 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.
Review each discovered image source with its usage and source-page counts instead of treating every repeated occurrence as a separate file.
Move from All Images to focused queues for alt text, dimensions, response codes, source types, formats, and responsive delivery.
Compare missing and present alt values, then open the source pages before deciding whether an image is informative, functional, complex, or decorative.
Find image uses without width or height data and review the affected page before changing markup, CSS, aspect ratio, or the underlying asset.
Separate successful, redirected, client-error, server-error, and broken image responses so unavailable assets can be traced to the pages requesting them.
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.
Compare images with and without a recorded srcset, then decide whether the page and asset actually need responsive candidates for their layout.
Open every crawled page using the same source to find the CMS field, component, template, stylesheet, or content entry where the fix belongs.
Begin with representative crawl coverage, interpret the issue in page context, repair the shared cause, and verify the public result in a comparable crawl.
Choose a crawl whose scope and rendering settings cover the templates you need to review. A partial crawl produces a partial image inventory.
Review the grouped counts for missing alt text, missing dimensions, unsuccessful responses, and missing srcset, then select the category tied to the current goal.
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.
Update the asset, URL, CMS field, component, template, CSS, or delivery rule that created the repeated pattern instead of patching each occurrence independently.
Check representative mobile and desktop pages, confirm the image response and markup, then run a comparable crawl to see whether the intended queue changed.
Grouped image evidence is especially useful for publishing libraries, ecommerce catalogues, redesigns, migrations, and repeatable agency audits.
Find repeated editorial images, missing contextual alternatives, and shared content patterns across articles, guides, and landing pages.
Trace product and category image problems across templates where one unavailable source or markup pattern can affect many shopping journeys.
Create a pre-release inventory, then look for moved sources, missing attributes, or responsive-delivery changes after a template or platform migration.
Turn grouped image evidence into a focused implementation queue while keeping each recommendation attached to the pages and purpose it affects.
A crawler can reveal missing or unsuccessful signals, but the image purpose, rendered layout, delivery strategy, and source-page context determine the correct fix.
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.
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.
Responsive candidates are useful for many raster images, but not every icon, vector, tiny asset, or fixed-size use needs the same delivery pattern.
Screpy records crawl evidence and source-page relationships. It does not automatically compress files, rewrite alt text, change markup, or guarantee image-search rankings.
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
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.
Learn the concepts behind this workflow and apply them with practical SEO guidance.
Learn image SEO basics, from choosing relevant visuals and file formats to alt text, compression, indexability, page speed, and user experience.
Read articleBuild a stronger blog SEO strategy with better design, image optimization, keyword research, content planning, internal links, and technical checks.
Read articleAvoid SEO mistakes that hold back rankings, including low-quality content, clickbait, duplicate pages, hard-to-read text, and poor user experience.
Read articleSEO case studies optimized to rank: choose intent-led keywords, show results, add schema and internal links, and distribute for steady organic traffic.
Read articleUnderstand alt-text context, dimensions, responsive sources, response failures, crawl scope, source pages, and what the report does not change automatically.
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.
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.
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.
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.
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.
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.
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.
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.
