Skip to content

chore: drop trailing keyword block from README#2

Merged
OussemaFr merged 1 commit into
mainfrom
chore/clean-readme-keyword-block
Jun 22, 2026
Merged

chore: drop trailing keyword block from README#2
OussemaFr merged 1 commit into
mainfrom
chore/clean-readme-keyword-block

Conversation

@OussemaFr

Copy link
Copy Markdown
Member

What

Removes the 12-keyword <sub> block at the bottom of README.md.

Why

Two reasons:

  1. Looks AI-spammy. A trailing keyword list at the end of a README is the textbook keyword-stuffing pattern Google's algorithm now penalizes. Modern hand-written READMEs almost never have these.
  2. It's redundant. Every important search term — facebook-scraper, kevinzg, facebook api alternative, instagram-scraper — already appears naturally in the README prose and section headings. Google ranks those in-context mentions higher anyway.

What handles SEO instead

Search surface How it's covered
Google (repo page indexing) Natural keyword mentions throughout README sections
GitHub's own search Repo About → Topics (set in repo settings)
Both Repo About → Description

So no SEO is actually lost — just the spammy-looking footer.

Test plan

  • README still renders cleanly to the License section
  • No reference to the keyword block in any other file (grep confirms)

Google's search algorithm penalizes obvious keyword stuffing, and a
12-keyword <sub> block at the bottom of a README is the textbook
pattern. The buy-intent terms (facebook-scraper, kevinzg, facebook
api alternative, instagram-scraper, etc.) already appear naturally
throughout the README prose and section headings, which is where
search engines actually want to find them. Repo Topics in the About
section handle GitHub's own keyword search.
@OussemaFr OussemaFr merged commit 57a7d9d into main Jun 22, 2026
6 checks passed
@OussemaFr OussemaFr deleted the chore/clean-readme-keyword-block branch June 22, 2026 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant