Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

SEO

SEO abilities of the Hostinger AI plugin's WordPress site MCP server. Read, update and audit SEO titles and descriptions. The abilities work with Yoast SEO, Rank Math or All in One SEO when one is act

Read, update and audit SEO titles and descriptions. The abilities work with Yoast SEO, Rank Math or All in One SEO when one is active, and with Hostinger’s built-in SEO fields otherwise.

Available: Always.

Ability
What it does
Type

Find the posts and pages whose SEO metadata has problems.

Read-only

Change SEO metadata on several posts or pages in one call, up to 50 per call.

Changes the site · Safe to retry

Read the SEO metadata of one post or page.

Read-only

Change the SEO metadata of one post or page.

Changes the site · Safe to retry

Audit SEO Metadata

hostinger-ai/seo-audit · Read-only

Find the posts and pages whose SEO metadata has problems.

No required parameters.

Optional parameters (4)
Parameter
Type
Default
Description

post_type

array of string

Post types to audit. Defaults to posts and pages.

issues

array of missing_title, missing_description, title_too_long, description_too_long, description_too_short, missing_canonical, noindex

Only report these issue types. Defaults to all of them except missing_canonical, which is on by default only when no SEO plugin is active.

limit

integer

20

How many posts to examine, newest first. Default 20, maximum 100. This is a scan window, not a result count: posts without issues are left out of "posts", so fewer entries come back than the limit, and posts outside the window are not examined at all. Compare "scanned" against "total_available" (every post of the requested types, not just the problem ones) and page with "offset" to cover the whole site.

offset

integer

0

Number of matching posts to skip, for paging through results.

Description sent to AI tools

Find the posts and pages whose SEO metadata has problems. Start here for any site-wide SEO question rather than guessing which pages to check: "check my site SEO", "how is my SEO", "which pages are missing meta descriptions", "find SEO problems", "are any pages hidden from Google", "what should I improve". Reports a missing or overlong meta title, a missing, overlong or too-short meta description, and a noindex directive. "missing_canonical" is only checked by default on sites with no SEO plugin, because the SEO plugins derive canonicals at render time and leave the stored value empty; ask for it explicitly to check it anyway. Each entry gives you the post id plus its detected issues and its current values under "current"; to fix them, call seo-bulk-update with entries of the form {id, : } — lift the id out and put your replacements at the top level, do not send "current" back.

Bulk Update SEO Metadata

hostinger-ai/seo-bulk-update · Changes the site · Safe to retry

Change SEO metadata on several posts or pages in one call, up to 50 per call.

Required parameter
Type
Description

posts

array of object

Posts to update, each with an id and the SEO fields to change.

Description sent to AI tools

Change SEO metadata on several posts or pages in one call, up to 50 per call. Use this for anything phrased across multiple pages: "fix the missing meta descriptions", "shorten every title that is too long", "optimise the SEO of my blog posts", "noindex these pages". Pair it with seo-audit, which finds the posts that need fixing; for a single page use seo-update. Each entry needs an id plus the SEO fields to change; only the fields you pass are changed. Entries are processed independently, so one failure does not stop the rest — the response lists updated entries and failed entries with their reasons. An entry no provider could store anything for is reported as failed with the code seo_nothing_written, and "success" is true only when no entry failed and at least one entry actually wrote something. The output of seo-audit can be passed straight in as the posts array.

Get SEO Metadata

hostinger-ai/seo-get · Read-only

Read the SEO metadata of one post or page.

Required parameter
Type
Description

id

integer

ID of the post or page.

Description sent to AI tools

Read the SEO metadata of one post or page. Use this when asked what SEO settings a specific page has, or before rewriting them: "what is the SEO title of this page", "does this post have a meta description", "is this page hidden from Google", "what is the focus keyword", "what image is used when this page is shared". Returns the meta title, meta description, canonical URL, robots directives (noindex, nofollow, noarchive), focus keyword and social preview (Open Graph and X/Twitter) fields. This tool only reads and only handles one post: use seo-update to change values, seo-bulk-update for several posts, and seo-audit to find which posts across the site have SEO problems. Reads from the active SEO plugin (Yoast SEO, Rank Math or All in One SEO) and falls back to Hostinger storage when no SEO plugin is installed. The response reports which provider answered.

Update SEO Metadata

hostinger-ai/seo-update · Changes the site · Safe to retry

Change the SEO metadata of one post or page.

Required parameter
Type
Description

id

integer

ID of the post or page.

Optional parameters (11)
Parameter
Type
Description

seo_title

string

Meta title shown in search results. Pass an empty string to clear it.

meta_description

string

Meta description shown in search results. Aim for 70-160 characters.

canonical

string

Absolute canonical URL for this post.

focus_keyword

string

Primary focus keyword for this post.

robots

object

Search engine robots directives. Each directive is true, false, or the string "default" to clear the per-post setting so the site-wide default applies again. Passing false pins an explicit positive directive, which a later change to the site default will not override — use "default" when you mean "stop overriding". On sites using All in One SEO, setting any one directive pins all three for that post, because it stores a single all-or-nothing "use defaults" flag; and a request mixing "default" with an explicit value is refused there rather than silently inverted.

og_title

string

Open Graph title used by Facebook and LinkedIn previews.

og_description

string

Open Graph description used by social previews.

og_image

string

Absolute URL of the Open Graph preview image.

twitter_title

string

Title used by X/Twitter card previews.

twitter_description

string

Description used by X/Twitter card previews.

twitter_image

string

Absolute URL of the X/Twitter card image.

Description sent to AI tools

Change the SEO metadata of one post or page. Use this whenever asked to set or improve the SEO of a specific page: "write a better meta description for this page", "shorten the SEO title", "optimise this post for ", "hide this page from search engines", "stop Google indexing this", "set the canonical URL", "set the social share title or image". Accepts the meta title, meta description, canonical URL, robots directives (noindex, nofollow, noarchive), focus keyword and social preview (Open Graph and X/Twitter) fields. For more than one post in a single request use seo-bulk-update instead. Only the fields you pass are changed; pass an empty string to clear a field. Each robots directive is tri-state: true turns the directive on, false pins it off, and "default" removes the per-post override so the site-wide setting applies again. Writes to every active SEO plugin (Yoast SEO, Rank Math, All in One SEO), or to Hostinger storage when no SEO plugin is installed. "written_to" lists the providers that stored something, "skipped_fields" lists every field that was refused, and "skipped_by" says which provider refused each one ("input" means the value itself was invalid). When only one provider is listed in "active_providers", a skipped field was not stored at all; when several are, it may still be live on another. Values are read back from the primary provider only, so a field you cleared and a field the primary does not support both come back absent — use "skipped_by" to tell them apart.

Last updated

Was this helpful?