15 Claude Prompts for WordPress SEO & Page Updates (2027)

Connect WordPress to Claude through Otto's hosted Claude MCP connector using a single otto_mcp__ token to run 15 live prompts across 29 WordPress tools (15 read and 14 write), where every new post or page defaults to draft until you publish it. Across 227 tools across 15 integrations in Otto MCP, Claude cross-checks Search Console, GA4, and PageSpeed Insights while cutting token usage by 80–90% versus 3,000-row CSV uploads. If you only run one prompt today, run Prompt 1 below to pull striking-distance search queries from Google Search Console and draft content updates directly into WordPress without touching a spreadsheet.

The five starter prompts below let you inspect search performance, refine metadata, update core page text, audit media files, and evaluate mobile performance through live tool calls.

Query Google Search Console for the top 20 queries from the last 28 days with an average position between 8 and 20 and impressions over 250. Cross-reference these queries against existing WordPress posts. Identify three posts where adding a dedicated section targeting these terms would improve search coverage, and draft the text for each section as a revision note.

Fetch the current WordPress posts in the primary category that received impressions over the last 30 days according to Google Search Console. Review their current title tags against Google Search Central guidance, ensuring each title is descriptive, concise, and avoids keyword stuffing. Draft updated titles for the three posts with the lowest click-through rates.

Fetch the WordPress page with the slug "services". Check the opening section, business hours, and contact details. Propose updated text that reflects our current service menu, and stage the updated copy as a draft revision for review.

Inspect the last 30 items in the WordPress media library. Identify any images that lack descriptive alt text or contain file names in place of functional descriptions. Draft clear, context-specific alt text for each identified image and update the media records.

Run psi_analyze_url on our WordPress site homepage and our top-performing service page for mobile devices. Return the Core Web Vitals diagnostics for LCP, CLS, and INP. List the top three performance bottlenecks and draft specific steps to address them in WordPress.

Connect Claude to Otto MCP to run these prompts against your live accounts. New WordPress posts and pages stay in draft until you publish them, and Otto ships live changes only after you approve them.

Managing WordPress SEO manually forces operators to toggle between Search Console, spreadsheet exports, and the WordPress block editor. Running offline Claude prompts requires copying thousands of CSV rows into chat windows, consuming context windows without verifying whether changes match live page structures. Connecting Claude to Otto MCP bridges data analysis and draft-first content updates in a single workspace.

Otto's hosted Claude MCP connector operates through a secure HTTP endpoint at https://otto.islaintel.com/api/mcp. It links Claude directly to 227 tools across 15 integrations in Otto MCP without exposing raw API keys or passwords.

Otto Webmaster connects Claude to your live web stack using a single organization-scoped bearer token prefixed with otto_mcp__. Instead of saving WordPress application passwords, Meta tokens, or Google credentials inside AI chat clients, your integrations authenticate once inside Otto via OAuth. Claude communicates exclusively with the hosted MCP server, while OAuth secrets remain secure on Otto's infrastructure.

Under the hood, Otto's 29 WordPress tools interact with standard endpoints documented in the WordPress REST API Reference. These tools encompass 15 read operations and 14 write operations spanning posts, pages, media, categories, tags, comments, taxonomies, and site search. In the WordPress REST API posts schema, the status field controls publication state. In Otto MCP, new posts and pages created via write tools default to draft. Live pages remain unaffected until you explicitly review and publish them.

When diagnosing SEO performance, Claude pairs WordPress tools with read-only endpoints from Google Search Console and PageSpeed Insights. The Google Search Console searchAnalytics.query API provides performance metrics grouped by dimensions like query and page, returning clicks, impressions, ctr, and average position. Read-only access ensures search performance data is queried without risk of altering property configurations.

For performance assessments, Otto includes a built-in psi_analyze_url tool powered by the Google PageSpeed Insights documentation. It tests real-world Chrome User Experience Report (CrUX) field data—including Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP)—alongside Lighthouse diagnostics using Otto's platform API key. You can review our Connect WordPress to Otto setup guide and How to Connect Claude to Otto MCP to establish these connections.

┌────────────────────────────────────────────────────────┐
│                   Claude MCP Client                    │
│        (Claude Desktop, Claude Code, Web Chat)         │
└───────────────────────────┬────────────────────────────┘
                            │ Bearer: otto_mcp__***
                            ▼
┌────────────────────────────────────────────────────────┐
│           Otto Hosted MCP Gateway (/api/mcp)           │
│         227 Tools across 15 Connected Platforms        │
└───────┬───────────────────┼────────────────────┬───────┘
        │                   │                    │
        ▼                   ▼                    ▼
