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

> 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%).

HTML: https://parse.gl/research/schema-markup-bylines-and-freshness-in-ai-citations · Site index: https://parse.gl/llms.txt · Published: 2026-11-20

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.

## Key figures

- **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%))

## 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.

**Structured metadata presence on AI-cited HTML pages by engine**

| Item | Value |
| --- | --- |
| Any JSON-LD: ChatGPT Search | 69.48% |
| Any JSON-LD: Google AI Mode | 75.86% |
| Any JSON-LD: Perplexity | 85.55% |
| Article family schema: ChatGPT Search | 20.83% |
| Article family schema: Google AI Mode | 38.23% |
| Article family schema: Perplexity | 52.71% |
| Author byline: ChatGPT Search | 26.42% |
| Author byline: Google AI Mode | 44.77% |
| Author byline: Perplexity | 55.35% |
| Any parsed date: ChatGPT Search | 37.88% |
| Any parsed date: Google AI Mode | 55.18% |
| Any parsed date: Perplexity | 68.07% |

_329,519 unique cited HTML pages inspected November 1 to November 19, 2026 (pages cited by multiple engines count in each engine row)._

> Perplexity cites pages with author bylines and dates at roughly double ChatGPT Search's rates, reflecting its heavier pull toward editorial and news sources.

## 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**

| Engine | HTML pages | JSON-LD (%) | Article (%) | FAQPage (%) | Product (%) | Review (%) | Byline (%) | Dated (%) |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| ChatGPT Search | 263838 | 69.48 | 20.83 | 19.38 | 14.15 | 7.79 | 26.42 | 37.88 |
| Google AI Mode | 79824 | 75.86 | 38.23 | 19.91 | 10.68 | 6.26 | 44.77 | 55.18 |
| Perplexity | 5371 | 85.55 | 52.71 | 30.7 | 14.17 | 9.2 | 55.35 | 68.07 |

_Rates measured on unique cited HTML pages per engine, November 1 to November 19, 2026._

> 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**

| Schema.org @type | Cited HTML pages | Share of cited pages (%) |
| --- | --- | --- |
| Organization | 167577 | 50.86 |
| ListItem | 145611 | 44.19 |
| BreadcrumbList | 142164 | 43.14 |
| ImageObject | 119571 | 36.29 |
| WebPage | 117387 | 35.62 |
| WebSite | 113941 | 34.58 |
| Person | 85725 | 26.02 |
| Question | 64315 | 19.52 |
| Answer | 64293 | 19.51 |
| FAQPage | 63926 | 19.4 |
| SearchAction | 60516 | 18.36 |
| Article | 53416 | 16.21 |
| EntryPoint | 49837 | 15.12 |
| PostalAddress | 45896 | 13.93 |
| ReadAction | 41256 | 12.52 |
| Offer | 37517 | 11.39 |
| ContactPoint | 36603 | 11.11 |
| PropertyValueSpecification | 36396 | 11.05 |
| Product | 26476 | 8.03 |
| ItemList | 24187 | 7.34 |

_Distinct cited HTML pages containing each @type inside parsed JSON-LD blocks, November 1 to November 19, 2026._

> Even after Google scaled back FAQ rich snippets in classic SERPs, FAQPage markup still appears on nearly one in five AI-cited HTML pages.

## 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
- **Pages with an author byline:** 101,703
- **Pages with a parsed date:** 138,147
- **Dated pages in 2005-2026 window:** 138,134

> 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**

| ageBucket | ChatGPT Search | Google AI Mode | Perplexity |
| --- | --- | --- | --- |
| <= 30d | 34.28% | 26.47% | 35.09% |
| 31-90d | 23.3% | 20.66% | 26.59% |
| 91-180d | 14.86% | 17.17% | 15.21% |
| 181-365d | 12.57% | 16.33% | 12.96% |
| 1-2y | 6.85% | 9.78% | 5.58% |
| 2y+ | 8.14% | 9.58% | 4.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._

> 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.

## 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**

| Source type | Dated pages | Median age (days) | <= 30d (%) | <= 6m (%) | <= 1y (%) | Over 2y (%) |
| --- | --- | --- | --- | --- | --- | --- |
| editorial | 14785 | 42.7 | 40.98 | 80.83 | 90.59 | 5.2 |
| directory | 3114 | 46.1 | 40.91 | 76.27 | 87.25 | 7.45 |
| blog | 4050 | 52.4 | 37.09 | 76.99 | 88.59 | 6.59 |
| documentation | 7157 | 63.3 | 34.99 | 74.78 | 85.93 | 6.29 |
| saas | 37999 | 66.8 | 32.29 | 73.22 | 86.53 | 6.54 |
| finance | 3775 | 72.8 | 31.66 | 68.4 | 81.51 | 9.75 |
| general | 33414 | 77.4 | 30.92 | 69.67 | 85.44 | 7 |
| news | 5660 | 87.5 | 31.93 | 65.23 | 78.99 | 12.49 |
| ecommerce | 6247 | 91.2 | 33.02 | 62.03 | 73.57 | 16.62 |
| reference | 9358 | 101.4 | 26.35 | 62.94 | 76.46 | 13.45 |
| developer | 1610 | 111.8 | 26.09 | 62.24 | 81.74 | 9.5 |
| education | 1513 | 131.6 | 23.13 | 55.72 | 71.32 | 15.99 |
| health | 1865 | 160.9 | 21.66 | 52.87 | 71.21 | 16.41 |
| social | 3856 | 192.9 | 15.12 | 47.38 | 69.09 | 14.5 |
| government | 2498 | 202.1 | 16.37 | 46.56 | 66.65 | 20.06 |
| community | 733 | 240.3 | 15.14 | 45.29 | 57.16 | 26.19 |

_Source categories with at least 500 dated HTML pages (valid dates 2005 through Nov 2026), November 1 to November 19, 2026._

> 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**

| Source type | Question reach | Pages | JSON-LD (%) | FAQPage (%) | Author (%) | Dated (%) | Median bytes |
| --- | --- | --- | --- | --- | --- | --- | --- |
| blog | 1 question | 3862 | 88.53 | 35.34 | 66.99 | 76.1 | 12454 |
| blog | 2 questions | 710 | 88.59 | 39.3 | 70.7 | 78.87 | 14808 |
| blog | 3+ questions | 692 | 92.63 | 38.44 | 75.72 | 85.12 | 15454 |
| directory | 1 question | 7717 | 74.96 | 21.8 | 20.93 | 29.96 | 8521 |
| directory | 2 questions | 1388 | 80.04 | 24.64 | 22.26 | 31.77 | 11776 |
| directory | 3+ questions | 1420 | 80.28 | 21.76 | 19.72 | 27.11 | 11926 |
| documentation | 1 question | 17978 | 41.46 | 1.55 | 16.64 | 24.89 | 5981 |
| documentation | 2 questions | 4383 | 44.44 | 1.73 | 17.29 | 27.1 | 6711 |
| documentation | 3+ questions | 5933 | 47.06 | 2.21 | 17.24 | 25.54 | 7023 |
| ecommerce | 1 question | 29236 | 79.11 | 12.46 | 11.23 | 15.44 | 5379 |
| ecommerce | 2 questions | 4932 | 78.79 | 14.46 | 11.48 | 18.21 | 5584 |
| ecommerce | 3+ questions | 4743 | 79.93 | 15.81 | 9.47 | 17.9 | 5395 |
| editorial | 1 question | 11882 | 92.23 | 46.24 | 69.14 | 81.6 | 16738 |
| editorial | 2 questions | 2862 | 92.56 | 47.83 | 69.88 | 83.82 | 18155 |
| editorial | 3+ questions | 3234 | 93.54 | 49.35 | 71.21 | 86.61 | 20349 |
| news | 1 question | 5579 | 80.61 | 13.84 | 55.51 | 68.65 | 9928 |
| news | 2 questions | 1164 | 81.87 | 21.05 | 53.52 | 69.76 | 12699 |
| news | 3+ questions | 1465 | 85.53 | 27.78 | 52.9 | 72.9 | 17366 |
| saas | 1 question | 53419 | 77.46 | 26.47 | 30.88 | 45.92 | 7952 |
| saas | 2 questions | 12966 | 77.19 | 27.73 | 29.62 | 45.03 | 8260 |

Showing 20 of 21 rows (Reach breakdown). Full CSV: /research/schema-markup-bylines-and-freshness-in-ai-citations/dataset.csv

_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)._

> 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**

| Site section | Study benchmark | Recommended focus |
| --- | --- | --- |
| Editorial guides and company blog | 89% to 94% JSON-LD; 42.7d to 52.5d median age | Expose Person author bylines, accurate modified dates, and FAQPage sections on multi-question guides. |
| SaaS product and pricing pages | 77.7% JSON-LD; flat ~8 KB size across reach tiers | Keep Organization and Product/Offer facts clean; avoid bloating product pages for length. |
| Technical documentation | 41.46% to 47.06% JSON-LD; 1.55% to 2.21% FAQPage | Update specs on release rather than adding synthetic bylines or FAQ wrappers. |
| Perplexity and Google AI Mode targets | 44.77% to 55.35% author; 55.18% to 68.07% dated | Make authorship and last-updated dates unambiguous in both visible HTML and JSON-LD. |

> 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.

Related: [Plan structured content updates around AI citations](https://parse.gl/use-cases/plan-content) · [Schema markup implementation for AI visibility](https://parse.gl/blog/schema-markup-ai-visibility-implementation)

## Method

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.

## Data

- [Full study dataset (CSV)](https://parse.gl/research/schema-markup-bylines-and-freshness-in-ai-citations/dataset.csv): All 63 rows across engines, top 20 Schema.org types, age distributions, source types, and multi-question reach tiers.

## Sources

- [Ahrefs: Does schema markup improve AI visibility?](https://ahrefs.com/blog/schema-ai-citations/)
- [Ahrefs: Do AI assistants prefer to cite fresh content?](https://ahrefs.com/blog/do-ai-assistants-prefer-to-cite-fresh-content)
- [Google Search Central: Changes to FAQ and HowTo rich results](https://developers.google.com/search/blog/2023/08/howto-faq-changes?hl=en)

## For agents

- [Study dataset (CSV)](https://parse.gl/research/schema-markup-bylines-and-freshness-in-ai-citations/dataset.csv)
- Any brand's shares and rivals, with 95% ranges: `https://agent.parse.gl/v1/tools/check_brand?subject=%3Cbrand-domain%3E`
- Sample answers in a market: `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: `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: `https://parse.gl/api/public/search?q=<words>`

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.

- 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 ($0.05 on Gemini and Claude).
- 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.
- An agent can save work before signup: `POST https://agent.parse.gl/v1/workspaces`
- Connect an assistant: `https://agent.parse.gl/mcp`

[Prices](https://parse.gl/pricing.md) · [Map of the site](https://parse.gl/llms.txt)
