CrawlProof fix: Some blog images lack alt text - #42
Merged
Merged
Conversation
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CrawlProof automated fix for the following audit finding:
Check:
images.alt(priority 3)What changed:
app/(marketing)/blog/page.tsxapp/(marketing)/blog/[slug]/page.tsxWhy:
Fixed empty
alt=""attributes on blog images in both the blog listing page (app/(marketing)/blog/page.tsx) and the individual blog post page (app/(marketing)/blog/[slug]/page.tsx). Replacedalt=""withalt={\${p.title} featured image`}/alt={`${post.title} featured image`}`, using the post's title to generate descriptive, meaningful alt text for all blog featured images.Generated by Claude Sonnet 4.6 in agentic mode (13 tool iterations). Review the diff before merging — automated edits are not infallible. Disagree with the change? Close the PR and apply the fix manually using the audit recommendations on your CrawlProof project page.
Docs: https://crawlproof.com/docs/aeo-score