Schema.org structured data
Search engines crawl HTML tables but rank them better when they're tagged with Schema.org structured data. Pro can emit JSON-LD describing your table — useful for pricing tables, product comparison tables, FAQ tables, and other commercial content where snippet enhancement matters.
Enable schema output
- Open the table in the editor.
- Open the Pro features panel.
- Toggle Schema.org markup on.
- Pick a schema type from the dropdown: Table (generic), ItemList, or Product (if rows describe purchasable items).
- Save.
From now on, every page rendering the table also includes a <script type="application/ld+json"> block before the closing </body>.
What gets emitted
For the generic Table type, MMTable emits an object describing column count, row count, and header values. For ItemList, each row becomes an itemListElement with the leftmost column as the name. For Product, each row maps to a Product object with name, description, and (if column types say so) price.
Inspect the actual markup by viewing the page source on the front end and searching for "application/ld+json".
Verify with Google's Rich Results Test
Once the table is live, paste the page URL into Google's Rich Results Test. It'll parse the JSON-LD and tell you what enhancements (if any) the markup qualifies for.
Note: getting structured data right is necessary but not sufficient for rich snippets. Google decides per-page based on overall page quality, user intent, and a hundred other signals. Don't expect a featured-snippet upgrade overnight.
Column type matters for Product schema
If you pick Product as the schema type, MMTable looks at column types to figure out what goes where:
- The first column becomes
name. - The first
currency-typed column becomesoffers.price(with the column's prefix aspriceCurrency). - Other text columns join into
description.
If you want richer Product markup (SKU, brand, availability), use a dedicated schema plugin alongside MMTable — Pro's Product schema is intentionally minimal.
Multiple tables on one page
Each table emits its own JSON-LD block. Search engines accept multiple blocks per page. No conflict.