Monitor JSON-LD Schema Changes with Apify in n8n

Detect JSON-LD and structured data regressions every day—using Apify inside n8n

This n8n workflow monitors your selected URLs (and optional sitemaps) for JSON-LD, Microdata, and RDFa schema markup changes. It runs daily and outputs only negative results—such as removed schema types, new issue codes, score drops, or HTTP errors—so you can quickly catch SEO-impacting issues.

What this workflow does

• Schedules a daily run to audit the configured targets once per day.
• Reads configuration inputs including the target page URLs, optional sitemap URLs, a state namespace, first-run behavior, and a maximum page limit.
• Uses Apify’s Structured Data Change Monitor actor to check each page’s structured data and store state for comparison.
• Filters results to regressions only, including:
  • Removed schema types
  • New issue codes
  • Decreased scores
  • HTTP status errors
• Outputs a trimmed record per affected page containing the URL, final URL, status code, title, score fields, schema types removed, new issue codes, and issue details for downstream alerting or tracking.

Use cases

• SEO monitoring for SaaS products: catch structured data regressions when templates, CMS content, or deployments change.
• Site quality assurance: detect markup issues early by watching JSON-LD schema type removals and score drops.
• Automation engineers’ alerting pipelines: feed only negative structured data changes into your existing incident tracking.

Technical details

• Verified node: @apify/n8n-nodes-apify (install if needed in your n8n instance)
• Integrates with Apify via your Apify API token credential
• Uses n8n nodes including Schedule Trigger, Apify node, and supporting nodes such as set, code, and sticky note

Run once to establish a baseline (when configured), then enable the workflow to monitor your structured data changes daily.