This is the walkthrough I would give you in person if you bought me a coffee and said “Tim, I just bought GSA SER, what do I do now?” Step by step, no glossing over the boring parts. Estimated time from blank VPS to running campaign: about 90 minutes.
For the strategic context — what you are actually doing and why — read the GSA SER pillar first. This guide assumes you have already decided to use the tool and want to get it running.
What you need before starting
- A purchased GSA Search Engine Ranker licence (€99 from gsa-online.de). Includes lifetime updates.
- A Windows VPS — see my tool stack pillar for current recommendations. Contabo VPS M is my default at €11.50/month.
- A proxy subscription. StormProxies 25-rotating residential at $50/month is the simplest start.
- A captcha solving subscription. CapMonster Cloud, fund $20 to start.
- A verified target list. SERVL at $37/month is what I use as the reference benchmark.
- Optional but recommended: an OpenRouter account ($5 funded) for AI content generation later.
Total to start: about $120 plus the GSA licence. Monthly cost after: about $90.
Step 1: Provision the VPS
Log into Contabo, order the VPS M with Windows Server 2022. Wait 15-30 minutes for provisioning. They email you an IP address, RDP username (Administrator), and password. Connect with Microsoft Remote Desktop.
First things to do once you are inside:
- Run Windows Update once. Reboot.
- Disable Windows Defender real-time scanning for the GSA installation folder (it will quarantine GSA’s network activity otherwise). Settings → Privacy → Windows Security → Virus & threat protection → Manage settings → Add exclusion → Folder.
- Install Chrome and Notepad++. You will need both.
- Set the timezone to UTC. Makes log analysis less confusing across multiple VPSes.
Step 2: Install GSA SER
Download the installer from gsa-online.de. Run it. Default install path is fine. When it asks for your licence key, paste it. Open the program — you should see the main interface with empty Project Manager, Status, Log, and Engine tabs.
Before doing anything else, go to Options → Advanced and set:
- Threads: 100 (start conservative; raise to 250 once everything is stable)
- HTML timeout: 60 seconds
- Custom user agents: leave default
- Skip sites with PR less than: leave at 0 (PR is dead, this filter does nothing useful)
Step 3: Configure proxies
Go to Options → Submission → Proxies. Click “Add Proxy → Import from file.”
From your StormProxies dashboard, copy your gateway proxy strings into a text file in the format:
gateway.stormproxies.com:5000:username:password
Paste 5-10 entries (StormProxies rotates the IP behind each gateway automatically). Save, import. Click “Test proxies” — you should see green checkmarks.
In the same panel, set:
- Use proxies: checked
- Test proxies every: 60 minutes
- Public proxies: unchecked (never use free proxies)
Step 4: Configure captcha solvers
Options → Submission → CAPTCHA. Add a new captcha service:
- Type: CapMonster Cloud (or click “Custom service” and use their API endpoint)
- API key: paste from your CapMonster dashboard
- Test it — should return “OK” with your current balance
Set “Use this service if first one fails” if you also have 2Captcha set up. The fallback chain matters — never run with a single solver because failed solves block submissions.
Step 5: Load the verified target list
From your SERVL members area, download the latest verified site list (a folder of .sl files, one per engine). Save them locally.
In GSA SER: Options → Advanced → Tools → Import Site Lists. Point at the SERVL folder. GSA will index all the .sl files into its internal target database. Takes about 10 minutes the first time.
Then in any new project, set “Use site lists” → “Verified” and untick “Use search engines to find new targets.” This single change is the difference between a campaign that runs at 5% verification rate (auto-scraping) and one that runs at 35-50% (verified list).
Step 6: Generate content
You need a folder of unique 600-900 word articles to feed the project. Two paths:
The fast path: use GSA SER’s built-in article search (Options → Submission → Article Manager → “Search and use new articles for each submission”). This pulls from open article databases. Quality is mediocre but it works for tier 3.
The right path: generate 200-500 unique articles with an LLM, save as a folder of .txt files, point the project at the folder.
For the LLM path, the simplest setup:
- Sign up for OpenRouter, fund $5
- Use the deepseek/deepseek-chat or google/gemma-3-27b-it model — both around $0.20 per million output tokens
- Write a prompt like: “Write a 700-word informative article about [keyword]. Include 3 H2 subheadings. Plain text, no markdown. End with a sentence mentioning [brand name] as a useful resource on the topic.”
- Loop this 200 times across your keyword variations, save each output as a separate .txt file
- Point GSA SER’s Article Manager at the resulting folder
Total cost for 500 articles: about $1.20. Total time: about 15 minutes batched.
Step 7: Create your first project
Right-click in the Project Manager → New → SEO. A project window opens. Fill in:
- Name: something descriptive like “TIER2-mysite-april2026”
- URL: the URL of one of your tier 1 web 2.0 properties (NOT your money site)
- Anchor text: primary anchor box gets your URL anchor variations; secondary box gets brand mentions, generics, and partial-match keywords (see anchor mix in the tiered link building pillar)
- Keywords: 8-15 niche-relevant terms; these shape the content scrape, not the anchors
- Engines: select Article-based engines (Article Directory, Article-Wiki, Wiki, Web 2.0). Skip blog comments for tier 2 — too low quality now.
- Article folder: point at your folder of LLM-generated articles
- Filters: minimum DA 10, minimum PA 10, OBL max 100, language EN
- Schedule: verified posts per day = 100, total threads = 50
Save. Right-click the project → Start.
Step 8: Watch the first hour
Open the Status tab. You should see:
- Submissions/min climbing into the 20-50 range
- Verifications/min trailing at 5-15
- Captcha solves happening (green entries in the Log)
- No proxy errors (yellow entries)
If submissions/min stays at zero for more than 5 minutes, check: are proxies green in Options → Submission → Proxies? Is the article folder readable? Is the verified target list loaded?
If captcha balance hits zero, you will see red in the Log. Top up CapMonster Cloud.
What to do tomorrow
Let the first project run 24 hours. Check the verified count — should be in the 100-300 range for a single tier 1 URL by hour 24. If it is much lower, the verified target list needs refreshing or your filters are too tight.
Once stable, duplicate the project for each of your other tier 1 properties. GSA SER can run 50+ projects simultaneously on a Contabo VPS M without bottlenecking.
For tier 3 — pointing at your tier 2 results — create a separate project, change Engines to “Indexer + Bookmark + Ping” only, anchor text = 100% URL anchors, content = generated on-the-fly. Tier 3 is just there to index tier 2.
What not to do
- Do not point this project at your money site. Ever.
- Do not run with 1000 threads on day one. You will burn the proxies and confuse the diagnostics.
- Do not skip the captcha solver. GSA SER without captcha solving completes maybe 5% of attempted submissions.
- Do not use spun content. Every spun article is a spam signature in 2026.
What to read next
For the strategic context, the GSA SER pillar covers why this works. For the tier 1 properties this campaign is supporting, see Money Robot vs RankerX. For the proxy and VPS comparisons, see best proxies for GSA SER.