##################
  ####### Billar #####
## TELEGRAM.ME/mbmbms ##
  ## Indexator v9.2 ##
   #################

RECOMMENDED VPS / VDS / HOSTING: https://goo.gl/ji26qj and https://goo.gl/9ZiB6x


Upgrade to v9 for ALL:
- Read the NEW requirements in the column "Installation:" (below)
- Replace the files with new ones
- CHMOD 0777 / tmp / and all files inside
- "Settings" -> Click "Regenerate" -> "Save"
- "Shells" -> Click the "Insert Indexer Code" -> "Save" -> "Restore Includ"


v9
- Support for PHP7 + APCU: increased performance and a significant reduction in the consumption of RAM.
- Updating of layout and description (including manual)
- 23 bug fixes
- updating the run algorithm to the current one for 2018


v8
- The kernel has been optimized. Up to 60%
- Script auto-update script: u.php (Can be put on cron)
- Improved base of cloaca
- Increased the "range" and "the number of links to the page" to 5 (was 3).
- Improved link output
- Made 2 versions of the script: RU (Google + Yandex) and BURG (Google + Yahoo + Bing (MSN))
- Fixed many minor bugs and bugs (logic + design)

Welcome to the world of carefree SEO! And one of the doors to this wonderful world is called the indexer of the billy :)

Indexer - a script for instant indexing of pages in search engines. For this, sites (donors) are used, where you place a special code for the script.
This code uses a specific algorithm to place links on your donors database, thus:
- For minutes, even novo-registers in the index (In Yandex attracts fast, in google - the index in an hour)
- It raises positions (MF, LF kei - TOP-10 in most cases of the run by the indexer). Khrumer with an anchor run did not give a similar result.
- Does not create spamming (effect of exploding links)


What sets the script apart from competitors?
- The best cloaca: uses its own IP bots database + autocomplete database (based on the script's experience) + filter by user-agent'y
- AutoIncloud: the script will automatically place Includ
- Flexible setting: the choice of a priority search engine, the distribution of links to certain categories of donors, setting the number of published links and their multiplication
- Mode "SAPE": to increase the position of high-frequency caches (works on minimum HF queries, for example: steam stealer, download update windows 7 x64)
- The most hidden work, allows you to keep donors without loss for a long time





Installation:
DO NOT INSTALL SCRIPT STILL THE IP WILL BE CONNECTED.
After receiving the script, immediately send me the IP server (if you are an old client, then together with the old IP), on which to draw the binding:
1) IP server
1.1) If you are an old client, then the old IP + new IP
2) ICQ / Skype / E-Mail which will be supported and updated

Change IP license:
Write to TELEGRAM.ME/mbmbms, send the old and the new IP. Setup only after changing the IP address


Requirements: PHP> = 5.3 (re: PHP 7.0) + MySQL + PDO + (InnoDB - otherwise it will not install stupidly) + PHP-APC> = 3.1.4 + APCu_BC (https://pecl.php.net/package/ apcu_bc)

Installation instructions for APCu -> https://serverpilot.io/community/articles/how-to-install-the-php-apcu-bc-extension.html

I'm not asked to install, configure.
I support the script, trust the hoster.

0) url_fopen = on; curl; PHP as Apache (Normally tuning in ISPManager. In PHP, like CGI - does not work (pages are not added))
If pages are not considered - 100% problem either in PHP-APC or its inoperability.

1) Upload scripts to the root of the domain. Those. site.ru/admin.php
www_ru - RU version
www_en - BURGEH version
httpd.conf -> php_admin_value open_basedir none
my.cnf -> max_allowed_packet = 16M

2) Open admin.php, enter the required data for installation
2.1) Set permissions on the root folder, the tmp folder (and files inside), and the folder 'pinger' - 0777 (recursively and the folder with the script), if the installation does not occur (config.ini is not created).
If this also did not help, open admin.php and change error_reporting to 1. See the error - solve the problem.
3) Use the script
4) Add execution of the script (once a week) to Cron: http://site.ru/optimize.php


