Run SEO scan

<Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>

Scans the app for SEO problems and returns the score and checklist in two parts. The score is a single 0-100 number with a letter grade. The checklist is the individual checks, each pass, warn, or fail, that produced the score.

The scan reads the app's own configuration and also fetches the live site over HTTP to check what it really serves for robots.txt, sitemap.xml and the home page. Those three run in parallel with a five-second timeout each and one retry, so expect a few seconds, and up to about ten when the live site is slow to answer.

An app that isn't published yet still scans, but its live checks have nothing to fetch. Rather than reporting every check that fails as a result, Base44 reports only the root cause and drops the downstream failures that just restate it, in this case that the app isn't published. The same collapsing applies when the live site's host can't be reached at all. Instead of one warning per probe, you get a single row for the host being unreachable.

Base44 also stores the result, so Get SEO score and Get last SEO scan return this same scan until the next one runs, without needing to scan again. Storing the result is best-effort and can't fail the scan itself, so a successful call here only promises the scan that just ran, not that the two report endpoints already reflect it. Read them back if you need to be sure they're in sync.

The score and the checklist are stored separately, and two scans running at once can interleave those two writes. So if you read both report endpoints, compare their scanned_at before treating the numbers as one scan's.

Each check that Base44 can act on carries a fix_action. Read it to see what the builder offers.

The overall score isn't a simple tally of passing and failing checks. Category scores are weighted differently, and some critical checks can further cap the overall score when they fail. That's why score.overall doesn't add up to a plain count of failing checks, even though the passed, warnings and failures counts inside each category are exact. Use failures from Get SEO score if you need the exact total across every category.

<Warning>The response includes fields beyond the ones documented here. Don't rely on undocumented response fields, as they can change at any time.</Warning>

{
  "result": {
    "score": {
      "overall": 82,
      "grade": "B",
      "categories": {
        "meta_tags": {
          "failures": 0,
          "passed": 4,
          "score": 80,
          "warnings": 1
        }
      }
    },
    "checks": [
      {
        "category": "ai_discoverability",
        "description": "Turn on the AI site guide so AI engines can understand your app.",
        "id": "llms_txt",
        "status": "warn",
        "title": "AI-readable site guide is off"
      }
    ],
    "scanned_at": "2026-09-03T09:15:00+00:00"
  }
}