Ecommerce SEO
Product Metadata
Product Metadata is the governed set of fields that identifies and describes a product, its offer and its search presentation across the page, structured data and connected merchant systems.
What it means
The set can include product name, brand, identifiers, category, variant attributes, Title tag, Meta description, image information, price, currency, availability and Canonical URL. These fields have different owners and refresh rates: Google may generate title links and snippets from multiple page sources, while Product and Offer properties must remain accurate for their documented use.
Why it matters
Field-level provenance prevents a polished title from masking stale stock, mismatched identifiers or a feed and page that describe different variants.
Example
A shoe SKU record assigns the catalogue system as owner of GTIN, colour and size, the commerce platform as owner of price and stock, and the CMS as owner of title and description; a publish check rejects conflicting values.
Common mistakes
Do not reduce metadata to two meta tags, generate identifiers, reuse one description across variants, hide outdated availability, stuff title tags, assume Google must display supplied text or update fields without an owner.
How AYSA handles this
Signals reviewed
field name, field value, source system, owner, refresh time, variant key, page value, markup value
Problem AYSA can identify
AYSA can detect duplicate titles, missing field owners, impossible identifiers and page, schema or merchant values that disagree.
Recommendation prepared
The proposal assigns authoritative sources and corrects only the fields that fail uniqueness, accuracy or synchronization checks.
Approval preview
The reviewer sees field-level before and after values, provenance, affected SKUs, generated-text labels and rollback data.
Execution
AYSA can update approved metadata in supported systems; authoritative price, stock and catalogue identifiers cannot be invented.
Verification
A post-publish comparison reconciles source, rendered page, canonical, structured data and connected merchant values by SKU or variant.
Limits
AYSA's evidence is page- and workflow-bound; automated recommendations, generated text and review logs do not automatically certify AI Act or legal compliance, and applicable Article 50 duties require a separate role-and-use assessment from 2 August 2026.
Sources and further reading
- Google Search Central — Influencing title links — Official search documentation
- Google Search Central — Control snippets and meta descriptions — Official search documentation
- Google Search Central — Introduction to Product structured data — Official search documentation
- Google Search Central — Merchant listing structured data — Official search documentation
- Schema.org — Product — Schema.org vocabulary
- European Commission — AI Act Article 50 transparency guidelines — Official European Commission guidance
Written by Marius Dosinescu. Reviewed by AYSA SEO Editorial Team · 2026-07-28 00:00:00.
Quick answers
Frequently asked questions
Is Product Metadata only the title tag and meta description?
No. It can also include identifiers, attributes, offer data, images, canonical URL and structured fields.
Will Google always display the supplied product title and description?
No. Google can generate title links and snippets from multiple sources on the page and web.
SEO execution campaign
Less SEO work. More organic growth.
AYSA monitors your website, finds opportunities, prepares the work, asks for approval and executes accepted changes so you can grow without living in SEO tools.
