Making WordPress.org

Opened 3 years ago

Closed 19 months ago

#5677 closed defect (bug) (fixed)

Lock down / hide / noindex https://cpanel.jobs.wordpress.net/

Reported by: jonoaldersonwp's profile jonoaldersonwp Owned by:
Milestone: Priority: lowest
Component: Jobs (jobs.wordpress.net) Keywords: seo
Cc:

Description (last modified by jonoaldersonwp)

https://cpanel.jobs.wordpress.net/ and https://webmail.jobs.wordpress.net/ are currently indexed in Google.

These probably shouldn't be publically accessible, but if that's necessary then they should, at the very least, be noindex'd (either by including a meta robots directive in the head, or, returning an x-robots-tag HTTP header).

Change History (5)

#1 @jonoaldersonwp
3 years ago

  • Description modified (diff)

Th

#2 follow-up: @dd32
3 years ago

These probably shouldn't be publically accessible

That's unfortunately how cPanel works, and they're intentionally so.

Having these accessible is not a security issue either.

but if that's necessary then they should, at the very least, be noindex'd (either by including a meta robots directive in the head, or, returning an x-robots-tag HTTP header).

Unfortunately due to these (and the server configuration) being controlled by cPanel directly, it's not viable to do these AFAIK.

It's probably possible to disable the proxy subdomains configuration on the server, removing all of these entries for the host, but I'm not sure who/what is using the hosting or reliant upon the feature (It also controls things like Outlook mail configuration amongst other things).

#3 in reply to: ↑ 2 @dd32
3 years ago

Replying to dd32:

Unfortunately due to these (and the server configuration) being controlled by cPanel directly, it's not viable to do these AFAIK.

It looks like cPanel has fixed this a few years ago by adding the robots.txt entry. This should be reported upstream to cPanel I think for a more modern fix, and can be closed here (Since we can't modify the indexing locally)

This ticket was mentioned in Slack in #meta by tellyworth. View the logs.


3 years ago

#5 @jonoaldersonwp
19 months ago

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.