Parse
IndexPricing
Sign in
  1. Research
Research
JSON-LD schema, author bylines, and content age on 329,519 AI-cited pages

JSON-LD schema, author bylines, and content age on 329,519 AI-cited pages

Published Nov 20, 2026

On this page
  • Engine metadata split
  • Schema families
  • Top 20 JSON-LD types
  • Bylines and dates
  • Freshness by engine
  • Freshness by source
  • Multi-question reach
  • Study scope
  • What to do next
  • How we measured
  • Sources
  • More like this
  • Engine metadata split
  • Schema families
  • Top 20 JSON-LD types
  • Bylines and dates
  • Freshness by engine
  • Freshness by source
  • Multi-question reach
  • Study scope
  • What to do next
  • How we measured
  • Sources
  • More like this

Dimitry ApollonskyFounder, Parse

DataWhat reviewed means

Do AI engines actually rely on structured schema, visible author bylines, and recently updated content when choosing what to cite, or do those signals differ sharply across engines and page types?

We inspected parsed HTML and JSON-LD metadata on 329,519 unique pages cited by organic ChatGPT Search, Google AI Mode, and Perplexity answers from November 1 to November 19, 2026. We measured Schema.org types, author bylines, HTML/JSON-LD dates, content age across 16 source categories, and multi-question reach.

Across 329,519 unique AI-cited HTML pages inspected in November 2026, 70.86% carry JSON-LD schema, 30.86% expose an author byline, and 41.92% expose a published or modified date (median age 74.5 days across 138,134 valid dated pages). Perplexity cites pages with author bylines (55.35%) and HTML dates (68.07%) at roughly double ChatGPT Search's rates (26.42% and 37.88%).

Perplexity and Google AI Mode favor schema, bylines, and dates far more than ChatGPT Search

Structured signals separate the three engines cleanly. On Perplexity (5,371 HTML pages), 85.55% of cited pages carry JSON-LD schema, 52.71% carry Article-family schema, 55.35% expose an author byline, and 68.07% expose a parsed HTML date.

Google AI Mode (79,824 HTML pages) sits in the middle at 75.86% JSON-LD, 38.23% Article-family schema, 44.77% author bylines, and 55.18% HTML dates. ChatGPT Search (263,838 HTML pages) cites docs, product pages, and undated evergreen URLs much more freely: only 26.42% carry a byline and 37.88% carry a parsed date.

Carry JSON-LD schema
70.86%

233,513 of 329,519 cited HTML pages

From 69.48% on ChatGPT Search to 85.55% on Perplexity

Expose an author byline
30.86%

101,703 of 329,519 pages

Perplexity (55.35%) is over 2x ChatGPT Search (26.42%)

Carry a parsed HTML/JSON-LD date
41.92%

138,147 pages total; 138,134 valid in age cohort

58.08% expose no parsed HTML date

Median age of dated pages
74.5 days

Perplexity 56.8d · ChatGPT 63.9d · Google AI Mode 101.9d

Google AI Mode cites pages 79% older than Perplexity

Structured metadata presence on AI-cited HTML pages by engine

  • ChatGPT Search
  • Google AI Mode
  • Perplexity
  • Any JSON-LD
  • ChatGPT Search69.48%
  • Google AI Mode75.86%
  • Perplexity85.55%
  • Article family schema
  • ChatGPT Search20.83%
  • Google AI Mode38.23%
  • Perplexity52.71%
  • Author byline
  • ChatGPT Search26.42%
  • Google AI Mode44.77%
  • Perplexity55.35%
  • Any parsed date
  • ChatGPT Search37.88%
  • Google AI Mode55.18%
  • Perplexity68.07%
  • 0%50%100%
329,519 unique cited HTML pages inspected November 1 to November 19, 2026 (pages cited by multiple engines count in each engine row).

Takeaway

Perplexity cites pages with author bylines and dates at roughly double ChatGPT Search's rates, reflecting its heavier pull toward editorial and news sources.
  • Ahrefs: Does schema markup improve AI visibility?

FAQPage schema spikes to 30.7% on Perplexity, while Product schema holds near 14% on ChatGPT and Perplexity

Across all 329,519 unique cited HTML pages, Article-family markup (Article, BlogPosting, or NewsArticle) appears on 24.99%, FAQPage on 19.4%, Product or SoftwareApplication on 13.34%, and Review or AggregateRating on 7.44%.

Perplexity leads every editorial schema category, hitting 30.7% FAQPage and 9.2% Review-family markup. Google AI Mode carries the lowest Product-family schema share (10.68% vs 14.15% on ChatGPT Search and 14.17% on Perplexity), aligning with Google's tilt toward editorial commentary over vendor product pages.

