fix(seo): put the brand first in the landing title, scope the docs title - #42
Merged
Merged
Conversation
Searching the brand term now returns the docs homepage above the landing page. Nothing is broken — the landing is still index,follow with a valid canonical — the two pages simply compete, and docs wins on the query: docs What is CaptureFlow? | CaptureFlow h1: What is CaptureFlow? landing Open-source screen recorder ... — CaptureFlow h1: no brand at all Docs names the brand twice in its title and its h1 is the query as a question. The landing trails the brand at the end of a feature-led title. For a bare brand query docs is the better on-page match, so it took the slot — and it is the page that cannot convert anyone. The landing title now leads with the brand. The docs site title becomes "CaptureFlow Docs", so its pages read "What is CaptureFlow? | CaptureFlow Docs" and stop competing for the bare term; that also matches the og:title the docs already published. themeConfig.siteTitle is untouched, so the nav wordmark still reads CaptureFlow. Neither change is visible to a reader — both only alter the tab and the SERP. The h1 is left alone: adding the brand there is hero copy, not a metadata fix.
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.
Searching the brand term now returns the docs homepage above the landing
page. Nothing is broken — the landing is still
index, followwith a validcanonical and nothing in robots.txt blocks it. The two pages simply compete for
the query, and docs wins it.
<title><h1>Docs names the brand twice in its title and its h1 is the query as a question.
The landing trails the brand at the end of a feature-led title, and its h1 does
not contain the brand at all. For a bare brand query docs is the better on-page
match, so it took the slot — and it is the page that cannot convert anyone.
Changes
CaptureFlow — Open-source screen recorder with shareable links.SITE_TITLEalso feedsog:titleandtwitter:title, so all three move together.CaptureFlow Docs, so pages readWhat is CaptureFlow? | CaptureFlow Docsand stop competing for the bareterm. This also matches the
og:titlethe docs already published.themeConfig.siteTitleis deliberately untouched, so the visible nav wordmarkstill reads "CaptureFlow" — only the tab and the SERP change. Verified in a
real build: nav renders
CaptureFlow, and the only occurrence of "CaptureFlowDocs" outside
<head>is inside VitePress's inlined__VP_SITE_DATA__scriptpayload.
Not in this PR
The landing h1 has no brand in it. That is the largest remaining on-page
gap for a brand query, but it is visible hero copy rather than a metadata fix,
so it is a decision for the author, not something to slip into an SEO change.
Verification
<title>andog:titlebrand-firstWhat is CaptureFlow? | CaptureFlow Docs; a sub-page toSelf-hosting overview | CaptureFlow Docspnpm typecheckgreen, 37/37 web tests pass, docs build cleanExpectations
This will not flip overnight. Titles are re-read on the next crawl, and the
apex was last crawled Aug 10. Worth requesting indexing for
/after deploy.Also worth being honest about ceiling: the AI Overview for this query now
describes CaptureFlow as "a name shared by a few different software tools…
most notably an AI-powered content distribution platform." Google's entity
model still treats .ai as the primary CaptureFlow, and no title change moves
that — only backlinks will.