SEO Crawlability Audit API API ID: 12792

Checks a public homepage’s SEO crawlability, indexability, robots.txt, sitemap, canonical, title, meta description, and H1 signals.
Use this API from your AI agent via MCP
Works with OpenClaw, Claude Code/Desktop, Cursor, Windsurf, Cline and any MCP-compatible AI client.
Docs & setup
Create a skill by wrapping this MCP: https://mcp.zylalabs.com/mcp?apikey=YOUR_ZYLA_API_KEY

SEO Crawlability Audit API checks whether a public website homepage can be crawled and understood by search engines.

The API checks homepage HTTP status, redirect behavior, robots.txt availability, sitemap availability, canonical tag, indexability signals, title tag, meta description, H1 tag, SEO crawlability score, grade, and findings.

The API returns a score, grade, findings, severity levels, homepage status, redirect information, robots.txt status, sitemap status, canonical status, indexability status, title tag status, meta description status, H1 status, usage information, safety notes, and disclaimer.

This API is useful for developers, SaaS builders, SEO platforms, SEO consultants, web agencies, marketing agencies, site monitoring services, domain monitoring services, website audit services, hosting companies, managed service providers, and companies that monitor customer or vendor websites.

The API performs passive homepage-level checks only. It does not hack, brute force, attempt logins, scan private systems, submit forms, test checkout flows, crawl full websites, crawl full sitemaps, scrape restricted content, bypass robots.txt, or require customer passwords or private secrets.

The API response includes a data_disclaimer field explaining that the audit is based only on public homepage, HTTP, redirect, robots.txt, sitemap, canonical, indexability, title tag, meta description, and H1 data and is provided for technical review purposes. Results should be reviewed before use in SEO, compliance, operational, or business decisions.

API Documentation

Endpoints


Checks a public homepage’s SEO crawlability and indexability signals, then returns a score, grade, findings, severities, robots.txt, sitemap, canonical, title, meta description, and H1 details.



                                                                            
GET https://zylalabs.com/api/12792/seo+crawlability+audit+api/25122/homepage+seo+crawlability+audit
                                                                            
                                                                        

Free test requests remaining: 3 of 3.


API EXAMPLE RESPONSE

{
  "target": "example.com",
  "normalized_url": "https://example.com/",
  "checked_at_utc": "2026-06-12T04:48:33.648250+00:00",
  "score": 65,
  "grade": "D",
  "findings_found": 5,
  "findings": [
    {
      "code": "robots_txt_missing",
      "severity": "low",
      "message": "robots.txt was not found."
    },
    {
      "code": "sitemap_missing",
      "severity": "medium",
      "message": "No reachable sitemap was found."
    },
    {
      "code": "canonical_missing",
      "severity": "low",
      "message": "Canonical tag was not found."
    },
    {
      "code": "title_too_short",
      "severity": "low",
      "message": "Title tag is shorter than 20 characters."
    },
    {
      "code": "meta_description_missing",
      "severity": "medium",
      "message": "Meta description is missing."
    }
  ],
  "customer_name": null,
  "plan": null,
  "requests_used": null,
  "monthly_limit": null,
  "usage_month": "2026-06",
  "auth_type": "api_key",
  "status_code": 200,
  "final_url": "https://example.com/",
  "redirects": [],
  "redirect_count": 0,
  "content_type": "text/html",
  "x_robots_tag": null,
  "robots_txt": {
    "url": "https://example.com/robots.txt",
    "available": false,
    "status_code": 404,
    "parse_status": "not_available",
    "error": null,
    "sitemap_urls": [],
    "blocks_all_common_bots": false
  },
  "sitemap": {
    "discovered_urls": [
      "https://example.com/sitemap.xml"
    ],
    "checked_count": 1,
    "available": false,
    "results": [
      {
        "url": "https://example.com/sitemap.xml",
        "available": false,
        "status_code": 404,
        "parse_status": "not_available",
        "error": null,
        "url_count": 0,
        "sample_urls": []
      }
    ]
  },
  "canonical": {
    "present": false,
    "url": null,
    "mismatch": false
  },
  "indexability": {
    "meta_robots": null,
    "meta_noindex": false,
    "meta_nofollow": false,
    "x_robots_tag": null,
    "x_robots_noindex": false,
    "appears_indexable": true
  },
  "metadata": {
    "title": "Example Domain",
    "title_length": 14,
    "meta_description": "",
    "meta_description_length": 0,
    "h1_count": 1,
    "h1_sample": [
      "Example Domain"
    ]
  },
  "safety_notes": [
    "Passive public homepage-level check only.",
    "No login attempts, form submissions, exploit checks, or private-system access."
  ]
}

Homepage SEO Crawlability Audit - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/12792/seo+crawlability+audit+api/25122/homepage+seo+crawlability+audit&domain=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

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 SEO Crawlability Audit API simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

🚀 Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

SEO Crawlability Audit API FAQs

The endpoint returns an analysis of a public homepage's crawlability and indexability, including a score, grade, findings, severity levels, and details about the robots.txt, sitemap, canonical tag, title, meta description, and H1 tags.

Key fields include "score," "grade," "findings," "status_code," "final_url," and details about the robots.txt, sitemap, canonical tag, title, meta description, and H1. Each finding includes a "code," "severity," and "message."

The response is structured in JSON format, with a top-level object containing metadata (e.g., "target," "checked_at_utc") and nested arrays for findings, each detailing specific issues related to SEO crawlability.

The endpoint provides information on HTTP status, redirection behavior, availability of robots.txt and sitemap, canonical tags, indexability signals, and SEO elements like title, meta description, and H1 tags.

Users can customize requests by specifying the target URL of the homepage they wish to analyze. The API will then return crawlability data specific to that URL.

Typical use cases include reviewing homepage crawlability signals, checking indexability indicators, monitoring public website setup, and identifying page-level SEO items that may need review or adjustment.

Data reflects passive checks of publicly accessible homepage information at the time of the request. Results may vary as pages, metadata, robots.txt, sitemap files, redirects, and related settings change.

Findings may include missing robots.txt, missing sitemap, missing canonical tag, short title text, missing meta description, redirect details, and indexability signals. Each finding includes a severity value and message.

General FAQs

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.

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.

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.

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 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.

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.
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]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs