Can I move my license to a different machine?

License can be migrated once a month.

Which parameters come from or are evaluated by Clusteric PREMIUM API?

Artificial Intelligence spam evaluation: API_SPAM,
Link’s visibility in Google: SERP_VISIBILITY, SERP_TOPIC, SERP_SUBTOPIC, SERP_KEYWORDS, SUBPAGE, GOOGLE_TITLE, EST_VISITS, KEYWORD_CAT, KEYWORD_SUBCAT, SERP_RESULTS, RANK_PL / RANK_UK / RANK_US / RANK_NL, SEARCHES_PL / SEARCHES_UK / SEARCHES_US / SEARCHES_NL
Social stats (homepage): FB_Total, FB_Likes, FB_Shares, FB_Comments, Google+, StumbleUpon, Pins, LinkedIn,
Social stats (subpage): FB_Total_subpage, FB_Likes_subpage, FB_Shares_subpage, FB_Comments_subpage, Google+_subpage, StumbleUpon_subpage, Pins_subpage, LinkedIn_subpage,
Domain’s link profile strenght and risk factors: DOMAIN_PROFILE_POWER, DOMAIN_PROFILE_RISK,
Black hat lists occurrences: BH_LISTS_OCCURS,
Probability, that domain was build essentially for link building or is a part of link network: PBN_PROBABILITY,
Probable hosting owner information: HOSTING,

Do I need proxies to use Clusteric Search Auditor?

In most cases, proxies are not neccessary to perform valuable analysis (as most of domain parameters can be obtained from Clusteric Server cache).
Proxies should be used to download subpage-level parameters, eg.: checking duplicate content (DUPLICATE_CONTENT), Google cache (Cache_date, Cache_title), PAGE_PR (for many links) or PAGE_INDEXED param (page-level indexation, not to mistake with: INDEXED (whole domain indexation), which can usually be obtained from cache and does not require proxies). You also should use proxies if you choose to disable Clusteric server cache in options.

Which parameters can be obtained from Clusteric Server Cache?

INDEXED (Google indexation)
DOMAIN_PR (Domain Page Rank) – this parameter is deprecated (as Google discontinued providing its value to the public)
WEB_ARCHIVE (first occurrence in web.archive.org)
ALEXA_RANK, ALEXA_LOCAL, ALEXA_BL (alexa.com rankings)
SOCIAL params (homepage): FB_Likes, FB_Shares, FB_Comments, FB_Total, Google+, Twitter, StumbleUpon, Diggs, Pins, LinkedIn, Reddit, Delicious, Buzz
WHOIS data: WHOIS_created, WHOIS_expiry, WHOIS_registrar, WHOIS_email, WHOIS_DNS

How to choose an optimal number of threads?

Clusteric Link Auditor specifies two values:
Number of onsite threads – depends mostly on two resources: your Internet connection (bandwidth) and CPU speed. For instance, 10 threads (default value) works fine with 2 Mbit/s  Internet connection at about 10-15% CPU utilisation on 2.5GHz dual core processor. It is advised to monitor your computer/network performance and slowly increase the number of threads (analysis by analysis) if you still got free resources.
Number of off-site threads – mostly depends on the processed params and resources such as proxies/API credentials. For instance, if you want to download page-level Google-related params (cache, duplicate content) and use huge number of threads, you should add some good quality proxies as well. When using poor quality proxies, you might also increase the number of retries in case of error.

Can I audit/correct existing disavow file?

It’s easy with Clusteric Search Auditor!

Please read more here.

Link Auditor manual – table of contents