Skip to content

Most “Where to Submit” engines seem inactive today

Hello everyone,

Sorry if some of this might not be 100% accurate — I’m not an expert. I just tried to collect information here and there on the web because I was struggling to understand why some of the “Where to Submit” engines in GSA SER were not producing any links anymore.
I hope it’s okay to share what I noticed, and maybe it can help others too.

From what I understand, many of the old engines (especially forum scripts and CMS platforms) simply don’t work in 2025. They either don’t exist anymore, or the websites using them have switched to modern protections like Cloudflare, JavaScript checks or login systems that GSA SER can’t bypass.

For example, engines like phpBB, SMF, vBulletin, XenForo, IPBoard, Joomla Blog, Drupal Blog, Wordpress Article, BuddyPress, and many article directory scripts — they just don’t allow automated posting anymore. Most of them require JS, or captcha steps that SER can’t handle, or have closed registrations completely.

The same seems to happen with many old directory scripts, gallery scripts, video CMS, social network clones, Q&A scripts, guestbooks, classified ads scripts, and so on. They used to work years ago, but today almost all installations have either been abandoned, shut down, or protected behind systems that block bots.

Because of this, even if the engines are still listed inside SER, in real life almost none of them generate backlinks anymore. I’m not saying this to criticize — just trying to understand why my projects weren’t producing anything, even with good proxies, good emails and the correct setup.

Personally, I think SER still has a lot of potential, but maybe the submission engines need to be updated with newer platforms that still allow automated posting today.
Only a few engines still work consistently (things like MediaWiki, DokuWiki, TikiWiki, simple blog comments, public bookmarks, rentry.co, etc.). Everything else looks “alive” in the interface, but in practice doesn’t produce results.

So this is just my humble opinion, as a normal user:
maybe it’s time to add new engines to match the modern web, because most old engines simply don’t work anymore.

Again, sorry if something I wrote is not perfectly correct — I’m still learning.
Thank you for reading.

Tagged:

