schema.org/EntryPointNo rich result
EntryPoint schema
The URL template a potential action resolves to.
Where to use it
Nested inside a potentialAction.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
entry-point.json
{
"@context": "https://schema.org",
"@type": "EntryPoint",
"urlTemplate": "https://www.seoforsolos.com/search?q={search_term_string}",
"actionPlatform": "https://schema.org/DesktopWebPlatform",
"contentType": "text/html"
}Properties
| Property | Status |
|---|---|
urlTemplate | Required |
actionPlatform | Recommended |
contentType | Recommended |
The three mistakes this type attracts
- 01A urlTemplate with no placeholder.
- 02Pointing at a route behind authentication.
- 03Omitting it and putting the template directly on the action.
Related types
Where this appears in the playbook
- Structured data: what each type is for and which ones earned their place.
- The schema graph: composing types into one graph with stable identifiers.
- One JSON-LD script per page, holding one @graph
- Stable @id anchors that cross-reference rather than duplicate
- Optional fields are omitted, never emitted as empty strings
Questions
What is the EntryPoint schema type for?
The URL template a potential action resolves to. Use it on: nested inside a potentialAction.
Which EntryPoint properties are required?
EntryPoint requires one property: urlTemplate. It also recommends 2: actionPlatform, contentType.
Does EntryPoint produce a rich result?
EntryPoint does not produce a Google rich result. It is still worth shipping, because its value is entity resolution and answer extraction rather than search result presentation.
What is the most common EntryPoint mistake?
The most common EntryPoint mistake is: A urlTemplate with no placeholder.