┌──────────────┐    ┌──────────────┐     ┌──────────────┐
│  WordPress   │    │Google Search │     │  PageSpeed   │
│   REST API   │    │   Console    │     │   Insights   │
│  (29 Tools)  │    │ (Read-Only)  │     │(psi_analyze) │
└───────┬──────┘    └──────────────┘     └──────────────┘
        │
        ├─► New Posts/Pages: status: draft
        └─► Critical Pages: Human Approval Locked

Search Console prompts 1–5 combine live query metrics with draft-first content creation through the Otto AI SEO Agent. Connect Google Search Console to Otto to give Claude read-only visibility into your search metrics.

Prompt 1: Low-CTR, high-impression query gap analysis

This prompt identifies queries that earn impressions in Google search results but fail to generate clicks, highlighting clear optimization opportunities.

Query Google Search Console for search data from the past 28 days. Filter for queries that earned at least 400 impressions with an average position between 4.0 and 12.0, but have a click-through rate below 2.5%. Fetch the corresponding WordPress post for each identified query using wp_get_posts. Analyze the current headings and body text, and draft two paragraphs of new content answering the user query directly to incorporate into the post as a draft update.

Prompt 2: Concise title tag optimization adhering to Google Search Central guidance

This prompt addresses title readability. Google Search Central title link guidance notes that while there is no strict character limit on <title> elements, title links are truncated in search results to fit device screens.

Inspect the five WordPress posts with the highest impressions and lowest CTR over the last 30 days using Google Search Console data. Read the current title and excerpt of each post. Propose three revised title options per post that are descriptive, concise, avoid keyword stuffing, and place critical identifying terms first so they remain clear if truncated on mobile devices. Stage the preferred option for each post as a draft revision.

Prompt 3: New blog post drafted to WordPress targeting striking-distance keywords

This prompt spots striking-distance keywords (positions 11 through 20) in Search Console and drafts a structured post directly to your CMS with status: draft.

Analyze Google Search Console query data for terms averaging position 11.0 to 20.0 with over 200 monthly impressions that lack a dedicated, targeted WordPress post. Select the strongest topic cluster. Use wp_create_post with status="draft" to create a complete 1,200-word informative article with appropriate H2 and H3 subheadings, an excerpt, and suggested categories based on wp_get_categories. Confirm the post ID and verify the draft status.

Prompt 4: Internal linking audit between related WordPress posts

This prompt scans existing WordPress content to build logical internal links between newer articles and established pillar content.

Use wp_get_posts to pull the titles, slugs, and excerpts of our last 20 published WordPress posts. Group them into three thematic topic clusters. Identify five instances where an older, high-authority post should link to a related newer post. Output the exact sentence from the source post, the recommended anchor text, and the target post URL.

Prompt 5: Search intent refresh for decaying posts

This prompt compares recent and prior Search Console periods to flag decaying posts and refreshes outdated information without modifying live pages.

Compare Google Search Console query data from the last 30 days against the same period 90 days ago. Identify the top two WordPress posts exhibiting drops in clicks exceeding 20%. Fetch the live content of both posts via wp_get_posts. Pinpoint outdated references, missing subtopics, or shifted search intent. Draft refreshed introductory sections and updated subheadings, staging them as draft updates.

Service-page prompts 6–10 use the Otto AI Website Manager to handle ongoing website maintenance tasks. Otto is built for service businesses and small teams—including clinics, law firms, studios, gyms, and salons—that need their site kept current without hiring a full-time marketer. Enrique Gomez, owner of Enzo Maverick Pilates, said: "Otto has been pivotal for us. The ease of making website changes on the fly lets us sharpen our brand and revise as fluidly as we need." Clinic operators can also review how to get more patients from your clinic website in 2027 for guidance on organizing treatment descriptions.

Prompt 6: Service-page and clinic bio updates

This prompt updates treatment descriptions and team bios to reflect seasonal offerings or staff changes.

Fetch our core service pages using wp_get_pages. Review the page copy against our updated treatment offerings. Identify sections that contain outdated practitioner bios, obsolete session pricing, or retired modalities. Draft updated content for each section with clear call-to-action buttons, keeping critical contact forms and checkout links unchanged. Stage the revisions for review.

Prompt 7: Local business hours, NAP, and pricing update

This prompt maintains consistent Name, Address, and Phone (NAP) details alongside business hours across WordPress pages and your Google Business Profile.

Fetch the WordPress "contact" and "about" pages. Query our connected Google Business Profile via read-only tools to verify our recorded business hours, street address, and phone number. Check whether the WordPress page copy matches our live Google Business Profile records. If discrepancies exist, draft the exact text corrections required on WordPress and stage the update for owner confirmation.

Prompt 8: Media library audit for missing alt text and asset optimization

This prompt identifies missing image descriptions across your media library. Otto features automatic image optimization in Otto v1.1.5, which automatically compresses new uploads and processes media during scheduled maintenance passes.

Use wp_get_media to inspect the 40 most recently uploaded media items. Identify every image record where the alt_text attribute is empty or contains an automated file name like "IMG_4021.jpg". For each missing entry, review the associated post context and draft descriptive, accessible alt text that accurately portrays the image. Apply the updates to the media records.

Prompt 9: Category and tag consolidation

This prompt cleans up taxonomy bloat using the /wp/v2/categories and /wp/v2/tags endpoints to merge duplicate tags and unused categories.

Fetch all site taxonomies using wp_get_categories and wp_get_tags. Identify tags with zero assigned posts, tags that duplicate category names, and near-identical variations. Create a clean taxonomy consolidation plan that lists which tags to delete, which tags to merge, and which core categories to retain for a cohesive topic hierarchy.

Prompt 10: WordPress comment moderation and FAQ extraction

This prompt reads user inquiries submitted through /wp/v2/comments to identify recurring customer questions suitable for post updates.

Fetch the last 50 approved WordPress comments using wp_get_comments. Identify three recurring customer questions regarding service logistics, pricing, or appointments. Draft a clear FAQ block with structured answers addressing these questions, and stage it as an update to the relevant service page.

Performance prompts 11–15 audit mobile Core Web Vitals, align landing page copy with paid ad traffic, and synchronize multilingual content. To understand how slow loading speeds degrade campaign efficiency, see how Core Web Vitals drift causes paid traffic revenue leaks.

Prompt 11: Mobile Core Web Vitals audit using psi_analyze_url

This prompt assesses real-world mobile speed using CrUX field metrics and Lighthouse diagnostics via Connect PageSpeed Insights to Otto.

Run psi_analyze_url for strategy="mobile" on our primary landing page URL. Report the field metrics for Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP). Identify specific render-blocking resources, uncompressed images, or heavy scripts flagged by Lighthouse diagnostics, and output an action plan for WordPress optimization.

Prompt 12: High-CPA paid ad landing page diagnostic and draft revision

This prompt compares paid ad campaign messaging against target landing page copy, addressing conversion friction and high acquisition costs.

Read the top two paid ad sets with the highest cost-per-acquisition over the past 30 days using our connected ad integrations. Fetch the destination landing page content using wp_get_pages. Compare the primary ad hooks, offers, and value propositions against the headline and hero copy of the WordPress landing page. Draft an aligned hero headline, sub-headline, and proof section, and stage the revisions as a draft update.

Prompt 13: Layout shift (CLS) and image dimension fix

This prompt audits landing pages for missing image width and height attributes that cause disruptive content shifts during loading.

Run psi_analyze_url on our three most visited service pages to inspect layout stability diagnostics. Review the HTML markup of the target pages using wp_get_pages to find images, embed blocks, or banners that lack explicit width and height dimensions. Draft revised HTML snippets specifying correct aspect ratios to eliminate layout shifts, and stage the changes as drafts.

Prompt 14: Bilingual translation and synchronization from English to /es/* WordPress drafts

This prompt translates published English posts into structured Spanish drafts under the /es/* URL structure used on multilingual websites.

Fetch the latest published English WordPress blog post via wp_get_posts. Translate the complete title, excerpt, and content body into natural, idiomatic Spanish tailored for our target audience. Create a corresponding Spanish draft post with status="draft", setting the appropriate slug prefix under /es/ and mapping the categories to their Spanish counterparts. Confirm the new draft post ID.

Prompt 15: Pre-publish staging verification and WhatsApp change-log briefing

This prompt verifies staged WordPress drafts against SEO guidelines and summarizes pending changes before publication. Otto supports approving content changes directly from WhatsApp (v1.1.0), allowing owners to review updates on their mobile devices.

Inspect the three WordPress posts currently in draft status using wp_get_posts with status="draft". Check each draft for the presence of an H1 title, descriptive alt text on featured images, meta description formatting, and functional internal links. Prepare a concise summary briefing that details what was changed and confirms that each post remains safely in draft status pending approval.

Operating AI agents on production websites requires strict permission controls. Otto enforces safety guardrails that separate content staging from live publishing across your digital channels.

In Otto MCP, write operations across WordPress posts and pages default to draft (status: draft). Content created by Claude stays invisible to site visitors until a site administrator reviews the formatted layout in wp-admin and hits publish.

Checkout, contact, and legal pages always require human approval in Otto core before live changes ship, so billing flows, contact forms, and privacy disclosures stay under your control. Every deployment and site-edit pass is logged in otto_get_change_log, providing a clear audit trail of site revisions. On code-managed websites, Otto opens changes as GitHub pull requests complete with preview URLs for review before merging.

This draft-first behavior in WordPress differs sharply from social publishing tools. When publishing to Facebook Pages or Instagram through Otto MCP, posts go live immediately upon command execution and require Reviewer or Admin permissions. Because organic social feeds lack native draft states for API publishing, ad and social write tools require the Master plan. Similarly, LinkedIn Ads write operations create campaigns in a DRAFT state by default, requiring administrative rights and explicit confirmation (confirm=true) before activation, while $0 budgets are automatically rejected.

Analytics, search telemetry, and store administration tools—including Google Analytics 4, Google Search Console, Google Ads, Google Business Profile, YouTube, Google Sheets, Shopify, and PageSpeed Insights—are strictly read-only within Otto MCP. Claude can query your search queries, session metrics, or catalog inventory to inform content drafts, but cannot alter tracking scripts, delete conversion goals, modify product records, or adjust advertising budgets.

Otto Webmaster is built by IslaIntel in San Juan, Puerto Rico, as an AI webmaster and digital marketing teammate. It handles the recurring technical and maintenance tasks typically billed under agency retainers—including search optimization, page edits, performance checks, and reporting—while you maintain complete editorial control.

Pricing structure

Otto Trial, Pro, and Master plans govern both the core web platform and the hosted MCP server.

• $1 Trial (3 days): Offers full access to Pro features, covering WordPress page updates, technical SEO maintenance, and read-only diagnostics across connected ad and social accounts. Every trial includes a complimentary homepage redesign built from your existing photos and copy, requiring your approval before deployment.
• Pro ($199/month, or $99/month billed annually): Designed for service businesses and small teams requiring weekly site management, SEO updates, and cross-channel performance reporting.
• Master ($3,500/month, or $3,000/month billed annually): Adds write access and campaign management across Meta Ads, Google Ads, and social publishing channels with human approval gates on every live change. Cancel anytime on any plan.

Honest limitations

Otto is not a static website builder or template warehouse; it maintains and improves the site your business already operates. Write access across paid advertising and social media channels requires the Master plan. White-label agency portals remain limited.

Otto does not promise Google Map Pack placement, specific search positions, or ChatGPT citations; it structures websites, schema, listings, and reviews so search engines and AI assistants can read and understand the business.

Against single-purpose tools, Ryze AI focuses primarily on paid ads and SEO/GEO workflows, whereas Otto also manages live website edits and organic social publishing. Synter offers paid media connectors across 40+ ad networks for Claude, ChatGPT, and Cursor users, but does not manage websites or technical SEO deploys. Opteo covers Google Ads only, with no Meta Ads, SEO, website management, or Claude MCP server. Holo (tryholo.ai) scans a website URL to generate ad variations and social posts without a Claude MCP server or live WordPress deploys. Blaze AI helps solo marketers turn a brief into social posts and blog copy rather than deep GA4 or Meta Ads Manager diagnostics.

The Otto CLI for terminal agents is in active development, meaning the hosted MCP endpoint (https://otto.islaintel.com/api/mcp) is the supported connection path today. Third-party platforms not in our official catalog—such as Wix, Webflow, and TikTok—are not supported.

Frequently asked questions

How do I connect WordPress to Claude without sharing passwords in chat?

Connect your site inside Otto using standard credentials, which are stored securely on our server. You then configure Claude using your organization's otto_mcp__ token pointing to https://otto.islaintel.com/api/mcp. Claude interacts with your site through mediated tool calls without ever reading or storing your actual WordPress password.

Can Claude accidentally publish unfinished blog posts to my live website?

No. All new posts and pages generated via Otto's WordPress write tools default to draft status (status: draft). Drafts remain private within your WordPress admin dashboard until you manually review and publish them.

What makes running Claude prompts through MCP better than uploading CSV exports?

Uploading a raw 3,000-row Ads Manager CSV into Claude can consume 40,000 to 80,000 tokens in a single turn, quickly exhausting model context limits. Pasting large Search Console exports into chat burns context for the same reason—thousands of rows in one message—without giving Claude live tools to query aggregated metrics. Querying metrics through Otto MCP returns relevant data subsets instead, reducing token usage by 80–90% while providing direct tools to stage drafts based on the findings.

How are critical pages like checkout or contact forms protected?

Otto core locks checkout, contact, and legal pages behind mandatory human approval gates. Even if a prompt targets site-wide revisions, these designated URLs cannot be modified without your explicit approval.

Can I approve WordPress content updates from my phone?

Yes. With Otto's WhatsApp integration (v1.1.0), you receive notifications of pending content changes and can approve or reject updates directly within WhatsApp without logging into the desktop dashboard.

Connect Claude to Otto MCP to run live WordPress SEO prompts with built-in draft-first protection.