Agent guide

Website Intelligence API for AI agents

Separate technical crawl hygiene from capped AEO/content authority evidence for public websites. This agent guide explains when to call Website Intelligence API, when not to call it, which outputs to inspect, and how to route human users to RapidAPI or product docs.

Subscribe or test on RapidAPI Human API page Worked use case Checklist

When an agent should call this API

You want to know whether bots can access and parse the site.
You need to check whether answer engines have enough FAQ, EEAT, service, location, review, and curated llms.txt context to cite confidently.
You want a compact diagnostic before deciding which site signals to fix next.
You want to compare technical and AEO readiness using a single public-site analysis.

Do not call it for

Not a search ranking, AI citation, traffic, or revenue predictor.
Not permission to scan private, internal, or customer sites you do not own or control.
Not a full SEO suite, content generator, or automatic site patcher.

First call for agents

Use the smallest request, then inspect named outputs.

curl -X POST 'https://website-intelligence-api.linkridge.net/v1/site-intel/analyze' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: <your-api-key>' \
  -d '{
  "url": "https://linkridge.net/"
}'

Prefer marketplace auth? Open in RapidAPI for plans, keys, and interactive testing.

Response fields to inspect

{
  "domain": "linkridge.net",
  "requestedUrl": "https://linkridge.net/",
  "fetchability": {
    "ok": true,
    "status": 200
  },
  "score": 50,
  "technical_crawl_score": 50,
  "max_score": 100,
  "category_scores": {
    "fetchability": { "score": 20, "max": 20 },
    "metadata": { "score": 12, "max": 25 },
    "crawl_policy": { "score": 8, "max": 20 },
    "structured_data": { "score": 0, "max": 10 },
    "llm_readiness": { "score": 10, "max": 15 },
    "freshness": { "score": 0, "max": 10 }
  },
  "aeo_authority_score": {
    "score": 60,
    "uncapped_score": 72,
    "status": "needs_review",
    "caps_applied": [
      {
        "code": "missing_faq_answer_depth_cap",
        "cap": 70,
        "recommendation": "Add FAQPage-backed answer content before treating AEO readiness as strong."
      },
      {
        "code": "thin_eeat_proof_cap",
        "cap": 60,
        "recommendation": "Add named experts, team, license, testimonial, case-study, or review proof."
      }
    ]
  },
  "top_gaps": [
    {
      "code": "missing_structured_data",
      "severity": "medium",
      "evidence": "No JSON-LD structured data types were extracted.",
      "recommendation": "Add schema.org JSON-LD for the relevant entity types."
    },
    {
      "code": "missing_sitemap_signal",
      "severity": "medium",
      "evidence": "No sitemap was declared in robots.txt and /sitemap.xml did not expose a sitemap.",
      "recommendation": "Add a sitemap and reference it from robots.txt."
    }
  ]
}