AI Content Monetisation Site

This step does two things: get a server, and resolve your domain onto it.

Any entry-level cloud VPS will do — 2 vCPU and 2 GB of RAM is enough, for roughly US$10–15 a year on a promotional plan. Don't take 1 core and 1 GB: a hosting panel wants around 500 MB by itself, and anything else on top will thrash.

Once you have the IP, add A records at your registrar:

• Host @, pointing at the server IP
• Host www, pointing at the same IP

Propagation takes 5 minutes to 2 hours. Usually it's done before your coffee is.

After you SSH in, run the installer for your distribution.

CentOS:
yum install -y wget && wget -O install.sh https://download.bt.cn/install/install_6.0.sh && sh install.sh

Ubuntu / Debian:
wget -O install.sh https://download.bt.cn/install/install-ubuntu_6.0.sh && sudo bash install.sh

Press Y through the prompts. When it finishes you get a panel URL, a username and a password.

Do these three immediately:

1. Open the panel URL in a browser and log in
2. When the recommended-install dialog appears, pick LNMP or LAMP with PHP 7.4 — you won't use PHP, but having it costs nothing
3. Change the username and password in the panel settings

The panel's default port is 8888. If it won't open, allow port 8888 in the server's firewall.

In the panel:

1. Sites → Add site
2. Domain: yourdomain and www.yourdomain
3. Leave the root at /www/wwwroot/yourdomain
4. Don't enable FTP or a database — a static site needs neither
5. Submit

Then open the site's root directory in the file manager and upload everything you wrote locally:

• index.html
• wizard.html
• data/ — every JSON file
• assets/
• scripts/

Open the domain when it's done. If you see the home page, you're on track.

The site opens now, but it's empty. The content lives in JSON.

Edit these one by one in the panel's file manager:

1. data/config.json → site name, description, feedback channel
2. data/scenarios.json → the scenario list; delete anything you don't want
3. data/steps.json → the core file. Every step's title, body and checklist lives here, and copy like what you're reading drops straight in
4. data/faq.json → common questions
5. data/links.json → global promo links, i.e. your affiliate URLs

Save and reload. JSON is strict: no missing quotes, no trailing commas, brackets balanced. One mistake and the whole site renders blank.

The AI helper is local keyword matching. You write questions and answers into faq.json; someone types into the box on the wizard page, and the JS matches keywords and returns the answer.

faq.json shape:

{
  "keyword-id": {
    "keywords": ["dns", "not resolving", "ping fails"],
    "answer": "1. Check the A record points at the right IP; 2. wait ten minutes; 3. flush DNS locally"
  }
}

Write several variants per concept or the hit rate stays low: "can't open", "can't connect" and "won't load" should all reach the same answer.

The scripts live in scripts/ as plain shell text. Someone clicks copy on the wizard page and runs it on their own machine. You never execute anything in the browser — that's a server-side action.

This is the point of the whole exercise.

Common channels:

1. Cloud provider affiliate programmes — apply through each vendor's partner programme and put your referral links into the global array in links.json
2. AI tool invite programmes — sign up for the affiliate or invite scheme and place the link in the relevant step's promo slot
3. Placement rules

• At most one promo slot per step, and it must not push the content aside
• Keep it restrained, and state the promotional nature once in the footer
• Give promo links rel="sponsored noopener"

1. Compliance

• The disclaimer field in config.json already carries the wording
• It renders automatically at the bottom of the page

Don't open with a wall of ads. Readers aren't stupid. Give away the substance first, and put the promo where it reads as "by the way, this is what I use".

Last step: make it actually run.

HTTPS: panel → site → SSL → Let's Encrypt → request, then tick force HTTPS. Free, a year at a time, renewed for you by the panel.

SEO:

1. Write sitemap.xml and upload it to the root
2. Write robots.txt allowing all crawlers
3. Verify the site and submit the sitemap in the search platforms
4. Give every page a meta description

Analytics: put the snippet in <head> in index.html.

Monitoring: the panel has its own, or point a free uptime monitor at the site and have it notify you by email or a chat webhook when it goes down.

Backups: panel → scheduled tasks → package /www/wwwroot/yourdomain to object storage weekly. Don't wait until you've been hacked to wish you had.

Day to day:

• Update steps → edit steps.json
• Add a FAQ → edit faq.json
• Swap a promo link → edit links.json