{"final_url":"https://www.example.com/","status_code":200,"is_soft_404":false,"status_code_name":"OK","status_code_meaning":"Request succeeded.","redirect_hops":[{"hop":1,"url":"https://www.example.com/","status_code":200}],"redirect_count":0,"checks":[{"name":"status_code","passed":true,"explanation":"Status code = 200"},{"name":"soft_404_test","passed":true,"explanation":"Soft 404 not detected"},{"name":"x_robots_tag","passed":true,"explanation":"X-Robots-Tag permits indexing"},{"name":"meta_robots","passed":true,"explanation":"Meta robots permits indexing"},{"name":"robots_txt","passed":true,"explanation":"robots.txt allows crawling"},{"name":"meta_refresh_0","passed":true,"explanation":"No immediate meta refresh"}],"indexability":"indexable","error_message":null}
curl --location --request GET 'https://zylalabs.com/api/10687/google+indexability+checker+api/20241/indexability+checker?url=https://www.example.com/' --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 Google Indexability Checker 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 commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
The Google Indexability Checker API helps developers, SEOs, and site owners ensure pages are eligible for inclusion in Google’s index. Send a URL and get a clean JSON verdict (indexability) plus human-readable explanations for each check: HTTP status, soft-404 detection, robots directives (HTTP + HTML), robots.txt allow/deny, meta refresh traps, and redirect behavior. Use it to gate deployments, monitor large sites, or quickly debug indexing problems across product/catalog pages.
One-call verdict: indexability = indexable, conditionally_indexable, or not_indexable (see guide below).
Rich diagnostics: checks[] includes passed booleans with plain-English explanation.
Redirect awareness: Full redirect_hops with redirect_count and final_url.
Robots everywhere: Evaluates X-Robots-Tag headers, HTML meta robots, and robots.txt.
Soft-404 test: Flags thin/empty pages masquerading as 200s.
Consistent schema: Fixed, easy-to-parse fields for audit dashboards and CI bots.
Response Field Glossary:
final_url (string) — Resolved URL after redirects.
status_code (number) — HTTP status of the final URL.
status_code_name (string) — Standard reason phrase (e.g., “OK”, “Moved Permanently”).
status_code_meaning (string) — Human-readable explanation.
is_soft_404 (boolean) — Heuristic for pages that look like 404/empty content despite 200.
redirect_count (number) — Number of redirects followed.
redirect_hops (array) — Each hop: { hop, url, status_code }.
checks (array) — Individual checks with:
name (string) — Identifier (e.g., status_code, soft_404_test, x_robots_tag, meta_robots, robots_txt, meta_refresh_0).
passed (boolean) — True if requirement satisfied.
explanation (string) — Short reason you can surface directly in UI.
indexability (string) — Overall verdict:
indexable — All critical checks pass.
conditionally_indexable — Generally OK, but minor caveats detected (e.g., unusual canonical patterns, non-blocking meta refresh with delay, etc. [Customize to your backend logic if/when you include such checks]).
not_indexable — One or more critical blockers (noindex, disallow, 4xx/5xx, immediate meta refresh, soft-404).
error_message (string|null) — Populated if the check fails due to fetch/parse errors.
It means no critical blockers were detected (HTTP 200/OK, no noindex, robots.txt allows, no soft-404, no immediate meta refresh), so the page is eligible to be indexed by Google.
No. Indexing is ultimately Google’s decision. We verify common technical prerequisites for eligibility.
Yes. We report each hop in redirect_hops, the redirect_count, and the final_url.
Both HTTP X-Robots-Tag headers and HTML <meta name="robots"> tags.
Yes. We fetch and parse robots.txt for the host to determine if crawling is allowed for the submitted URL.
Look at checks[] for a failed item (e.g., meta_robots noindex, robots_txt disallow, soft-404). The explanation will tell you why.
We follow them to a final destination. If the end of the chain is indexable, you’ll see indexable = indexable.
For now we do not support batch requests, send individual calls per URL for now. Bulk inputs will be coming soon. 😊
Average response time is 1–3 seconds, depending on the site’s loading speed and redirect chain length. Complex pages or slow servers may take slightly longer.
Indirectly, yes. While it doesn’t influence ranking directly, ensuring pages are technically indexable is the foundation of good SEO. The API helps you catch blockers that would otherwise prevent Google from indexing your content at all.
The Indexability Checker endpoint returns a JSON object containing information about a URL's indexability status, including HTTP status, soft-404 detection, robots directives, and redirect behavior.
Key fields include `final_url`, `status_code`, `is_soft_404`, `redirect_count`, and `checks[]`, which provide detailed diagnostics on the URL's indexability.
The response is structured as a JSON object with a top-level indexability verdict, followed by detailed fields like `checks[]` for individual diagnostics, making it easy to parse and analyze.
The API provides information on HTTP status codes, soft-404 detection, robots directives (X-Robots-Tag and meta robots), and redirect behavior, helping users assess a page's indexability.
Users can customize requests by submitting different URLs to the endpoint, allowing for tailored checks based on specific pages or sections of a website.
Fields like `status_code_name` provide a standard reason phrase (e.g., "OK"), while `checks[].explanation` offers human-readable reasons for each check, aiding in quick diagnostics.
Typical use cases include monitoring large websites for indexability issues, debugging specific pages, and ensuring new deployments meet Google's indexing criteria.
Data accuracy is maintained through real-time checks against the submitted URL, ensuring that the API reflects the current state of the page as seen by Google.
The Indexability Checker evaluates several aspects, including HTTP status codes, soft-404 detection, X-Robots-Tag headers, HTML meta robots, robots.txt rules, and immediate meta refresh traps. Each check provides a boolean result and a human-readable explanation.
The `checks[]` array contains individual checks with fields like `name`, `passed`, and `explanation`. Each entry indicates whether a specific requirement was met and provides a brief reason, helping you quickly identify potential issues.
The `is_soft_404` field is a boolean that indicates whether the page appears to be a soft-404, meaning it returns a 200 status but contains little or no content. This helps identify pages that may mislead search engines about their actual content.
The API tracks redirects through the `redirect_hops` array, which lists each hop's URL and status code. The `redirect_count` indicates how many redirects were followed, ensuring you understand the final URL's indexability status.
The `final_url` field shows the resolved URL after all redirects have been followed. This is crucial for understanding which URL is ultimately being evaluated for indexability, especially if multiple redirects are involved.
Yes, the API allows you to identify specific indexing issues by examining the `checks[]` array. Each check provides insights into potential blockers, such as noindex directives or disallowed robots.txt rules, enabling targeted troubleshooting.
The `error_message` field provides information if the check fails due to fetch or parse errors. This helps diagnose issues with the URL submission process, allowing you to take corrective actions if necessary.
You can submit any publicly accessible URL for analysis. The API is designed to evaluate standard web pages, ensuring they meet Google's indexing criteria based on the checks performed.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund