🔍 What Does the 'offers': null Error Mean?

When OTTO generates schema markup for your pages, it pulls structured data from the content it finds on that page. If OTTO detects a Product Schema on your page but cannot find pricing, availability, or offer-related content, it inserts 'offers': null as a placeholder in the generated schema.

This is not a system crash or a bug — it means OTTO found a schema type that typically includes an Offers field, but the corresponding data was either absent from the page or not yet provided. Search engines like Google may flag a null Offers field as incomplete structured data, which is why it surfaces as an error in your schema report.

📋 Understanding OTTO Schema States: 'Review' vs. 'FOUND'

OTTO assigns each schema one of two states to help you manage your markup:

• Review — OTTO has drafted a schema based on page content, but it requires your approval before being applied. Fields may be incomplete.
• FOUND — OTTO has detected an existing schema already present on the page (e.g., hardcoded in your theme or CMS). OTTO surfaces it so you can see and manage it, but it originates from your site's existing code.

A common point of confusion: customers are sometimes told that FOUND schemas cannot be edited or removed. This is incorrect. Both Review and FOUND schemas can be managed within OTTO — you can edit individual fields, leave non-applicable fields empty where acceptable, or work with your developer to remove hardcoded schemas from the source if needed.

⚙️ How OTTO Auto-Populates the Offers Field

When you click Regenerate on a schema, OTTO re-scans the page and attempts to pull fresh data. Here is what happens depending on your page content:

• If pricing or offer data exists on the page — OTTO will auto-populate the Offers field with values it finds (price, currency, availability, etc.).
• If no offer data exists on the page — OTTO will again return 'offers': null. Regenerating alone will not fix this if the underlying page content does not include offer information.

Regeneration is a useful first step, but it is not a guaranteed fix. If your page genuinely does not contain product pricing or availability, you have additional options outlined below.

✅ When Is an Empty or Null Offers Field Acceptable?

Not every business sells products or services with listed prices. If the Offers field does not apply to your page or business model, leaving it null or omitting it entirely is often acceptable. Consider the following:

• Google's structured data guidelines do not require an Offers field for all Product schemas, but they do recommend it for better eligibility in rich results like price snippets.
• A null Offers field will typically generate a warning rather than a critical error in Google Search Console, meaning your schema is still valid — just not fully enhanced.
• If the Offers field genuinely does not apply to your business (e.g., you list products but handle pricing offline or via inquiry), it is safe to remove or omit this field.

🛠️ How to Resolve the 'offers': null Error in OTTO

Follow the steps below based on your situation:

1. Go to the left sidebar and select OTTO SEO, then navigate to your schema markup section within OTTO.
2. Locate the schema showing the 'offers': null error and open it for editing.
3. Option A — Your page has pricing data: Click Regenerate to prompt OTTO to re-scan the page. If pricing, availability, or offer details are present in your page content, OTTO will auto-populate the Offers field. Review the result and approve the schema.
4. Option B — You want to add offers manually: Instead of regenerating, click into the schema editor and manually enter the Offers details — including price, price currency, and availability. This is the most reliable method when your page content is minimal or structured in a way OTTO cannot easily parse.
5. Option C — Offers do not apply to your business: In the schema editor, you can clear the Offers field entirely or remove that property from the schema. An empty or omitted Offers field will not break your schema — it will simply not qualify for offer-related rich result features. Save and approve the updated schema.

🔗 Note: Relative vs. Absolute URLs in Schema

Some customers experiencing schema errors alongside the null Offers issue have also encountered a separate problem: OTTO or an existing schema may be generating relative URLs (e.g., /products/item) instead of absolute URLs (e.g., https://www.yoursite.com/products/item) in fields like url or image. Search engines require absolute URLs in structured data. If you notice URL-related warnings in Google Search Console alongside your schema errors, check that all URL fields in your schema use the full absolute format including the protocol and domain.

💡 Quick Reference: Which Option Should I Use?

• Page has pricing content but offers show null → Regenerate the schema, then review and approve.
• Page content is sparse or OTTO cannot detect pricing → Manually enter Offers details in the schema editor.
• Offers do not apply to your business or page → Clear or omit the Offers field; this is safe and will not invalidate your schema.
• Schema is marked FOUND and appears hardcoded → Edit the field in OTTO, or work with your developer to update the source code directly.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.