Full schema, byline, and date profile by AI engine

JSON-LD (%) · 3 results

  • Perplexity85.55%
  • Google AI Mode75.86%
  • ChatGPT Search69.48%
  • 0%50%100%
Explore the data (3 rows)
ChatGPT Search263,83869.4820.8319.3814.157.7926.4237.88
Google AI Mode79,82475.8638.2319.9110.686.2644.7755.18
Perplexity5,37185.5552.7130.714.179.255.3568.07
Rates measured on unique cited HTML pages per engine, November 1 to November 19, 2026.

Takeaway

Audit structured metadata by engine: ChatGPT Search frequently cites schema-light product and documentation pages, while Perplexity concentrates on richly marked-up articles and FAQs.

Entity and navigation schema appear on half of cited pages, while FAQPage (19.4%) tops Article (16.21%)

Looking at individual Schema.org @type tags across all 329,519 HTML pages shows why raw JSON-LD totals look high. Baseline site-identity and navigation types lead the list: Organization appears on 50.86% (167,577 pages), ListItem on 44.19% (145,611), BreadcrumbList on 43.14% (142,164), ImageObject on 36.29%, WebPage on 35.62%, and WebSite on 34.58%.

Among content-specific types, Question (19.52%), Answer (19.51%), and FAQPage (19.4%, 63,926 pages) edge out the bare Article type (16.21%, 53,416 pages) and more than double Product (8.03%, 26,476 pages) and ItemList (7.34%, 24,187 pages).

Top 20 JSON-LD Schema.org @type occurrences across 329,519 AI-cited pages

Share of cited pages (%) · Top 10 of 20

  • Organization50.86%
  • ListItem44.19%
  • BreadcrumbList43.14%
  • ImageObject36.29%
  • WebPage35.62%
  • WebSite34.58%
  • Person26.02%
  • Question19.52%
  • Answer19.51%
  • FAQPage19.4%
  • 0%20%40%60%
Explore the data (20 rows)
Organization167,57750.86
ListItem145,61144.19
BreadcrumbList142,16443.14
ImageObject119,57136.29
WebPage117,38735.62
WebSite113,94134.58
Person85,72526.02
Question64,31519.52
Answer64,29319.51
FAQPage63,92619.4
SearchAction60,51618.36
Article53,41616.21
EntryPoint49,83715.12
PostalAddress45,89613.93
ReadAction41,25612.52
Offer37,51711.39
ContactPoint36,60311.11
PropertyValueSpecification36,39611.05
Product26,4768.03
ItemList24,1877.34
Distinct cited HTML pages containing each @type inside parsed JSON-LD blocks, November 1 to November 19, 2026.

Takeaway

Even after Google scaled back FAQ rich snippets in classic SERPs, FAQPage markup still appears on nearly one in five AI-cited HTML pages.
  • Google Search Central: Changes to FAQ and HowTo rich results

Only 30.86% of cited pages carry an author byline and 41.92% expose a parsed date

While 70.86% (233,513) of cited HTML pages carry JSON-LD, explicit editorial signals are far less common. Only 30.86% (101,703 pages) expose an author byline in parsed HTML or metadata, and only 41.92% (138,147 pages: 119,966 with a published timestamp and 124,627 with a modified timestamp) expose a machine-readable page date.

Nearly three in five cited HTML pages (58.08%) carry no parsed published or modified date at all. Missing dates or author blocks do not disqualify documentation, product pages, or vendor homepages from earning citations.

Pages with JSON-LD schema
233,513

70.86% of 329,519 HTML pages

Pages with an author byline
101,703

30.86% of 329,519 HTML pages

Pages with a parsed date
138,147

41.92% (119,966 published; 124,627 modified)

Dated pages in 2005-2026 window
138,134

74.5 days median age (13 invalid dates excluded)

Takeaway

Bylines and timestamps are standard on publisher articles, yet well over half of all AI-cited pages earn citations without them.

Google AI Mode cites pages 79% older (101.9 days median) than Perplexity (56.8 days)

Across the 138,134 dated pages with valid published or modified timestamps between 2005 and November 2026, median page age at inspection is 74.5 days. Freshness differs sharply by engine.

Perplexity leans newest with a 56.8-day median (35.09% updated within 30 days and 61.68% within 90 days), followed by ChatGPT Search at 63.9 days (34.28% within 30 days and 57.58% within 90 days). Google AI Mode pulls a noticeably older mix at 101.9 days median (79% older than Perplexity), with only 26.47% within 30 days and 19.36% over one year old.

Share of dated AI-cited pages across content age brackets by engine

  • ChatGPT Search
  • Google AI Mode
  • Perplexity
Explore the data
<= 30d34.2826.4735.09
31-90d23.320.6626.59
91-180d14.8617.1715.21
181-365d12.5716.3312.96
1-2y6.859.785.58
2y+8.149.584.57
138,134 unique dated HTML pages (ChatGPT Search: 99,931; Google AI Mode: 44,046; Perplexity: 3,656), November 1 to November 19, 2026.

Takeaway

Perplexity and ChatGPT Search skew heavily toward pages updated in the last 90 days, while Google AI Mode keeps older evergreen pages in rotation longer.
  • Ahrefs: Do AI assistants prefer to cite fresh content?

Editorial pages turn over 4.7x faster (42.7 days median) than government sources (202.1 days)

Content age follows the publisher's update model more than a blanket AI recency rule. Across 16 source categories with at least 500 dated pages, editorial sites (42.7 days median; 80.83% within six months), directories (46.1 days), and blogs (52.4 days) carry the newest dates, followed by documentation (63.3 days) and SaaS sites (66.8 days).

At the other end, developer hubs (111.8 days), education sites (131.6 days), health publishers (160.9 days), social threads (192.9 days), government domains (202.1 days, 4.7x older than editorial), and community forums (240.3 days; 26.19% over two years old) stay cited years after publication.

Median content age and freshness shares across 16 source categories

Median age (days) · Top 10 of 16

  • community240.3
  • government202.1
  • social192.9
  • health160.9
  • education131.6
  • developer111.8
  • reference101.4
  • ecommerce91.2
  • news87.5
  • general77.4
  • 0100200300
Explore the data (16 rows)
editorial14,78542.740.9880.8390.595.2
directory3,11446.140.9176.2787.257.45
blog4,05052.437.0976.9988.596.59
documentation7,15763.334.9974.7885.936.29
saas37,99966.832.2973.2286.536.54
finance3,77572.831.6668.481.519.75
general33,41477.430.9269.6785.447
news5,66087.531.9365.2378.9912.49
ecommerce6,24791.233.0262.0373.5716.62
reference9,358101.426.3562.9476.4613.45
developer1,610111.826.0962.2481.749.5
education1,513131.623.1355.7271.3215.99
health1,865160.921.6652.8771.2116.41
social3,856192.915.1247.3869.0914.5
government2,498202.116.3746.5666.6520.06
community733240.315.1445.2957.1626.19
Source categories with at least 500 dated HTML pages (valid dates 2005 through Nov 2026), November 1 to November 19, 2026.

Takeaway

Keep editorial listicles and product blogs refreshed every 45 to 60 days, while preserving stable authoritative URLs for reference, docs, and health.

Multi-question news and editorial pages carry twice the FAQPage schema and length, while SaaS stays flat

Comparing pages cited for 1 question against workhorse pages cited for 3 or more questions within the same source type separates real signals from site-category averages. On news sites, 3+-question pages double FAQPage adoption (27.78% vs 13.84%) and run 75% longer in median markdown length (17,366 bytes vs 9,928 bytes). Editorial 3+-question pages rise to 93.54% JSON-LD, 49.35% FAQPage, and 20,349 bytes; blogs climb from 66.99% to 75.72% author bylines and 76.10% to 85.12% dates.

By contrast, SaaS and documentation show almost zero metadata lift from 1 question to 3+ questions. SaaS sits flat on JSON-LD (77.46% vs 77.74%), FAQPage (26.47% vs 27.14%), and length (7,952 vs 8,491 bytes), and documentation sits flat on author bylines (16.64% vs 17.24%) and FAQPage (1.55% vs 2.21%).

Metadata and page size by source type and question reach

Filter by source type to see how JSON-LD, FAQPage, bylines, dates, and page size change between 1-question and 3+-question pages.

FAQPage (%) · Top 10 of 21

  • editorial · 3+ questions49.35%
  • editorial · 2 questions47.83%
  • editorial · 1 question46.24%
  • blog · 2 questions39.3%
  • blog · 3+ questions38.44%
  • blog · 1 question35.34%
  • news · 3+ questions27.78%
  • saas · 2 questions27.73%
  • saas · 3+ questions27.14%
  • saas · 1 question26.47%
  • 0%20%40%60%
