Repository navigation
docs: improve README discoverability for search - #80
Merged
Merged
Conversation
The repo page is absent from Google's index, and the README body is the only part of it search engines read for topical signals. Add the vocabulary developers actually search for and answer the decision-stage questions on the page itself. - Name the command line, terminal, and Go binary in the intro, alongside the runtimes pobear does not require. - Add a documentation nav line above Quick start. - Add three FAQ entries: scraping from the terminal, the Go runtime question, and how pobear differs from the Decodo CLI. The FAQ comparison also separates pobear from Decodo/cli, which targets the same "web scraping CLI" queries from the opposite default.
Updated instructions for using the Decodo provider with pobear to include rendering option.
Updated README to include a hyperlink for pobear.
The repo description now carries the search keywords, so the original line moves into the README, where it reads as a tagline rather than as the only thing Google knows about pobear.
ChinchillaLover9000
approved these changes
Oct 29, 2026
ASDCD154
approved these changes
Oct 29, 2026
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
github.com/Decodo/pobearis not in Google's index.site:github.com/Decodo/pobearreturns zero results, and even searching the repo's exact description phrase returns nothing. The only indexed page that mentions pobear isgithub.com/orgs/Decodo/repositories.The README body is the part of the repo page search engines read for topical signals, so this PR adds the vocabulary developers actually search for and answers the decision-stage questions on the page itself.
Changes
docs/references. The help.decodo.com page slots in first here once it ships.h3and map directly onto real queries:The last one also separates pobear from
Decodo/cli, which targets the same "web scraping CLI" queries from the opposite default: every Decodo CLI request goes through the API, while pobear fetches directly and escalates only when blocked.No wording outside these additions was changed.
Not in this PR
The repo's title tag and meta description are built from the repo description field, not the README H1:
Updating the description, topics (currently 3, vs 14 on
Decodo/cli), and homepage is the larger lever and needs a repo settings change rather than a commit.Test plan
#quick-startand#developmentresolve