Table structure

Which sheets the service creates when exporting results, and what the sheet with domain lists looks like

Result sheets

The service creates the result sheets itself — nothing has to be prepared in the spreadsheet in advance. A sheet name is made of the section tag and the domain zone: the zone is taken from the domain ending and written in capitals (site.nl → NL, example.com → COM).

SectionSheet nameExample
Domain selection(DS)-ZONE(DS)-NL
Link check(LC)-ZONE(LC)-NL
Site DR(DR)-ZONE(DR)-NL
Domain history(WA)-ZONE(WA)-NL

Inside a sheet the first row holds the column headers. Every next task is appended below: first a row with the task name, then the rows of its domains. Nothing is overwritten.

Domains of one task from different zones are split across different sheets: .nl domains go to the NL zone sheet, .com domains to the COM zone sheet.
ScreenshotA connected spreadsheet with the sheets the service created: the tabs at the bottom read (DS)-NL and (WA)-NL; on the open sheet there is the column header row, a highlighted row with the task name below it and the domain rows under that.

The sheet with domain lists

When the domains for tasks are taken from the spreadsheet itself, the service reads the sheet named "База данных" (Russian for "database"). The name is matched exactly, character for character.

The sheet name is written in Russian — "База данных" — regardless of the interface language. A translated or renamed sheet will not be found by the service.

Each column of this sheet is a separate task:

RowContentDescription
1A date, for example 24.11Goes into the task name
2 and belowDomains, one per rowThe domain list of the task, for example example.com
The task name is assembled from the date and the zones of its domains: the zones are sorted alphabetically and listed separated by /. A column with the date 24.11 and the domains example.com, test.nl gives the task "24.11 COM/NL". To set the zone by hand, append it to the date after #: a column with 24.11#NL creates the task "24.11 NL" — whatever endings the domains in the list have.

Example of the "База данных" sheet

ABC
24.1117.1110.11
site.nlsite1.cadomain.de
test.nlsite2.caweb.de
domain.nlsite3.ca...

Column A in this example gives the task "24.11 NL", column B — "17.11 CA", column C — "10.11 DE".

Important

  • One column is one task. Empty cells in the domain list are skipped, gaps in a column do no harm.
  • Domains are cleaned up automatically: https://, www., the path after the domain and the port are dropped, and the case is lowered.
  • Repeats of the same domain inside a column are removed, and values that do not look like a domain are dropped and counted as invalid.
  • A column the service has already taken into work (the same date and the same set of domains) is not run again — the task will not be created twice.
Do not add a row with the zone under the date: everything below the first row is treated as domains by the service. A cell such as NL is not a domain — it simply lands in the counter of invalid values. The zone is set with the # tag in the cell with the date.