WordPress.org

Making WordPress.org

Changes between Initial Version and Version 1 of Ticket #5024


Ignore:
Timestamp:
02/10/2020 02:56:41 PM (22 months ago)
Author:
jonoaldersonwp
Comment:

Alternatively, @jdevalk

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5024 – Description

    initial v1  
    33This omits all of the Rosetta sites, and represents a huge blind spot in our understanding of reach, performance, and issues/opportunities.
    44
    5 To provide access we either need to:
     5Google Search Console supports a "Domain Property" account type, which includes access to performance statistics for all hostnames 'beneath' (and including) https://wordpress.org; i.e., all of the rosetta sites.
     6
     7To provide access to this we need to do one of the following:
    68- 1. Manually verify/add/delegate access to each/all *.wordpress.org sites, individually (via adding a HTML file to the public root directory), including future domains or;
    79- 2. Add a txt record to the wordpress.org domain to verify a nominated individual, and have them delegate access as desired.
     10- 3. As a user with `Publish` capabilities on Google Tag Manager, @joostdevalk could gain authenticated access to the Domain Property account, and provide me and/or others with read access.
    811
    9 My preference would be for #2, given the number of unknown/forgotten *.wordpress.org sites, and the continued overhead of manual, individual verification.
     12My preference would be for #3, given Joost's existing trusted status, the number of unknown/forgotten *.wordpress.org sites (which we'd never register, therefore never see / know about), and the continued overhead of manual, individual verification.
    1013
    1114With that in place, I'd appreciate full read access to the domain property, in order to better understand and optimize our performance.