Which privacy and language fields are documented for MathSolver?

Definition: In Google's MathSolver structured data, usageInfo identifies the privacy policy for the math problem solving site, while inLanguage identifies the language or languages the site supports. Google lists usageInfo as required and inLanguage as recommended.

Key facts

• Google's MathSolver structured data documentation places usageInfo under required properties and gives it the type URL.
• The same documentation defines usageInfo as the privacy policy for the math problem solving site.
• Google places inLanguage under recommended properties and describes it as the language or languages supported by the site.
• Schema.org's usageInfo definition describes further information about a CreativeWork and allows a CreativeWork or URL as the value.
• Schema.org's inLanguage definition asks authors to use a language code from the IETF BCP 47 standard.

What does usageInfo identify?

Google documents usageInfo as a required MathSolver property with the type URL. Its description is specific: “The privacy policy for your math problem solving site.” A MathSolver implementation therefore uses this field for the URL of the site's privacy policy.

Schema.org gives the property a wider meaning across CreativeWork: it can point to further information, including purchasing details or resource-specific licensing options. The same Schema.org page says that usageInfo can be used alongside license, which identifies licenses applying to content. Google's MathSolver definition selects the privacy policy meaning for this structured data type.

{
  "@type": ["MathSolver", "LearningResource"],
  "url": "https://www.mathdomain.com/",
  "usageInfo": "https://www.mathdomain.com/privacy"
}

The URL in Google's example uses a /privacy path. The example shows the field as a string URL inside the MathSolver object.

What does inLanguage describe?

Google lists inLanguage as a recommended MathSolver property with the type Text. The documentation describes it as “The language(s) that are supported by your math problem solving site” and points to a table of possible languages. It shows "en" for an English solver and "es" for a Spanish solver.

Schema.org defines inLanguage as the language of content, a performance, or an action. It directs authors to use one of the language codes from the IETF BCP 47 standard. For MathSolver markup, this makes the value a language identifier for the solver's supported interface or solving resource, with the code format guided by that standard.

Google's bilingual home page example contains two MathSolver objects. One uses the English name, URL, privacy URL, and inLanguage: "en"; the other uses Spanish equivalents and inLanguage: "es". Google also says the Spanish markup could be placed directly on the Spanish URL instead of beside the English markup.

How should both fields appear in JSON-LD?

The two fields can appear in the same MathSolver object. The privacy field is a URL, and the language field is a text code. Google's example includes them with the solver name and URL:

{
  "@context": "https://schema.org",
  "@type": ["MathSolver", "LearningResource"],
  "name": "An awesome math solver",
  "url": "https://www.mathdomain.com/",
  "usageInfo": "https://www.mathdomain.com/privacy",
  "inLanguage": "en"
}

These fields sit alongside the other MathSolver properties in Google's example, including potentialAction and learningResourceType. usageInfo addresses the site's privacy policy. inLanguage adds the supported language information that Google marks as recommended.

How can you check the fields?

Google's MathSolver documentation includes the Rich Results Test in its structured data workflow. It says to validate the code with that test and fix critical errors. The documentation also recommends deploying a few pages containing the structured data and using the URL Inspection tool to test how Google sees the page. A site can check that its MathSolver object contains the privacy policy URL and the intended language code before deployment.

Related terms

• Structured data
• JSON-LD
• HTML lang attribute

FAQ

Is usageInfo required for MathSolver?

Yes. Google lists it among the required MathSolver properties and defines its value as the URL of the privacy policy for the math problem solving site.

Is inLanguage required for MathSolver?

Google lists inLanguage as a recommended property. It describes the language or languages supported by the math problem solving site and shows language codes such as en and es in its examples.

Can one MathSolver describe more than one language?

Google's example represents English and Spanish with two MathSolver objects. It also says the Spanish markup could be placed directly on the Spanish URL.

Is usageInfo the same as license?

No. Schema.org describes usageInfo as further information about a CreativeWork and says it can be used alongside license. Google's MathSolver documentation assigns usageInfo the narrower privacy policy role.

Sources

1. Google Search Central, "Math solver (MathSolver) structured data", 18 December 2025
2. Schema.org, "usageInfo", 16 September 2026
3. Schema.org, "inLanguage", 16 September 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer