pageEnd

pageEnd · Not mentioned by Google

Appears in

• ScholarlyArticle

What is it?

The page number where a published work ends within a larger volume or issue. This property records the final page of an article, chapter, or section as it appears in print or PDF pagination.

Why this matters for AEO

When a user asks an AI engine for a specific journal article, the AI can return the exact page range alongside the title and DOI. A query like "where is the FRBR review by Smiraglia published?" gets a precise answer: pages 360 to 368 in Library Resources & Technical Services, rather than a vague citation.

What the specs say

Schema.org: Integer, Text. The page on which the work ends; for example "138" or "xvi". schema.org/pageEnd

Google: Not mentioned. No dedicated Google structured data page exists for ScholarlyArticle.

How to find your value

• Journal PDF — Footer or header of the last page of the article
• DOI metadata — CrossRef API response for the article DOI
• Publisher website — Article landing page, typically in the citation block
• BibTeX export — The pages field (e.g., pages = {360--368})

Format and code

The value is either an integer or a text string (for Roman numerals like "xvi").

{
  "@context": "https://schema.org",
  "@type": "ScholarlyArticle",
  "name": "Be Careful What You Wish For: FRBR, Some Lacunae, A Review",
  "author": "Smiraglia, Richard P.",
  "pageStart": "360",
  "pageEnd": "368"
}

Roman numeral example:

{
  "@context": "https://schema.org",
  "@type": "ScholarlyArticle",
  "name": "Foreword",
  "pageStart": "ix",
  "pageEnd": "xvi"
}

Webflow implementation

Static pages

Add the page range in a JSON-LD script block in Page Settings > Custom Code (Before ):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ScholarlyArticle",
  "name": "Article Title",
  "pageStart": "360",
  "pageEnd": "368"
}
</script>

CMS template pages

Create a plain text field in your CMS collection for pageEnd. Reference it in the JSON-LD embed using Webflow's dynamic field syntax.

In Schema HQ

Your CMS fields to pageStart and pageEnd automatically when the ScholarlyArticle type is selected. No manual JSON editing required. is mapped automatically

Real examples

Schema.org official example:

{
  "@type": "ScholarlyArticle",
  "isPartOf": "#issue",
  "description": "The library catalog as a catalog of works...",
  "sameAs": "https://doi.org/10.1080/01639374.2012.682254",
  "pageEnd": "368",
  "pageStart": "360",
  "name": "Be Careful What You Wish For: FRBR, Some Lacunae, A Review",
  "author": "Smiraglia, Richard P."
}

Taylor & Francis (Library Resources and Technical Services):

{
  "@type": "ScholarlyArticle",
  "author": "Carlyle, Allyson.",
  "name": "Understanding FRBR as a Conceptual Model: FRBR and the Bibliographic Universe",
  "pageEnd": "273",
  "pageStart": "264"
}

Related fields

• pageStart
• abstract
• citation
• pagination

FAQ

Does pageEnd accept Roman numerals?

Yes. The property accepts both Integer and Text values, so "xvi" and "368" are both valid. Use text strings for front matter numbered in Roman numerals.

Should pageEnd always be paired with pageStart?

Almost always. A page range without both endpoints is incomplete. Use both properties together to give the full span of the work within its parent publication.