Skip to main content
POST
Propose an AI search fix for approval
Beta. Hands your edited fix to the Marketer as one action waiting for approval. Nothing is sent until a person approves it in the approval queue. Both kinds always need a person and can never be set to always allow.
  • github_pull_request: once approved, a new branch named geo-fix/..., one commit of path on that branch, and a pull request into your default branch. Your default branch is never written to, and nothing is merged: you review and merge in GitHub. An existing file gains the section at its end; a missing one is created. Needs the Marketer’s Docs repository connected to GitHub.
  • wordpress_draft: once approved, a post with status draft. Nothing offers to publish it from here. Needs the Marketer’s Website and blog connected to WordPress.
With neither connected, an approved fix is recorded as not sent; copy the text instead. Requires the agent.update permission. Answers 404 unless both AI search visibility and AI employees are switched on for your deployment.
string
required
github_pull_request or wordpress_draft.
string
required
One line, at most 200 characters. The pull request’s or the post’s title.
string
required
The section, at most 8000 characters.
string
github_pull_request only: a .md or .mdx file in the repository, such as docs/answers/sync.md. No part may start with a dot, and when the connection names a folder the file must be inside it. Anything else returns 400, or is not sent.
string
Why, for the pull request’s description. At most 2000 characters.
string
required
The gap’s tracked question.
string
required
The gap’s engine: openai, anthropic or perplexity.

Response

201 with the task, as handing an employee work returns it: its one action is marketer.geo_fix.pull_request or marketer.geo_fix.draft, with status: "pending" and requires_approval: true.
Last modified on November 12, 2026