[wp-meta] [Making WordPress.org] #5835: (re)instate "noindex" mode on the Patterns Directory

[Making WordPress.org]

#5835: (re)instate "noindex" mode on the Patterns Directory
-------------------------------+---------------------
 Reporter:  jonoaldersonwp     |       Owner:  (none)
     Type:  defect             |      Status:  new
 Priority:  high               |   Milestone:
Component:  Pattern Directory  |  Resolution:
 Keywords:  seo performance    |
-------------------------------+---------------------

Comment (by jonoaldersonwp):

 @bradleyt Where did you test?
 Running Lighthouse in Chrome gives me the attached results, which are
 pretty terrible.

 @dd32 Improving the performance is going to take more than a few tickets;
 it's going to require fundamental re-architecting (including all the time
 and resource needed to even scope and plan that). We're simply not
 resourced to do that, and we can't afford to wait indefinitely for
 theoretical improvements whilst we continue to deliver a terrible
 experience to/for our users.

 Wearing my marketing hat briefly, this also exposes us to competitive
 risk/ridicule. It wouldn't take much for Wix/etc to campaign on the back
 of how un-performant WordPress' shiny new features are, compared to them
 (who're all investing in improving their performance; see
 https://wordpress.slack.com/archives/C0GKJ7TFA/p1625646182449000).

 Do we have a marketing plan for Patterns which involves SEO, or which
 relies on page-level discovery of patterns from search? Do we have an SEO
 plan? If not, then I don't think that re-introducing the `noindex`
 directive is a problem. And if we do, then we should `noindex` until the
 pages are optimized and performant.

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