fix(seo): revalidate share images and link the author profile - #139
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Unversioned share-image URLs previously advertised a year of immutable caching, allowing replaced artwork to remain stale. Static share-image responses now use
public, max-age=0, must-revalidate.Article Open Graph authors now reference the canonical profile URL,
https://f0rr0.dev/journey, instead of the author's display name.Based on fresh
origin/nextatee3a073. Validation: three focused SEO/Markdown tests and production Next build pass; running-server checks confirm the renderedarticle:authorURL and share-image cache header. Lint and typecheck pass. Existing build filesystem-tracing and GitHub embed fallback warnings remain. Previously cached third-party copies may still require a refresh by the sharing service.