SEOPress MCP where empty means inherit

Adding an FAQ schema row to a SEOPress page in three calls

SEOPress MCP schema work follows a fixed order, because a manual structured-data row has to exist before its fields can be filled. seopress-set-post-schema-type creates the row at index 0 (or the index you give) with a type such as faq. seopress-list-schema-fields with that type then returns the exact meta keys it accepts, which matters because the key stem does not match the type name, and tells you that the FAQ questions are a repeater, an array of question and answer pairs. seopress-edit-post-schema finally merges the fields into that row.

Two flags on seopress-get-post-schema decide whether any of it reaches the page. rendering_enabled reflects SEOPress Pro's site-wide rich snippets switch; when it is false the rows are stored and nothing is printed. disabled_all is the per-post switch that turns off automatic template schema for that page. Read both after the edit, then check the page source or a rich results test for the JSON-LD. Every question and answer in an FAQ row should also appear in the visible page text; structured data that describes content visitors cannot see is a reason for search engines to ignore it, and valid markup never guarantees a rich result. The custom type takes one raw JSON-LD script, which deserves the same review as any code you paste into a page.

A per-post SEOPress redirect or a seopress_404 entry?

SEOPress offers two places to redirect a URL, and the agent can reach both. The redirect block in seopress-edit-post-seo, part of GoBuildWP's Pro copy of that ability, attaches the redirect to an existing post: enabled, a 301, 302 or 307 type, a target URL, and logged_status to apply it to everyone, only logged-in users or only visitors. It follows the post, so it suits retiring a page that still exists in WordPress. Sending type 0 clears it.

A seopress_404 entry, created with seopress-create-redirect, matches a path or regex whether or not any post exists there, and is the only option for URLs from an old site structure. Entries in seopress_404 also accept 410 and 451 with no destination. Avoid having both on the same URL; when a redirect misbehaves, ask the agent to check the post's redirect block as well as the redirect list.

Finding the 404s that actually get traffic

seopress-list-redirects with view 404 returns logged 404s newest first, with a count and last hit on each row, up to five hundred per call with an offset for paging. It does not sort by hits. For a site with a long log, the agent pages through the whole view, sorts by count itself and reports the top entries; ask for that explicitly so it does not stop at the first page. The compact rows leave out referrer and user agent, so the agent fetches those with seopress-get-redirect only for the shortlist.

Promoting a logged entry into a redirect with seopress-edit-redirect keeps its history and can be undone. Deleting entries cannot, since a SEOPress delete is a hard delete, so clearing old log noise is a confirmed, permanent job best left to SEOPress's own bulk actions.

SEOPress settings an agent may read but not change

seopress-get-settings reads the titles, social, knowledge graph, sitemap, advanced and analytics groups, with licence and API keys redacted, and reports whether the SEOPress Pro licence is active. Archive noindex toggles and the per-post-type title overrides live in the titles group, which is where a sitewide noindex surprise is usually found. The dedicated SEOPress settings abilities are read-only, and automatic schema template rules are only listed. Review changes in SEOPress's own screens; a separately authorized execute-php call under Developer Full Access can use plugin or WordPress APIs outside this metadata workflow. The SEOPress reference lists every field.

• "Read only: which of our service pages have manual schema rows, and is rich snippet rendering switched on?"
• "Add an FAQ row to the pricing page with these four questions, then show me the stored row."
• "Go through the whole 404 log and give me the twenty URLs with the most hits, with referrers."