GoogleCrack
Regular Member
- Feb 23, 2012
- 329
- 153
I am going to show you how to get a Domain Authority 78 & Page Authority 83 backlink from the Google Chrome Web store.
I have saved you the trouble of making it. Download the file here
STEP 1: Building The App
We are going to need two things:
- A file called manifest.json
- An icon
The first thing we're going to do is
1. Create a new folder somewhere (name and location are not important)
2. Find an icon somewhere. You can use a site likefindicons.com. A good size is 128 by 128 pixels. Download the icon and put it in your folder. Rename the file, for our example, let's just call it "icon.png"
3. Download this file: Download the file here
4. Change the red parts to whatever you need. If you'd want to build a Chrome app that launches the BBC homepage, you could write BBC launcher under "name" and put "http://bbc.co.uk" under "url"s and "web_url". In our example case we would write:
4. Save this text-file in your folder under the name manifest.json
Step 2: Upload the App
If you need the app ID or an OAuth access token to complete your app's code, then you need to upload the app while you're still writing its code. Otherwise, you can wait until the app is finished. You can upload your app many times before publishing it.
Here's how you upload your app:
If your app's manifest and ZIP file are valid, then within seconds you should see a page that lets you edit your app.
Step 3: Provide store content
Using the dashboard's edit page for your app, add the store listing information that isn't in the ZIP file, such as a long description, screenshots, videos, and links to related sites. See Supplying Images for help on designing the images for your app, and Branding Guidelines for information on how you can use Google brands.
Step 4: Pay the developer signup fee
Before you publish your first app, you must pay a one-time $5 developer signup fee. You'll see a reminder in the dashboard until you pay the fee. For more information, including troubleshooting tips, see the Registration article.
Note: If you used the Chrome Developer Dashboard before —to publish an extension, for example—you won't see a fee reminder, and you don't need to pay the fee.
Step 5: Publish the app
Publishing your app usually involves a few steps:
Optional. Publish your app to test accounts, so a few trusted testers can try out the app and its install/payment flow.
Note: If you support Chrome Web Store Payments, you can't buy your own app using your developer account due to Google Checkout restrictions. You should first publish to test accounts so that you can test the payment system.
Congrats now you have a Do-Follow link from the Chrome Web Store
You can view my app here
Hope you see some great position movements with this quality back link
I have saved you the trouble of making it. Download the file here
STEP 1: Building The App
We are going to need two things:
- A file called manifest.json
- An icon
The first thing we're going to do is
1. Create a new folder somewhere (name and location are not important)
2. Find an icon somewhere. You can use a site likefindicons.com. A good size is 128 by 128 pixels. Download the icon and put it in your folder. Rename the file, for our example, let's just call it "icon.png"
3. Download this file: Download the file here
4. Change the red parts to whatever you need. If you'd want to build a Chrome app that launches the BBC homepage, you could write BBC launcher under "name" and put "http://bbc.co.uk" under "url"s and "web_url". In our example case we would write:
4. Save this text-file in your folder under the name manifest.json
Step 2: Upload the App
If you need the app ID or an OAuth access token to complete your app's code, then you need to upload the app while you're still writing its code. Otherwise, you can wait until the app is finished. You can upload your app many times before publishing it.
Here's how you upload your app:
- Go to the Chrome Developer Dashboard.
- Sign into the developer account you chose in Step 1.
- Click the Add new item button.
If you've never uploaded an item before, you need to accept the developer agreement before going on. - Click Choose file, navigate to your ZIP file, and click Upload.
If your app's manifest and ZIP file are valid, then within seconds you should see a page that lets you edit your app.
Step 3: Provide store content
Using the dashboard's edit page for your app, add the store listing information that isn't in the ZIP file, such as a long description, screenshots, videos, and links to related sites. See Supplying Images for help on designing the images for your app, and Branding Guidelines for information on how you can use Google brands.
Step 4: Pay the developer signup fee
Before you publish your first app, you must pay a one-time $5 developer signup fee. You'll see a reminder in the dashboard until you pay the fee. For more information, including troubleshooting tips, see the Registration article.
Note: If you used the Chrome Developer Dashboard before —to publish an extension, for example—you won't see a fee reminder, and you don't need to pay the fee.
Step 5: Publish the app
Publishing your app usually involves a few steps:
Optional. Publish your app to test accounts, so a few trusted testers can try out the app and its install/payment flow.
Note: If you support Chrome Web Store Payments, you can't buy your own app using your developer account due to Google Checkout restrictions. You should first publish to test accounts so that you can test the payment system.
- Click the edit page's Preview changes button, and verify that your app's listing looks great and has all the information it should.
- Verify that your app and any websites and supporting pages all work well and look as nice as possible.
- Publish any new websites and supporting pages that your app requires.
- Publish your app.
Congrats now you have a Do-Follow link from the Chrome Web Store
You can view my app here
Hope you see some great position movements with this quality back link
Last edited:
