Slim SEO ability reference

What Slim SEO needs before these load

2 of the 3 also ship in GoBuildWP Free 1.18.6 under the same names, marked “Also in GoBuildWP Free” below. They need no GoBuildWP Pro licence, but each retains its own dependency, feature and permission checks. Where Free's copy does less, its own description follows Pro's. When Pro's richer copy passes its gates, it registers first and answers.

Slim SEO must be active; the module looks for its SLIM_SEO_VER constant, and each call returns slim_seo_not_active when it is missing. No version floor is set. Storage and rendering were checked against Slim SEO 4.11.0, and when a version lacks one of the renderer methods the kit returns the unrendered value or null instead of failing. Callers pass GoBuildWP's own permission check (manage_options, or super admin on multisite) and edit_posts, and must be able to edit the post itself, otherwise slim_seo_forbidden. The free plugin's get and update handle the title, description and noindex flag only and leave the row's canonical and images as stored; the rendered values and check-setup are Pro.

Slim SEO editions

free

Everything a post overrides is one slim_seo row

Slim SEO does not spread its data over several meta keys. A post's overrides are one array in the slim_seo post meta row, with the keys title, description, canonical, noindex, facebook_image and twitter_image. The kit writes it the way Slim SEO's own save does: sanitize_text_field() on each value, empty entries dropped, and the whole row deleted once nothing is left. It adds one step Slim SEO skips, slashing the array before update_post_meta(), so backslashes survive.

The before-image for wppilot/rollback-change is that single row. There is no Open Graph title or description to store: Slim SEO prints the meta title and description on social cards, and the two image fields are the part that can differ.

Noindex can be switched on, never forced off

The noindex key is either 1 or absent, so robots_index accepts default, index or noindex but index and default both clear the flag. A post type marked noindex in Slim SEO's settings gives its posts a noindex directive whatever the post says, and a site with search engines discouraged does the same. rendered.noindex_source names which of post, post_type or site is responsible.

Slim SEO drops the canonical link from a noindexed page, so rendered.canonical comes back empty in that case even when the post stores one.

Which title the page actually gets

rendered.title_source is post, post_type, front_page or wordpress. With no title on the post and none on its post type, Slim SEO leaves WordPress's own document title in place even though its renderer would report its default template; the kit reports title_source wordpress and a null title rather than name a title the page does not have. Titles and descriptions may use variables such as {{ post.title }}, {{ sep }} and {{ site.title }}, and the setup call gives the separator from WordPress's document_title_separator filter, which defaults to a hyphen.

The setup call reads Slim SEO's settings field by field and never returns the whole option, because that option also holds an AI provider API key.

Representative call sequence

This sequence describes the documented calls and checks to perform. It is not a recorded result from an installed WordPress site. Inspect returned errors and partial results, then verify the saved values and affected output before proceeding.

Find out why a page shows WordPress's default title and give it a proper one.

1. 01 wppilot/slim-seo-get-post-seo Returns title_source wordpress and a null rendered title, showing neither the page nor its post type sets a title.
2. 02 wppilot/slim-seo-check-setup Shows the page post type's empty title template and the separator {{ sep }} will produce.
3. 03 wppilot/slim-seo-update-post-seo Writes a title using {{ sep }} and {{ site.title }}; the response shows title_source post and the rendered result.

Questions about Slim SEO