Note: Setting Up Your Shadow Domain
The Shadow Domain proper can be set up in various manners.
1. A tarball (a tar.gz packed archive file) is generated
   containing all phantom pages. (See below for the details.)
   This file is then uploaded to the Shadow Domain proper via
   FTP or Telnet.

There are two possible ways to do this:
a) directly, by logging in to your Shadow Domain and by
   downloading the file from your temporary output directory
   using whatever FTP client is available, e.g. WU-FTP - 
   please consult your FTP client's documentation to learn how
   to do this as we cannot cover such basics here.
b) indirectly, by downloading the file to your local system
   first and uploading it to the Shadow Domain from there.

On the Shadow Domain, log in via Telnet, switch into your Shadow
Domain directory, e.g. by typing:
cd /usr/www/htdocs/shadowdomain
Next, you will have to unpack the archive file.
Enter the following command:
tar -xz -f project.tar.gz

function: x extract files from an archive
  option: z uncompress data with gzip
          f use archiv file
The file will now be unpacked into the Shadow Domain's
Document Root (main) directory.

2. Download all files in the temporary output directory
   to your local system and upload them from there to the
   Shadow Domain via FTP.
3. For your temporary output directory, select the Shadow
   Domain's main directory. This ensures that all generated
   phantom pages will be stored right where they belong.
   Note that to achieve this, you will have to set the Shadow
   Domain's main directory's permissions to:
   "chmod 777" [drwxrwxrwx]

We recommend either method #1 or #2 as this will enable you to
test the whole procedure within a contained environment.
Option #3 will probably be the method of choice for the more
experienced user.
Close window ]
Field: "Tarball file name"
Define the tarball (a tar.gz packed archive file) file name
(without system path) in this field.
The generated tarball(s) will be stored in directory "tarballs".

Standard Mode: In Standard Mode, the character string defined here
will be treated as an absolute name. Thus, entry "project-1.tar.gz"
will give you a single tarball file named "project-1.tar.gz".

Bulk Mode: In Bulk Mode, any character strings entered here will be
combined with your respective Shadow Domain(TM) names to create
unique, easy to distinguish archive files. Thus, if you define e. g.
"project-1.tar.gz" in this field, tarballs generated may be named
"", "",

Field: "Only files newer than"
When generating further phantom pages for an existing Shadow
Domain at some later point, you may opt to create a tarball
containing only these newly created pages.
To do this, enter a date shortly before generation of your new
phantom pages in this field.
Date syntax: 2002-09-22 12:30:00
Now, upload this new, smaller tarball to the Shadow Domain and
unpack it as outlined above.

Button: "Generate tarball"
By clicking on this button, you will create and save the

Text area: "Submission URLs"
The newly generated phantom pages will be listed in this
window. These are the URLs which will also be saved in the
submissions list file for submission to the search engines.
Close window ]
Text area: "Logs"
For each job during which phantom pages are created, a log entry
is written into a dedicated log file and displayed in this text
area window. This allows you to check the various parameters
specified during the generation process, enabling you to further
fine tune the overall SEO process at a later point in time after
conducting a thorough ranking analysis and success evaluation of
your Shadow Domain's phantom pages.

2006-02-01, 02:14 -- Project Sports Site #1 -- -- Job 02 -- keywords.txt --
descriptions.txt -- sportscontent.txt -- 5 kB -- 1.5 % 
-- 2 skips
This sample log excerpt displays:
- the date and time the logged job was conducted 
  (i.e. "2006-02-01, 02:14")
- the Project Name (e.g. "Project Sports Site #1")
- the Shadow Domain for which phantom pages were generated
  (i.e. "")
- the number of the job run for this particular Shadow Domain
  (i.e. "Job 02")
- the name of the keyword file used (i.e. "keywords.txt")
- the name of the description file used
  (i.e. "descriptions.txt")
- the name of the fillertext content file used
  (i.e. "sportscontent.txt")
- the size of the body text generated (i.e. "5 kB")
- the keyword density specified (i.e. "1.5%")
- the number of skips specified (i.e. "2")
The log file's name is: "log.txt"
It is located in directory: "admin/"
Close window ]