Table name, table description, row count, column count, last-edited timestamp, last-edited user, and the header row. Any cell value can be referenced by row/column index too, which is handy for tables that have a fixed first column like a country code or a year.

By default, SleekPixel uses the largest table by row count, on the assumption that it is the main one. You can override with a per-post setting that names the table id you want featured, or with a template rule that always picks the first embedded shortcode.

Yes. TablePress fires tablepress_event_saved_table on every save and on every CSV import. SleekPixel hooks that action, looks up which posts embed the affected table id, and regenerates each OG image in a background queue.

Yes. The header row and the first data row are both first-class template fields, and you can pin a specific cell, like a total at the bottom, by passing its row and column index. That covers ranking tables and summary tables nicely.

Use TablePress table descriptions or category tags as a routing field. SleekPixel templates can switch accent color, badge text, and layout block based on any field, so finance tables can look different from sports tables without duplicating templates.

No. SleekPixel registers a higher-priority filter on wpseo_opengraph_image and rank_math/opengraph/facebook/image, so the TablePress-aware image wins. Your existing SEO plugin still handles meta description and twitter:card type.

The OG image is a static snapshot, so client-side sort and filter do not change what the share looks like. The snapshot reflects the table as stored, which is typically what readers expect when they click in.

Locally. SleekPixel renders into wp-content/uploads/sleek-pixel/ on your own server and the og:image URL points to your domain. No external API calls and no per-render fees.