> ## Documentation Index
> Fetch the complete documentation index at: https://docs.base44.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Get last SEO scan
> This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.
Returns the app's last SEO scan in full: its score and every check.
Same payload [Run SEO scan](/api-reference/run-seo-scan) returned when it ran, so poll this rather than re-scanning to re-read a result. 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. That is also the field to compare against [Get SEO score](/api-reference/get-seo-score): the score is stored separately, so the two can briefly answer from different scans.
This endpoint is limited to 30 requests per minute per app, and that budget is shared with the app's other SEO endpoints.
The response includes fields beyond the ones documented here. Don't rely on undocumented response fields, as they can change at any time.
## OpenAPI
````yaml /developers/references/app-management/app-management-openapi.json get /api/apps/{app_id}/seo/last-scan
openapi: 3.1.0
info:
title: Base44 App Management API
version: 1.0.0
servers:
- url: https://app.base44.com
security:
- ApiKeyAuth: []
paths:
/api/apps/{app_id}/seo/last-scan:
get:
summary: Get last SEO scan
description: >-
This API is in beta. Endpoints, fields, and behavior may still
change, so avoid depending on it in production.
Returns the app's last SEO scan in full: its score and every check.
Same payload [Run SEO scan](/api-reference/run-seo-scan) returned when
it ran, so poll this rather than re-scanning to re-read a result. 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. That is also the field to compare against [Get SEO
score](/api-reference/get-seo-score): the score is stored separately, so
the two can briefly answer from different scans.
This endpoint is limited to 30 requests per minute per app, and that
budget is shared with the app's other SEO endpoints.
The response includes fields beyond the ones documented here.
Don't rely on undocumented response fields, as they can change at any
time.
operationId: get_last_seo_scan_api_apps__app_id__seo_last_scan_get
parameters:
- name: app_id
in: path
required: true
schema:
type: string
description: ID of the app.
title: App Id
description: ID of the app.
example: 6820f3a4e7b91d003c45a1f2
responses:
'200':
description: The last scan, or `null` if the app has never been scanned.
content:
application/json:
schema:
$ref: '#/components/schemas/LastSEOScanResponse'
'401':
description: Missing or invalid credentials.
'403':
description: >-
You don't have access to this app, or you used a workspace API key.
These endpoints accept a user's credentials only.
'404':
description: App not found.
'429':
description: Rate limit exceeded (30 requests per minute).
components:
schemas:
LastSEOScanResponse:
properties:
result:
anyOf:
- $ref: '#/components/schemas/SEOScanReport'
- type: 'null'
description: The app's most recent scan, or `null` if it has never been scanned.
type: object
title: LastSEOScanResponse
description: The stored scan, wrapped in the field the endpoint returns it under.
SEOScanReport:
properties:
score:
$ref: '#/components/schemas/SEOOverallScore'
description: The score this scan produced.
checks:
items:
$ref: '#/components/schemas/SEOCheckResult'
type: array
title: Checks
description: >-
The checks behind the score, in the order Base44 reports them. Not
every check it ran: 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.
example:
- 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:
type: string
title: Scanned At
description: When the scan ran, as an ISO 8601 UTC timestamp.
example: '2026-09-03T09:15:00+00:00'
type: object
required:
- score
- scanned_at
title: SEOScanReport
description: 'An SEO scan: its score and every check behind it.'
SEOOverallScore:
properties:
overall:
type: integer
title: Overall
description: Overall SEO score for the app, 0 to 100.
example: 82
grade:
type: string
title: Grade
description: 'Letter grade for `overall`: `A`, `B`, `C`, `D` or `F`.'
example: B
categories:
additionalProperties:
$ref: '#/components/schemas/SEOCategoryScore'
type: object
title: Categories
description: >-
Per-category breakdown, keyed by the same category names the checks
carry: `meta_tags`, `crawlability`, `structured_data`,
`ai_discoverability` and `content_quality`. Base44 can add a
category, so read the map rather than assuming these five. Every
category in the map is scored, including one this scan ran no checks
for, which scores 100 with all three counts at zero.
example:
meta_tags:
failures: 0
passed: 4
score: 80
warnings: 1
type: object
required:
- overall
- grade
title: SEOOverallScore
description: The scan's score, overall and per category.
SEOCheckResult:
properties:
id:
type: string
title: Id
description: >-
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.
example: llms_txt
category:
type: string
title: Category
description: >-
Which part of the score this check feeds: `meta_tags`,
`crawlability`, `structured_data`, `ai_discoverability` or
`content_quality`.
example: ai_discoverability
title:
type: string
title: Title
description: >-
Short name of the check, phrased for the finding rather than the
subject, so it changes with `status`.
example: AI-readable site guide is off
status:
type: string
enum:
- pass
- warn
- fail
title: Status
description: >-
Outcome of the check. A `warn` scores 50 against the category and a
`fail` scores 0. Not every check can return all three.
example: warn
description:
type: string
title: Description
description: What the check found, written for the app's owner.
example: Turn on the AI site guide so AI engines can understand your app.
details:
items: {}
type: array
title: Details
description: >-
Supporting detail for the finding, usually one object per page or
entity involved. The keys differ per check, so treat the entries as
opaque.
example:
- issue: Duplicate title
page: Pricing
fix_action:
anyOf:
- $ref: '#/components/schemas/SEOFixAction'
- type: 'null'
description: >-
The remedy the Base44 builder offers, or `null` when the check
passed or can't be fixed in-app. Read it for display: applying it
isn't part of this API.
info_only:
type: boolean
title: Info Only
description: >-
`true` when the finding is environmental, such as DNS or hosting,
and can't be resolved from inside the app.
default: false
example: false
type: object
required:
- id
- category
- title
- status
- description
title: SEOCheckResult
description: One check from the SEO scan.
SEOCategoryScore:
properties:
score:
type: integer
title: Score
description: >-
Score for this category, 0 to 100. A passing check counts 100, a
warning 50 and a failure 0, averaged over the category's checks.
example: 80
passed:
type: integer
title: Passed
description: >-
Checks in this category that passed. A plain count, so the three
counts add up to the category's checks in `checks`.
default: 0
example: 4
warnings:
type: integer
title: Warnings
description: Checks in this category that returned a warning.
default: 0
example: 1
failures:
type: integer
title: Failures
description: Checks in this category that failed.
default: 0
example: 0
type: object
required:
- score
title: SEOCategoryScore
description: One category's slice of the overall score.
SEOFixAction:
properties:
type:
type: string
title: Type
description: Identifier of the action the Base44 builder offers for this check.
example: enable_llms_txt
label:
type: string
title: Label
description: Label the builder shows on the button for this action.
example: Enable AI site guide
params:
additionalProperties: true
type: object
title: Params
description: >-
Arguments to pass with the action. Empty on every action a scan
emits today; keep reading it rather than assuming it stays empty.
example: {}
type: object
required:
- type
- label
title: SEOFixAction
description: The remedy Base44 offers for a check, for display.
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: api_key
description: Personal API key.
````