---
title: "Get last SEO scan"
method: GET
path: "/api/apps/{app_id}/seo/last-scan"
---

# Get last SEO scan

`GET /api/apps/{app_id}/seo/last-scan`

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

Returns the app's last SEO scan in full, its [score and checklist](/developers/references/apps-api/sections/seo#the-score-and-the-checklist) together.

This returns the same score and checklist [Run SEO scan](/api-reference/run-seo-scan) returned when it ran, so poll this rather than re-scanning to re-read a result. Anything else that scan's response carried isn't persisted, so it never appears here. It returns `null` until the app is scanned at least once, and the result is only as current as the last scan, so read `scanned_at` before acting on it.

The score and the checklist are stored separately, and two scans running at once can interleave those two writes. So compare `scanned_at` with the one [Get SEO score](/api-reference/get-seo-score) returns before treating the two as one scan's.

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

## Path parameters

- `app_id` string, required — ID of the app.

## Response `200`

The last scan, or `null` if the app has never been scanned.

- LastSEOScanResponse — The stored scan.
  - `result` SEOScanReport — An SEO scan: its score and every check behind it.
    - `score` SEOOverallScore, required — The scan's score, overall and per category.
      - `overall` integer, required — Overall SEO score for the app, 0 to 100.
      - `grade` string, required — Letter grade for `overall`: `A`, `B`, `C`, `D` or `F`.
      - `categories` object — Per-category breakdown, keyed by the same category names the checks carry: `meta_tags`, `crawlability`, `structured_data`, `ai_discoverability` and `content_quality`, plus `indexing_performance` when Google Search Console integration is enabled for you. Base44 can add another category, so read the map rather than assuming this list is complete. Every category in the map is scored, including one this scan ran no checks for, which scores 100 with all three counts at zero.
    - `checks` SEOCheckResult[] — The checks behind the score, in the order Base44 reports them. Not every check it ran appears here. A failure that only restates an upstream one is dropped in favour of the root cause, so an unpublished or login-gated app returns the one gating failure rather than the dozen findings that follow from it.
      - `id` string, required — Identifier of the check. Stable across scans, but a check can be missing from a later scan rather than change status, because Base44 collapses cascading failures into their root cause.
      - `category` string, required — Which part of the score this check feeds: `meta_tags`, `crawlability`, `structured_data`, `ai_discoverability`, `content_quality`, or `indexing_performance` when Google Search Console integration is enabled for you.
      - `title` string, required — Short name of the check, phrased for the finding rather than the subject, so it changes with `status`.
      - `status` 'pass' | 'warn' | 'fail', required — Outcome of the check. A `warn` scores 50 against the category and a `fail` scores 0. Not every check can return all three.
      - `description` string, required — What the check found, written for the app's owner.
      - `details` unknown[] — Supporting detail for the finding, usually one object per page or entity involved. The keys differ per check, so treat the entries as opaque.
        - unknown
      - `fix_action` SEOFixAction — The remedy Base44 offers for a check, for display.
        - `type` string, required — Identifier of the action the Base44 builder offers for this check.
        - `label` string, required — Label the builder shows on the button for this action.
        - `params` object — Arguments to pass with the action. Empty on every action a scan emits today; keep reading it rather than assuming it stays empty.
      - `info_only` boolean — Environmental findings, such as DNS or hosting issues that can't be resolved from inside the app, set this to `true`. Everything else is `false`.
    - `scanned_at` string, required — When the scan ran, as an ISO 8601 UTC timestamp.

## Other responses

- `401` — Missing or invalid credentials.
- `403` — You don't have access to this app, you used a workspace API key, or you used a read-only personal access token. These endpoints accept a user's credentials only, and none of them accept a read-only credential, including the ones that only read.
- `404` — App not found.
- `429` — Rate limit exceeded. The base limit is 30 requests per minute, shared with the app's other SEO endpoints. See [Rate limits](/developers/references/apps-api/get-started/rate-limits) for the multiplier your plan gets.

## Changes

> 18 revisions in range; 1 not diffed.

- **2026-09-03** `9f4b5dac6451` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/adexad/apis/base44-app-management-api/changes/api/apps/:app_id/seo/last-scan/get.md)

---

[API](https://skmtc.dev/adexad/apis/base44-app-management-api.md) · [All operations](https://skmtc.dev/adexad/apis/base44-app-management-api/llms.txt) · [OpenAPI document](https://skmtc.dev/adexad/apis/base44-app-management-api/revisions/28fc82924122?raw)