feat(seo): position the landing on what people search for - #49
Open
JheisonMB wants to merge 4 commits into
Open
Conversation
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.
The landing was positioned on brand words nobody searches, and what each
experiment is had drifted into four copies that disagreed. This fixes the
mechanism first and the words second.
What each page presents socially
All eight experiment pages shared one Open Graph image — the UniverLab logo and
SCI · CLI · BIO. Sharing the texforge link produced a card that named neithertexforge nor what it does.
scripts/og/build-og.mjsalready existed and already used the right technique(text outlined to paths with
opentype.js, brand tokens, rasterised throughheadless Chrome because social scrapers do not render SVG). It is now
parameterised per experiment, in the shape of the sibling generator in
UniverLab/.github, reading name, tagline and accent fromsrc/lib/experiments.tsandsrc/i18n/rather than holding a second copy ofthem. Each card carries the product as subject and the wordmark as endorsement.
One owner for the positioning line
texforge said one thing in its title, another in its meta description, a third
in its GitHub repository description and a fourth in the og image. Nobody wrote
four versions on purpose — each surface was edited on its own day.
The repository is now the owner and GitHub is a mirror: a check reports drift
between the English tagline and the repository description, and a separate
explicit command applies it. The build never writes to GitHub, and with no token
the check reports skipped rather than passed, so it cannot break a
contributor's build.
Titles that state the problem
Every page used
{Name} — UniverLab: two brand names in the most valuable sloton the page. Titles now lead with the problem and close with the brand, and
descriptions carry the substance in searchable terms. The Spanish is translated
by intent rather than by words, and technical terms stay in English because that
is how they are searched and spoken.
The hero taglines are unchanged — the poetic line stays where a human who
already arrived reads it, and the title carries the query.
SCI · CLI · BIOalso stays exactly where it was, as a brand mark rather than as a description.
Two things worth calling out:
query, because the angle there is that git hooks are underused.
localised, and it says what the lab makes instead of naming a category that
has no search volume — so title and description finally agree.
Verified against the built HTML rather than the diff: 84 pages, 144 tests,
check:i18ngreen, hreflang intact.