docs(site): per-page meta descriptions + richer homepage title for discoverability#109
Open
tenequm wants to merge 1 commit into
Open
docs(site): per-page meta descriptions + richer homepage title for discoverability#109tenequm wants to merge 1 commit into
tenequm wants to merge 1 commit into
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
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.
Why
glim_web_search(Exa) doesn't surfacetenequm/pondfor product queries - 0-star mirrors of the repo rank above it. Root cause is upstream at Exa: it ranks on semantic similarity of captured page text, not stars/backlinks, and our own canonical surfaces gave it weak, undifferentiated signal.Two clean, entirely invisible metadata fixes (no visible page change - verified the description text lands only in
<meta description/og/twitter>, never a rendered text node):Changes
index.mdx- richer<title>(pond - lossless storage and search for AI agent sessions) + a landingdescription. The one-word<title>pond</title>was weak against semantic queries.description. Previously every page fell back to the same generic config description, so they all advertised the identical thing to the crawler. Now each page carries its own topic + real search terms (MCP tools, remote storage, install matrix, exit codes, etc.).No body/visual content was added to any page.
sitemap.xml+robots.txtalready ship, so crawl discovery was never the gap.Verification
pnpm buildpasses (37 pages generated).<head>only; zero visible text nodes.