Explore the data (21 rows)
saas1 question53,41977.4626.4730.8845.927,952
ecommerce1 question29,23679.1112.4611.2315.445,379
documentation1 question17,97841.461.5516.6424.895,981
saas3+ questions17,57277.7427.1429.0244.748,491
saas2 questions12,96677.1927.7329.6245.038,260
editorial1 question11,88292.2346.2469.1481.616,738
directory1 question7,71774.9621.820.9329.968,521
documentation3+ questions5,93347.062.2117.2425.547,023
news1 question5,57980.6113.8455.5168.659,928
ecommerce2 questions4,93278.7914.4611.4818.215,584
ecommerce3+ questions4,74379.9315.819.4717.95,395
documentation2 questions4,38344.441.7317.2927.16,711
blog1 question3,86288.5335.3466.9976.112,454
editorial3+ questions3,23493.5449.3571.2186.6120,349
editorial2 questions2,86292.5647.8369.8883.8218,155
news3+ questions1,46585.5327.7852.972.917,366
directory3+ questions1,42080.2821.7619.7227.1111,926
directory2 questions1,38880.0424.6422.2631.7711,776
news2 questions1,16481.8721.0553.5269.7612,699
blog2 questions71088.5939.370.778.8714,808
blog3+ questions69292.6338.4475.7285.1215,454
Unique cited HTML pages (latest Nov 1 to Nov 19, 2026 observation with parsed metadata) grouped by distinct questions citing the URL (1, 2, or 3+ questions).

Takeaway

Longer guides with FAQPage and clear timestamps align with wider question reach on blogs, news, and editorial publishers, whereas SaaS and docs earn multi-question citations through product utility rather than extra schema.

Study scope and counting rules

This analysis inspects 329,519 unique AI-cited HTML pages drawn from each page's latest November 1 to November 19, 2026 fetch that returned parsed HTML metadata across organic ChatGPT Search (263,838 pages), Google AI Mode (79,824 pages), and Perplexity (5,371 pages) answers. Because an identical URL can be cited by more than one engine, per-engine page counts sum above the unique page total.

Schema.org @type counts inspect parsed JSON-LD blocks only; microdata and RDFa outside JSON-LD are not included. Effective page age uses the parsed modified timestamp falling back to published timestamp and covers 138,134 valid dated pages between January 1, 2005 and inspection time (excluding 13 out-of-range timestamps from the 138,147 pages with any parsed date). All metrics describe properties observed on cited pages and do not constitute a randomized test against uncited pages.

What to do with these numbers

Match your metadata work to your page type and target engine instead of bolting identical Article and FAQPage templates onto every URL. On vendor blogs, guides, and editorial comparisons, keep visible author bylines, valid published/modified timestamps, and structured Q&A blocks fresh inside a 45-to-60-day cadence, especially if Perplexity and Google AI Mode matter in your category.

On SaaS product pages and technical documentation, focus on Organization identity markup, Product/Offer clarity, and factual accuracy rather than inflating page length or forcing FAQPage schema where buyers only need crisp specs.

Metadata and freshness priorities by content layer

Technical documentation41.46% to 47.06% JSON-LD; 1.55% to 2.21% FAQPageUpdate specs on release rather than adding synthetic bylines or FAQ wrappers.
SaaS product and pricing pages77.7% JSON-LD; flat ~8 KB size across reach tiersKeep Organization and Product/Offer facts clean; avoid bloating product pages for length.
Perplexity and Google AI Mode targets44.77% to 55.35% author; 55.18% to 68.07% datedMake authorship and last-updated dates unambiguous in both visible HTML and JSON-LD.
Editorial guides and company blog89% to 94% JSON-LD; 42.7d to 52.5d median ageExpose Person author bylines, accurate modified dates, and FAQPage sections on multi-question guides.

Takeaway

Use schema, bylines, and update dates to keep guides and editorial pages machine-readable, and stop expecting template schema alone to lift thin product pages.
  • Plan structured content updates around AI citations
  • Schema markup implementation for AI visibility

How we measured

We analyzed 329,519 unique AI-cited HTML pages from their latest November 1 to November 19, 2026 crawl inspection across organic ChatGPT Search (263,838 pages), Google AI Mode (79,824 pages), and Perplexity (5,371 pages) answers. Content-age distributions cover 138,134 dated pages with valid HTML or JSON-LD dates between 2005 and November 2026.

AI-cited HTML pages carrying JSON-LD schema
70.86%

233,513 of 329,519 unique cited HTML pages

AI-cited HTML pages exposing an author byline
30.86%

101,703 of 329,519 pages (55.35% on Perplexity vs 26.42% on ChatGPT)

