Indexare in google rapid

[iulik]

Am folosit metoda asta pe un site nou, am indexat in google peste 5000 de link-uri. Puteti sa trimiteti doar 200 de link-uri intr-o zi (de pe un cont), in maxim o zi doua apar toate link-urile in google.

 

Nu stiu daca voi fi penalizat in timp, nu va recomand sa o folositi daca aveti site-uri vechi.

 

--------------------

STEP 1:
Setting up the Indexing API: creating a service account and JSON key Let's start by setting up access in the Indexing API console. Go to Google Cloud Platform and create a service account there.
 

Here you can enter the desired project name or leave the suggested one. We leave the location as it is, editing is optional.
 

We continue to create a service account: you should see the following window in front of you (you will have a different project name):
 

1. Next, enter another arbitrary name.
2. Assign the role of this account - Owner.
 

Next, create a new key and download it to your computer.
 

STEP 2:
The ready key is needed to run the scanning script (download the script from Github).
The script will be in the form of a folder, one of the files of which will be called service_account.
 

Next, you need to replace the content of the service_account file with the content of your downloaded JSON key. As a result, the service_account file in the script folder will look something like this:
 

The script is ready. Now it needs to be linked to Google Search Console.

STEP 3.
Linking the script to the Google Search Console To do this, assign the client_email from our JSON key as the full owner. This is how it looks in Google Search Console:
 

It remains only to enable the use of the Index API in our project. To do this, follow the link. Select a service account and enable the API.

Our script is now ready to use.


STEP 4

For work we need node.js, download here.
After installation, run PowerShell on your computer and enter the command "npm install requests"
WE are completely ready to work


Running the script:
How to start: In the script folder (which you downloaded from Github and added the JSON key), find the urls. Enter up to 100 addresses to be scanned there. In total, you can send 200 addresses per day, so create two packets of 100 each.
Call PowerShell. You enter the command "node index.js". Wait a few seconds and see the answer 200 OK.
 

Edited June 15, 2022 by iulik

[UnixDevel]

De ce nu sa folosesti RPC servers cred ca e mai usor 
Eu folosesc chestia asta intr-un cms facut cu laravel si de fiecare data cand creez un post nou am un job care ping-uieste o lista de 2000 de website-uri ce folosesc RPC.
Deobicei imi apare in google in media intr-o ora sau 2

 

[iulik]

11 hours ago, lzomedia said:

De ce nu sa folosesti RPC servers cred ca e mai usor 
Eu folosesc chestia asta intr-un cms facut cu laravel si de fiecare data cand creez un post nou am un job care ping-uieste o lista de 2000 de website-uri ce folosesc RPC.
Deobicei imi apare in google in media intr-o ora sau 2

 

Ping-ul pe rpc nu functioneaza pentru mine pentru site-uri noi, mai rapid am indexat in google cu metoda din topic.

[UnixDevel]

Eu nu folosesc neaparat RPC de la google,

Am o lista de server,

Interesanta ideea de a folosi api-ul direct de la google.

din ce citesc 

The Indexing API allows any site owner to directly notify Google when pages are added or removed. This allows Google to schedule pages for a fresh crawl, which can lead to higher quality user traffic. <b> Currently, the Indexing API can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject</b>. For websites with many short-lived pages like job postings or livestream videos, the Indexing API keeps content fresh in search results because it allows updates to be pushed individually.

Ei recomanda sa faci ping la sitemap mai degraba .

Observ ca acea limita de 200 se poate creste prin submit de request.

Oricum interesant topicul 

[Sandu]

Lista de RPC-uri pentru ping:

http://rpc.pingomatic.com/
http://rpc.icerocket.com:10080/
http://blogsearch.google.com/ping/RPC2
http://1470.net/api/ping
http://api.feedster.com/ping
http://api.moreover.com/RPC2
http://api.moreover.com/ping
http://api.my.yahoo.com/RPC2
http://api.my.yahoo.com/rss/ping
http://bblog.com/ping.php
http://bitacoras.net/ping
http://blog.goo.ne.jp/XMLRPC
http://blogdb.jp/xmlrpc
http://blogmatcher.com/u.php
http://bulkfeeds.net/rpc
http://coreblog.org/ping/
http://mod-pubsub.org/kn_apps/blogchatt
http://www.lasermemory.com/lsrpc/
http://ping.amagle.com/
http://ping.bitacoras.com
http://ping.blo.gs/
http://ping.bloggers.jp/rpc/
http://ping.cocolog-nifty.com/xmlrpc
http://ping.blogmura.jp/rpc/
http://ping.exblog.jp/xmlrpc
http://ping.feedburner.com
http://ping.myblog.jp
http://ping.rootblog.com/rpc.php
http://ping.syndic8.com/xmlrpc.php
http://ping.weblogalot.com/rpc.php
http://ping.weblogs.se/
http://pingoat.com/goat/RPC2
http://rcs.datashed.net/RPC2/
http://rpc.blogbuzzmachine.com/RPC2
http://rpc.blogrolling.com/pinger/
http://rpc.icerocket.com:10080/
http://rpc.newsgator.com/
http://rpc.pingomatic.com
http://rpc.technorati.com/rpc/ping
http://rpc.weblogs.com/RPC2
http://topicexchange.com/RPC2
http://trackback.bakeinu.jp/bakeping.php
http://www.a2b.cc/setloc/bp.a2b
http://www.bitacoles.net/ping.php
http://www.blogdigger.com/RPC2
http://www.blogoole.com/ping/
http://www.blogoon.net/ping/
http://www.blogpeople.net/servlet/weblogUpdates
http://www.blogroots.com/tb_populi.blog?id=1
http://www.blogshares.com/rpc.php
http://www.blogsnow.com/ping
http://www.blogstreet.com/xrbin/xmlrpc.cgi
http://www.mod-pubsub.org/kn_apps/blogchatter/ping.php
http://www.newsisfree.com/RPCCloud
http://www.newsisfree.com/xmlrpctest.php
http://www.popdex.com/addsite.php
http://www.snipsnap.org/RPC2
http://www.weblogues.com/RPC/
http://xmlrpc.blogg.de
http://xping.pubsub.com/ping/
http://rpc.copygator.com/ping/