browserRequirements

browserRequirements · Not mentioned by Google

Appears in

• WebApplication

What is it?

browserRequirements describes what a user's browser needs to run a web application. It is a plain text string that states runtime dependencies in human-readable form, such as "Requires JavaScript" or "Requires HTML5 support." This property helps search engines and AI systems understand the technical prerequisites before recommending an app to users.

Why this matters for AEO

When a user asks an AI engine "What do I need to run [app name]?", the AI looks for explicit requirement statements in structured data. browserRequirements provides that answer directly. Without it, the AI must scrape page copy or guess based on the app category. With it, AI engines can filter out apps that won't work in a user's environment and surface accurate compatibility info in conversational answers.

What the specs say

Schema.org: Text. Specifies browser requirements in human-readable text. For example, "requires HTML5 support." schema.org/browserRequirements

Google: Not mentioned. Field not listed in Google's structured data documentation for SoftwareApplication/WebApplication. Google Software App docs

How to find your value

• Dev team — Ask your frontend engineers what browser APIs the app depends on
• Docs — Check your app's system requirements or compatibility page
• Package.json — Look at browserslist or engine requirements
• Common values — "Requires JavaScript", "Requires HTML5 support", "Requires WebGL", "Chrome 90+"

Format and code

browserRequirements takes a plain Text value. List all browser-level requirements in a single string.

{
  "@context": "https://schema.org",
  "@type": "WebApplication",
  "name": "Cookie Creator",
  "url": "https://www.darrenscookies.com/cookie-creator",
  "description": "Create your own delicious cookie recipes with our fun cookie creator game!",
  "applicationCategory": "Game",
  "browserRequirements": "Requires JavaScript. Requires HTML5.",
  "softwareVersion": "1.0.0",
  "operatingSystem": "All"
}

Multiple requirements

Separate requirements with periods or commas within the same string:

{
  "@context": "https://schema.org",
  "@type": "WebApplication",
  "name": "DataViz Pro",
  "browserRequirements": "Requires JavaScript, HTML5 Canvas, and WebGL. Chrome 90+, Firefox 88+, or Safari 14+."
}

Webflow implementation

Static pages

Add JSON-LD in Page Settings > Custom Code (before </head>):

{
  "@context": "https://schema.org",
  "@type": "WebApplication",
  "name": "Your App Name",
  "url": "https://yoursite.com/app",
  "browserRequirements": "Requires JavaScript and HTML5 support"
}

CMS template pages

If listing multiple web apps via a CMS collection, create a plain text field for browser requirements and reference it in the JSON-LD embed on the collection template page.

In Schema HQ

browserRequirements is emitted in WebApplication schema when the field is populated in the page configuration. Enter the requirement string and it generates valid JSON-LD automatically.

Real examples

Darren Lester documents a Cookie Creator web app with explicit browser requirements:

{
  "@type": "WebApplication",
  "name": "Cookie Creator",
  "browserRequirements": "Requires JavaScript. Requires HTML5.",
  "operatingSystem": "All"
}

Source: darrenlester.com

Dan Taylor SEO recommends browserRequirements as a core property for SaaS subscription product schema:

{
  "@type": "WebApplication",
  "name": "SaaS Product",
  "browserRequirements": "Requires Javascript and HTML5 support"
}

Source: dantaylor.online

Related fields

• operatingSystem
• softwareVersion
• applicationCategory
• permissions

FAQ

Should I list specific browser versions in browserRequirements?

Only if your app genuinely requires a minimum version. Generic web apps that work on modern browsers are better served by "Requires JavaScript and HTML5 support." Adding version numbers creates maintenance overhead and can exclude users unnecessarily.

Is browserRequirements required for WebApplication schema?

No. Google does not mention it, and schema.org lists it as an optional property. However, it adds useful context for AI engines and improves the completeness of your WebApplication markup.