Setup Guide

GET TRAFFICFORGE
LIVE IN UNDER AN HOUR

This guide walks you through every step of the TrafficForge Self-Serve setup — from getting your API key to publishing your first SEO pages live on Google.

~45 minTotal setup time

0Technical experience needed

$0Platform hosting cost

~$5/moMax AI API cost (heavy use)

Before You Start

Requirements

You'll need accounts at three free services. Cloudflare hosting is permanently free. GitHub is free. AI API cost is typically under $5/month for heavy daily use.

Account	Cost	What It's For	Sign Up
Google / Gmail	Free	Gemini API key + Search Console	accounts.google.com
GitHub	Free	Stores your SEO pages as files	github.com/signup
Cloudflare	Free forever	Hosts and serves your pages live	dash.cloudflare.com

💡Tip: If you already have a website, you don't need to move it. You'll just add a subdomain (like listings.yoursite.com) pointing to your TrafficForge pages. Your main site stays exactly where it is.

Step 1 of 7 · ~5 minutes

Get Your AI API Key

TrafficForge uses AI to write your SEO pages. You supply your own API key — you pay the AI provider directly at their standard rates with zero markup. Most users spend $1–5/month total.

Recommended Option A — Google Gemini (Free Tier)

Gemini has a generous free tier that's enough for most users. No credit card required to start.

Go to Google AI StudioVisit aistudio.google.com/apikey and sign in with your Google account.
Click "Create API Key"Select "Create API key in new project" — Google sets everything up automatically.
Copy your keyIt starts with AIza. Copy it now — you won't see it again in full.
Paste into TrafficForge SettingsOpen TrafficForge → Settings → paste in the AI API Key field.

ℹ️Free tier limits: Gemini 2.0 Flash is free up to 15 requests/minute. That's enough to generate 50–100 pages per day at no cost.

Option B — OpenAI (GPT-4o Mini)

OpenAI produces slightly higher-quality output but has no free tier.

Go to OpenAI PlatformVisit platform.openai.com/api-keys.
Add a payment methodGo to Billing → Add payment method. Add $10 as a starting credit.
Create a new API keyClick "Create new secret key". Name it "TrafficForge". Copy it immediately — OpenAI only shows it once. Key starts with sk-.
Paste into TrafficForge SettingsOpen TrafficForge → Settings → paste in the AI API Key field.

Step 2 of 7 · ~10 minutes

Set Up Your GitHub Repository

GitHub stores your SEO pages as HTML files. When TrafficForge generates a page, it pushes a file to this repo. Cloudflare watches the repo and deploys every new file automatically.

Create a New Repository

Go to GitHub and sign ingithub.com
Click "+" → New repository
Fill in the detailsName: listings-yoursite · Visibility: Public · Check "Initialize with README" · Click Create.

Create a Personal Access Token

Go to GitHub → Settings → Developer settings → Personal access tokens → Tokens (classic)
Click "Generate new token (classic)"
Set Note: "TrafficForge", Expiration: No expiration, Scopes: ✅ repo (top-level)
Click "Generate token" and copy immediatelyStarts with ghp_. GitHub only shows it once.

⚠️If you close the page before copying, you'll need to generate a new token.

Add a Homepage (index.html)

In your repo, click "Add file" → "Create new file"Name it index.html.

Paste a basic placeholder

<!DOCTYPE html>
<html><head>
  <meta charset="UTF-8">
  <title>Your Site</title>
</head><body>
  <h1>Coming Soon</h1>
</body></html>

Click "Commit new file"

Step 3 of 7 · ~10 minutes

Connect Cloudflare Pages

Cloudflare Pages watches your GitHub repo and makes every file live on the web within seconds of a push. Free, fast, and requires no server management.

Connect Your GitHub Repo

Log into Cloudflaredash.cloudflare.com
Go to Workers & Pages → Create → Pages → Connect to Git
Connect GitHub and select your repoAuthorize Cloudflare, then select the repo you just created.
Click "Begin setup"

Build Settings

Setting	Value
Framework preset	None
Build command	Leave blank
Build output directory	`/`

⚠️Do NOT set a build command. Your repo contains plain HTML files — no build step is needed or wanted.

Verify First Deploy

Click "Save and Deploy"Should complete in under 30 seconds.
Visit your .pages.dev URLCloudflare gives you a free URL like listings-yoursite.pages.dev. Confirm your index.html loads.

Step 4 of 7 · ~10 minutes

Add a Custom Domain

Most businesses use a subdomain of their existing site — like listings.yourdomain.com. Your main website is not affected at all.

Add the Domain in Cloudflare Pages

In your Pages project → Custom domains tab → Set up a custom domain
Enter your subdomaine.g. listings.yourdomain.com. Click Continue.
Cloudflare shows you the DNS record to addIt's a CNAME pointing to your .pages.dev URL. Keep this page open.

Add the DNS Record

Type	Name	Value
CNAME	`listings`	`listings-yoursite.pages.dev`

Add this at your domain registrar (GoDaddy, Namecheap, etc.) or in Cloudflare DNS if your domain is already on Cloudflare.

Fixing DNS Conflicts

⚠️If you get a "CNAME conflict" error, delete all existing A, AAAA, TXT, and SRV records for that subdomain name first, then add the CNAME.

DNS changes propagate in 5–30 minutes. Your .pages.dev URL works immediately while you wait.

Step 5 of 7 · ~5 minutes

Configure TrafficForge Settings

Open TrafficForge and fill in your settings. This is where the app learns about your business and gets permission to push pages to your repo.

Site Info

Field	Example
AI API Key	`AIza...` or `sk-...`
Site Name	Acme Plumbing
Site URL	https://listings.yourdomain.com
Niche / Industry	plumbing services, Dallas TX
Tagline	Dallas's Most Trusted Plumbers
Phone / Email / Address	Your business contact info

GitHub Fields

Field	Value
GitHub Token	Your `ghp_...` token from Step 2
GitHub Repo	`username/repo-name` (not the full URL)

ℹ️Repo format: johndoe/listings-mysite — not https://github.com/johndoe/listings-mysite.

Step 6 of 7 · ~5 minutes

Set Up Google Search Console

Tell Google your site exists, submit your sitemap, and monitor rankings. Without this, Google may take weeks longer to discover your pages.

Add Your Property

Go to search.google.com/search-console
Click "Add property" → URL prefixEnter your full URL: https://listings.yourdomain.com

Verify via HTML Meta Tag

On the verification screen, click "HTML tag"Copy the meta tag Google shows you.
Add it to your index.html in GitHubPaste inside the <head> section. Commit the change.
Wait ~1 minute for Cloudflare to deploy, then click "Verify" in Search Console

⚠️DNS verification often fails when you have a CNAME on the subdomain. The HTML meta tag method works every time.

Submit Sitemap

After your first page push, go to Search Console → Sitemaps
Enter sitemap.xml and click SubmitTrafficForge creates and updates this file automatically on every push.

Step 7 of 7 · ~5 minutes

Generate & Publish Your First Pages

Everything is connected. Time to generate pages and push them live.

Research Keywords

Open the Keywords tab in TrafficForge
Enter a seed keywordThink about what your customers search right before calling you. Examples: "plumber near me Dallas", "emergency plumbing Houston", "water heater installation cost".
Click "Research Keywords"TrafficForge generates 100+ variations with volume, competition, and intent scores.
Focus on green-scored keywords firstGreen = low competition + transactional intent = fastest rankings.

Generate Pages

Select 10–20 keywordsCheck the boxes next to your best opportunities.
Click "Generate X Pages"Each page takes 5–15 seconds. TrafficForge writes a complete page: title, H1, meta, body, FAQs, and schema markup.
Preview before pushingClick the eye icon to check quality.

Push to GitHub

Click "🚀 Push X to GitHub"This button appears once GitHub settings are filled in.
Watch the progress"Pushing 1/15... Pushing 2/15..." — after all pages push, TrafficForge updates your sitemap.xml automatically.
Cloudflare deploys within 30–60 secondsNo action needed.

Verify Pages Are Live

Check GitHubNew HTML files should appear in your repo.
Visit a pageNavigate to https://listings.yourdomain.com/your-page.html
Check sitemapVisit https://listings.yourdomain.com/sitemap.xml

🎉You're live. Check Google Search Console in 1–2 weeks to see impressions appearing for your keywords.

Troubleshooting

Common Issues & Fixes

Deploy Not Updating

Symptom	Fix
Site shows old content	Hard refresh: Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac)
Cloudflare "Disconnected from Git"	Pages → Settings → Git Integration → reconnect GitHub
Push succeeded but files not in GitHub	Check repo format in Settings — must be `username/repo-name`, no URL

DNS Not Working

Error	Fix
"CNAME and other data" conflict	Delete all A, AAAA, TXT, SRV records for that subdomain, then add the CNAME
"Not Activated" in Cloudflare	Wait 10–30 minutes. Check at dnschecker.org

GitHub Push Errors

Error	Fix
401 / Bad credentials	Generate a new token and update it in TrafficForge Settings
404 / Not Found	Double-check repo format: `username/repo-name`
Token works on some repos only	Confirm token has the top-level repo scope checked

Search Console Issues

Issue	Fix
Verification fails with meta tag	Wait 1–2 minutes for Cloudflare to deploy the change, then try verifying again
Sitemap "Couldn't fetch"	Push your first batch of pages first — the sitemap is created on first push
Pages showing "Discovered — not indexed"	Normal. Use URL Inspection → "Request Indexing" for your most important pages

FAQ

Frequently Asked Questions

Can I use TrafficForge with my existing WordPress site? +

Yes. TrafficForge publishes standalone HTML pages on a subdomain — completely separate from WordPress. Your main site continues running exactly as it does.

Do I need to know how to code? +

No coding required. The only technical steps are creating a GitHub repo and adding a DNS record — both are covered step by step above. If you can copy/paste and follow instructions, you can complete this setup.

Will Google penalize me for AI-generated pages? +

Google's guidelines focus on content quality and helpfulness — not how it was created. TrafficForge generates substantive pages with real business info, FAQ sections, structured schema markup, and proper meta tags.

What happens to my pages if I cancel? +

Your GitHub repo and Cloudflare Pages account are yours. Every page you've already published stays live permanently. You lose the ability to generate new pages, but all existing content remains indexed and ranking.

Reference

Full Cost Breakdown

Service	Cost	Notes
GitHub	Free	Public repos are always free
Cloudflare Pages	Free forever	Unlimited bandwidth, 500 deploys/month
Google Gemini API	Free tier	~$1–3/month for 300 pages on paid tier
OpenAI GPT-4o-mini	~$2–4/month	At 300 pages/month typical usage
TrafficForge	$49/month	Includes everything

SETUP COMPLETE. GO BUILD.

Everything is connected. Your first pages are live. The businesses that publish consistently win the rankings game.

Open TrafficForge → Need Help?

GET TRAFFICFORGELIVE IN UNDER AN HOUR

Requirements

Get Your AI API Key

Recommended Option A — Google Gemini (Free Tier)

Option B — OpenAI (GPT-4o Mini)

Set Up Your GitHub Repository

Create a New Repository

Create a Personal Access Token

Add a Homepage (index.html)

Connect Cloudflare Pages

Connect Your GitHub Repo

Build Settings

Verify First Deploy

Add a Custom Domain

Add the Domain in Cloudflare Pages

Add the DNS Record

Fixing DNS Conflicts

Configure TrafficForge Settings

Site Info

GitHub Fields

Set Up Google Search Console

Add Your Property

Verify via HTML Meta Tag

Submit Sitemap

Generate & Publish Your First Pages

Research Keywords

Generate Pages

Push to GitHub

Verify Pages Are Live

Common Issues & Fixes

Deploy Not Updating

DNS Not Working

GitHub Push Errors

Search Console Issues

Frequently Asked Questions

Full Cost Breakdown

SETUP COMPLETE. GO BUILD.

GET TRAFFICFORGE
LIVE IN UNDER AN HOUR