image-seo-audit
Skill3 starsChanged 5 months agoMITView on GitHub
Audit a website's images for SEO and Core Web Vitals. Crawls pages to find images with missing or empty alt text, missing width/height (layout shift), no lazy loading, oversized files, legacy formats (no WebP/AVIF), generic filenames, and broken image URLs. Use when the user asks to audit, analyze, check, or improve image SEO, alt text, image accessibility, image file sizes, image formats, or image loading performance of a website.
- Installs packages
2 other projects use a version of this.
Adopted by
Most recently taken up by
- teachskillofskills-ai/DigitalMarketingPro-techshutheir own version, first seen Oct 11, 2026
- indranilbanerjee/digital-marketing-protheir own version, first seen Feb 12, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- indranilbanerjee/digital-marketing-pro★ 934same name
- teachskillofskills-ai/DigitalMarketingPro-techshu★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- canonical-tag-auditSkill
- content-quality-auditSkill
- core-web-vitals-auditSkill
- external-link-auditSkill
- full-seo-auditSkill
- heading-structure-auditSkill
- internal-link-auditSkill
- keyword-cannibalization-auditSkill
- llms-txt-auditSkill
- meta-data-auditSkill
- mixed-content-auditSkill
- open-graph-auditSkill
- pagination-auditSkill
- redirect-auditSkill
- robots-txt-auditSkill
- schema-markup-auditSkill
- site-architecture-auditSkill
- sitemap-auditSkill
- soft-404-auditSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 3 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill when the user asks to:
- Distinctive: line 22
Before starting, confirm with the user:
- Very specific: line 34
If a sitemap is available (/sitemap.xml), it is used to get the canonical page list.
- Very specific: line 38
Use scripts/extract_images.py to build an image inventory:
- Very specific: line 51
Use scripts/audit_images.py to run all audit checks against the inventory:
- Very specific: line 79
Write a report following the structure in references/report-template.md:
- Distinctive: line 90
Never start with "image of" or "picture of": screen readers already announce it as an image
- Very specific: line 91
Use alt="" only for purely decorative images.
- Very specific: line 97
Add alt text to the hero image on /: alt="Team of nurses reviewing a patient chart at a bedside"
- Very specific: line 98
Add width and height to the 6 product thumbnails on /shop to stop layout shift
- Very specific: line 105
If the user wants the report as a .docx (for example, to share with stakeholders or attach to a ticket), save the Markdown report to a file …
- Very specific: line 115
If the user wants the raw findings as a spreadsheet (for filtering, sorting, or triage in Sheets or Excel), convert the audit's …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Image SEO Audit
Audit the images of a website and produce an actionable SEO and performance report.
When to use this skill
Use this skill when the user asks to:
- Audit or analyze the images on a website for SEO or accessibility
- Find images with missing, empty, or poor
alttext - Find images that cause layout shift (missing
width/height) or load slowly (no lazy loading, oversized files) - Identify images served in legacy formats instead of WebP/AVIF
- Find broken images or generic, uninformative filenames
Inputs to collect
Before starting, confirm with the user:
- Site URL or local files: a live site root URL (e.g.,
https://example.com), a sitemap URL, a list of URLs, or a local folder of HTML files. - Scope: full site, a specific section (e.g.,
/blog/), or a list of URLs. - Crawl limits: max pages (default 500) for live crawls.
- File checks: whether to fetch each image to measure byte size and detect broken images (the
--check-filesflag; slower but enables the oversized-file and broken-image checks). - Size budget: the byte threshold above which an image is "oversized" (default 200 KB).
Workflow
Step 1: Gather the page set and extract images
- If a sitemap is available (
/sitemap.xml), it is used to get the canonical page list. - Otherwise, the crawler starts from the homepage following only same-host links.
- For local HTML folders, all
.htmlfiles are enumerated.
Use scripts/extract_images.py to build an image inventory:
python3 scripts/extract_images.py https://example.com --max-pages 500 --check-files --output image_inventory.json
# already crawled once (e.g. in a full SEO audit)? skip the crawl and reuse the shared cache:
# python3 scripts/fetch_pages.py https://example.com --output page_cache.json
# python3 scripts/extract_images.py --from-cache page_cache.json --check-files --output image_inventory.jsonFor every <img> the inventory records: absolute src, alt (null if the attribute is absent vs. empty string if alt=""), width/height attributes, loading, whether it has a srcset, whether it sits inside a <picture>, and its position in the page. With --check-files, each unique image URL is HEAD-requested to record HTTP status, content type, and byte size.
Step 2: Run the audit checks
Use scripts/audit_images.py to run all audit checks against the inventory:
python3 scripts/audit_images.py image_inventory.json --max-bytes 200000 --output audit_report.jsonThe oversized-file and broken-image checks only run if the inventory was built with --check-files.
Step 3: Evaluate the audit checks
Evaluate each check defined in references/audit-checks.md. The core checks are:
| Check | Severity |
Missing alt attribute | High |
| Broken image (non-200 URL) | High |
Missing width/height (layout shift) | Medium |
| Oversized file (> size budget) | Medium |
| Not lazy-loaded (below the fold) | Low |
Legacy format with no modern <picture> source | Low |
| Generic filename | Low |
| Alt text too long (> 125 chars) | Low |
| Redundant alt prefix ("image of…") | Low |
Empty alt="" (decorative: confirm intent) | Informational |
| Duplicate alt reused across many images | Informational |
Step 4: Produce the report
Write a report following the structure in references/report-template.md:
- Summary: pages crawled, images found, alt-text coverage %, issue counts by severity
- Issues: one section per failing check, listing the page, the image, and a specific fix
- Prioritized action list: ordered by severity and estimated impact
Step 5: Recommend fixes
For each issue, give a concrete, copy-pasteable recommendation. When drafting alt text:
- Describe what the image shows and its purpose on the page, in roughly 5–15 words
- Never start with "image of" or "picture of": screen readers already announce it as an image
- Use
alt=""only for purely decorative images; never invent details not visible in the image - For dimensions, recommend the exact
width/heightattributes (or CSSaspect-ratio) that match the rendered size - For oversized or legacy images, recommend compressing and serving WebP/AVIF via
<picture>with a fallback
Example recommendations:
- Add alt text to the hero image on
/:alt="Team of nurses reviewing a patient chart at a bedside" - Add
widthandheightto the 6 product thumbnails on/shopto stop layout shift - Convert
/images/hero.png(1.4 MB) to WebP and serve it through<picture>; this image loads on every page
Optional: export the report
As a Word document (.docx)
If the user wants the report as a .docx (for example, to share with stakeholders or attach to a ticket), save the Markdown report to a file and convert it:
python3 scripts/md_to_docx.py report.md --output report.docxscripts/md_to_docx.py uses only the Python standard library (no pip install) and renders headings, tables, lists, links, bold/italic, and code blocks. Offer this whenever a user asks for a Word doc, a .docx, or a shareable/downloadable report.
As a CSV of findings (.csv)
If the user wants the raw findings as a spreadsheet (for filtering, sorting, or triage in Sheets or Excel), convert the audit's audit_report.json directly:
python3 scripts/findings_to_csv.py audit_report.json --output findings.csvscripts/findings_to_csv.py is also standard-library only. It writes one row per finding, with check and severity columns prepended and list fields (e.g. the pages sharing a duplicate value) joined with ; . Unlike the .docx, which reformats the written report, the CSV is a direct dump of the structured findings: offer it whenever a user wants the data itself, a spreadsheet, or to slice findings by check or severity.
Resources
scripts/md_to_docx.py: convert the Markdown report into a Word (.docx) document (standard library only)scripts/findings_to_csv.py: flatten the audit findings JSON into a CSV, one row per finding (standard library only)references/audit-checks.md: full definitions, thresholds, and rationale for every audit checkreferences/report-template.md: report output structurescripts/extract_images.py: crawl a site and build the image inventory (add--check-filesfor size/format checks)scripts/audit_images.py: run audit checks against an image inventory JSON file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

