Frequently Asked Questions
- What does SiteAnalyzer do?
- Who is SiteAnalyzer for?
- What kind of resources does SiteAnalyzer crawl?
- Can I export the results?
- What are Visualizations?
- How is your product better than its analogs (Screaming Frog, Netpeak Spider, etc.)?
- Is it possible to scan 1 million page sites or even more?
- How many iterations are recommended for calculating PageRank?
- How to preserve all projects when updating the SiteAnalyzer?
- What does the "lack of resources" in the program log error mean?
- Sites are not scanned through Tilda, why?
- SiteAnalyzer System Requirements
- Is the SiteAnalyzer compatible with Linux and MacOS systems?
SiteAnalyzer programatically scans your website and extracts important site information which is then stored for your reference. You can use this data it to spot mistakes and drive improvements.
Digital marketing and SEO experts. Evaluating websites with hundreds/thousands of pages is tedious, time-consuming and error-prone. SiteAnalyzer compresses hours of work into minutes.
Yes! Everything SiteAnalyzer captures is available for Excel, CSV and PDF export so you can crunch the data however you'd like. You can also generate XML sitemaps for search engines.
Graphical, visual representations of the sites.The Site Map visualization lets you quickly grasp the site hierarchy and navigational graph, while the URL Structure visualization enables you to understand the site URL organization and URL segment weights.
We believe that the main advantages of SiteAnalyzer over competitors are as follows:
- High-speed scanning that does not concede with concurents.
- Ability to enlist all projects instead of downloading them one by one, as is the case with most competitors.
- 80% of the SiteAnalyzer features are the same as in paid analogs, so you will have all the tools needed for site analysis.
We are planning to implement all the main tools our competitors have quite soon, and also add our own to provide an even better user experience.
The program was tested in two operating systems: Windows XP and Windows 10.
- Windows XP x32 (3 GB RAM):
- scanned URL (html-pages): 92 000
- analyzed URI (pages, images, scripts, documents, etc.): 296 316
- elapsed time: 2 hours 50 minutes
- Windows 10 x64 (8 GB RAM):
- scanned URL (html-pages): 118 000
- analyzed URI (pages, images, scripts, documents, etc.): 2 334 260
- elapsed time: 6 hours 12 minutes
Therefore, as we can see the program can scan sites of almost any volume; it all depends on the RAM memory on your PC. The more RAM memory – the more site pages it will be able to scan.
P.S. Send your highscores of scanned pages (preferably with screenshots) and we'll include them in this FAQ.
The more iterations – the fewer errors in calculations.
For instance, after the 10th iteration, the weight value changes to thousandths and ten thousandths, i.e. values so small that can easily be neglected.
Even a couple of iterations will be enough to see the difference in weight.
We recommend using 10 iterations.
Usually, when you update the SiteAnalyzer, the results of previous scans are saved. However, when you bring in changes to database structure (this happens with major updates), you have to scan the projects again.
The best way to do this:
- Run the current version.
- Select the sites you need in the list of projects.
- Use the context menu to copy them to the clipboard.
- Launch a new version of the program.
- Add bulk-copied sites (click on the plus icon and paste the URL from the clipboard).
- Rescan the necessary sites if needed.
Sometimes when you scan large volumes with many threads in a log, you may receive the following error message: "The project scan is stopped due to lack of computer resources. We recommend changing the scan settings".
This error message comes up when the program is running and there is a shortage of system resources in the operating system. In this case, the scanning of the current project automatically stops. This is done to prevent the occurrence of system errors and the correct recording of data in the database.
To prevent this type of error, it is recommended to increase the amount of RAM on your computer, switch to 64-bit Windows, and optimize the scanning parameters in the program settings (reduce the number of threads, limit the number of pages for parsing).
When you try to scan projects through the Tilda site builder, you can often get a 307 redirect response code, and the site scanning will be stopped. This is due to Tilda internal protection against DDoS to parse the site. A possible solution is to set long delays between requests in the program settings (5-10 seconds), but it might not help solve the issue.
Tilda Technical Support Official Comment: This redirect is done by the integrated DDoS protection system. If you proceed using site scanners, then the protection will trigger more frequently. In this case, it triggered the "human" check and the service failed it. We cannot disable the protection system, since it is designed for the security of all sites. The protection is disabled in the case of search bots.
The SiteAnalyzer does not have high system requirements. If your computer has Windows XP and above, you can safely run the program to audit the site without any problems.
Microsoft Windows versions: 11/10/8/7/Vista/XP (32 & 64-bit).
So far the program is supported on Windows OS; we currently don’t carry out development for other platforms. However, if there is growing interest in the program, we will make it compatible with other platforms as well.
P.S. You can run SiteAnalyzer using Wine on OC Linux (which is an alternative implementation of the Win32 API that allows users of UNIX-like operating systems to run 32- and 64-bit applications). See help page on Wine emulator.