Top SEO api resources and tools

Developing a project for my team, I investigate few days over the web trying to find the best, suitable, price-affording SEO (Search Engine Optimization) API package in order to develop a customer-based SEO tool.

My top requirements over statistics data, given a page URL, was:

  • page rank
  • link analysis
  • content analysis
  • competitor analysis
  • keyword analysis

Outside the SEO battle is very confusing: different opinions, trends, ideas, guidelines.. Anyway, this is what I found.

1. Web SEO Analytics (http://www.webseoanalytics.com)
pro: the most complete among this list, good price, it relies on different search engines
cons: daily limits on requests / reports

2. Alexa Web Information Service (http://aws.amazon.com/awis)
pro: enough complete, request based pricing (you pay what you really use)
cons: Alexa is the data owner

3. SEOmoz Site Intelligence API (http://www.seomoz.org/api)
pro: good API, free version available, good documentation
cons: major / exclusive focus on link analysis concepts

4. OpenCalais API (http://www.opencalais.com)
pro: stable and robust api, great keyword suggestion tools
cons: focused only on content / keyword analysis

5. Wordsfinder API (http://www.wordsfinder.com)
pro: keyword extractor and traffic extimator API
cons: not free, few data

6. AlchemyAPI (http://www.alchemyapi.com/api)
pro: good API, free version available, good documentation
cons: major / exclusive focus on keyword analysis and content analysis concepts

7. Majestic SEO Enterprise API (https://www.majesticseo.com/support/subscriptions/enterprise-api)
pro: based on a good web-based gui service
cons: few data and statistics, basically focused on link analysis

8. Compete API (http://developer.compete.com)
pro: it provides graphical icons indicators to statistics
cons: exclusive focus on domain analysis

9. Ginzametrics API (http://ginzametrics.com/api.html)
pro: ranking and keyword analysis, good interface, http based, free of charge
cons: in beta version at the moment (2011-03-04)

I don’t want to consider search engine proprietary API for three main reasons:

  1. They relies only on that search engine data
  2. They are in constant development
  3. I should work more on my tool aggregating more (one for each search engine) API packages instead of few

Another big reason is that search engine are going to shut down / deprecate the free search API (for obvious reasons!).

Latest articles

Matteo Pelucco Written by:

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *


× 8 = seventy two