Elke GSA SER-gebruiker deelt dezelfde profielen en opmerkingen — dat hebben we nu opgelost.

If you run GSA Search Engine Ranker, you have spent hours on the things that feel like they matter. Verified lists. Proxies. Thread counts. Article quality. Anchor ratios.

Almost nobody looks at two fields sitting in the project options: About Yourself en Blogreactie. They come pre-filled, they look busy and heavily spun, and they work. So they get left alone.

Those two fields are also the most duplicated text in the entire GSA SER ecosystem. The same names, the same towns, the same comments, posted by thousands of different people to millions of different sites, for well over a decade. This is what is actually in them, why that is a problem, and what we changed today.

💡 Kortom

The default About Yourself and Blog Comment text is shared by nearly every GSA SER user alive — which makes it the one footprint no verified list can fix for you.

From today, every project built through GSA SER Builder generates its own profile and comment text, written for that site’s audience, in that project’s language.

• The stock About Yourself field draws from the same fixed pools — around 100 first names, 100 surnames, and 100 town names — in every project it has ever been pasted into.
• The stock Blog Comment field is a harvested spam corpus. Comment filters have had those exact sentences on file since around 2011.
• Both are English only, so a Turkish, Thai, or Japanese campaign has been introducing itself in English on sites where nobody writes English.
• The stock comment block also drops jouw money keyword onto unrelated blogs, because it uses the wrong GSA macro.
• Every GSA SER Builder project now ships 50 unique profiles and 100 unique comment templates, in the project language, built from the site’s own audience.

🔧 What these two fields actually do

Both feed the account-creation and posting side of GSA SER, not the article side. That is exactly why they escape review: you never read them in your delivered content, but every target site does.

Both accept spin syntax, and GSA SER picks a fresh variant for every account and every post. That is the part people rely on — and it is also what hides the problem. Heavy spinning inside a block that everybody shares produces enormous variation inside your campaign, and none at all between you and the next user.

🎯 The footprint, in plain terms

A footprint is any pattern that ties your links to each other, or ties them to somebody else’s. Most GSA SER discussion covers the first kind. This is the second kind, and it is much larger.

1. The same person, on thousands of unrelated sites

Waarom het belangrijk is: the default profile text is built from fixed lists — roughly 100 first names, 100 surnames, 100 town names, plus lists of films, hobbies and cars. Spun together, they produce millions of combinations, which sounds ideal. But the ingredients never change. Every project using the default is drawing from the same jar.

What to check: open your project options, look at About Yourself, and search the text for a town name. If you find a list of Canadian towns that has nothing to do with your business, you are on the community default.

What a bad sign looks like: your profiles describe a 34-year-old Nuclear Power Engineer from Baie-Comeau who enjoys obscure films and drives a Bugatti Royale. Charming — and also sitting on tens of thousands of profiles built by other people.

2. Comment text the filters already know

Waarom het belangrijk is: the default comment block is not written copy. It is a scraped set of real spam comments, and it shows. Lines like “I have been surfing online more than 3 hours today”, “I will right away take hold of your RSS feed”, and the one comparing BlogEngine, WordPress, B2evolution and Drupal have been circulating since around 2011.

What to check: take any sentence out of your Blog Comment field and search it in quotes on Google. If it returns thousands of results, every comment filter has seen it too.

What a bad sign looks like: comments that get accepted, then quietly disappear a week later. That is not bad luck. That is a filter recognising the text.

3. The wrong language on the wrong site

Waarom het belangrijk is: the defaults are English. If your project is Turkish, Thai, Indonesian, or Japanese — and your verified list is filtered to that language — your accounts have been writing English to an audience that does not.

What to check: compare your project language against the language of both fields. For most users, they will not match.

What a bad sign looks like: a Turkish blog, a Turkish article, and an English “Great post, thanks for sharing!” underneath it. A human moderator needs one second to make that call.

4. Your own keyword, posted on other people’s blogs

Waarom het belangrijk is: this one is a plain mistake in the default block. GSA SER has two families of comment macros, and they point in opposite directions:

The default block contains the line “Yes! Finally something about %keyword1%.” On a page about garden furniture, that comment tells the moderator exactly what you are doing. Every other line in the block is generic, which is what makes this one stand out.

What to check: search your Blog Comment field for %keyword. If it is there, take it out.

That last column is the whole point. You cannot buy your way out of this with a better verified list, more proxies or a faster VPS. The text itself has to change.

⚙️ What we changed

Every project built through Asia Virtual Solutions “GSA Search Engine Ranker-projecten – Klaar voor jou” or GSA SER Builder now generates both fields for itself.

Profiles. While we analyse your site, we already work out who its audience is. That audience description now also produces 50 short profile bios — different ages, occupations, regions, interests and sentence shapes — written in your project language with names and places that belong to that language. A Turkish project gets Turkish names and Turkish cities. A Spanish project gets neither.

Comments. Each project also gets 100 comment templates in the project language, built with spin syntax so they expand into thousands of distinct comments. Roughly one in four refers to the page being commented on using %blog_title% of %meta_keyword%, which is what a real reader would do. None contain %keyword%.

🚩 Red flags in your current setup

Worth checking on any project you are running right now, whoever built it:

• About Yourself mentions towns, films, or cars with no connection to your business or your market.
• A sentence from your Blog Comment field returns thousands of exact-match Google results.
• Your project language is not English, but both fields are.
• %keyword% of %keyword1% appears anywhere in your comment text.
• Comments get accepted and then vanish within days.
• Both fields are identical across every project you own — and across every project you have ever bought.

💡 How to check and fix your own projects

You do not need us for this. If you run your own setup, it is worth an hour of your time:

• Open a project in GSA SER, go to the Data tab, and read both fields end to end. Most people never have.
• Copy three sentences out of the comment field and search each one in quotes. That tells you how public your text is.
• Delete every %keyword% en %keyword1% from the comment field. Replace them with %blog_title% of %meta_keyword%, which describe the page you are posting on instead of your own site.
• If your campaign is not in English, rewrite both fields in the campaign language. Twenty real comments in the right language beat two hundred in the wrong one.
• Write your profile bios around plausible people from your market, not from a name generator. Keep them short and ordinary.
• Keep the spin syntax. It is doing useful work — it just needs source text that is yours.

🔧 Or let the project arrive that way

We have been building done-for-you GSA SER projects since December 2012, and have delivered nearly 5,000 of them. GSA SER Builder is the automated version of that service: enter your URL, keywords, language, and campaign details, and receive a complete ready-to-import .ser file with unique articles, email accounts, images, and anchor groups — and now unique profiles and comments as well.

Projects start at $9.95 for a single tier and are delivered within 24 hours.

❓ Veelgestelde vragen

Does this replace my verified list or my proxies?

No — those solve different problems. A verified list decides where you can post. Proxies decide how many accounts you can create. This decides whether the text on those accounts looks like yours or like everybody’s. You need all three, and this is the one nobody was buying.

Is spin syntax still used?

Yes, heavily — GSA SER’s own help for the comment field recommends it. What changed is the source text, not the mechanism. Each of the 100 comment templates carries several spin groups, so the pool expands into thousands of variations before it repeats.

What if I upload my own custom template?

Your template still controls every setting in it — engines, filters, schedules, language restrictions. Only these two content fields are replaced with text written for your project. Everything you deliberately configured ships exactly as you uploaded it.

Welke talen worden ondersteund?

All 22 project languages we offer, including Turkish, Thai, Japanese, Korean, Chinese, Russian, Indonesian, Vietnamese, Arabic, Hindi, Bengali and Slovenian. If a project’s text cannot be generated for any reason, it falls back to a prepared set in the same language rather than to English.

Will my older projects be updated?

New projects get this automatically. Projects already delivered keep the text they shipped with. If you want an older campaign rebuilt with unique profiles and comments, contact us and we will look at it.

Can I still edit the fields myself after import?

Yes. It is a normal .ser file, so everything stays editable in GSA SER exactly as always. If you want to add your own comments to the pool, nothing stops you.

📚 Gerelateerde artikelen

• GSA SER Builder — what changed in the first month
• Done-for-you GSA SER projects, explained
• Our GSA SER project service