Median content age across 138,134 dated pages
74.5 days

41.92% of cited pages expose a parsed HTML or JSON-LD date

Cited pages carrying FAQPage schema
19.4%

63,926 pages, topping Article @type directly (16.21%)

Get the data

Full study dataset (CSV)All 63 rows across engines, top 20 Schema.org types, age distributions, source types, and multi-question reach tiers.

Sources

  1. Ahrefs: Does schema markup improve AI visibility? (opens in a new tab) · accessed November 20, 2026
  2. Ahrefs: Do AI assistants prefer to cite fresh content? (opens in a new tab) · accessed November 20, 2026
  3. Google Search Central: Changes to FAQ and HowTo rich results (opens in a new tab) · accessed November 20, 2026

More like this

How old are the pages AI cites?
45.1% of 769,006 AI citations with a structured publication date are over 1 year old, while 52.0% of modified-dated citations were updated within 90 days.
How long are the pages AI cites?
ChatGPT Search cited pages had a median length of 1,000 words vs 1,368 on Google AI Mode in Aug to Nov 2026, led by 3,098-word reviews and 1,026-word vendor sites.
Do FAQ pages get cited by AI?
Pages labeled as FAQs accounted for less than 1% of citation links in the answers we studied.
How long does AI take to notice a website change?
When AI-cited pages changed a dollar amount, only 26.5% of cases reached AI answers within 60 days, and 48.3% kept quoting the old one.
Noindex, JS walls, and canonical mismatches on 378,392 AI-cited pages
16.99% of 378,392 AI-cited pages failed simple direct HTTP fetch, while 2,392 cited HTML pages carried noindex and 7,533 carried cross-domain canonicals.
HTML token bloat vs. Markdown twins and llms.txt across 300 AI-cited sites
46.00% of 300 top AI-cited sites serve /llms.txt and 15.00% honor Accept: text/markdown, cutting median page weight 25.41x across 62 paired pages while 19.67% fail plain HTTP fetch.
For agents: this page as Markdown, https://parse.gl/research/schema-markup-bylines-and-freshness-in-ai-citations.md. JSON, MCP · free for the last 90 days, $0.01 a check
Open in ChatGPT (opens in a new tab) Open in Claude (opens in a new tab)

This page

As Markdown: https://parse.gl/research/schema-markup-bylines-and-freshness-in-ai-citations.md
As CSV: https://parse.gl/research/schema-markup-bylines-and-freshness-in-ai-citations/dataset.csv
Reuse: Figures and tables on this page are free to republish with attribution: a link to https://parse.gl/research/schema-markup-bylines-and-freshness-in-ai-citations beside them. A standard followed link (dofollow) is preferred.

Read and search

Any brand's shares and rivals, with 95% ranges: GET https://agent.parse.gl/v1/tools/check_brand?subject=%3Cbrand-domain%3E
Sample answers in a market: GET https://agent.parse.gl/v1/tools/search_answers?args=%7B%22filter%22%3A%7B%22market%22%3A%5B%22%3Cmkt_id%3E%22%5D%7D%7D
Cited pages in a market: GET https://agent.parse.gl/v1/tools/search_cited_pages?args=%7B%22filter%22%3A%7B%22market%22%3A%5B%22%3Cmkt_id%3E%22%5D%7D%7D
Search the index: GET https://parse.gl/api/public/search?q=<words>

Connect

Connect an assistant: https://agent.parse.gl/mcp

An agent can save work before signup: POST https://agent.parse.gl/v1/workspaces

What it costs

No account: Public figures and up to 5 examples per list, about 120 brands a day per address.
Free account: $5 in credit, your brand's first check (20 buyer questions) and a free weekly check.
After your first top-up: Exports and deeper search results. The first top-up starts at $5.
Live checks: $0.01 per question per engine.
Full public answers and pages: 25 free per day, then $0.005 each.
Public answers older than 90 days: $0.001 each the first time your workspace counts or lists one, then yours.

Prices: https://parse.gl/pricing.md

Map of the site: https://parse.gl/llms.txt

Audit schema, freshness, and metadata on the pages AI cites in your market

Start free in your browser.
Parse

Index

  • Brands
  • Markets
  • Topics
  • How we measure

For agents

  • Docs
  • Connect
  • Workflows
  • llms.txt

Parse

  • Use cases
  • Pricing
  • Research
  • Blog
  • Compare

Company

  • About
  • Contact
  • Corrections

© 2026 Parse, Inc. All rights reserved.

Privacy PolicyTerms of Service