SETUP GUIDE · ABOUT 3 MINUTES

Connect your feeds to GSA SER

Install one file, select the feeds your project needs, and run. GSA SER pulls verified targets through your private SurgeFeed access. The four category feeds are filtered to OBL < 50 at verification; the 30-Day Surge Pool is the deliberate unfiltered exception.

Log in to grab your engine pack

Your personal user_se.dat — with your license key baked in — is in your members area. Log in with an active plan to download it.

Before you start

What you'll need

✓An active GSA Link Surge plan. Your feed only works while your subscription is active — the key validates on every pull.

✓GSA Search Engine Ranker installed on your PC or VPS.

✓Your usual GSA setup — proxies and a captcha service (e.g. your solver of choice). Nothing changes there; our feed only supplies the targets.

Step 1 · Get your pack

Download your engine pack

It's a single small file called user_se.dat. It contains all five of your feeds — All, Contextual, SERnuke, Authority and Pool — 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.

Step 2 · Install it

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.dat into that folder.
Already have a user_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.

Windows Run dialog with %appdata% typed in

The GSA Search Engine Ranker folder in AppData with user_se.dat placed inside

Step 3 · Select your feeds

Tick your feeds in the project

The engines are installed globally, but each project chooses which to use. Open your project's Options tab and find Search Engines to use under How to get Target URLs. You'll now see five new entries:

GSA Link Surge - All — broad verified coverage, filtered to OBL < 50
GSA Link Surge - Contextual — in-content placement targets, filtered to OBL < 50
GSA Link Surge - SERnuke — SERnuke-engine targets, filtered to OBL < 50
GSA Link Surge - Authority — OBL < 50 with additional Majestic and Moz screening
GSA Link Surge - Pool — the 30-Day Surge Pool: verified, deliberately not OBL-filtered, for Tier 2 and below

Untick every other search engine (Google, Bing, etc.) and tick only the GSA Link Surge feed(s) you want for that project. This limits search-engine queries to your selected feeds. Other target sources enabled in your project can still supply URLs.

A real GSA SER project Search Engines tab with the five GSA Link Surge engines ticked: All, Authority, Contextual, Pool and SERnuke

Step 4 · Max throughput

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.

Turn the search-engine wait off. GSA SER → Options → Submission → uncheck "Custom time to wait between search queries". A 30–60s wait here is the #1 reason a feed feels "slow" — it's idle time between every pull, not the feed.

Tick "Skip Proxy" on the engines. That makes GSA fetch your feed directly (faster, no proxy failures on the pull itself). Your proxies are still used for the actual submissions — exactly as they should be.

GSA SER Options Submission tab with the search-query wait-time setting highlighted

Step 5 · Run it

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.

♻

Continuously re-verified

Targets are re-checked and failed targets are pruned. A target's status can change between checks; verification is not a guarantee of a successful placement.

🎯

Clear feed filters

OBL < 50 applies to the four category feeds at verification. Only Authority / Tier 1 Safe adds Majestic & Moz screening. The 30-Day Surge Pool is not OBL-filtered.

🔒

Tied to you

Your account key is validated on every feed request. Access requires an active plan. You can rotate the key from your account; update your engine pack afterward.

Choosing feeds

Which feed for which campaign

Select feeds to match your campaign. Newer operators should build Tier 1 manually and start GSA Link Surge on Tier 2 and supporting tiers. Experienced operators can evaluate Authority / Tier 1 Safe with their own content, anchor and risk controls; the name describes selectivity, not guaranteed safety.

Feed	Best for
All Verified Links	Broad verified coverage across supported platforms, filtered to OBL < 50. A starting point for supporting-tier campaigns.
Contextual	In-content placement targets, filtered to OBL < 50. Choose when the placement type fits your campaign; no do-follow-only guarantee.
SERnuke Engines	Verified targets organised for the SERnuke engine set, filtered to OBL < 50.
Authority / Tier 1 Safe	OBL < 50 plus Majestic and Moz screening. This additional screening applies only to Authority and does not guarantee placement quality, indexing or rankings.
30-Day Surge Pool	The complete verified pool, deliberately not OBL-filtered, reset every 30 days. Intended for Tier 2 and below.

The 30-Day Surge Pool is a superset: it includes targets that also appear in the four category feeds. Do not add all five feed counts together. For OBL-filtered targeting, choose the category feeds and leave Pool unticked.

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.

Optional · Add a feed by hand

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:

GSA SER Edit Search Engine window filled in for a GSA Link Surge feed: name, URL with the key hidden, INTERNATIONAL, expected links 100, Skip Proxy

Field	Value
Name	`GSA Link Surge - All` (or Contextual / SERnuke / Authority / Pool)
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)

Then open your project's Search Engines list, untick the defaults, tick your new engine, and run.

Good to know

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.

Troubleshooting

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.

Back to your members area → Still stuck? Contact us

⚡ Start Surging — Low-OBL verified links from $47/mo