Features Pricing FAQ API Docs Blog
Signup / Login
Select Page

AI Google Search Questions API

Description

Long-tail keywords are one of the most potent strategies for all marketers to go after. But what kind of keywords should you focus on? One answer to that question is: questions!

This endpoint generates a set of the most commonly searched Google questions related to your topic of choice. Our AI will search its massive database of entries to look for phrases that people continuously inquire about. This can be a great source of inspiration for you to build your content around.

Endpoint Cost

1 token/credit per unique keyword (question) - Unique keywords are keywords that are not in our local cache.

Minimum cost per execution is capped at 1 token/credit per request

Endpoint

> POST https://api.jsonrepo.com/v1/seo/ai_search_questions

Headers

Field Description
X-API-Key Required Your API Key

Parameters

Field Type Description
input String Required Format: English alphanumerical string.
Length: 3 <= input <= 30
limit Integer Optional The number of maximum recommendations to be generated by our AI
Default: 15
Range: 1 <= limit <= 30

Understanding Endpoint Cost:

Say you want to get 10 questions related to a particular topic. Simply fire a request to our servers with the input set to the desired topic and the AI will then do its best to satisfy your requirements.

However, Because AI output is non-deterministic, the endpoint may return a couple of duplicate keywords if you run the same request twice. In order for you to not get charged for those duplicates, we deduct from the total cost any keywords that exist in our cache. That way your maximum cost is:

(1 * 10) - number of cached keywords

While this may seem complicated, in reality, it is far cheaper than most other alternatives out there as it maintains creative output without burdening you with high running costs.

Response

A successful request will result in a populated payload field with the expected output.

Response Time:

AI output is bound by the efficiency of the model and the prompt enabling it. The bigger your limit is, the longer the request will take to process. Please be patient as processing the information could sometimes take between 1 and 5 seconds.

Example

// Generate `3` questions that are related to the topic `shoes`

curl -X POST https://api.jsonrepo.com/v1/seo/ai_search_questions \
-H "X-API-Key: {YOUR_API_KEY_HERE}" \
--data-urlencode "input=shoes" \
--data-urlencode "limit=3"
// Server Response

{
    "http_code": 200,
    "http_message": "Ok",
    "timestamp": 1732455738,
    "message": "Successful execution.",
    "payload": {
        "questions": {
            "input": {
                "input": "shoes",
                "limit": 3
            },
            "output": [
                {
                    "id": 3059,
                    "keyword": "how to clean white shoes",
                    "volume": 33100,
                    "competition": 52,
                    "cpc": 0.84,
                    "trend": [
                        {
                            "year": 2023,
                            "month": "November",
                            "value": 40500
                        },

                        // 12 months data
                        ...

                        {
                            "year": 2024,
                            "month": "October",
                            "value": 33100
                        }
                    ],
                    "last_updated": "24 November 2024",
                    "region": "global",
                    "length": 24,
                    "difficulty": 3,
                    "volume_score": 5,
                    "ad_score": 3,
                    "origin": "cache"
                },
                {
                    "id": 3060,
                    "keyword": "what are the most comfortable shoes",
                    "volume": 2900,
                    "competition": 100,
                    "cpc": 0.37,
                    "trend": [...],
                    "last_updated": "24 November 2024",
                    "region": "global",
                    "length": 35,
                    "difficulty": 2,
                    "volume_score": 2,
                    "ad_score": 3,
                    "origin": "cache"
                },
                {
                    "id": 3058,
                    "keyword": "what are the best running shoes",
                    "volume": 390,
                    "competition": 100,
                    "cpc": 0.33,
                    "trend": [],
                    "last_updated": "24 November 2024",
                    "region": "global",
                    "length": 31,
                    "difficulty": 2,
                    "volume_score": 1,
                    "ad_score": 2,
                    "origin": "cache"
                }
            ]
        }
    }
}

Errors

A failed request will result in an error output as detailed in Error Rules. If the endpoint validation fails due to missing, badly formatted or invalid parameters, the endpoint will return HTTP code 400 along with a message detailing the error.

// Request without `input` field

{
    "http_code": 400,
    "http_message": "Bad Request",
    "timestamp": 1731791691,
    "message": "'input' must be provided as an alphanumeric string of size 3 to 30 characters.",
    "payload": []
}