Skip to content

AI visibility

Do authorship and dates affect AI citations

Answer engines weight recency and attribution when choosing between sources that say similar things. An undated page loses to a dated one, and the fix is structured-data fields you already have the values for.

What 13x checks

This is rule aeo.author-and-freshness in the public registry: Authorship and freshness signals. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.

Surface
AI visibility
Score weight
4 of the readiness score
Scope
Reported as skipped when the page renders only with JavaScript
Applies
To every site

Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.

The fix

The same text the audit hands you when this check fails on your own site.

Add authorship and a modified date. For an article or a docs page:

html code
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "The page title",
  "author": { "@type": "Person", "name": "Your Name" },
  "publisher": { "@type": "Organization", "name": "example.com" },
  "datePublished": "2026-01-15",
  "dateModified": ""
}
</script>

Show the date visibly too — "Last updated " — because a reader deciding whether to trust the page looks for the same signal a model does.

Only claim a dateModified you actually change. A date bumped on every deploy while the content sits still is the kind of signal that gets discounted.

Framework-specific versions

Where the change differs enough to be worth writing out separately.

Does your site have this problem?

13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.

No signup. Results in 30 seconds.

More ai visibility checks