noindex old content
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 333
- Forks
- 127
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 11
Description
Worth noting that there’s a middle ground before we reach “delete”, where we could tactically (or automatically) noindex pages that don’t meet a relevancy or currentness threshold.
That’ll prevent them from showing up in Google etc, and should also prevent them from showing up in on-site search mechanisms.
Then they’re addressable via direct links, but not otherwise discoverable.
That’ll also mean that we don’t need to consider the (considerable) overhead of configuring and managing 301 redirects for deleted content (without having, say, a handy SEO plugin in place to manage this), as well as updating all of the content that links to those pages…
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Learn WordPress content-maintenance proposal and its referenced comment; no files, tests, or entry points are named in this issue. Clarify which pages qualify as old or irrelevant, how noindex affects on-site search, and what implementation area owns that behavior. Done should mean qualifying pages remain directly accessible but are excluded from external and on-site discovery.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100