Leave a request
Feedfetcher is a service that Google uses RSS and ATOM of the Google News and Pubsubhububub. Feedfetcher retains and periodically updates the ribbons that are requested by users of services or applications. Only tape of podcasts are indexed in the Google search engine. However, if the tape does not meet the standards of ATOM or RSS, it can still be indexed. In this section, you will find answers to the most frequently asked questions about how this user data obtaining tool works.
When users add a service or application using Feedfetcher data, Google tries to get the contents of the tape for display. Since Feedfetcher's requests occur at the initiative of users, not automatic robots, Feedfetcher does not take into account the rules in Robots.txt.
If the tape of your site is publicly available, Google cannot limit access to it. One way is to configure the server so that it sends errors 404, 410 or other condition codes for the Feedfetcher user-agent.
If your tape is provided through a blog or site, use the appropriate settings on the platform or contact the hosting provider to limit access to the tape.
Feedfetcher should not request tapes from your site more than once per hour. For often updated updates, updates can occur more often. However, due to delays on the network, it may seem that Feedfetcher makes requests more often.
Feedfetcher requests ribbons at the request of applications or services users. Perhaps the user requested a tape on a non -existent URL.
Feedfetcher makes tapes on user actions. Perhaps the request came from the user who knows about your "secret" server, or accidentally introduced it in the address line.
Feedfetcher receives tapes only after users clearly launch services or applications that request data. This behavior makes Feedfetcher a human agent, not an automatic robot, so he ignores notes in Robots.txt.
You can prevent the data of Feedfetcher data by configuring the server 404 or 410 error for the Feedfetcher user-agent user.
Feedfetcher was developed for distributed work on several machines in order to increase performance. It also helps to reduce the use of the passage strip due to the localization of machines near the requested sites.
IP addresses used by Feedfetcher can be found in the User-Triggered-fetChers- Google.json object.
Feedfetcher usually uploads only one copy of each file upon receipt of the tape. Sometimes, when cars are restarted, a situation may arise in which pages are repeated.
Unlike conventional web crauls, Feedfetcher is not looking for links for scanning. It scans only those URLs that users provide through services or applications.
If you still have questions, you can find help on the Search Central forum or contact the SEO company for any issue through email: info@seo.computer or WhatsApp: +79202044461.
ID 192
