What is WebPageElement structured data, and how do you use it?

What types of web page elements can you mark up?

WebPageElement structured data covers individual parts of a page rather than the whole document. Schema.org defines a web page element as a discrete unit on a page, such as a table or an image. More specific subtypes exist to represent structural components, including WPHeader for page headers, WPFooter for footers, WPSideBar for sidebars, and SiteNavigationElement for site navigation blocks.

Adding structured data provides a standardized format for providing information about a page and classifying page content. Google uses structured data on the web to understand page content and gather information about entities like people, books, or companies. Providing this context can enable rich results that create more engaging search listings and encourage users to interact with a site.

How do CSS selectors and XPaths identify page elements?

Structured data definitions for web page elements rely on precise technical locators to pinpoint content in the page layout. Schema.org specifications allow you to identify elements using either a CSS selector or an XPath. These locators tell automated parsers exactly where a given element resides inside the document object model.

In many web layouts, a single conceptual component consists of distinct items spread across the page. Schema.org rules clarify that when a CSS selector or XPath produces multiple matches within a page, those matches can together constitute a single conceptual web page element. This rule applies across general page elements, site navigation blocks, headers, footers, and sidebars.

How does speakable markup interact with page elements?

The speakable property is a specialized structured data field that identifies sections within an article or webpage best suited for audio playback using text-to-speech technology. Google Search Central documents that adding speakable markup allows search engines and applications to identify content to read aloud on Google Assistant-enabled devices. Web pages with this markup can use Google Assistant to distribute content through audio channels and reach a wider base of users.

When setting up speakable structured data, focus on highlighting key points rather than selecting an entire article. Google recommends targeting sections that take around 20-30 seconds of content per section, which corresponds to roughly two to three sentences. The speakable property can be repeated an arbitrary number of times using CSS selectors and XPaths as content locators.

What guidelines govern WebPageElement structured data?

Structured data must strictly reflect the actual content present on the page where it is coded. Google Search Central guidelines state that structured data must be coded using in-page markup on the page the information applies to. You should never create blank or empty pages simply to hold structured data, nor should you add structured data for content that is not visible to human users.

Schema.org elements also support descriptive properties to clarify their role within a document. A page element can use a property to indicate whether that specific web page element is the main subject of the page. Additionally, elements like headers, footers, sidebars, and navigation blocks can reference an abstract, defined as a short description that summarizes a creative work.

How do you test and troubleshoot WebPageElement markup?

Troubleshooting structured data requires verifying both the underlying code placement and the rendered HTML elements. You can diagnose implementation issues by systematically checking selector precision, content visibility, and page placement.

1. 01Step 1: Check that the structured data markup is embedded directly in the in-page code of the page describing the content, rather than hosted on a blank page.
2. 02Step 2: Test every CSS selector and XPath in your browser developer tools to verify that they accurately match the intended visible elements.
3. 03Step 3: Confirm that all targeted text sections are visible to users and, if using speakable markup, fit within the recommended 20-30 seconds audio length.

Common questions