Note: Phantom Pages - General Outline
Phantom pages are ordinary static HTML pages that derive their
name from the fact that they are not intended for human perusal.
They are intendend for search engine spiders only who will crawl
them. By contrast, human visitors will be redirected in realtime
to your main or Core Domain.
Input wise, phantom pages are generated from predefined
elements:
- Keywords/Search Phrases
- Descriptions
- Fillertext
The fantomas shadowMaker™ program can generate an unlimited
amount of unique phantom pages by randomizing the choice of
fillertext which, on the phantom page proper, constitutes the
body text, to be augmented/"innoculated" by your predefined
keywords/search phrases to your predefined keyword density.
This is the basic structure of a phantom page:
HEAD
- title
- META Keywords
- META Description
BODY
- description
- cross links
- random content (processed to feature keywords/search phrases
                  in predefined density)

Field: "Shadow domain (http://...)"
Enter your Shadow Domain's full URL in this field.
E.g.: http://www.yourshadowdomain.com/
This entry will be required for building the URLs in your
search engine submission list.

Checkbox: "Generate index page(s) only"
Select this option e. g. if you want to generate fresh
index pages in a subsequent run. This will allow you to
optimize your index page(s) for additional keywords, etc.

Checkbox: "Overwrite existing index page(s)"
Select this option to overwrite any existing index page(s)
generated in a previous run.

If this checkbox is not selected with previously generated
index pages on your system, the following error message
will pop up:

"There are already existing index pages. Please
choose overwrite before you start creating
new ones."

To remediate this situation, return to Step 4 and select
the overwrite option.

Field: "Title of index page"
Enter a fixed title for your Shadow Domain's index (home) page in
this field.

You may optionally select "Choose keyword of index page" here.
(More on this function further below.)

Now, if you enter a title with the placeholder symbol "#" here, e. g.
"We offer great # stuff!", the placeholder will be replaced by the
pertinent keyword or keyword phrase during page generation.

If you don't select the option "Choose keyword of index page", the
placeholder will be removed. In the example above, this would simply
generate an index page with the text "We offer great stuff!" in the
title tag.

Text area: "Body text of index page"
By default, the body text of your Shadow Domain's index (home) page is exempt
from randomization and must be entered in this text area field.

IN STANDARD MODE:
If you select option "Choose keyword of index page" but fail to enter
text for "Body text of index page" in the textarea field, the index page's
body text will be generated randomly from the fillertext file as for any other
phantom page. The program will also include a selected keyword or search phrase
into this page's body text. (See pursuant description.)

Checkbox: "Choose keyword of index page"
When selecting this option, the index page will be optimized for a keyword or
search phrase. As the program cannot know of itself which particular keyword
or search phrase you want to optimize the index page for, you are offered three
possible options to choose from.

Radiobox: "Select randomly from keyword file"
Select this option if you want the keyword or search phrase to be selected
randomly from the standard keyword file as defined under either
"Keyword flat file (name)" or "Keyword CSV file (name):" above.
(Choice of keyword file will depend on which of these two options you have
selected.)

Radiobox: "Keywords for random selection" (with text area)
This option allows you to manually define a separate list of keywords or search
phrases for your index page only.

Each keyword must be entered in a separate line.

Example:

keyword1
keyword2
keyword3
search phrase1
search phrase2
search phrase3

Radiobox: "Additional keyword flat file (path/name) for random selection" (with entry field)
As a third "Choose keyword of index page" option, you can have the program pull your keyword
from a dedicated plain text file. Define this file's name in the entry field.

If you enter a file name only, the file in question must reside in directory
"input/input_keywords".

Else, please define the full system path along with the file name.

Field: "Title of phantom pages"
The phantom page titles will be generated according to a fixed
mechanism, integratng the relevant keyword/search phrase with a
text to be predefined by you in this field.
The keyword/search phrase will be represented by a place holder.
Example:
--------
Best # here
We offer #
Find infos about #
During phantom page generation, the place holder # will be
replaced by the keyword/search phrase relevant to the phantom
page in question.
Thus, the final titles in our example might look like the
following:
Best online casinos here
We offer security solutions
Find infos about search engine optimization

Tip: For optimum ranking and traffic generation results, we
recommend using short, snappy titles of no more than two to max.
four terms (plus keywords/search phrases).

Field: "Text above cross links"
On the phantom page, following the page description right at the
top of the BODY section, selected cross links to other phantom
pages will be listed.
By default, the first two links will point to the Shadow
Domain's index page and the sitemap (which will be generated
automatically), followed by 4 additional links selected
randomly. This cross linking mechanism ensures that all phantom
pages are cross linked multiple times across the whole Shadow
Domains, thus avoiding possibly orphan pages which are viewed
unfavorably by the search engines.
You can optionally include further text above the cross links
section. (E. g. "printer friendly copy", or similar.)

Field: "Text under cross links"
Text optionally entered in this field will be added immediately
below the cross links section.

Field: "Max. links per sitemap"
If generating a large number of phantom pages for a domain,
it is recommended not to feature all internal links on a single
sitemap page. (In an attempt to weed out mere link farms, some
search engines will limit the number of links their spiders may
follow per given page.)

This parameter lets you define the maximum of links to be featured
on your domain's sitemap pages.

In accordance with this parameter, the program will create multiple
sitemap pages which will then be linked to in aggregate from a top
sitemap page.

To accomodate very large numbers of links, the program may also
generate multiple layered sitemap top pages.

Checkbox: "Include Title attribute for links"
Check this box if you want to include title attributes for the
links on your sitemap page(s).

This will create title tag entries in the following format (example):
<a href="key-phrase-01-01.html" title="key phrase">key phrase</a>

Field: "Content text weight (kB)"
In this field you can determine the size of the randomized body
text to be included in the phantom pages.
Note that the actual file size will be somewhat larger due to
additional overhead being added by HTML tags and JavaScript
code.
Tip: When generating several phantom pages per targeted
keyword/search phrase in varying keyword densities
(recommended), we suggest you also experiment with varying
content text sizes for optimum ranking results.

Field: "TARGkd"
Enter the targeted keyword density in this field.
To achieve the predefined keyword density, the phantom page body
text is basically processed as follows:
First, any occurences of predefined listed keywords/search
phrases possibly already included by chance in the fillertext
will be deleted and replaced by place holders. This avoids the
issue of inadvertently increasing the density of any given
keyword/search phrase beyond the predefined mark.
Next, the place holder will be replaced by the keyword/search
phrase desired for the page in question.
Finally, the text will be processed further to fine tune the
exact keyword density to the desired value.

Checkbox: "Include Cache Buster"
If you want to cloak for Google, you should implement a cache
buster (JavaScript code) on every phantom page redirecting
human viewers to the target URL.
Note that this won't provide you with 100% security - if someone
turns off JavaScript functionality in their browser, they will
still be able to see your phantom page code! However, this is
the next best option to being stigmatized by Google for using
their own proprietary NOARCHIVE tag.
If you select the checkbox "Include Cache Buster", a JavaScript
section wiil be included in every phantom page with the
respective target URL.