Passer au contenu
SilktideAide

AI schema signals

Silktide checks that pages which already describe themselves with structured data include two fields AI assistants and search engines rely on: when content was last updated, and links to your organization's verified profiles.

This check never nags pages that have no at all. It only fires when you have already declared an Article or Organization entity in but omitted a field answer engines use heavily:

  • dateModified on Article, NewsArticle, or BlogPosting - the freshness signal.
  • on Organization - links your official profiles so engines can confirm who you are.

Both fields are recommended rather than required, so a finding is a warning, not an error.

Why this matters

AI-generated answers increasingly cite web sources, and the engines behind them weight recency and identity confidence heavily. A well-maintained dateModified tells them the content is current; sameAs links connect your brand to verifiable profiles such as Wikipedia, LinkedIn, and official social accounts, so the engine can be confident it is citing the real you.

Since these fields go into schema you already maintain, adding them is low effort with a disproportionate payoff for answer-engine visibility.

How to fix it

Add the missing field to the schema block the finding names:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Example article",
  "datePublished": "2026-05-01",
  "dateModified": "2026-07-10"
}
</script>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Company",
  "sameAs": [
    "https://en.wikipedia.org/wiki/Example_Company",
    "https://www.linkedin.com/company/example"
  ]
}
</script>

Most platforms generate this markup from a plugin or theme setting, so the fix is often filling in a profile URL or enabling modified dates rather than editing code. Keep dateModified honest - update it when the content genuinely changes.

How Silktide tests this

  1. Test only indexable pages that contain at least one JSON-LD block.
  2. If an Article, NewsArticle, or BlogPosting schema is present without a non-empty dateModified, flag the page.
  3. Otherwise, if an Organization schema is present without a non-empty sameAs, flag the page.
  4. Report at most one finding per page, in that priority order.

An author's Person schema is not checked for sameAs. It can help, but plenty of good pages have authors with no public profiles to link.

Troubleshooting

My page has no structured data and was not flagged

That is by design. Whether a given page should carry schema at all is a contextual judgment, so this check only improves schema you have already chosen to publish.

I fixed one field and a different finding appeared

The check reports one finding per page in priority order, so resolving the dateModified finding can reveal a sameAs finding on the same page. Each points at a real missing signal.

Learn more

Dernière mise à jour

Cette page vous a-t-elle été utile?