[wp-meta] [Making WordPress.org] #5024: Provide/verify access to *.wordpress.org sites in Google Search Console.

[Making WordPress.org]

#5024: Provide/verify access to *.wordpress.org sites in Google Search Console.
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  task            |      Status:  new
 Priority:  high            |   Milestone:
Component:  General         |  Resolution:
 Keywords:  seo analytics   |
----------------------------+---------------------

Old description:

> Currently, (I, and) the marketing team only has access to / reports in
> Google Search Console (the source of much of our SEO intelligence for
> wordpress.org) are limited to https://wordpress.org.
>
> This omits all of the Rosetta sites, and represents a huge blind spot in
> our understanding of reach, performance, and issues/opportunities.
>
> To provide access we either need to:
> - 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;
> - 2. Add a txt record to the wordpress.org domain to verify a nominated
> individual, and have them delegate access as desired.
>
> My preference would be for #2, given the number of unknown/forgotten
> *.wordpress.org sites, and the continued overhead of manual, individual
> verification.
>
> With that in place, I'd appreciate full read access to the domain
> property, in order to better understand and optimize our performance.

New description:

 Currently, (I, and) the marketing team only has access to / reports in
 Google Search Console (the source of much of our SEO intelligence for
 wordpress.org) are limited to https://wordpress.org.

 This omits all of the Rosetta sites, and represents a huge blind spot in
 our understanding of reach, performance, and issues/opportunities.

 Google 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.

 To provide access to this we need to do one of the following:
 - 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;
 - 2. Add a txt record to the wordpress.org domain to verify a nominated
 individual, and have them delegate access as desired.
 - 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.

 My 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.

 With that in place, I'd appreciate full read access to the domain
 property, in order to better understand and optimize our performance.

--

Comment (by jonoaldersonwp):

 Alternatively, @jdevalk

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5024#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org