Download your engine pack
It's a single small file called user_se.dat. It contains all five of your feeds — All, Contextual, SERnuke and Authority — each as its own GSA search engine, with your license key already baked in. New here? Start with what the verified target feeds include.
You can re-download it anytime from your members area. Keep it private — it's tied to your account.
Drop user_se.dat into GSA's folder
GSA SER loads custom search engines from one file in its settings folder. Here's exactly where it goes.
- Close GSA SER completely. Right-click its tray icon → Exit if it's minimised. It must be fully closed, or it won't pick up the new engines.
- Open GSA's settings folder:
C:\Users\<YourName>\AppData\Roaming\GSA Search Engine Ranker\AppData is a hidden folder. The quick way in: press Win + R, type%appdata%, press Enter — then open the GSA Search Engine Ranker folder. (Or turn on hidden files: in File Explorer → View → Show → Hidden items.) - Copy
user_se.datinto that folder.Already have auser_se.dat? That means you have your own custom engines. Don't overwrite it — open both files in Notepad and paste our five[GSA Link Surge - …]blocks at the end of your existing file, then save. Overwriting would delete your own engines. - Start GSA SER again. That's the file installed.
Tick your feeds in the project
The engines are installed globally, but each project chooses which to use. In any project's Search Engines tab you'll now see five new entries:
- GSA Link Surge - All — every verified target we process
- GSA Link Surge - Contextual — contextual, in-content placements
- GSA Link Surge - SERnuke — SERnuke-engine targets
- GSA Link Surge - Authority — high-authority, Tier-1-safe
One setting that unlocks your LPM
GSA throttles real search engines (Google, Bing) to avoid bans. Your feed is a private server — there's no ban risk — so remove that throttle or you're just adding dead time between pulls.
Start the project and watch it pull
Start (or resume) your project. GSA immediately begins pulling verified targets from your feed and submitting through your normal setup.
Always fresh
Every run pulls current targets. Dead and spammy ones are pruned on our side, so you never post to them.
Low OBL, no junk
OBL<50 on the four category feeds; Authority / Tier 1 Safe adds Majestic & Moz screening. No indexers, trackbacks, exploits or 301 filler.
Tied to you
Your key validates on every request. Cancel or re-issue and the feed stops instantly — nothing reusable ever leaves.
Which feed for which campaign
You can tick more than one. A common setup: Authority/Contextual on money-site tiers, All on lower tiers.
| Feed | Best for |
|---|---|
| All | Maximum volume — lower tiers, link-juice tiers, and churn-and-burn. Mixes every platform we verify. |
| Contextual | Contextual in-content links (articles, wikis, social) — great for tier 1 & 2 to a money site. |
| SERnuke | Targets from SERnuke engines — power tiers and blasting lower layers. |
| Authority | High-authority, Tier-1-safe targets — the most conservative feed for pointing directly at money sites. |
How the feeds work as custom search engines
GSA SER has a built-in mechanism for adding custom search engines — its own user_se.dat file, where each entry teaches the software to query a source and parse target URLs out of the response. That mechanism is exactly how GSA Link Surge connects: the file you installed above defines five custom search engines, one per feed, each pointing at your private feed URL with your key already embedded.
That is why there is nothing else to install and nothing to re-import. When a project runs, GSA SER “searches” your feeds the way it would search any engine — except every result is a verified target from the current pool. Fresh targets appear in the same run-loop the software already uses; dead targets simply stop appearing. If you ever add your own custom engines later, they live in the same file — just append them below the five [GSA Link Surge - …] blocks.
Prefer to add a feed manually?
You don't need to if you used the pack above. But if you'd rather add a single feed by hand, grab its link from your members area, then in GSA SER go to Options → Search Engines → Add and enter these values:
| Field | Value |
|---|---|
| Name | GSA Link Surge - All (or Contextual / SERnuke / Authority) |
| URL | paste that feed's link from your members area |
| Country | INTERNATIONAL |
| Start page/index | 0 |
| Increase page/index | 0 |
| Expected links per page | 100 |
| Ignore / Only mask, inurl, intitle, link, Modify html | leave empty |
| Skip Proxy | your choice (ticked = faster pulls) |
Use a search engine, not "import"
GSA's one-time "Import Target URLs → from website" grabs a single batch and stops. Adding the feed as a search engine makes GSA keep pulling fresh targets every run — that's the whole point of a live feed.
If something looks off
The engines don't show up in GSA
GSA was probably still running when you added the file. Fully close it (tray → Exit) and reopen. Double-check the file is named exactly user_se.dat and sits directly in %appdata%\GSA Search Engine Ranker\, not in a sub-folder.
GSA shows lots of "no engine matches"
Normal. The All feed mixes every platform, and GSA only submits to ones it recognises and that you've enabled in the project. Enable more engines, or use the Contextual / Authority feeds for tighter targeting.
GSA pulls nothing / "invalid or expired key"
Make sure your plan is active and you're using the current pack. If you re-issued your key, download user_se.dat again from your members area — the old key stops working the moment you re-issue.
GSA says "filter … matches content"
That's GSA's own blocked-words filter in your project settings rejecting a page's content — not the feed. Adjust the filter list in your project if you want those targets.
"download failed" / 403 / 503 with a PROXY note
That's your proxies failing to load a target page (or the target being down) — unrelated to the feed. Check your proxy list and thread count.
It feels slow
Almost always the search-engine wait (Step 4). Uncheck "Custom time to wait between search queries", and tick Skip Proxy on the engines.