rewrite_for_geo
Rewrites content for AI answer synthesis engines by enriching entities and framing comparisons, making it more likely to be cited in multi-source summaries.
Instructions
Rewrite a content block for Generative Engine Optimization: entity-rich, comparison-ready, synthesis-friendly. Tuned for surfaces that summarize across sources (Perplexity, Google AI Mode, Claude search).
Read-only on input. Does NOT write back to the source URL - returns the rewritten content as a string.
This tool delegates the actual rewrite to the calling LLM via MCP sampling - it does not call any external API itself. The MCP host's model produces the rewrite. Output may vary across runs (model-dependent).
When to use: optimizing for synthesis-style answers across multiple sources. For direct-answer (BLUF + FAQ) optimization on a single page, use rewrite_for_aeo instead.
Either url or text must be provided. target_query is required.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Public URL whose content should be fetched and rewritten. Either this OR `text` is required. | |
| text | No | Raw content to rewrite directly. Either this OR `url` is required. | |
| target_query | Yes | The user query the rewrite should answer. Required - drives entity selection and comparison framing. | |
| add_comparison_table | No | If true, inject an explicit X-vs-Y comparison table into the rewrite (useful for `X vs Y` queries). Default false. | |
| max_words | No | Soft word budget. Default 1500. Range 100-5000. | |
| respect_robots | No | If true (default), respect robots.txt when fetching `url`. Ignored when `text` is used. |