# Pages with a broken schema.org Action (potentialAction)

A per-URL report: one row per page that matches, over the pages a crawl reached.

## What this report returns

A schema.org `potentialAction` advertises an operation agents can invoke, e.g. a SearchAction that wires up site search.

A row appears here when any of these is wrong, worst first:

-   **Missing Target**The `potentialAction` has no target, so agents have no endpoint to call.**Fix** Add a target EntryPoint with a `urlTemplate`, e.g. `"https://example.com/search?q={search_term_string}"`.
-   **Target Missing EntryPoint**The action's target has no usable endpoint; a SearchAction needs an EntryPoint `urlTemplate` (a bare URL can't carry the query), while other actions accept a bare URL.**Fix** Give the target an EntryPoint with a `urlTemplate`.
-   **Missing query-input**A SearchAction lacks query-input, so agents don't know what parameter to submit.**Fix** Add `"query-input": "required name=search_term_string"`, matching the `urlTemplate` placeholder.
-   **Unknown Type**The `potentialAction`'s `"@type"` is not a schema.org Action type (those all end in `"Action"`, such as SearchAction or OrderAction), so consumers ignore it.**Fix** Use a real schema.org Action type.
-   **Insecure Target**An action's target URL is plain http://, so the search or form input an agent submits through it travels unencrypted and can be read or altered. A Lumar bar: schema.org allows any URL.**Fix** Point the target at the https endpoint, e.g. `"urlTemplate": "https://example.com/search?q={search_term_string}"`.
-   **UrlTemplate Missing Placeholder**The SearchAction's `urlTemplate` has no {placeholder}, so an agent has nowhere to inject the query value.**Fix** Include the placeholder, e.g. ?`q={search_term_string}`, and mirror its name in query-input.

Security checks are provisional; precision has not yet been measured. A clean row is not a security assessment.

## The columns it shows

Every defect this technology can carry is a column in the grid, worst first, so nothing is hidden behind a filter you have to know to apply.

-   schema:Action Valid`schemaActionValid`
-   schema:Action Security Risk Detected`schemaActionSecurityRiskDetected`
-   schema:Action Findings`schemaActionFindings`
-   schema:Action Types`schemaActionTypes`
-   schema:Action Missing Target`schemaActionMissingTarget`
-   schema:Action Target Missing EntryPoint`schemaActionTargetMissingEntryPoint`
-   schema:Action Missing query-input`schemaActionMissingQueryInput`
-   schema:Action Unknown Type`schemaActionUnknownType`
-   schema:Action Insecure Target`schemaActionInsecureTarget`
-   schema:Action urlTemplate Missing Placeholder`schemaActionUrlTemplateMissingPlaceholder`
-   Ruleset Version`rulesetVersion`
-   Security Check Status`securityCheckStatus`
-   Related Security Frameworks`securityFrameworkReferences`

## About schema:Action

Declares actions an agent could take from this page.

[Read how schema:Action is checked](https://agentic-readiness.lumar.io/docs/capabilities/schema-action), including the specification it is validated against and a worked correct and broken example.

## Running it

This report comes with Agentic Readiness in Lumar and appears on every crawl of any project that has it turned on. [See the whole set](https://agentic-readiness.lumar.io/scan-at-scale), or check a single URL with the [scanner on this site](https://agentic-readiness.lumar.io/), which runs the same code with no account.

[Get Lumar pricing →](https://www.lumar.io/pricing/)