SEO de-tuning

Open
#107 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend, web-dev

Research direction

Start by tracing the TypeScript entry points for the /final-review/, /clusters/, and /about/ routes and how they expose pages to search engines. Verify the result against the listed URLs: only /about/ should remain indexable, while every other route should be excluded.

Written by the indexing model from the issue text.

Description

Google is indexing pages under the final-review route (e.g., https://queue.rfc-editor.org/final-review/rfc9999/). These pages and the cluster pages under the https://queue.rfc-editor.org/clusters/ should not be indexed. Actually, everything except https://queue.rfc-editor.org/about/ is ephemeral and shouldn't be indexed.

h/t @sginoza

Dominant language
TypeScript
Stars
1
Forks
3
Avg merge
1d 8h
Merged PRs (30d)
8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ietf-tools/queue

All issues in ietf-tools/queue

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.