Comments

  • edited November 26
    here the tendency is towards a change in approach rather than towards improving the quality of solving. What will Sven say about this?
  • KonstantinKonstantin Ukraine
    edited November 27
    I have to say this thread reflects the exact reality of 2024–2025, and it’s not just a temporary slowdown or a proxy issue — it’s a structural problem across almost all legacy platforms SER was originally built around.
    Most “Where to Submit” engines are not just performing poorly…
    They are objectively dead in the modern web:
     - phpBB / SMF / MyBB / vBulletin / PunBB → registrations closed, captchas upgraded, anti-bot layers everywhere
     - Drupal / Joomla / older CMS engines → forms now require JS, dynamic tokens, invisible captchas
     - Guestbooks, directories, article platforms → either wiped out, turned into private sites, or filled with anti-spam walls
     - Many domains from old engines are simply abandoned, expired, or redirect to generic hosts
    The result is simple:
    The engine list looks huge — but the number of actually alive and postable engines in 2025 is extremely small.
    SER still reports “submitted” counts, but the verified output shows the real picture:
    a tiny number of engines produce almost everything that still works today.
    In practice, only a few categories remain somewhat reliable:
    - some MediaWiki instances
    - a small fraction of open blog comment systems
    - a handful of public paste/notes platforms
    - very rare CMS installations without JS challenges
    Everything else is practically non-functional from an automated posting perspective.
    This is not a complaint — it’s simply the current web environment.
    Anti-automation systems, Cloudflare, tokenized forms, login barriers, and real-time JS checks have eliminated almost all of the “classic” automated posting targets.
    ---
    And here is the important part:
    SER remains an extremely powerful tool — but the engine list no longer reflects real-world survivability.
    Right now the UI suggests hundreds of engines.
    In reality, maybe 5–10% are capable of producing links in 2025.
    From a product perspective, this means:
    - many engines need a fresh audit
    - some should probably be retired
    - others need modernized scripts or new approaches
    - the ecosystem SER was built on has changed dramatically
    I’m not criticizing the software — it has served the community for over a decade —
    but it might be time to rethink the engine layer and bring it in line with today’s web.
    If that happens, SER could stay relevant for many more years.
  • KonstantinKonstantin Ukraine
    edited November 27
    One more point worth mentioning — and I think many long-term SER users will agree:
    It might be extremely valuable to run a modern-day “engine audit” and identify which engines still produce verifiable results in 2025.
    Not to remove anything right away, but simply to get a realistic picture of what’s alive and what’s not. The market has changed drastically, and this information alone would already improve the efficiency of SER campaigns.
    With such transparency, users could focus on engines that actually work instead of spending resources on legacy platforms that no longer exist in practice.
    Just an idea — but I believe it could make SER significantly stronger going forward.
    Thanked by 1Hunar
  • edited November 26
    actual
  • I just want to clarify something because it looks like my post may have been misunderstood, and I really didn’t want to create any controversy.

    I did not mean to criticize GSA SER at all. SER is a solid piece of software, and I fully respect the work behind it. What I described is not a problem caused by SER — it’s simply how the modern web has changed over the years. Many auto-postable platforms that existed 10–15 years ago are now protected, offline, or no longer allow automated submissions.
    This affects every backlink software, not only SER.

    I only wrote my message because I’m a user of SER and I like the software, so naturally I’m hoping to see it grow and adapt. My intention was not to complain, but to share what I noticed and maybe help improve things if possible.

    If my wording sounded wrong or too direct, that wasn’t intentional.
    I’m just a normal user trying to understand what still works today and what could be updated.

    Thanks for your understanding.

  • Thanks for clarifying — and I fully agree with you.

    None of this was meant as criticism toward SER or its development.
    Like you said, this is simply how the modern web evolved, and every tool in this space is facing the same reality.

    The reason this discussion is valuable is because SER still has great potential, especially for the types of engines that remain functional today.
    Understanding which platforms still work — and which ones no longer do — could help all of us use SER more efficiently.

    No controversy here at all — just users trying to understand the current landscape and share feedback that might help improve the experience for everyone.
  • I fully agree with @verdemuschio and @Konstantin.

    The reality is that the web has changed, and the software needs to adapt to 2025 defenses (Cloudflare, JS checks, etc.). Currently, we are burning through good proxies and emails trying to post to scripts that effectively no longer exist.

    A "Spring Cleaning" of the engine list or a dedicated update for modern platforms would make SER significantly more efficient. Quality over quantity is the only way forward now. Hopefully, the dev team can take this feedback on board!



  • It's time to completely revise the GSA Ser and make a global upgrade
  • SvenSven www.GSA-Online.de
    Well coding engines takes some time. Especially if someone only gives me a bunch of urls and thats it. Often they are not even from the same platform.
    Im OK to add new engines if they
    1. Consists of not just a few URLs in the wild
    2. I got some work done just like footprints, an account to test things, maybe instructions what to click to get a link...

    I agree that many engines are no longer working as there are hardly any sites that use them, but I also can not test this without a bit of help from you guys.

  • Hi @Sven,

    I remember the list of search engines I provided caused some problems for some people, so I'm stepping aside. But if anyone can provide Sven with a good list, come on guys. Sven tells us he's available, let's help him with the URLs.
  • Of course, we are ready to help and will do it with pleasure.
    Thanked by 1verdemuschio
  • KonstantinKonstantin Ukraine
    edited November 29

    Thanks everyone for the discussion — it really helped clarify what’s going on today with SER.
    I’ll add my perspective from a technical point of view, without any pressure — just ideas that might be useful.

    From my own tests, the problem is not SER as software.
    The problem is that the web has fundamentally changed:

    • many classic CMS engines from 2010–2016 don’t exist anymore

    • a lot of registration forms have been removed or locked

    • Cloudflare / JS challenges became default on many platforms

    • anti-bot fields and dynamic tokens became standard

    • some engines still work, but success rates are naturally much lower

    No tool can post where a form no longer exists — that’s simply how the modern web evolved.

    So instead of asking for major changes, here are practical and realistic suggestions that could help SER stay effective without rewriting the software.


    1) A small, community-driven “engine status review”

    Not to overload Sven — the opposite.
    Users can collect:

    • example URLs

    • footprints

    • form behavior

    • tokens

    • hidden fields

    • notes about anti-bot elements

    Sven would only need to review and integrate what is already prepared.

    This makes the process manageable.


    2) Label engines, instead of removing them

    Just something simple like:

    • Working (2025)

    • Low success

    • Likely inactive

    This helps users avoid wasting proxies and emails.
    Even this tiny change would have a big impact.


    3) Small improvements for modern anti-bot logic

    Nothing big — not JS rendering.
    But things like:

    • keeping session cookies

    • retrying with the same session

    • passing basic timestamp hidden fields

    • reading simple dynamic tokens

    Even these minimal additions would noticeably increase success rates on some platforms.


    4) Allow community-contributed engines

    Maybe once per month:

    • one or two user-created engines

    • Sven reviews them

    • adds them if they meet quality standards

    This keeps SER evolving without increasing Sven’s workload.


    5) Simple engine diagnostics

    Something like:

    Form not found  
    Registration disabled  
    Unexpected challenge  
    Engine likely inactive on this target
    

    This would help users understand what is happening, without guessing.


    Final thoughts

    SER still has strong potential in 2025 —
    but the engine list simply needs a bit of cleanup and modernization,
    and the community is ready to help with the data collection part.

    No pressure, no demands —
    just ideas that many users might find useful moving forward.

    Thanks again for keeping SER alive and for being open to this conversation.

    Thanked by 1Hunar
  • Thanks everyone for the discussion — it really helped clarify what’s going on today with SER.
    I’ll add my perspective from a technical point of view, without any pressure — just ideas that might be useful.

    From my own tests, the problem is not SER as software.
    The problem is that the web has fundamentally changed

    In fact, an initial premise was made about this precisely to avoid sparking controversy over SER. The software was never blamed, and in my opinion, with the right settings, it works more than well. The problem was attributed to the Web, which has completely changed, and to the difficulty of finding good proxies. The discussion was open on this.
  • verdemuschioverdemuschio Italy
    edited November 30
    I'd like to point out that, despite my efforts, I haven't received any backlinks for weeks. I've started a new project, but I'm not getting any results. For search engines I'm using international ones. The engines "Where to submit" I've currently set up based on the tiers I believe work best are as follows:

    Tier 1 (Main project):
    Press Release Script
    Rentry.co
    Wordpress XMLRPC
    DokuWiki
    MediaWiki
    TikiWiki

    Tier 2 (tier):
    Press Release Script
    Rentry.co
    Wordpress XMLRPC
    General Blogs
    BlogEngine
    Bravenet Comment
    PHP Fusion Comment
    Directory97 PRO
    IndexScript
    NL Directory
    Freeglobes
    php Link Directory
    PHP Weby
    Wordpress Directory
    Easy Guestbook
    Guestbook
    OpenBook Guestbook
    Web Wiz Guestbook
    Piwigo
    Pixelpost
    ZenPhoto
    Pligg
    Plikli
    Drigg
    PHPDug
    Public Bookmark
    Scuttle
    Trackback
    Trackback-Format2
    DokuWiki
    MediaWiki
    TikiWiki

    Tier 3 (tier tier) and Tier 4 (tier tier tier):
    Press Release Script
    Rentry.co
    General Blogs
    Bravenet Comment
    PHP Fusion Comment
    Directory97 PRO
    IndexScript
    NL Directory
    Freeglobes
    php Link Directory
    PHP Weby
    Wordpress Directory
    Easy Guestbook
    Guestbook
    OpenBook Guestbook
    Web Wiz Guestbook
    Piwigo
    Pixelpost
    ZenPhoto
    Pingback
    Pligg
    Plikli
    Drigg
    PHPDug
    Public Bookmark
    Scuttle
    Trackback
    Trackback-Format2
    0.gp
    0a.sk
    0cn.de
    0rz.tw
    0x6f776f2e7663.net
    101.gs
    135.it
    1aas.com
    1ab.in
    1o2.ir
    1s.pt
    1url.cz
    2.gp
    2.ly
    222.at
    2cm.es
    2tu.us
    3.ly
    301.link
    3le.ru
    4.gp
    4.ly
    42.pl
    5du.pl
    6.gp
    6.ly
    6b.cz
    7.ly
    7ee.ir
    8.ly
    8em.pl
    9.ly
    92url.com
    9en.us
    afit.edu
    AllEasySEO.com
    alturl.com
    anasayfa.info
    atikon.at
    ay.gy
    barhosting.com
    bea.sh
    beanybux.me
    beget.tech
    bin.wf
    bit.ly
    bool.icu
    bpl.kr
    BrokenScript
    btty.in
    byte.my
    cfg.me
    chilp.it
    cia.sh
    cisn.xyz
    cleanuri.com
    clickstat.xyz
    CodeCanopy URL Shortener
    come.ac
    cortas.as
    cuts.top
    cutt.us
    d--b.info
    da.gd
    dropmylinks.com
    dssurl.com
    dstats.net
    due.im
    e49.us
    e7.al
    easyurl.cc
    el32.com
    elpais.com
    ennt.net
    etinyurl.com
    fadurl.com
    filoops.info
    firsturl.de
    fly2.cf
    Free URL shortener
    g.asia
    g9.yt
    General URL Shortener
    GET API URL Shortener
    gg.gg
    gmy.su
    go.ht.gs
    goto.now
    gourl.gr
    hasurl.com
    herotel.com
    hideuri.com
    hirz.ir
    holyballs.com
    hts.io
    ic9.in
    icks.ro
    icux.xyz
    in.mt
    ina.am
    inbox.lv
    inshort.link
    inx.inbox.lt
    is.gd
    ito.mx
    ity.im
    ivyti.es
    ix.sk
    j9.click
    jiotools.com
    jplopsoft
    kmk.party
    krati.co
    ku.ag
    kub.sh
    kuc.cz
    kurzelinks.de
    kurzurl.net
    l8.nu
    lc.cx
    lil.so
    lilURL
    link-cut.com
    linkbun.ch
    linkcuts.org
    linky.nu
    ln4.ru
    lnk.bz
    lnkm.ee
    lnkz.at
    lopurl.com
    lyhyt.eu
    lynx.re
    m17.ca
    make-t.in
    merky.de
    merq.org
    miffy.me
    minik.link
    minilink.pro
    minilinks.dev
    miniplease.com
    miniurl.top
    mub.me
    muz.so
    myminiurl.net
    nah.uy
    nene.cz
    nowlinks.net
    nutshellurl.com
    ogy.de
    ohi.im
    opnlink.com
    ouo.io
    ourl.in
    owo.gay
    owo.vc
    p.asia
    pastein.ru
    peekurl.com
    Phishyurl (adult)
    Phishyurl (crypto)
    Phishyurl (dating)
    Phishyurl (financial)
    Phishyurl (gambling)
    Phishyurl (phishing)
    Phishyurl (shopping)
    Phishyurl (tech)
    PHPurl
    Phurl
    plu.sh
    Polr
    Premium URL Shortener
    psee.io
    ptiturl.com
    pxl.fm
    qi.lv
    qr.net
    qrurl.cc
    reducelnk.com
    rlu.ru
    s.coop
    S6L ShortURL
    sdu.sk
    seomafia.net
    shorl.com
    short-link.me
    short-url.uk
    shorter.me
    shortlink.uk
    shorturl.at
    shorturl.la
    shorturl.ma
    shorturl.re
    shorturl.ru
    shr.name
    shrink.im
    shrt.in
    shrturi.com
    shrunken.com
    sim.link
    singkat.link
    sini.la
    skrat.it
    skrun.ch
    smi.link
    smlr.org
    snipurl.com
    soo.gd
    surl.me
    surl.site
    t1p.de
    tals.top
    tau.lu
    teil.cc
    thinfi.com
    thrixxx.me
    tighturl.com
    tinie.link
    tinilink.com
    tinlie.com
    tiny.cc
    tiny.ee
    tiny.pl
    tinylink.in
    tinylink.info
    tinylink.onl
    tinyplease.com
    tinyurl.com
    tinyurl.nu
    tinyurlshortener.com
    to.ly
    tu15.com
    tw.gs
    u.to
    ubyt.es
    ukaz.to
    umeedwar.com
    ur.link
    uri.im
    URL Redirect
    url.hys.cz
    url.ie
    url2a.site
    url3.ru
    urlc.net
    urlcrop.com
    urlgo.in
    urli.info
    urls.day
    urlshortener.biz
    urly.it
    ux.nu
    ux9.de
    v.gd
    viewsiterank.com
    visitmy.link
    vurl.com
    w2.am
    wall.sh
    wc.tv.br
    wck.me
    wdurl.ru
    webthemez.com
    wee.so
    xzx.kr
    ykm.de
    ylink.bid
    YOURLS
    yourstudent.com
    yy7.com
    zap.buzz
    znouze.eu
    zzb.bz
    DokuWiki
    MediaWiki
    TikiWiki
Sign In or Register to comment.