Help me setting up my chern and burn spam set up please.

Bambarbiakirgudu

Regular Member
Joined
Nov 9, 2016
Messages
370
Reaction score
65
Hello guys.

i miss the ole fucking days that we spam the shit out of tons of content and blast bunch of links. I know things are evolved, changed a lot. but, what tools would You advice for chern and burn projects? argo for conten, rankerx, scrapebox to blast links vs. i can code a small peace of software to generate lots of pages as well. i m highly open to Your advices.
 
Hello guys.

i miss the ole fucking days that we spam the shit out of tons of content and blast bunch of links. I know things are evolved, changed a lot. but, what tools would You advice for chern and burn projects? argo for conten, rankerx, scrapebox to blast links vs. i can code a small peace of software to generate lots of pages as well. i m highly open to Your advices.
Ngl, the days off churn and burn seems to be done. There most you can do now is find low comp keywords and spam AI articles for those keywords.
 
Hello guys.

i miss the ole fucking days that we spam the shit out of tons of content and blast bunch of links. I know things are evolved, changed a lot. but, what tools would You advice for chern and burn projects? argo for conten, rankerx, scrapebox to blast links vs. i can code a small peace of software to generate lots of pages as well. i m highly open to Your advices.
Well, I guess, there is not really existing software and a small piece of software might not be enough anymore. This game builds on scale - and you will need a very robust system to carry the traffic (search engine bots tend to ddos you) and it has to handle everything mostly on autopilot, cause we might talk about some thousend domains, where each domain just makes 1-5 bucks of profit. Wich is a lot, if we talk about costs of 1 buck per domain. It's a mass game and needs a system able to handle mass in every aspect.
My Setup for example is a 32core server + MongoDB + FastAPI and ~5k lines of code for the endpoints...

The spam game got very techy these days ;)
 
Well, I guess, there is not really existing software and a small piece of software might not be enough anymore. This game builds on scale - and you will need a very robust system to carry the traffic (search engine bots tend to ddos you) and it has to handle everything mostly on autopilot, cause we might talk about some thousend domains, where each domain just makes 1-5 bucks of profit. Wich is a lot, if we talk about costs of 1 buck per domain. It's a mass game and needs a system able to handle mass in every aspect.
My Setup for example is a 32core server + MongoDB + FastAPI and ~5k lines of code for the endpoints...

The spam game got very techy these days ;)


i agree. but, if get the modern spam basics, can improve something probabely. Would You mind sharing what You do exactly? You may not want to share but, since not everyone has skills to do it or You may like to pm the least. Most likely i m not in Your marketting area though. so i don'T bite a slice from Your pie. :)
 
i agree. but, if get the modern spam basics, can improve something probabely. Would You mind sharing what You do exactly? You may not want to share but, since not everyone has skills to do it or You may like to pm the least. Most likely i m not in Your marketting area though. so i don'T bite a slice from Your pie. :)
Very classic Amazon Spam. Some thousend domains, some million keywords with one page for each keyword. So everything needs to be automated - domain registry&management, Cloudflare setup, setting up the content (I use AI generated spintax paragraphes, every page has a random sample of 5000 spintaxes). And I mostly aim for bing.
New domains make some bucks - about 1-3€ in the middle as profit (I have a good deal with my registrar, only paying 1€ for register) and keep up earning about 1€ per month, while they cost 0,2€.
As said, it still works, but in large scales. And it got more difficult. ~2 years ago I had 30k domains in my portfolio and might have been in the top ten of de domain owners xD
This does not work that good anymore, though. I had to get a bit picky with my domains ;)

I guess, the most effective modern trend is subdomain spam. Since the search engines do regard subdomains as an own entity, the whole domain will not burn. Wich makes investment cheaper. They are not that strong - but what keeps you from releasing basicly unlimitied subdomains? And as it's an own entity, the subdomain will most likly get indexed with it's home page. While from 5mio subpages perhaps 20k would have gotten to index, subdomains will go to 400k. They will not rank on the same level, but the mass does still bring users and therefore clicks.
 
  • Like
Reactions: GTC
Very classic Amazon Spam. Some thousend domains, some million keywords with one page for each keyword. So everything needs to be automated - domain registry&management, Cloudflare setup, setting up the content (I use AI generated spintax paragraphes, every page has a random sample of 5000 spintaxes). And I mostly aim for bing.
New domains make some bucks - about 1-3€ in the middle as profit (I have a good deal with my registrar, only paying 1€ for register) and keep up earning about 1€ per month, while they cost 0,2€.
As said, it still works, but in large scales. And it got more difficult. ~2 years ago I had 30k domains in my portfolio and might have been in the top ten of de domain owners xD
This does not work that good anymore, though. I had to get a bit picky with my domains ;)

I guess, the most effective modern trend is subdomain spam. Since the search engines do regard subdomains as an own entity, the whole domain will not burn. Wich makes investment cheaper. They are not that strong - but what keeps you from releasing basicly unlimitied subdomains? And as it's an own entity, the subdomain will most likly get indexed with it's home page. While from 5mio subpages perhaps 20k would have gotten to index, subdomains will go to 400k. They will not rank on the same level, but the mass does still bring users and therefore clicks.



