set_title: Agent-Applied SEO Title Changes
What the Get AI Traffic agent writes to your SEO title, the 60-character limit it refuses to cross, what it leaves alone, and how to roll it back.
Published on July 17, 2026
set_title is the tool the Get AI Traffic agent uses to write a page’s SEO title after you approve a fix. It sets the title element a search engine reads when it decides what to call your page in the results, then publishes it through your site’s connection.
This page documents what the tool touches, what it refuses to touch, and how to undo it. For the decision of what a page should be called, and whether the current title is worth changing at all, read Google Rewrites Six of Every Ten Titles, and Length Is Why. That question is a judgment call. This page is about the mechanics.
What it does
When you approve a title action item, the agent writes a title for the page and sets it. On WordPress the tool routes to whichever plugin owns your metadata: if Yoast owns it, the value goes to Yoast’s _yoast_wpseo_title field; otherwise the Get AI Traffic plugin stores and emits the tag itself. That routing starts from the site’s platform configuration, but the plugin gets the final say: it checks whether Yoast is actually running and uses Yoast’s field when it is, whatever the stored configuration says. So the title lands in the field your theme actually renders, even if the configuration is stale, instead of a second competing tag.
The tool enforces a hard length limit of 60 characters. If the title is longer, the tool rejects it and writes nothing: no ledger entry, no change to the page. That number is not arbitrary. Rewrites are least common between 51 and 60 characters, and past 70 they are effectively guaranteed, so a title that lands is one that has a chance of surviving to the results page.
What it will not touch
- Your H1 and the post’s display title. This tool sets the SEO title only. The heading on the page and the title your CMS shows in listings are left exactly as they are, which matters: matching the two is the most effective thing you can do to prevent a rewrite, and it stays your call.
- Titles that do not fit. An over-length title is refused outright rather than silently trimmed. Nothing is recorded and nothing is published until the value fits.
- Other head fields. It sets the title and only the title. The Open Graph title, the meta description, and the canonical are separate fields set by separate tools.
Timing
The new title is written to your site immediately, but search engines only see it on their next crawl, and they rewrite most titles regardless. Expect the title you supplied to start appearing over the following crawls rather than the same afternoon, and expect the engine to sometimes show its own version anyway.
Rolling back
Every applied change is written to the ledger with the prior title. roll_back restores the previous value exactly, whether that was an older title or an empty field.
Related tools
purge_cacheruns after an apply, so a cached copy of the old page does not keep serving the old title at the edge.set_social_metasets the Open Graph title, which is a different field. The SEO title is what a search engine shows;og:titleis what a share card shows. Setting one does not set the other.set_contentedits the page body, including the H1. Where a finding is really about the H1 rather than the title tag, that is the tool that touches it.
Findings this tool resolves
empty_title: a page has no title, so the engine names it from your headings or from anchor text written by someone else.short_title: a title of 20 characters or fewer, which is rewritten more than half the time.long_title: a title over 60 characters, which is truncated in the results and, past 70, rewritten almost every time.duplicated_title: the same title across several pages, which leaves a search engine to guess which one answers the query.
One finding it does not resolve: multiple_title_tags, where a page emits more than one title element. That is a template bug rather than a value to set, and writing an SEO title does not remove the second tag. It needs a fix in the theme.
Want this checked on your own site?
Get your free AI-visibility audit