FAQ:
Before contacting the support for any problems, check:
1) Do you have 0777 rights to the root, the tmp folder and the files inside
2) Is the PHP operating mode set to Apache (CGI will not work)
3) The script will only work on second-level domains (anti-bargaining). on domains 3go - will work in "demo" mode
4) NECESSARILY: look at the server error logs (error.log), there necessarily will be an error if it is present.
VERY common: PHP Warning: curl_setopt (): CURLOPT_FOLLOWLOCATION can not be activated when an open_basedir is set in ...
This error causes: a problem in the work of the auto-enloud, as well as the counting of pages does not work


It produces an error fsockopen, with fsockopen turned on and running.
In the / etc / hosts file, remove 127.0.0.1 for the domain
The IP server in PHP configurations must be real, and not equal to 127.0.0.1 (this is the basic setting) (SERVER_ADDR must be equal to this IP)

Recalculation of statistics does not work:
max_allowed_packet larger image
max_allowed_packet = 16M

The DB is flashing:
1. Speed ​​up MySQL. Moving temporary tables from disk (tmpdir) to RAM
2. Running optimize.php

With these parameters, everything is ok, it can fall due to a lack of memory, which often happens, you should look at the logs: /var/log/mysql/error.log, there it is always written what is wrong.

If you add links, there are donors, but do not chase the task:
So you, my friend, are one of those unique people who were too lazy to read the beginning of the manual and tell me the IP.
You have exactly 24 hours from the time of installation, to give me an IP (and after the activation of the license - to reboot the server), otherwise all donors will fall into the bank of Yandex.


Does not add a job, writes "no selected file":
If a job with more than 5000 links is not added, then the problem in the database limit is the maximum query length, or in the PHP limit for the maximum file size uploaded / maximum query size.
Verification: try adding 10 links.
Change the limit.
Maximum of 10 files can be added.

Not installing (refresh page):
Most likely there are no rights to the root where admin.php is located. Can not enroll config.ini
If this also did not help, open admin.php and change error_reporting to 1.
See the error - solve the problem. Errors are in the error logs (the placement is usually next to the root folder of the site (logs)).
error_log ... txt
Before you torment me with problems with the installation - look into the error logs!

Inklud does not work (does not add donors, pages):
Inklud not otstuchal: 99% guarantee that you have a problem with PHP-APC. or the IP server is not registered under license (write to me)
Or includ is not installed correctly. First of all, just run the script separately from donor, check if it will be added in this case.
Those. create a separate php file on the shell with the code includa and run. He must (MUST) tear in the admin panel.

