As A reader of my blog, you are able to save 15% on the retail price of any GSA tool! To get this discount use any of the links below or in my posts then use the coupon code “shaunmarrs” on the checkout page.
In this post, I will be going over how users are able to use GSA Search Engine Ranker to submit content to self-hosted domains provided they are running a content management system the tool has a supported engine for such as WordPress.
The two main things I have used this for in the past is to post content to my private blog network domains and to automatically push content out to my test network domains for various tests. The majority of the tests I run on my test network are more off page based and even without manually doing the on-page tweaks I would for a money site network domain they still provide enough data for me to understand if the test or method is worth scaling up or not.
How Do We Set The Project Up?
The projects only require a hand full of differences when compared to a regular contextual campaign. I prefer to only select the specific engine for the content management system my domains are running so in my case this is WordPress.
If I was using the tool to post hand written articles to my test network then I would want to tick the “Do not submit same article more than x times” as shown in the screenshot below, this will remove the risk of the same article being submitted multiple times to different domains and receiving a potential duplicate content penalty that ends up having an effect on your test results.
I usually turn off the option to pause the project after x submissions as I will set up one project per blast that I require the tool to complete. As I am going to provide SER with the admin login details for the domains there is no need to have captcha solving enabled for the project as no captchas will be presented.
As I load the login details directly into the project I also disable all methods for the project to acquire additional targets to prevent it from posting to both my test network and other WordPress sites held in my verified list as shown in the screenshot below.
Finally, as you are loading the admin login details into the project there will be no requirement for email verification. This means you can leave the default email in the email tab and the project will submit your articles to your self-hosted domains with no problems.
Loading The Login Details
Firstly, your login details have to be loaded in a predefined format that GSA Search Engine Ranker is able to understand to enable it to add the correct data in the correct fields to automate the submission of content to your self-hosted domains. The correct format for your login details is displayed below.
<login url>:<account username>:<account password>
This is how it would look with example data.
Secondly, I usually use the admin account for the domains but if you wish you are able to go into your content management system dashboard on the domain and add new user accounts if you prefer to have different accounts posting to the domain.
I am aware of two different ways a user is able to load login details into a project and both have their individual advantages depending on what you are doing. The first is ideal if you only have one project you wish to load the details into, all the user has to do is click the tools button on the bottom of the project options and complete the navigation shown in the screenshot below.
The second method I am aware of is ideal if you are setting up a bunch of projects to post to self-hosted domains as it allows you to add the details to multiple accounts at once. Simply select all of the projects you wish to load the login details of the self-hosted domains in the project pane and then complete the navigation shown in the screenshot below.
Either method will enable the user to load the details from either a file or their clipboard. Once the user has selected either option they will be presented with the following window.
Selecting yes will load the domains into the projects as targets, this means GSA Search Engine Ranker will post directly to them when the project is set to active. The user will then be presented with the confirmation window shown in the screenshot below.
Content management systems such as WordPress have a number of security features in place to protect webmasters. One of these is to prevent an account being logged in more than once at the same time. I know of two ways to get around this security feature, the first is to use the GSA Search Engine Ranker scheduler feature.
If you set the scheduler up as shown in the screenshot below SER will only allow a single project to run at a time meaning only one thread will be logged into per account, per domain at the same time effectively bypassing the security feature. Simply change the “Switch to next project after x minutes” to account for posting to the number of domains you require the project to submit to. A larget number of domains will require the projects to be left active for a longer period of time.
The second is just a theory of mine, I have not tested this but setting up a number of accounts on the self-hosted domains with the power to submit new content should get around this feature providing the details loaded into each project are for a different account as shown below.
This will load two different projects with two different accounts for the same domain meaning both projects should be able to have active threads logged into the same domain at the same time making content submissions.
Wrapping It Up
After Penguin 4 I believe the future of GSA Search Engine Ranker lies in either self-hosted domains or investing the time and money in building a higher quality verified target list as I explain in this post. So although this post may not be of much help to some users right now, I believe the information it provides will help massively in the coming months.