Well old school spam also contained mass sub spamming. What about using articles on static html pages? or actually i was thinkin to mass install wp pages too. but, it will burn too mutch resources i guess. On the other hand how do You get this mutch pages indexed? and what back link tool do You use?
 
What about using articles on static html pages?
Tried this, it's a nice sollution for traffic handling, since it's way more performant. I still had to switch, cause I'm relaunching my domains every 2-4 days. Generating static pages eats up a lot of performance - and disk space. That's why I switched to spintaxes, based on a seed wich is the whole url and I only need to create basicly the sitemaps (and a template per domain) on a launch or relaunch. While this takes perhaps 5 minutes per 1k domains with 5mio pages, it would take hell longer with static pages - and I don't want to know how many terrabytes this would fill up ;)
That's why I use FastAPI, it's really high performant as a backend sollution - and I can directly cache the spintaxes in as an list (basicly an array in python) in RAM.
I'm doing this for some years by now and performance was allways my hardest battle. I don't know how much earnings I lost, because my system broke under the pressure or search engines ddosed me, but it might be perhaps a 6 diggit sum by now =D

For indexing - as said, I go mostly for bing. It's easy to create webmaster console accounts automated - basicly the same process like with hotmail accounts - and getting the API Code, with that you can handle everything. It's pretty much sitemaps, bing loves it's sitemaps ;)
And while it seems small, we don't just talk about bing itself, but basicly every other search engine but google, since all are using it's index. And bing has a really strange mechanism, I guess it's their sandbox to handle the algo-paradox:
They randomly rank your crappiest sites for the most absurd keywords for a little time. I actually ranked for "Star Wars" on place 1 once. I don't know why. It's just weired. But exploidable. This is mostly the main income of the new domains, the monthly income is more google relatable. With some interlinking of the domains, google will start finding em by its own.
I tried to list em in search console as well, it did bring a push for sure - but there was too much manual work included, since google wants a mobile number every 3rd account (wich is not manual but kind of expansive compared to bing) and it uses oAuth wich makes the automated account generation kind of a pain in the ass.

I don't use any backlink tools. Interlinking partly, and all domains are dropped domains.
 
Tried this, it's a nice sollution for traffic handling, since it's way more performant. I still had to switch, cause I'm relaunching my domains every 2-4 days. Generating static pages eats up a lot of performance - and disk space. That's why I switched to spintaxes, based on a seed wich is the whole url and I only need to create basicly the sitemaps (and a template per domain) on a launch or relaunch. While this takes perhaps 5 minutes per 1k domains with 5mio pages, it would take hell longer with static pages - and I don't want to know how many terrabytes this would fill up ;)
That's why I use FastAPI, it's really high performant as a backend sollution - and I can directly cache the spintaxes in as an list (basicly an array in python) in RAM.
I'm doing this for some years by now and performance was allways my hardest battle. I don't know how much earnings I lost, because my system broke under the pressure or search engines ddosed me, but it might be perhaps a 6 diggit sum by now =D

For indexing - as said, I go mostly for bing. It's easy to create webmaster console accounts automated - basicly the same process like with hotmail accounts - and getting the API Code, with that you can handle everything. It's pretty much sitemaps, bing loves it's sitemaps ;)
And while it seems small, we don't just talk about bing itself, but basicly every other search engine but google, since all are using it's index. And bing has a really strange mechanism, I guess it's their sandbox to handle the algo-paradox:
They randomly rank your crappiest sites for the most absurd keywords for a little time. I actually ranked for "Star Wars" on place 1 once. I don't know why. It's just weired. But exploidable. This is mostly the main income of the new domains, the monthly income is more google relatable. With some interlinking of the domains, google will start finding em by its own.
I tried to list em in search console as well, it did bring a push for sure - but there was too much manual work included, since google wants a mobile number every 3rd account (wich is not manual but kind of expansive compared to bing) and it uses oAuth wich makes the automated account generation kind of a pain in the ass.

I don't use any backlink tools. Interlinking partly, and all domains are dropped domains.


Ah nice. what i understand from Your method that Your templates got only an index and sitemap contains index.html only right? so isn'T it kind of single static html page creation which i m trying to understand. On the other hand do You also create bing console by using fastAPI or a differant one?
 
Ah nice. what i understand from Your method that Your templates got only an index and sitemap contains index.html only right? so isn'T it kind of single static html page creation which i m trying to understand. On the other hand do You also create bing console by using fastAPI or a differant one?
No, this is just routing to API endpoints from nginx dirctly. For example the url thissubdomain.leads.to would just be a synonym for myapi.com/api/v1/renderhtmlandstuff?domain=leads.to&keyword=thissubdomain ;)
The endpoint than manages all the magic, like showing different stuff or redirecting. FastAPI is basicly a backend solution but can render and return html.

