About the API:
Keyword density is a foundational concept of search engine optimization (SEO). It’s important to understand how keyword density works, since it can have a direct impact on your site content’s visibility in search engine results pages (SERPs) and on the costs of your online marketing campaigns.
Keyword density refers to the number of times a keyword appears on a given webpage or within a piece of content as a ratio or percentage of the overall word count. This is also sometimes referred to as keyword frequency, or the frequency with which a specific keyword appears on a webpage.
This API will receive a text and it will deliver, as a JSON, the number of times that that word appears. Also, it will deliver a percentage of keyword density in the text.
This API is ideal to check how many occurrences are in a text on a webpage. This is great to improve your SEO. If you repeat several times a certain word, the SEO rank of that text will drop down.
This is a good tool to check the density and the number of times that a keyword appears, so you can have a better SEO rank for your page or texts.
Besides API call limitations per month, there is a limitation of 1 request per second.
Submit a text and immediately get a list of relevant words with a number of occurrences.
Object | Description |
---|---|
Request Body |
[Required] Json |
{"status":"ok","text_words":"30","unique_keywords":"27","density":[{"the":4,"augustus":1,"garrisoned":1,"sixteen":1,"only":1,"served":1,"praetorians":1,"legionaries":1,"than":1,"paid":1,"better":1,"italy":1,"in":1,"which":1,"were":1,"also":1,"peace":1,"public":1,"maintain":1,"to":1,"ostensibly":1,"cohorts":1,"nine":1,"guard":1,"praetorian":1,"created":1,"years":1}]}
curl --location --request POST 'https://zylalabs.com/api/831/keyword+occurrences+and+density+checker+api/592/get+ocurrences' --header 'Authorization: Bearer YOUR_API_KEY'
Submit a text and immediately get a list of relevant words with density (percentage).
Object | Description |
---|---|
Request Body |
[Required] Json |
{"status":"ok","text_words":"42","unique_keywords":"36","density":[{"roman":"7","the":"7","empire":"5","law":"5","codes":"2","well-established":"2","had":"2","already":"2","eastern":"2","impose":"2","and":"2","juridical":"2","parts":"2","most":"2","provinces":"2","in":"2","uniformly":"2","of":"2","functionaries":"2","to":"2","citizens":"2","held":"2","original":"2","jurisdiction":"2","over":"2","cases":"2","involving":"2","throughout":"2","courts":"2","but":"2","there":"2","were":"2","too":"2","few":"2","judicial":"2","procedures":"2"}]}
curl --location --request POST 'https://zylalabs.com/api/831/keyword+occurrences+and+density+checker+api/593/get+density' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Keyword Occurrences and Density Checker API REST API, simply include your bearer token in the Authorization header.
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.
Prices are listed in USD. We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble with paying by card, just contact us at [email protected]
Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further
Prices are based on a recurring monthly subscription depending on the plan selected β plus overage fees applied when a developer exceeds a planβs quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.
Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.
You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]
Service Level:
100%
Response Time:
844ms
Service Level:
100%
Response Time:
782ms
Service Level:
100%
Response Time:
389ms
Service Level:
100%
Response Time:
2,091ms
Service Level:
100%
Response Time:
7,214ms
Service Level:
100%
Response Time:
1,312ms
Service Level:
100%
Response Time:
3,406ms
Service Level:
100%
Response Time:
943ms
Service Level:
100%
Response Time:
2,445ms
Service Level:
100%
Response Time:
1,342ms
Service Level:
100%
Response Time:
1,835ms
Service Level:
100%
Response Time:
555ms
Service Level:
100%
Response Time:
2,114ms
Service Level:
100%
Response Time:
3,771ms
Service Level:
100%
Response Time:
6,358ms
Service Level:
100%
Response Time:
1,013ms
Service Level:
100%
Response Time:
2,091ms
Service Level:
100%
Response Time:
1,346ms