Skip to content

v0.8.2 - cf_managed_robots (managed robots.txt / Content-Signals control)

Choose a tag to compare

View all tags
@github-actions github-actions released this 02 Jun 23:24
v0.8.2
6f0962b

cf_managed_robots - the managed-robots / Content-Signals control tool, completing the robots feature line (detection 0.8.0 -> advisor 0.8.1 -> control 0.8.2). One new tool (59 tools / 13 prompts).

  • cf_managed_robots(action, zone?, ...) - get / configure / disable Cloudflare's managed robots.txt and Content-Signals policy on a zone (these ride on the Bot Management config; write API confirmed against Cloudflare's public OpenAPI schema, available on all Bot Management plan variants).
    • action="get" is read-only and un-gated; configure / disable are gated behind SEO_MCP_ALLOW_DESTRUCTIVE, need confirm=<zone>, and support dry_run.
    • Safe write path: GET -> overlay only the changed fields -> strip read-only fields -> PUT, so the rest of the zone's Bot Management config is never clobbered. Needs the Bot Management:Edit token scope for writes.
    • Managed robots.txt and the Content-Signals policy are mutually exclusive in Cloudflare; the tool validates this locally and returns INVALID_INPUT (no raw CF 400). Valid combos: managed_robots=true + cf_robots_variant="off" OR managed_robots=false + cf_robots_variant="policy_only".
    • Every response carries a caveat separating the stated-preference signals (ignored by Googlebot, not a ranking factor) from the levers that actually enforce at the edge.

Install: uvx seo-monster or pip install seo-monster==0.8.2. Full notes in CHANGELOG.

Assets 5
Loading