I don't see any instructions on how to set up GSA for FCS, other than the External API setting. I created an API key, tried a couple of IDs, left the URLs empty, but without URLS, it won't save the project.
What is the correct setup?
Thanks.
Blake
bestimtoolzHigh PR WEB 2.0 posting service - affordable !
Yeah, it could be great to know how to use it (((:
I don't have any account there so I can not tell you where to get the project ID from. If you have just one project running there, you can use "all" as ID and you should get the data into the project.
For those who do not figured how it works:
1. edit project
2. go to External APIs tab
3. enable FCS and enter project ID and API key.
4. upon verification start, it will also try to import the data from FCS and add the verified URLs.
So if I want to setup a project in SER to continuously build links to the links generated by FCS how would I do that? Kind of like a tier project but the project doesn't exist.
I would have thought when you entered in your api key in External APIs that you could then import urls from fcs into the url control.
The good news is that it does work , but it isn't quite doing what I think we were expecting.
In the API tab of an SER project enter your API key from FCS and enter the PROJECT ID which is a number next to the project name when you do a "View Projects" inside FCS.
Run your SER project as normal. When SER does a verify, as the final step SER will display "FCS IMPORT STARTED" and it will display each URL that it has received from FCS. Each of those URLs will be added to that project's verified links (you'll see them appear in the right hand pane of SER.
If you were then to do another tier to this project then SER would build links to your FCS posts.
Now that's added an extra layer that I think we didn't need. I was hoping that SER would import the URLs from FCS and stick them straight into the URL box of the Data tab of an SER project, but I guess it's a case of what were people expecting and what did they want ?
That would simply limit the whole case if it was imported to project urls. That way you would never know what anchor was used, what engine and would also not be able to do a reverify of the links.
The way it is build now is (in my opinion) the most flexible method.
When I was using Rankwyz for Web 2.0 posts I would export the posts from Rankwyz, and copy them into the URL box of the Data tab of my SER project. In that way I would be building links to my Web 2.0 posts via SER.
I can't see why that was inefficient and therefore can't understand why FCS API can't do the same thing ?
@filescape this way you never know what anchor text was used or what url was used in the project url you try to link to. If you don't care then fine, you can do the same for FCS as well. But for those who care it is the only way to do it as I implanted it now. It will work way better once you understand it.
Ialmosthaveit, I alreadyhavetheAPIandyougettheIDPROJECT.
FromwhatI'veread@SvenIhavetocreateaccountsinFCSandalsoprovidearticles,createblogwiththeir 5-10entrieswithmylinksonsomeofthem. Andjustatthatmoment to linkFCSprojectwith"SER",sothatyou importurlsofpagesthat theyhavebeenpublishedinthatFCSprojectisso?
Ifit wereso, would onlyservetoTier1,becauseIcan IneedforaTIER2manymorelinksandmanymoreblogsandmanymoreitems.BecausethethingwouldthatgetalistofalltheTIer1torivallinksacoupleofblogstoeveryone,it would behuge. IthoughtthatFCScreatedaccountsandthen"SER"wifepublish.
Whateverthemethodstillmeisnotatallclear,I thinkthatthefirstoptionis to runtheentireprojectinFCS (createblogs,createarticles,publishthemanddelete thedeleted)andonce to pass it to"SER" is correct?
FCS is not delivering accounts per API but just the verified links. Those get imported to the main project and you can run a tier linked to that that creates backlinks to the FCS links in that tier project.
@Sven I must be mad arguing with the man who WROTE the software BUT...
The way you have it set up at the moment, if I mouse over one of the verified links from FCS I see "Proj Engine : Unknown" and "Anchor Text : N/A". I normally set my lower tiers up with the option "Use Anchor Text from verified URL", and I guess that if I did that with the FCS URLs I'd end up with either nothing or "N/A" in the anchor text ?.
It's almost as if you're trying to POST to those FCS URLs whereas all we want to do is make posts linking to them. I don't understand why you'd need to know the engine.
Sorry to be a doubter, just think that we don't have it quite right at the moment
The following is my current process for backlinking FCS project URLs:
I export a list of completed URLS from my FCS project.
I set up my campaign in GSA, then I load in small batches of 25 URLs from the FCS export list for each run, or campaign. I use GSA a little bit differently than most, in that I don't do large blasts of backlinks. Smaller blasts with multiple campaigns using contextual only platforms.
So, what I was hoping for, was that I could set up my GSA campaign, activate FCS, load in the API and campaign ID, and have the verified/completed URLS automatically load into the GSA URL field.
filescape the anchor text as well as the URL to that verified URL is discovered as long as you have the URL used on the FCS article being present int he project-data-URL box. Then SER is able to verify the link correctly. The Engine/Engine Type is often not being resolved as SER doesn't have an engine for many of the FCS type of sites.
@Mitch I was thinking about it but the way it is build now is way more complete. The only issue you might have is to build up a dummy project with the money site (used in FCS). But way better than having a whole lot of target URLs in a project without knowing if they are still valid or not.
I also meant that FCS Networker builds Web 2.0 sites.
I post links to my main sites on these Web 2.0's.
Currently I am manually taking the URL's that FCS Networker posts to and setting up a project in GSA to add links to the Web 2.0's.
The best use of the API in my eyes would be for the FCS Networker Web 2.0 post and home page URL's to be added to a new GSA project for me to add backlinks to them.
If I understand GSA correctly, adding the URL's to the verified list means they will be used to add backlinks to the GSA project's target URL's NOT have backlinks added to them.
Have I got it right?
If yes then my suggestion for the API usage above should also be along the right lines?
As there seems to be so much confusion on how this works, I've detailed the steps below
1) Create a project in SER with minimal info and a dummy URL. Could even be your money site - doesn't matter as we're not going to build any links to it. 2) Paste your API and FCS Project details in the API tab 3) Set the SER project status to Verify and leave at Verify 4) Set up a tiered project pointing to the verify URLs of the FCS dummy project 5) Start your projects 6) SER imports your URLs from your FCS project, verifies they are live and then reverifies them based on your settings in Options 7) Once your FCS links are verified, your tiered projects start building links to them
This way, SER can keep verifying your FCS links are live and only build links to these live links. If it simply imported the links into the target URL, it would have no way of checking if they are live or not.
HinkysSEOSpartans.com - Catchalls for SER - 30 Day Free Trial
So now we can use SER for (besides building links) automatic re-verification of FCS links??? Not to mention we can use the nice export format of SER for FCS links. Oh yea. Sven, you're awesome and you just made my day!
@davbel correct but you should not use a dummy URL but the real one used in the FCS links. This way SER will be able to do re-verifications later on and also detect the proper anchor text used in it.
Comments
I don't see any instructions on how to set up GSA for FCS, other than the External API setting.
I created an API key, tried a couple of IDs, left the URLs empty, but without URLS, it won't save the project.
What is the correct setup?
Thanks.
Blake
I tried using the Project Name and I tried using the project URL number that displays in the browser URL field when clicking on the project name.
Blake
------------
I would have thought when you entered in your api key in External APIs that you could then import urls from fcs into the url control.
------------
That is what I was thinking as well.
Blake
The good news is that it does work
In the API tab of an SER project enter your API key from FCS and enter the PROJECT ID which is a number next to the project name when you do a "View Projects" inside FCS.
Run your SER project as normal. When SER does a verify, as the final step SER will display "FCS IMPORT STARTED" and it will display each URL that it has received from FCS. Each of those URLs will be added to that project's verified links (you'll see them appear in the right hand pane of SER.
If you were then to do another tier to this project then SER would build links to your FCS posts.
Now that's added an extra layer that I think we didn't need. I was hoping that SER would import the URLs from FCS and stick them straight into the URL box of the Data tab of an SER project, but I guess it's a case of what were people expecting and what did they want ?
That would simply limit the whole case if it was imported to project urls. That way you would never know what anchor was used, what engine and would also not be able to do a reverify of the links.
The way it is build now is (in my opinion) the most flexible method.
When I was using Rankwyz for Web 2.0 posts I would export the posts from Rankwyz, and copy them into the URL box of the Data tab of my SER project. In that way I would be building links to my Web 2.0 posts via SER.
I can't see why that was inefficient and therefore can't understand why FCS API can't do the same thing ?
What am I missing ??
The way you have it set up at the moment, if I mouse over one of the verified links from FCS I see "Proj Engine : Unknown" and "Anchor Text : N/A". I normally set my lower tiers up with the option "Use Anchor Text from verified URL", and I guess that if I did that with the FCS URLs I'd end up with either nothing or "N/A" in the anchor text ?.
It's almost as if you're trying to POST to those FCS URLs whereas all we want to do is make posts linking to them. I don't understand why you'd need to know the engine.
Sorry to be a doubter, just think that we don't have it quite right at the moment
Thanks
The following is my current process for backlinking FCS project URLs:
I export a list of completed URLS from my FCS project.
I set up my campaign in GSA, then I load in small batches of 25 URLs from the FCS export list for each run, or campaign. I use GSA a little bit differently than most, in that I don't do large blasts of backlinks. Smaller blasts with multiple campaigns using contextual only platforms.
So, what I was hoping for, was that I could set up my GSA campaign, activate FCS, load in the API and campaign ID, and have the verified/completed URLS automatically load into the GSA URL field.
Blake
Have a look here: http://docu.gsa-online.de/search_engine_ranker/external_apis#fcs_networker
I explained also why I added it the way I did there.
1) Create a project in SER with minimal info and a dummy URL. Could even be your money site - doesn't matter as we're not going to build any links to it.
2) Paste your API and FCS Project details in the API tab
3) Set the SER project status to Verify and leave at Verify
4) Set up a tiered project pointing to the verify URLs of the FCS dummy project
5) Start your projects
6) SER imports your URLs from your FCS project, verifies they are live and then reverifies them based on your settings in Options
7) Once your FCS links are verified, your tiered projects start building links to them
This way, SER can keep verifying your FCS links are live and only build links to these live links. If it simply imported the links into the target URL, it would have no way of checking if they are live or not.
@sven I don't think I missed anything did I?