If donors have appeared, but pages are not considered, most likely there is no IP license. I recommend to unsubscribe me within 24 hours
IP otherwise the donors are flying to the abends of Yandex (that's how we are fighting the barygs).

What server is needed to work:
RAM 1GB is enough for everyone. The processor is not that important.

What donors are needed:
As much as possible and better.
I have enough: 50-60 donors with index 5000+, TCI 50-1000.


There are problems with the script:
First of all, look at the server logs (error_log), there is likely to be an answer to your question.
If you can not solve the problem yourself, then write to me at ICQ 92619 with an excerpt from the server logs, where an error is visible due to which something does not work.
Write in format:
* Problem in operation (description) *
* Excerpt from logs *
* Link to admin, login, password *



In case of finding bugs - write, we will correct in the near future.



A brief FAQ-recommendation on the compilation of tasks:

I recommend to use ONLY [STATIC] run (links are remembered on the pages where they were first shown)
[DYN] run it makes sense to use ONLY if there is not enough space on the donors or a small number of them.

"Range" (0-5): setting for "competitiveness":
n - for no competitive queries (if there is no result in the issuance of the key) Each page contains only 1 link.
-1 + n + 1 - the previous link is published, the current one and the next one. This is for low-demand queries. When there are 1-15 sites in the issuance of a direct entry of the key.
-2 + n + 2 - for medium-competitive ones. When sites are 15-100.
3,4,5 - for highly competitive inquiries. When 100+
5 - maximum recommended parameter based on tests

"PINGER" (0-100%): I recommend using at a value of ~ 5-10% in any task.

"PRIORITY" (RU: Google, Yandex | EN: Google, Yahoo + Bing (MSN): I recommend always downloading 100% of the referenced links in the priority of Google + Yandex (if RU dory, and 50% if the burg, only for Google)

"RANDomize" (gallochka): if checked, then during the run, each new link MUST be on the donor, different from the previous one. I recommend to put this item ONLY if the amount of space on donors - an overabundance, as well as with very competitive requests.

"Pages / Link" (1-5): this setting depends only on the frequency of the referenced links. If kei LF - 1, MF - 2, HF - 3,4,5 (Do not forget to consider the competitiveness when setting the range).

LifeKhaki:
- You can simultaneously upload up to 10 link files
- You can specify the text before and after the link (in 1 line).
Напр: Where can I find <a href="http://site.ru/"> crane </a>?
- You can download files in a non-anchor form (pure link) and enter the anchor when adding
- You can not specify the name of the job (the name will consist of the names of the downloaded files_
- In the "job manager", the middle file reference is used as the reference under the job name.
- If you click on the progress bar of the "Range / Status" column, you will see detailed statistics, where you can see which page is the link.
Also on this page you can save links to pages of donors where links from tasks in TXT format are placed

Recipes for the run - with 100% guaranteed result:


EN
Low-competitive low-frequency kei by Yandex + Google: Priority "Yandex + Google", range -2 + n + 2, Number of links to 1 URL: 1, Category: ru + com
Highly competitive HF kei by Yandex + Google: Number of links: 3, range -3 + n + 3. Priority is separate from Yandex and separately Google (if you need Google, add the task separately a second time)

En
The most important thing is the number of links.
If you need to advance 2-3 requests and very quickly, then use the "Output HTML / JS" block to create end-to-end references.
The remaining settings correspond to the logic RU

_________________________________________

Manual

[Home] On this page, you add jobs to the indexer:
Links are posted on 2+ levels of donors (http://site.ru/*/*)

Dynamic or Static Run:
With dynamic links are shown on 1 page - 1 time. At a static - are remembered.

* Reference range:
** 0 - on each page of the donor one link is published (one by one from the job). Those. each link is published only once.
- Probability of sanctions for Dora and Donor is minimal
- Run more smooth and uniform
- Increase of positions only on LF Keys
- Absence of indexation to APA, or a small percentage of a fast index
** 1 - 3 links are published on each page. (n-1), n, (n + 1). Those. link to the current, the link is current and the link is next.
I personally use this range by default. I think the most optimal option.
- Speed ​​up to 30-50% of links
- Missing overshoots
- Positions are increased almost at all, medium-competitive low-end kei, as well as low-competitive SR kei (Actually kei for dory)
** 2 - (n-2), (n-1), n, (n + 1), (n + 2) = 5 links
- Already there is a clash of overshoots. Therefore, I recommend that you drive 50-80% of all Dora links.
- Fast forward up to 90% of links
- If the donors are of high quality, then they will increase their positions even in highly competitive SK cashes.
** 3 - (n-3), (n-2), (n-1), n, (n + 1), (n + 2), (n + 3) = 7 links
- We recommend this range only for very high quality donors
- The maximum possible effect with a full flight through the speedboat
- It's not strange, but the positions do not increase more than on the "2"

* Ping: Sending links along with the anhores to PING services.
Specify the% -number of the links in the file that will be randomly selected and pinged.
(You need to configure the script for this function)

* Priority: Select the priority search engine.
** Yandex or Google: the links will be placed on the donor, only after visiting the Yandex bot or Google respectively.
** Yandex + Google: Recommended if the runway is calculated for both PS. At the same time,% nt of references that fall through the fastboot is reduced by 2 times.

* Category: selection of certain donors that are placed in a certain category

Add links to a .txt file, format:
<a href="http://url/"> Anchor </a>
<a href="http://url/"> Anchor </a>
<a href="http://url/"> Anchor </a>
<a href="http://url/"> Anchor </a>
Encoding UTF-8 (it is desirable).

The full format is also supported:
Text text <a href="http://url/" alt="123" title="123"> Anchor </a> text text
Text text <a href="http://url/" alt="123" title="123"> Anchor </a> text text

Task Manager:
Tasks are placed page by page, 10 per page. (by the way, check the download speed of the manager for a large number of tasks / links).
Brakes are possible due to unchecked output logic.
** Column "project" (clickable, sorts alphabetically): job name
** Column "priority": shows the current priority of the job.
** Column "G. \ Y. Impressions": the number of times when Google or Yandex respectively saw "references" from the job.
Purely grows directly proportional to the circumambulation of donors.
** Column "Range / Status": shows the selected range of the job, as well as the "progress bar", which shows how much the job is completed.
Completely gray line - the task was not chased.
Completely green - the task was completely chased.
You can see the exact amount by hovering the mouse over the progress bar.

** "Pencil" button: editing a job
** "Link" button: viewing pages and links to them placed
** "Pause" button: useful only if the task has not been run completely. The job stops publishing new links, the next
active assignment
** "Delete" button: deletes the task, frees the occupied space on the donors.
It is important to understand that if you delete a job, links disappear from donors. I do not recommend doing this until the moment of the "exit" of the doorway from the index, since by deleting
links, you can trigger "flashing" links and thereby increase the likelihood of a ban. (both donors and the most runway site).

Additional functions:
* HTML / JS output: displays any code you need on the donor pages.
It is important to understand that both references from the indexer and this code are output in the place where the Includ is located. (In case of automatic inclusion - at the very bottom of the page).
* Editing job parameters: after adding a job, you can edit its name and settings using the button that is to the left of the job name.

[Donnor] Here is the manager of donors:
* General buttons:
** "UPLOAD: Shell": floods the shells to the donor with the "backdoor", which is built into the indexer's index. Fills in all donors, where the backdoor
is accessible "from outside" (sometimes, on script the scripts overlap the backdoor, 10-15% of cases do not break through on average).
The pouring occurs in the deepest found directory (At the root the random is selected and the deepest one is searched for in it).
Fills obfuscirovanny shell WSO 2.5. Password on shell = "Client password" (Settings tab)
Shells appear in the "shells" tab.

** "CHECK PHP-INCLUDE": checks the "from outside". Does not work, only if the inclusion is covered by the script of the donor (10-15% of the cases I have).
Fix it does not work.
If the "donor" was defined as not valid, then look at the "Last request" date, it immediately shows whether the donor is working or not.
Alternatively, check "from the shell" (for details see [Shelly])

** "DEL: NOTACTIVE": removes donors, which lasted more than 2 days ago.
Links that are placed on these donors will automatically start to be placed on available donors.

** "DEL: DERROR": deletes donors whose status after the check is "not active". I do not recommend this button because the check works not always right.
Links that are placed on these donors will automatically start to be placed on available donors.

** "ADD CAT": adds a custom category

* Table:
** Column "Donnor" (clickable, sorts alphabetically): displays the address on the donor with the transition without a pale link to the admin area. (anonym.to)
** Column "Sort by status" (clickable, sort by status): Displays the donors status after "Checking donors": "Green tick" - available, "?" - POSSIBLE can be deleted.
** Column "Pages":
*** First digit: shows the number of free pages (where there are no links)
*** Second digit: shows the number of occupied pages (with links placed on them)
*** Third digit: shows the total number of registered donor pages.
** Column "Last request" (clickable, sort by date): the most correct option is to determine whether the includ is working or not. Shows the time of the last denial of this donor to our site.
** Column "Shell": shows whether there is a shell in the "Shell" tab for this donor.
** Button "Pour shell": tries to fill shell on donor through backdoor inkluda. The button is inactive if the donor is marked as "inactive" or the shell is already in the "Shells" tab
** "Delete" button: removes the donor (it is restored when pushed) and all the links that are placed on it are automatically placed on available donors
** "Freeze" button: the admin panel stops publishing new links on this donor, and new pages are not registered either.
In this case, already published links are displayed.



[Shelly] Here is the manager of donors with automatic inclusion:
* The "Code to run on the shells" field: by default displays the obfuscated script for automatic inclusion.
You can replace it with any script for you (without encoding it with <?>, <? Php?>) Or use the code for manual inclusion.
Button "Insert Indexer Code" - inserts the indexed code of the indexer


* "Add new shells" field: opens the field for adding new shells.
Supports shells WSO 2.5, WSO 2.4, c99, r57 (On modified versions of shells, it may not work).
If with a password, add in the format:
http://site1.ru/shell.php;password
http://site2.ru/shell.php;password
http://site3.ru/shell.php;password

If there is no password, then:
http://site1.ru/shell.php
http://site2.ru/shell.php
http://site3.ru/shell.php

I recommend adding 10 shells in batches. Immediately after the addition, there is a "check" of the shell, as well as an automatic includ script, which is written in "Code to run on the shells."
If you add more than 10 shells, you may hang.
Automatic inclusion is placed at the end of the root index.php with a tick (to determine when the check "from the shell" the presence of the inkluda)


* Manager of shells:
* General buttons:
** "Check All" button: check the shells for availability and availability of the Includa "from shell".
** "Restore all" button: Sets the clone on the available (minted) shells, where the status of the Includa is "not placed".

Table:
** Column "Shell" (clickable, sort by alphabet): clickable links to shell.
** Column "Password": password for shell
** Column "Type": shows the name of the shell or "red exclamation mark" if the type of shell is not defined (in the case of the WSO - it is possible that the shell is just modified).
** Column "Status": shows the result of automatic inclusion.
** Check button: checks the shell for validity
** "Delete" button: removes the shell, without removing the inclusion.

[SAPE]: The second variant of the donors run, in which the maximum possible weight is passed to the defective links. Those. effect known to all sape.ru.
Links are placed at the 1st level of donors (http://site.ru/*)
* "Add links" fields:
** "Job name" field: job name for job manager
** "Links" field: links are added line by line in the format:
http: //site.ru / ...
http: //site1.ru / ...
** "Anchor" field: the names of the links that will be assigned when placing.
** Textbox: creates an environment for links in the format (the macro {url} will be replaced by one of the links.):
Text text {url} text.
Text {url} text text!
** Priority and category have the same functions as in the main indexer
** The "Number of pages per link" field: the number that determines how many pages each link from the "Links" field will display.

For example:
References:
http://site1.ru/
http://site2.ru/

Anchor:
my site
one of my sites

Texts:
Check out {url}!
Here is {url}.

Number of pages per link: 4


Result:
Check out <a href="http://site1.ru/"> my site </a>!
That's <a href="http://site1.ru/"> one of my sites </a>.
That's <a href="http://site1.ru/"> my site </a>.
Check out <a href="http://site1.ru/"> one of my sites </a>!
Check out <a href="http://site2.ru/"> my site </a>!
That's <a href="http://site2.ru/"> one of my sites </a>.
That's <a href="http://site2.ru/"> my site </a>.
Check out <a href="http://site2.ru/"> one of my sites </a>!




[Settings]: The settings of the entire indexer system.
* "Cleaning" fields: delete the data corresponding to the buttons from the database.
** "Clear statistics" button: clears all statistics, including registered pages of donors and links placed on them.

* Client Password: Sets the password for the backdoor, as well as for the flooded shell through the backdoor.
* "Client side code" field: unvisored code for inclusion on donors


Ping settings:
Proxy list for ping (used if filled): the proxy through which the ping is generated (I recommend for less palevosti)
Services for ping: services, through which ping

CRON file URL: a link to be placed on cron for pinging (under it there are ready commands for cron php and cron php)


_________________________________________


Update 6:
- Improved link publishing algorithm
- Added IP cloak to determine bots Yandex and Google
- Significant improvement of the code inclusion algorithm for donors
- Minor improvements and fixes to the design

Update 5:
- Updated inklud and encryption method
- Now on the shells there is a search for neighboring sites and they are also included
- Updated algorithm for distribution of links
- Fixed the problem of encoding Russian references
- Added recursive search for files for the code of code
- Reduce the load on the database ~ 45% by optimizing the code


UPDATE 4.6:
- Added dynamic run type (links are not remembered on pages)
- Added "randomization" of donors. Each new link is published on a donor other than the donor of the previous link.
- Minor fixes + bug fix on performance
- Bugs fixed in the interface


RELEASE:
- Now you can add links with the text environment, as well as sign the links with the alt, title
- Fixed problem with saving settings
- Improved the work of the new PING link module
- The job name is assigned either automatically (file name), or with your own (the field of adding)
- Improved performance statistics (managers will not lag more)
- Fixed issue with HTML / JS Output
- Added UPDATER for updating from the old version of the indexer (with saving links and donors, but the links are placed on the new one). Old inklud also works fine on the new version
script. Those. you just need to replace the scripts and run UPDATER for the database.
- Fixed the problem of progress bar
- Added output of errors in the case of not properly configured PHP
- Improved compatibility with different hosters
- OVER 9000 minor improvements and improvements. Thanks to all the testers for the work!
- Fixed problem with adding donors on some servers
- Improved compatibility with apache, ngnix.
- Fixed a problem with working with php-apc
- ADDED LINK PENGUID: new function, + 30% indexer efficiency
- Added the ability to randomly publish links (in the settings of "Random Jobs"): if the function is enabled, the links will be given with each request from a random job.
This significantly reduces the efficiency of the script in terms of fast indexing, but improves the "stability" of the doorway when indexing in the future.
- Removed all the trash in scripts from older versions
- ABSOLUTELY reworked logic. The fact that previously worked not as it should, now works perfectly.
- The maximum possible optimization of work with the database. Now the script is faster, more reliable and takes much less resources
- Added custom categories
- Added the ability to view the pages where the links are placed. This took the most time, as the logic of previous versions was radically different
from the implementation of this function. Apparently worth it to wait with this feature, because if it was not engaged, then all that in the plans for the near future (below is painted)
already would have been done. This is my mistake, sorry. I did not expect that I would have to so sweat over the structure of the database.
Now you can see the pages and links to them through the database. In the interface this function will be added at the next update (did not have time)
- Much more rigid binding. This is due to the constant distribution of the script to the left, as well as the sale of it by third-party people
- Many small edits on the work of the sections "donors" and "shells"
- In the script for Includa, a new method of connecting to the admin panel has been added, via sockets. Now the client will not work only if url_fopen = off
- Removed dorgen.panel, check the index and check the doorway (the scripts are left, did not have time to remove). Do not interfere
- Some code is obfuscated
- Grouped domains by subdomain.
- Added the ability to "delete" donors one at a time
- Added the ability to "freeze" the donor: Links that are already posted on the donor will be shown. However, new donor pages will not be registered
(accordingly, nothing will be placed on them)
- Links from the "main" indexer are placed only on pages of the 2nd level (site.ru/*/*), and links from SAPE on the first level pages (site.ru/*).
Thus, the tasks of the first and second will be carried out as much as possible relevant.
- Added "sorting" in the managers.
- The manual on working with the script is written (yes yes, at last I did it)