WordPress.org

Making WordPress.org

Opened 7 weeks ago

Last modified 7 weeks ago

#4646 reopened enhancement

Redirect login.wordpress.org/wp-login.php to login.wordpress.org/

Reported by: jonoaldersonwp Owned by:
Milestone: Priority: low
Component: Login & Authentication Keywords: seo analytics close
Cc:

Change History (8)

#1 @ocean90
7 weeks ago

  • Resolution set to wontfix
  • Status changed from new to closed

wp-login.php is still used as the action for the forms and to display error messages. There isn't much if any benefit in doing a redirect here.

#2 @jonoaldersonwp
7 weeks ago

  • Resolution wontfix deleted
  • Status changed from closed to reopened

Well, there's significant benefit. That's why I opened the ticket.
What are our alternatives/options to consolidate these URLs? We could reverse the direction of the redirect?

#3 @ocean90
7 weeks ago

  • Keywords reporter-feedback added
  • Type changed from defect to enhancement

And what are the benefits?

#4 @jonoaldersonwp
7 weeks ago

SEO and Analytics stuff. URL, value and reporting consolidation. It's certainly not mission-critical, and
there are more important things on the list - hence, the 'low' priority status.

But if I have to build a detailed business case on every ticket, then we'll lose to Wix and be long-dead before we get anywhere. I'd rather we trust that I understand the time/effort/value trade-offs well enough to only open worthwhile tickets, and to prioritise them roughly accordingly ;)

#5 @ocean90
7 weeks ago

  • Keywords close added; reporter-feedback removed

But if I have to build a detailed business case on every ticket,

Simply answering the "Why?" question would already be enough. Since login.wordpress.org can't be indexed I'm not sure why this ticket even exists.

#6 @jonoaldersonwp
7 weeks ago

Because it can still be crawled, and, because it's still in our analytics system. In its present format, it causes issues in both cases. Adding a noindex tag doesn't solve all of our problems.

#7 @dd32
7 weeks ago

While the page looks the same, it's not the same, and we can't remove it.

The most we can do is add a noindex tag here.
Since it already has a noindex I guess we could add a canonical header, but unless that's going to solve the issue entirely this is squarely a wontfix.

Last edited 7 weeks ago by dd32 (previous) (diff)

#8 @jonoaldersonwp
7 weeks ago

They already have a noindex property.

What's "not the same" mean, and, why can't we (resolve any discrepencies / solve any underlying silliness) and consolidate them?

Note: See TracTickets for help on using tickets.