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.

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). 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 paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

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.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.

Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.