Log files contain 100% accurate information on how search engines crawl your website, which inevitably makes log file analysis an essential part of website SEO. It`s hard to find an SEO specialist who wouldn`t be aware of that, and there is no wonder log file analysis gets more popularity over past years.
It doesn`t mean there are no questions related to the whole procedure, though.
– What information exactly is needed from logs?
– Is it safe to integrate log files to SEO tools?
– How do I make sure the info won`t leak to my competitors, or be sold to them?
These questions are fair, and in this article, we`re going to discuss them, as well as the ways to integrate log files to the JetOctopus tool.
Log file is usually a text file that contains each step Googlebot makes here, it includes server IP, client IP, timestamp of the visit, URL requested, Http status code, user-agent, method (get/post), etc.
What we need:
Apart from those main parts, there are also secondary but still meaningful logs components that provide clues about bots’ behavior:
How it works: theory
Each time bot makes a request, your server sends a small package of data (on average, 200-300 bytes) on our servers in real-time. We analyze this data immediately and store it in the system where data appears without delays in the Raw logs report.
How it works: practice
This technology is built on the base of the UDP protocol. The main advantage of this technology is that it doesn’t impact your server, and even if all our servers break down, it won’t impact your site’s productivity at all.
Security
The only way to intercept data via Live Stream log data transmission is to get direct access to the core routers between your server and our server. You don’t have to worry because it is almost impossible to realize.
How to do it
The only thing you need to do is to insert two lines of code for NGINX configuration.
As for the Cloudflare integration, all you will require is to insert a code for Cloudflare workers.
Please remember that your server doesn’t send us any sensitive data such as passwords, users’ credentials, etc.
This way of log integration leads to a time gap in data ( 1 hour to 1 day approximately). Thus you won’t know what is happening on your site at the particular moment. Nevertheless, this one is one of the most frequently used by our customers.
How it works
Together, we choose the way and place of log storage and share all needed access credentials.
Then, your system administrator should set up automatic data exporting for the previous day time that is available at the beginning of the present day.
It’s only a 1-time setup from the client’s side that will enable all next log updates in the storage, no need to export files manually every day.
Every morning JetOctopus retrieves fresh log data from the mentioned storage, analyze it, and import it in our system, so the dashboards will be updated automatically.
Security
This way of logs integration is the most secure. Files transfer is conducted via the HTTPS protocol. Data is only accessible through the IP and with the password.
When to use
This way is suitable only for uploading large volumes of historical logs in the JetOctopus dashboard. This process usually takes a few days.
How to do it
Your system administrator should set up data extraction for a particular period and transfer data via FTP, S3, etc.
Security
This way of logs integration is the most secure. Files transfer is conducted via the HTTPS protocol. Data is only accessible through the IP and with the password.
Before we continue:
The abovementioned ways can be combined for your convenience. For instance, you can download historical logs via Bulk Dump and then connect the Live Stream. If you ever decide to switch the way of integration, it won’t cause data loss in the JetOctopus interface.
From our experience, different users have specific attitudes and fears connected with the security of the data. And we totally get it.
So before using any tool we have to highlight that JetOctopus follows GDPR of personal data and doesn’t use any sensitive data like POST requests with users’ passwords, invoices data, etc. We don’t collect, analyze, and save this data.
We do not process and we do not save users’ IP addresses, even if you provide us with this data. An IP address is only saved in case the User-Agent line contains the word “bot” in it.
If you feel like you need an additional legal justification behind the data transfer we sign a mutual NDA (Non-disclosure agreement). It is not an obligatory part but is done at your request and you can suggest your own NDA document if needed.
Our Privacy Policy is disclosed on the website, where you have full access. Please make sure to read it carefully. It aims to help you understand what data we collect, what we use it for, and how you can exercise your rights.
Try Logs integration on our free 7-days trial.
Follow JetOctopus on Twitter and on YouTube.
And stay tuned!