Screpy - AI SEO Audit Tool MCP

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.

Audit website images Check one page free
Screpy Images report with grouped image URLs, response status, usage and source-page counts, plus alt-text and dimensions filters
Uber logo in Screpy SEO platform customer trust section
Philips logo in Screpy SEO platform customer trust section
FedEx Express logo in Screpy SEO platform customer trust section
Bosch logo in Screpy SEO platform customer trust section
Champion logo in Screpy SEO platform customer trust section
Iconfinder logo in Screpy SEO platform customer trust section
T-Mobile logo in Screpy SEO platform customer trust section
Carrefour logo in Screpy SEO platform customer trust section
Stanley logo in Screpy SEO platform customer trust section
Skoda logo in Screpy SEO platform customer trust section

Find Missing Alt Text

An image file can appear with different alternatives on different pages. Screpy groups the source and counts uses with missing or blank alt text, so you can find the affected context before writing a replacement.

  • Compare Missing Alt and Has Alt to find sources with at least one matching use; a group does not mean every use has the same alt text.
  • Open Source Pages to locate missing-alt counts, then inspect the actual image and wording on the published page.
  • Describe an informative image's relevant meaning or a linked image's destination. Keep intentionally decorative images silent with an empty alt attribute.
  • A filename or keyword list can clear a presence check without providing a useful alternative. Screpy does not grade meaning or generate the text.
Read the alt-text audit guide

Detect Broken Images

A missing product thumbnail and a blocked external image need different fixes. Use the recorded response classes and affected source pages to investigate the file, its URL and the rule serving it.

  • Broken includes 404, 410 and 500–599 responses. Investigate other 4xx responses, including 403 and 429, in Client Errors.
  • Review recorded 3xx responses separately. Check the final image manually before updating your own markup to a valid destination.
  • Trace repeated failures to their source pages to repair a shared media path or component instead of editing every occurrence.
  • A crawl status is a stored observation. Verify current access before removing an image; no recorded status does not automatically mean Broken.
Investigate broken image responses

Check Image Dimensions

Find image uses without a recorded width or height and identify repeated templates. This is a markup investigation: the image report does not measure the page's CLS or display a detailed width-and-height table.

  • Compare Missing Dimensions and Has Dimensions, then open Source Pages for the affected-use counts on each page.
  • Inspect actual dimensions, aspect ratio and reserved space in the page's markup and CSS; fix the shared image component when the pattern repeats.
  • Measure layout shifts separately. Present attributes can still be wrong, while a CSS container can reserve space even when attributes are missing.
Review dimensions and layout stability

Audit Responsive Images

Use Has Srcset and Missing Srcset to locate responsive markup across the crawl. Presence is the starting point; the browser's chosen file determines whether the implementation suits a mobile or desktop layout.

  • Prioritize large content images and shared templates. A small fixed-size icon or scalable SVG may not need multiple raster candidates.
  • On the source page, inspect srcset, sizes, the usable src fallback and the requested resource at representative widths and display densities.
  • Has Srcset does not validate every candidate, crop or file size. Check candidate responses, visual quality and loading behavior separately.
Read the responsive-image guide

Locate Image Source Pages

Group repeated image sources into a repairable inventory. Usage and distinct source-page counts help distinguish several appearances on one page from a shared component affecting many pages.

  • Choose a completed crawl with image collection enabled and enough page coverage. Images on undiscovered or blocked pages are outside the inventory.
  • Search image URLs, source-page URLs or alt text with at least three characters, within the selected preset and crawl.
  • Source Pages lists page URLs, use counts and missing-alt, missing-dimension and Broken counts. The selected preset and search also limit this list; clear them to inspect broader usage.
  • Open representative product, article or category pages to locate the responsible CMS field or template. After publishing, recrawl comparable pages rather than treating fewer discovered images as a repair.
Choose suitable crawl coverage

Review Image Sources

External, SVG and Data URI filters classify how images are supplied. Use each view to find dependencies or repeated delivery choices; the classification itself is not an SEO error.

  • Check an external image's ownership and current availability before replacing it. A separate image host can be a deliberate delivery choice.
  • Inspect SVG use in context instead of converting every vector. The filter is not a full format, accessibility or security validation.
  • Review embedded data URIs on the source page for repetition and page weight. They have no normal remote preview in the table; measure delivered bytes separately.
Compare image sources and formats

Export Image Audit Results

Download a focused list of image sources for implementation work. CSV and Excel export supports a handoff, while the source-page investigation explains which component or content needs changing.

  • The main table exports image URLs, response status, usage and source-page counts for the currently loaded page, not the entire filtered crawl.
  • Image previews, issue badges and Source Pages actions are not exported detail fields. The Source Pages dialog has no export control.
  • Keep the selected crawl and investigation scope with the file. Verify the published fix and comparable recrawl instead of interpreting an exported count as a live result.
Follow the image audit workflow

Talk about Image SEO Analysis. With SEO MCP.

Use SEO MCP to ask about images found in your completed crawl. Find missing alt text, inspect image records and trace each finding back to its source pages.

Explore Screpy SEO MCP Connect your AI assistant
  1. Screpy: Hello! Let’s look at Image SEO Analysis for example.com. What would you like to know?
  2. You: Which images on example.com are missing alt text?
  3. Screpy: Two images in this crawl have no alt text. Check their source pages and describe meaningful images; decorative images may correctly use empty alt text. Images to review: /images/linen-shirt.webp: /products/linen-shirt. /images/linen-trousers.webp: /products/linen-trousers.
  4. You: Turn that into a short action plan.
  5. Screpy: I’ll keep the evidence and recommendations separate. Review the findings, choose one change and check the results afterward. Your next steps: Review: Check the source and date of each finding.. Decide: Choose the first change to make.. Verify: Compare the results after the change..
  6. You: Can you explain the evidence in plain language?
  7. Screpy: Yes. Ask about a supported result and I can explain what it shows, where it comes from and what is still uncertain. Missing data stays unavailable; recommendations are not automatic fixes.

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.

  1. 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.

  2. Use All Issues as a queue, not a verdict

    Select the queue relevant to your goal: missing alt, missing dimensions, Broken or missing srcset. All Issues combines these signals; it does not classify every 4xx response or every decorative image as a defect.

  3. 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.

  4. 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.

  5. 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.

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.

Read the Image Audit guide

Related SEO guides

Learn the concepts behind this workflow and apply them with practical SEO guidance.

Explore all SEO articles

Image SEO Analysis FAQ

Understand alt-text context, dimensions, responsive sources, response failures, crawl scope, source pages, and what the report does not change automatically.

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 does Screpy Image SEO Analysis check?

Screpy groups image sources found in a completed crawl and shows their status, usage, source-page counts and issue counts. Presets cover alt presence, recorded dimensions, response classes, srcset, external sources, SVGs and data URIs. Inspect actual alt wording, dimensions and loading behavior on the source page; these are not detailed columns in the grouped table.

What counts as a broken image in the report?

The Broken preset includes recorded 404, 410 and 500–599 responses. Other 4xx responses, such as 403 or 429, remain in Client Errors; a missing status is not automatically Broken. Check the image URL and source page to distinguish a deleted file, access restriction, temporary server failure or intentional redirect before choosing a repair.

Does Image SEO Analysis compress or resize image files?

No. Screpy identifies crawl findings and their source pages; it does not compress files, generate alt text, resize assets or rewrite markup. Use the report to locate the shared cause, make the change in your CMS or code, and check rendered quality and delivery separately before recrawling.

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.

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.