[wp-trac] [WordPress Trac] #52900: Instantly index WordPress web sites content in Search Engines

[WordPress Trac]

#52900: Instantly index WordPress web sites content in Search Engines
-------------------------------------------------+-------------------------
 Reporter:  fabricecanel                         |       Owner:  (none)
     Type:  feature request                      |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  reporter-feedback has-patch has-     |     Focuses:
  unit-tests                                     |
-------------------------------------------------+-------------------------

Comment (by fabricecanel):

 Replying to [comment:31 dd32]:
 > @fabricecanel Can you please edit/delete any comments above that were
 made in error? It looks like you're quoting entire comments from above
 without adding any extra context or answers - or you might've, but it's
 inline with another comment? I'm not sure I can't tell :)
 >
 >> thanks for guiding me in WordPress world :)
 >  - I'm still not 100% convinced that having WordPress ping each of the
 engines individually is ideal, however, it's not the worst.
 >> Good news, we listen to the feedback as you, and we agree to move away
 from the ping all, starting next month (maybe sooner), you wile have to
 ping only one and we will ping others (requirement of the protocol to make
 it open - allowing new player and small player to participate)

 >  - I'm still not 100% convinced that having an API key / verification
 callback should be allowed.
 >> It allows webmasters/CMS to control what is crawled on the site. Evil
 people should not not a play at scale.

 >  - All supported providers would need to be defaulted in core, so as not
 to preference any given engine
 >> Agree this is why we open the protocol, you ping one, you ping all: no
 preference. Protocol is open to all search engines having a presence in a
 market.

 >  - No "exclude paths" functionality would be supported in a UI, filters
 should be exposed to add that
 >> This feature is requested for consideration for adoption, when we did
 some code, the wordpress experts should decide the best path to support
 IndexNow.

 >
 > Finally:
 >  - I think this should be developed as a plugin first, and then proposed
 to WordPress core as a feature plugin, to allow development of it to occur
 separately and then a suggestion to add it to core once feature complete.
 That would also allow site owners to opt-in to using this prior to
 WordPress fully implementing it (Which would be in WordPress 6.0 at the
 absolute earliest, Q2ish 2022 at a guess)
 >> IndexNow is an open protocol, @joostdevalk  feel free to adopt in
 Yoast, other tools, and learn from it and suggest improvement for core.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52900#comment:32>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform