Note: This page has been machine-translated. In case of doubt, the German version shall prevail.
The silent problem: Schema.org ages unnoticed
Imagine you carefully built @type: Product, name, brand, price and availability into your Schema.org markup two years ago. Google says "great", the Rich Results Test gives the green light. You check it off.
Two years later, someone asks ChatGPT: "Which lawn mower is quiet and suitable for 300m²?" ChatGPT looks for noise level in decibels, maximum area, battery runtime and a mulching function. Your markup has none of them. A competitor who keeps their Schema.org current names all four values. They get recommended. You don't.
AI systems like ChatGPT, Perplexity and Gemini continuously look for ever more specific product attributes. What counted as complete schema in 2024 is incomplete in 2026. Whoever doesn't keep up loses reach, silently and gradually.
Why Schema.org goes stale without you noticing
Schema.org itself barely changes. But the expectations of the AI systems change constantly, driven by:
- New search trends: Users ask AI ever more detailed questions. "Which vacuum cleaner has a HEPA filter and is suitable for pet hair?" was still rare in 2022; today it's standard.
- New product categories: E-mobility, AI-powered devices, sustainability details — new fields emerge, old ones gain importance.
- Competition: When your competitor adds fields you don't have, AI systems favor their more precise data for identical queries.
- AI model updates: GPT-4o, Perplexity Sonar Pro, Gemini 2.0 — every new version understands and weights fields differently.
The result: your Schema.org markup is technically valid but outdated in substance. The Rich Results Test still says "okay", but AI recommendations become rarer.
Why manual upkeep takes so much effort
It can be done by hand, but in day-to-day work there is rarely time for it. The table shows how much effort is involved:
| Task | Manual | With Feed-AI |
|---|---|---|
| Knowing the current AI fields | Hours of research per category | Automatic weekly scan |
| Spotting missing fields | Manual comparison, error-prone | Automatic check across all categories |
| Notifying users | Doesn't scale beyond 100+ products | Automatic email with the exact fields |
| Checking whether fields are filled | Manual, one product at a time | Dashboard badge " Update fields" |
| Time required | Several hours/month | Automatic check, fields completed in the form |
Whoever manages 10 products in 3 categories can theoretically still handle it by hand. Whoever has 50 or 500 products cannot. And even with 10 products: who really remembers every month to check what AI systems currently need?
How AI systems penalize incomplete data
AI systems like ChatGPT, Perplexity and Gemini work on a simple principle: the source with the most complete, most precise information wins.
When a user asks "Which fully automatic coffee machine has a built-in grinder and costs under €600?", here's what happens:
The AI looks for products with these attributes
Grinder present (bool), price (number), type (enum: fully automatic). AI systems prioritize sources that provide these fields in structured form.
Comparison of the available sources
Source A has: name, price — but no grinder field. Source B has: name, price, grinder: "yes", type: "fully automatic", milk system, warranty. Source B wins.
Source B gets recommended
The AI cites Source B's product because it can answer the query completely. Source A isn't worse — it just has an outdated schema.
This isn't about having a better product. It's about the AI knowing that your product meets the query. Whoever doesn't communicate that won't get found, regardless of product quality.
Step by step: how to keep Schema.org current
For anyone who wants to tackle it manually, here's the guide:
Take stock: which fields do you currently have?
Check your Schema.org markup with the Google Rich Results Test. Note every field present. That's your starting point.
Actively query the AI systems
Ask ChatGPT or Perplexity: "Which properties do you mention when someone asks for the best [your category]?" The attributes in the answer are the fields you need.
Add and fill the missing fields
Close the gaps. Priority goes to fields with direct purchasing impact: price, availability, specific technical properties, warranty, certifications.
Set a repeat interval
Schedule this check at least quarterly. Better: monthly. Best of all: automatically — for example with the Feed-AI freshness check, which automates the check and notifies you of missing fields.
How Feed-AI detects and flags missing fields
Feed-AI is an AI visibility platform for manufacturers, retailers and service providers. Once entered, Feed-AI checks every week which fields are currently relevant to AI and tells you when your listings should be updated.
It works in three stages:
AI Field Scout — weekly scan
Every Monday, Feed-AI analyzes via the Perplexity search engine which product attributes AI systems currently query for each category. The result is automatically compared against the existing fields.
Freshness check — automatic notification
When missing fields are detected, affected users receive an email: "New fields are available for your products — please add them for the best AI hit rate." Dashboard note included.
Add once, markup gets updated
Users fill in the suggested fields in the form. From that, Feed-AI automatically generates updated Schema.org markup on the product page, fully crawlable for GPTBot, PerplexityBot and all other AI crawlers.
Feed-AI includes an automatic freshness check in every plan. It runs weekly, detects field gaps across categories and notifies users proactively, so they don't have to do anything to discover the problem.
The reality: even pros make this mistake
In the classic SEO world, Schema.org is seen as a one-time technical task: set it up, done. That mindset is defensible for Google SEO — Google's algorithm rarely changes its field preferences radically.
With AI systems it's different. ChatGPT, Perplexity and Gemini are large language models that are continuously updated and learn from live web searches. Their "expectations" of structured data evolve with every update.
An electrician set up their Schema.org markup carefully in 2023: name, location, type of service. Excellent for the time. In 2026, Perplexity regularly asks for the following on electrician queries: response time, emergency service, master craftsman business, liability insurance, guild membership. None of these fields were in the 2023 markup. The result: competitors with more complete markup may be named more readily for comparable queries.
Frequently asked questions
Why isn't it enough to set up Schema.org once? +
AI systems like ChatGPT and Perplexity keep learning and look for ever more specific product attributes. What counted as complete schema in 2024 can already be incomplete in 2026 — for example because new fields like energy efficiency class, sustainability details or AI compatibility became relevant. Outdated Schema.org data is used less often by AI systems as a source for answers.
How do you notice that your own Schema.org has gone stale? +
That's the tricky part: you usually don't notice it right away. The AI hit rate declines gradually over months. Only a direct comparison with competitors or a structured AI visibility check makes the problem visible. Feed-AI runs this check automatically every week and notifies users when new relevant fields are detected.
Which Schema.org fields matter most to AI in 2026? +
For products: name, brand, description, offers (price, currency, availability), aggregateRating, image. Plus, depending on category: warranty, technical specifications, energy efficiency, delivery time. For services: areaServed, serviceType, priceRange, certifications, response time. AI systems place the most weight on specific, measurable attributes.
What is the Feed-AI freshness check? +
The Feed-AI freshness check is a weekly automatic scan. It compares the product attributes AI systems currently query against the existing fields of a listing. If important fields are missing, users receive an automatic notification with concrete improvement suggestions — they then add the fields themselves in the form.
How long does it take for stale data to measurably affect AI visibility? +
There is no fixed timeframe. AI systems crawl and refresh their knowledge at different intervals; GPTBot, PerplexityBot and Googlebot visit active pages partly on a weekly basis. If a competitor provides more complete data, it may be named more readily for comparable queries. The effect usually sets in gradually, which is why it is rarely noticed right away.
Is Feed-AI only for large companies? +
No. Feed-AI is aimed at manufacturers, retailers and service providers of every size — from retail to the hair salon to the SaaS vendor. The Starter plan at €19/month is designed for up to 10 products or services.