Update landing-page OG image and serve a real robots.txt#51
Merged
Conversation
Deploy Previewhttps://preview-pr-51.easl.dev Updated at 2026-06-03T11:05:47.014Z |
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
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.
Why
The easl.dev social preview was broken: it was a raw, awkwardly-cropped screenshot at a non-standard size, so links shared on Twitter/LinkedIn/Slack looked unfinished. Separately,
/robots.txtreturned the landing-page HTML instead of a robots file, which is wrong for crawlers.What
easl.devlink. This is what people now see when they share easl.dev.easl.dev/robots.txtnow serves a propertext/plainrobots file allowing crawlers, instead of falling through to the landing page.Note: existing Twitter/X cards may still lag until X's per-URL cache (~7 days) expires — that's platform-side caching, not something this change controls.