Mobile Schema Markup
Ankit Agarwal · Head of Marketing
Mobile schema markup is structured data served on the mobile version of a page. There is no mobile-only schema; it must match desktop for mobile-first indexing.
What is Mobile Schema Markup?
Mobile schema markup refers to the structured data, usually written in JSON-LD using the Schema.org vocabulary, that appears on the mobile version of a web page. There is no mobile-specific schema type. Because Google indexes the mobile version of pages, structured data must be present and identical on mobile for the page to stay eligible for rich results.
The term is mostly relevant for sites with separate mobile templates or m-dot URLs, where markup is often forgotten. On responsive sites the same markup serves every device automatically.
In short, “mobile schema markup” is a parity check rather than a separate technique. The question to ask in every audit is whether Googlebot Smartphone sees the same JSON-LD as a desktop browser, with valid syntax and values that match what users see on the page.
How it works
Google’s mobile-first indexing guidance says:
- Make sure mobile and desktop versions have the same structured data.
- On separate mobile URLs, update URLs inside the structured data to the mobile URLs.
- Do not add structured data that describes content not visible on the mobile page.
A quick check process:
- Run key templates through the Rich Results Test, which uses a smartphone crawler by default.
- Use URL Inspection in Search Console to view the rendered HTML as Googlebot Smartphone.
- Monitor Search Console’s rich result reports for sudden drops after releases.
Examples
- For example, a SaaS blog’s mobile theme omits the Article and BreadcrumbList JSON-LD that the desktop theme includes. Breadcrumbs vanish from mobile and desktop results alike. Moving the markup into a shared layout fixes it.
- An events page loads Event schema with a tag manager script that times out on slow mobile connections. Rendering the JSON-LD server-side makes it reliable.
Best practices
- Put JSON-LD in shared layouts, not device-specific components.
- Render structured data server-side where possible rather than injecting it with tag managers.
- Keep markup consistent with visible content, including prices, ratings and dates.
- Validate with both Google’s Rich Results Test and the Schema.org validator.
Common mistakes
- Expecting FAQ or HowTo rich results that Google no longer shows for most sites.
- Marking up reviews or ratings that are not visible on the page.
Mobile Schema Markup and AI search
Structured data helps search engines and AI systems identify entities, products and authors on a page, which supports accurate descriptions in AI Overviews and assistant answers. It is not a guarantee of citation, but clean Organization and Product markup reduces ambiguity about who you are. See schema markup and entity optimization.
Related terms
Sources
Frequently asked questions
Is there a separate schema type for mobile pages?
No. Schema.org has no mobile-specific types, and Google does not require different markup for phones. 'Mobile schema markup' simply means making sure the mobile version of each page carries complete, valid structured data, because that is the version Google indexes.
Why did my rich results disappear?
Common causes include structured data present only on desktop templates, markup injected by a script that fails on mobile, policy changes (Google limited FAQ rich results to authoritative government and health sites and removed HowTo rich results in 2023), or markup that no longer matches visible content.
Which schema types matter for B2B SaaS?
Organization, WebSite, BreadcrumbList, Article or BlogPosting, SoftwareApplication or Product where appropriate, and Event or VideoObject for webinars and videos. FAQPage markup can still help other search engines and AI systems understand Q&A content even where Google no longer shows the rich result.
