Yes, sleekPixelImage is a normal scalar string field on the ContentNode interface, so Apollo, urql, and graphql-request all see it on schema introspection. Add it to your fragment alongside title and uri and the value flows into your normalized cache like any other field. No client side configuration is required.

The field name and signature are stable across WPGraphQL versions because they are registered through the public register_graphql_field API. If WPGraphQL ever changes that API, SleekPixel updates the integration in a point release. Schema posts targeting older versions keep working because the cached PNGs remain valid files.

Yes. A query like { posts { nodes { title sleekPixelImage } } } returns the PNG URL for every node in the connection. The resolver reads the cached file path without spawning a render per item, so a 100 node query stays fast. Initial first-render cost happens once on the WordPress side per post.

WPGraphQL Smart Cache caches GraphQL responses by tag, and sleekPixelImage participates in the same tag map used by the post node. Editing a post invalidates the response cache and the PNG cache together, so headless front ends consuming the cached response always see a fresh image URL after the edit.

Yes. The template supports multiple variants, and you can return the headless variant URL from sleekPixelImage while the traditional og:image meta tag points at the standard variant. Useful when a Next.js consumer wants a 1080 by 1080 square card while the WordPress site wants the classic 1200 by 630.

Yes. Any custom post type that opts into WPGraphQL through show_in_graphql equals true gets the sleekPixelImage field automatically if it is also bound to a SleekPixel template. Custom interface types added via register_graphql_interface_type can be included by adding them to the resolver registration array.

WPGraphQL stores its current version in the WPGraphQL constant exposed as WPGRAPHQL_VERSION and mirrored in wp_options. SleekPixel reads the constant at render time, so the mark always reflects the live deployed version. Override per post by setting a sleekpixel_mark custom field with a value like 1.14.

Yes for any post status that is publicly queryable through WPGraphQL, like publish and inherit for attachments. Draft and private posts only expose sleekPixelImage to authenticated requests with the right capability, matching the visibility rules WPGraphQL already enforces on those nodes.