Opened 6 years ago
Last modified 6 years ago
#4685 new defect (bug)
Disallow /changeset in https://core.trac.wordpress.org/robots.txt
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | lowest | |
Component: | Trac | Keywords: | seo |
Cc: |
Description
Add a disallow rule for /changeset.
Change History (6)
#2
@
6 years ago
Because there are ~13,000 low-quality, undifferentiated, unoptimised pages indexed, sucking value out of the rest of the site.
If somebody's willing to invest radical improvements in the trac site to bring it up to standards, we could get away with having these indexed. In their current state, they're a drain.
Are you suggesting that people search/Google for specific queries, and expect/find these pages? Can you give me some example queries and scenarios?
#3
@
6 years ago
I agree, /changeset
URLs are useful and valuable. Lets not block them.
There's potentially a better request here, which is to noindex the specific files urls on it, such as /changeset/\d+/trunk/.....
which are less useful in search results.
#4
@
6 years ago
Ok, let's alter the approach to add rules for requests containing:
*old_path=
/trunk
/branches
Why would we block changesets from search? They're very valuable.