The templates are basicly just a randomized html construct around the content. I wanted to avoid using the same html as footprint ;)
This is nothing, a user would see, they are redirected to a centralized landing page.

For creating bing accounts, I use a single script. I could have worked it in, but this would have to use proxies - and I can use it on a VPS with a rotating VPN as well. It does not have to produce thousends of accounts and this is just way cheaper ;)
But yes, the whole system is mostly build up to work on fastAPI, I mostly used the microservice idea ;)

And I talk so freely about this, because I know - this is not so simple to recreate. =D
There is a lot of work with a new problem you didn't even know this would be a problem every stage in development. As said, blackhat got techy, if you do it right^^
 
No, this is just routing to API endpoints from nginx dirctly. For example the url thissubdomain.leads.to would just be a synonym for myapi.com/api/v1/renderhtmlandstuff?domain=leads.to&keyword=thissubdomain ;)
The endpoint than manages all the magic, like showing different stuff or redirecting. FastAPI is basicly a backend solution but can render and return html.

The templates are basicly just a randomized html construct around the content. I wanted to avoid using the same html as footprint ;)
This is nothing, a user would see, they are redirected to a centralized landing page.

For creating bing accounts, I use a single script. I could have worked it in, but this would have to use proxies - and I can use it on a VPS with a rotating VPN as well. It does not have to produce thousends of accounts and this is just way cheaper ;)
But yes, the whole system is mostly build up to work on fastAPI, I mostly used the microservice idea ;)

And I talk so freely about this, because I know - this is not so simple to recreate. =D
There is a lot of work with a new problem you didn't even know this would be a problem every stage in development. As said, blackhat got techy, if you do it right^^


Well nice contribution to my project, thank You. and by the way what Your site maps contains exactly?
 
Hello guys.

i miss the ole fucking days that we spam the shit out of tons of content and blast bunch of links. I know things are evolved, changed a lot. but, what tools would You advice for chern and burn projects? argo for conten, rankerx, scrapebox to blast links vs. i can code a small peace of software to generate lots of pages as well. i m highly open to Your advices.
Here's a workflow for my churn and burns when PAAs were all the rage:

1) get an account with a SERP API provider like valueserp (one that gives all data as a nicely formatted json or xml file is a big plus) and an OpenAI API key (or any other AI content generation API).

2) choose a niche and select a seed keyword, eg 'gardening'.

3) query the SERP API for the seed keyword, setting max results to 100 if possible and specifying a location if you're targeting a specific geo.

4) extract all the PAA questions from the SERP, and all the related searches from the SERP (a decent API will provide this already extracted), and store them in a db.

5) Use your OpenAI API to generate an answer for each question, create a page from combining all questions and answers.

6) query the SERP API for the next extracted related search in our db.

7) continue to step 4 every x minutes/hours depending on how quickly you want to grow your site.

This is a simplified version, and takes into account that you should be able to work with databases and create simple scripts to output data as html pages. It also doesn't cover internal linking, keyword cleaning (you'll get some totally irrelevant keywords eventually) etc. But for a completely automated setup, this was all you needed. PAAs are no longer the belle of the ball but many of mine are still raking in the traffic for longtails and bringing in the bucks.

Good luck!
 
Here's a workflow for my churn and burns when PAAs were all the rage:

1) get an account with a SERP API provider like valueserp (one that gives all data as a nicely formatted json or xml file is a big plus) and an OpenAI API key (or any other AI content generation API).

2) choose a niche and select a seed keyword, eg 'gardening'.

3) query the SERP API for the seed keyword, setting max results to 100 if possible and specifying a location if you're targeting a specific geo.

4) extract all the PAA questions from the SERP, and all the related searches from the SERP (a decent API will provide this already extracted), and store them in a db.

5) Use your OpenAI API to generate an answer for each question, create a page from combining all questions and answers.

6) query the SERP API for the next extracted related search in our db.

7) continue to step 4 every x minutes/hours depending on how quickly you want to grow your site.

This is a simplified version, and takes into account that you should be able to work with databases and create simple scripts to output data as html pages. It also doesn't cover internal linking, keyword cleaning (you'll get some totally irrelevant keywords eventually) etc. But for a completely automated setup, this was all you needed. PAAs are no longer the belle of the ball but many of mine are still raking in the traffic for longtails and bringing in the bucks.

Good luck!


Interlinking would be a tough process i think?
 
Interlinking would be a tough process i think?
For C&B it doesn't need to be too in-depth. While I'd like to say there was a topical map maintained by an algorithm, and I was using AI to identify relevant articles - I just went with mysql's MATCH fulltext function. Eg:
Code:
SELECT id, slug, MATCH(article) AGAINST ('$this_keyword') AS relevance FROM articles WHERE MATCH(article) AGAINST ('$this_keyword') ORDER BY relevance DESC LIMIT 0,$num_articles
So this uses the 'match' value generated by mysql as a relevance score, and ranks the articles on that.

Anchor a few of these in each article (after you get a decent amount of pages up and running), include a 'next' and 'previous' article link, x latest articles links etc.
 
Back
Top