Recipes: ready prompts for Woodander MCP

Each recipe has the prompt, the tools it uses and what needs your approval. Replace example.com and my-product with your own site and project slug. Ask list_sites or discover_list_products first if you are not sure of the names.

1. Weekly SEO review #

Run the Woodander seo_review prompt for example.com and give me the three
things worth doing this week.

Tools: the seo_review prompt calls the read tools, such as search_console_summary, search_opportunities and get_audit. Scope: read:seo. Approval: none, it only reads.

2. Which pages lost clicks? #

Compare my Search Console clicks for example.com over the last 28 days with the
previous period. Then list the pages with the most impressions and tell me
which ones need attention.

Tools: search_console_summary, search_console_pages. Scope: read:seo. Approval: none. The page list is a 28-day snapshot of synced data.

3. Quick wins from search queries #

Show search opportunities for example.com: queries at positions 4 to 20 and
queries with low CTR in the top 5. Suggest a title and meta description for each page.

Tools: search_opportunities, search_console_queries. Approval: none.

4. Fix tracking with Tag Manager #

Analyze tracking for example.com in Tag Manager. List missing events and
duplicates. Then propose the tags and triggers to fix them in the Woodander workspace.

Tools: gtm_analyze_tracking, then gtm_create_trigger, gtm_create_tag, gtm_create_version. Scopes: read:gtm, write:gtm. Approval: in Manual mode every create is a proposal you apply in the Workspace. Publishing is a separate step: gtm_publish_version gives you a confirmation link. Check events arrive after publishing. Rollback is gtm_rollback.

Sign-ups and purchases should be fired from a confirmed signal, such as a success page, not from a button click. The analysis flags clicks that fire them.

5. Move hard-coded tags into Tag Manager #

Scan example.com for hard-coded tracking snippets and plan the move to Tag Manager.
Do not publish anything.

Tools: gtm_scan_site, gtm_plan_migration. Scope: read:gtm. Approval: none for the plan. Removing snippets happens in your code, and you publish together with that deploy, or events count twice.

6. Update my project FAQ #

Read the page of my-product on Discover. Rewrite the FAQ so it answers the
five most likely buyer questions. Save it as a draft change.

Tools: discover_product_page, discover_update_page. Scopes: read:products, write:products. Approval: Manual mode, you apply the proposal. The edit goes to your draft, and editors approve it before the page changes (unless you are a trusted owner).

7. Post a Newsroom Brief #

Write a two-sentence Brief announcing our new pricing page and post it for my-product.

Tool: discover_post_brief. Scope: write:products. Approval: a Brief is public, so in Manual and Hybrid it waits for your confirmation. Your monthly Brief quota applies. discover_product_page shows how many are left.

8. Reply to a review #

Show the latest reviews of my-product and draft a polite reply to the newest one.

Tools: discover_reviews, discover_reply_review. Approval: replies are public, so you confirm in Manual and Hybrid. Read the draft before you approve it.

9. Keyword ideas, then track #

Give me keyword ideas for "invoice software for freelancers" in Germany for
example.com, and pick the five with the best volume against competition.

Tools: keyword_ideas, then tracked_keywords and rank_history to see what you already track. Scope: read:keywords. Approval: none. A new search uses one of your daily keyword lookups. Repeating it the same UTC day is free. Adding keywords to tracking is done in SEO → Rank tracking in the Workspace.

10. Uptime check #

Check uptime for all my sites and tell me about incidents in the last week.

Tool: uptime_status. Scope: read:seo. Approval: none. The list is empty if your plan has no uptime monitoring.

11. Make my site faster #

Run the Woodander speed_fix prompt for example.com. Check the home page and my
two best pages on mobile, find the files in this repository behind every slow
resource and show me the diffs before you change anything.

Tool: pagespeed_check, plus search_console_pages to pick the pages. Scope: read:seo. Approval: none for the checks. You approve the code changes in your editor. The tool returns what Google PageSpeed knows: the score, field data from real visitors, and for each problem the exact resources (render-blocking scripts and styles, unused JavaScript and CSS with bytes, oversized images, fonts, the LCP element, layout-shift elements, long tasks, third parties, cache lifetimes, redirects). Only pages of your own sites can be checked, and the plan needs site audits. You get 30 fresh runs an hour; a repeat within 10 minutes is cached and free. After you deploy, ask for the same page again to see the change.

Tips #

• Say which site or project you mean. Otherwise the assistant has to guess.
• Ask it to show the diff before it asks for a change.
• Start with Manual mode. See Modes and approvals.

Next step #

Run recipe 1 today, and 4 if your tracking has gaps.