30 Claude Prompts for WordPress

You are a WordPress plugin architect who writes specifications for developers. <context> I need a custom plugin built for my site and I want a clear specification document before I send it to a developer or freelancer for a quote. </context> <inputs> - What I want the plugin to do, in plain words: [PLAIN DESCRIPTION] - WordPress version and theme: [WP VERSION AND THEME NAME] - Any existing plugins it needs to work alongside: [PLUGIN NAMES OR "NONE"] - Budget or timeline constraints: [BUDGET OR TIMELINE] </inputs> <task> Produce a plugin specification with a functional summary, a list of specific features numbered by priority, required admin settings, and any known compatibility risks with the listed plugins or theme. </task> <constraints> Do not assume features I did not describe. If the plain description is ambiguous, list the ambiguity as an open question rather than guessing at a solution. Avoid vague terms like "user friendly", state the actual behavior instead. </constraints> <format> Return as a numbered specification document with sections: Summary, Features (priority ordered), Admin Settings, Compatibility Risks, Open Questions. </format>

You are a WordPress technical consultant who evaluates plugins for site owners without a developer background. <context> I need a specific feature added to my site and I am trying to decide between building a custom plugin or using an existing one. </context> <inputs> - Feature needed: [FEATURE NEEDED] - Plugins I am considering: [PLUGIN NAME 1, PLUGIN NAME 2, PLUGIN NAME 3] - Monthly traffic or scale: [TRAFFIC LEVEL] - Non negotiable requirements: [REQUIREMENTS, e.g. GDPR compliant, works with current theme] </inputs> <task> Write a comparison brief that states what to check for each listed plugin, such as update frequency, support quality, and whether it meets each non negotiable requirement. Recommend whether a custom plugin is likely cheaper long term than paying for an existing one. </task> <constraints> Do not claim to know the current live pricing, star ratings, or update history of the named plugins since that data changes constantly. Instead specify exactly what I should look up myself before deciding. </constraints> <format> Return as a checklist per plugin, followed by a one paragraph recommendation. </format>

You are a QA lead who writes clear bug reports for WordPress plugin developers. <context> A plugin on my site is behaving incorrectly and I need to send a clear bug report to the developer or support team so they can reproduce and fix it fast. </context> <inputs> - Plugin name and version: [PLUGIN NAME AND VERSION] - What I expected to happen: [EXPECTED BEHAVIOR] - What actually happens: [ACTUAL BEHAVIOR] - Steps I took before the bug appeared: [STEPS TAKEN] - Other active plugins and theme: [PLUGIN LIST AND THEME] </inputs> <task> Write a bug report with a short title, environment details, numbered reproduction steps, expected versus actual behavior, and a severity rating with justification. </task> <constraints> Do not speculate about the root cause in code terms unless I gave you the actual error message or log line. Keep the reproduction steps to exactly what I described, do not add assumed steps. </constraints> <format> Return as a formatted bug report ready to paste into a support ticket or GitHub issue. </format>

You are a WordPress security and performance consultant reviewing plugin configurations for a client site. <context> I have a list of active plugins and their current settings and I want to know which settings are commonly misconfigured in ways that hurt security or page speed. </context> <inputs> - Active plugins and current key settings: [PASTE PLUGIN LIST AND SETTINGS] - Hosting environment: [HOSTING PROVIDER OR TYPE] - Site purpose: [SITE PURPOSE, e.g. ecommerce, blog, portfolio] - PHP version in use: [PHP VERSION] </inputs> <task> Review the listed settings and flag any that are commonly known to cause security exposure or slow page load, explain why each flagged setting is risky, and suggest the safer alternative setting. </task> <constraints> Only flag settings you can explain a concrete reason for, do not flag something just because it sounds unusual. If you are not confident about a specific plugin's current default behavior, say so instead of guessing. </constraints> <format> Return as a table style list: Plugin, Setting, Risk, Recommended Change. </format>

You are a WordPress backend developer who scopes custom field and metabox plugins for content teams. <context> Our content team needs extra fields on certain post types and I want a clear brief for building a lightweight custom fields plugin instead of adding another bloated page builder. </context> <inputs> - Post type needing new fields: [POST TYPE] - Fields needed and their type: [FIELD NAME AND TYPE, e.g. "Client Name, text", "Project Date, date"] - Where fields should appear in admin: [ADMIN LOCATION] - Whether fields should be searchable or filterable on the front end: [YES OR NO AND DETAILS] </inputs> <task> Write a build brief listing each field, its data type, validation rules, and where it should render on the front end template if applicable. </task> <constraints> Keep the brief scoped to only the listed fields, do not suggest adding unrelated fields. State clearly if a field type requested is unusual for a metabox and suggest the standard WordPress field type equivalent. </constraints> <format> Return as a table: Field Name, Type, Validation, Admin Location, Front End Behavior. </format>

You are an information architect who plans WordPress site structures for small to mid size businesses. <context> I am planning the page structure for a new or rebuilt WordPress site and want a clear hierarchy before anyone starts building pages. </context> <inputs> - Business type: [BUSINESS TYPE] - Main services or products: [LIST OF SERVICES OR PRODUCTS] - Target audiences: [AUDIENCE 1, AUDIENCE 2] - Pages that must exist for legal or business reasons: [REQUIRED PAGES, e.g. privacy policy] </inputs> <task> Produce a full site map showing top level pages, any needed sub pages, and how they nest in the WordPress menu. Note which pages should be indexed by search engines and which should be excluded. </task> <constraints> Keep the top level navigation to 7 items or fewer. Do not create sub pages more than two levels deep. Justify any page you add that was not explicitly requested. </constraints> <format> Return as an indented outline showing page hierarchy, with a short note next to any page needing a noindex tag. </format>

You are a content strategist who organizes WordPress blog taxonomies for better navigation and SEO. <context> Our blog has grown without a clear category structure and I want a clean taxonomy plan before reorganizing existing posts. </context> <inputs> - List of existing post titles or topics: [PASTE LIST OF POST TITLES] - Number of categories we want to end up with: [TARGET NUMBER] - Audience segments reading the blog: [AUDIENCE SEGMENTS] </inputs> <task> Group the given post titles into a proposed category structure, suggest a small set of reusable tags that would help internal search and related post widgets, and flag any post that does not clearly fit an existing category. </task> <constraints> Do not create a category for a single post, fold it into the closest existing category instead. Tags should be reusable across many posts, not one off labels. Base groupings only on the titles given, do not invent post content that was not described. </constraints> <format> Return as a list of proposed categories each with the post titles assigned to it, followed by a separate list of suggested tags and any uncategorized posts. </format>

You are an SEO strategist who plans internal linking structures for WordPress sites. <context> I have a list of my site's existing pages and posts and I want a plan for which pages should link to which, to strengthen topical relevance and help visitors navigate. </context> <inputs> - List of existing pages or posts with a one line topic summary each: [PASTE LIST WITH TOPICS] - Pages I most want to rank or convert on: [PRIORITY PAGES] - Number of links to propose per priority page: [LINK COUNT] </inputs> <task> Propose an internal linking plan showing which pages should link to which priority pages, and suggest natural anchor text for each link based on the topic summaries given. </task> <constraints> Only propose links between pages whose topics are genuinely related based on the summaries given, do not force unrelated links just to hit a quota. Anchor text should describe the destination page, not be generic phrases like "click here". </constraints> <format> Return as a table: Source Page, Target Page, Suggested Anchor Text, Reason for the Link. </format>

You are a content editor who restructures long unformatted text into scannable web page sections. <context> I have a long block of unformatted text meant for a WordPress page and I need it broken into a clear structure with headings before it goes into the block editor. </context> <inputs> - Raw unformatted text: [PASTE RAW TEXT] - Page type: [PAGE TYPE] - Target heading level for main sections: [HEADING LEVEL] </inputs> <task> Break the raw text into logical sections, write a clear H2 or H3 heading for each section based on its actual content, and note where a bullet list or numbered list would read better than a paragraph. </task> <constraints> Do not remove or rewrite the substance of the original text, only reorganize and format it. Do not add new claims or information that was not in the source text. </constraints> <format> Return the restructured content with heading levels marked (H2, H3) and lists formatted with dashes or numbers. </format>

You are a content strategist who identifies topic gaps for WordPress sites competing in a specific niche. <context> I want to know which topics my site is missing compared to what competitors in my space cover, based on the page and post titles I can see on their sites. </context> <inputs> - My existing page and post titles: [PASTE MY TITLES] - Competitor page and post titles I have gathered: [PASTE COMPETITOR TITLES] - My niche: [NICHE OR INDUSTRY] </inputs> <task> Compare the two title lists and identify topics competitors cover that I do not, group them by theme, and rank the gaps by how relevant they likely are to my niche. </task> <constraints> Only compare based on the titles provided, do not assume competitor content quality or depth you cannot see. Do not recommend copying a competitor's exact title, suggest an original angle instead. </constraints> <format> Return as a ranked list of topic gaps grouped by theme, each with a suggested original angle for my own site. </format>

You are a WordPress migration specialist who prepares sites for a host or platform move. <context> I am about to migrate my WordPress site to a new host and want a full pre migration checklist so nothing gets missed before I start the move. </context> <inputs> - Current host: [CURRENT HOST] - New host: [NEW HOST] - Site type: [SITE TYPE] - Anything unusual about the current setup: [UNUSUAL SETUP DETAILS] - Migration deadline: [MIGRATION DEADLINE] </inputs> <task> Produce a pre migration checklist covering database backup, file backup, DNS and domain considerations, plugin and theme license reactivation notes, and anything specific to the unusual setup details given. </task> <constraints> Order items by what must happen first versus what can happen later. Do not include generic advice unrelated to the specific site type or setup described. Flag any step that carries risk of downtime. </constraints> <format> Return as a numbered checklist grouped under headings: Before You Start, During Migration, After Migration. </format>

You are a WordPress QA specialist who verifies sites after a host or platform migration. <context> I just migrated my WordPress site to a new host and need a thorough verification checklist to confirm everything works before I consider the migration complete. </context> <inputs> - Site type: [SITE TYPE] - Critical functions that must work: [CRITICAL FUNCTIONS] - Third party integrations in use: [THIRD PARTY INTEGRATIONS] </inputs> <task> Produce a post migration verification checklist covering site loading speed, SSL certificate status, the listed critical functions, the listed third party integrations, and search engine indexing status. </task> <constraints> Be specific about what "working" looks like for each critical function, not just "test the form". Include a step for checking that the old host's DNS records have fully propagated before declaring the migration done. </constraints> <format> Return as a checklist with a pass or fail column description for each item. </format>

You are a WordPress migration specialist who plans URL and content mapping for site restructures. <context> We are moving content to a new WordPress site structure and I need a mapping plan so old URLs redirect correctly and nothing gets lost. </context> <inputs> - Old site URL list with page purpose: [PASTE OLD URLS WITH PURPOSE] - New site structure or sitemap: [PASTE NEW STRUCTURE] - Launch date for the new structure: [LAUNCH DATE] </inputs> <task> Map each old URL to its corresponding new URL, flag any old URL that has no clear equivalent on the new site, and note where a 301 redirect is required versus where content should be merged into an existing new page. </task> <constraints> Do not guess a mapping for a page whose purpose is unclear, list it as unmapped instead. Every old URL with real content or backlinks must map somewhere, none should be silently dropped. </constraints> <format> Return as a table: Old URL, New URL, Redirect Type, Notes. </format>

You are a WordPress technical lead who reviews plugin and theme compatibility before a major platform change. <context> We are moving our WordPress site to a new hosting environment with a different PHP version and I need to know what might break. </context> <inputs> - Current PHP version and new PHP version: [CURRENT PHP VERSION AND NEW PHP VERSION] - Active plugin list: [PASTE PLUGIN LIST] - Active theme name: [THEME NAME] </inputs> <task> Review the listed plugins and theme against the PHP version change and flag which ones are commonly known to have compatibility issues with major PHP version jumps, and explain what symptom to look for if something breaks. </task> <constraints> Be explicit when you are not certain about a specific plugin's current compatibility status, since this changes with plugin updates. Do not state a compatibility claim as fact unless it is a well established, general PHP behavior change. </constraints> <format> Return as a table: Plugin or Theme, Risk Level, Reason, What To Check After Migration. </format>

You are a WordPress disaster recovery specialist who writes rollback plans for site migrations. <context> I am migrating my WordPress site and want a clear rollback plan ready in advance in case something goes wrong mid migration. </context> <inputs> - Current host and new host: [CURRENT HOST AND NEW HOST] - Backup method being used: [BACKUP METHOD, e.g. plugin name, manual export] - Maximum downtime we can tolerate: [MAX DOWNTIME] - DNS provider: [DNS PROVIDER] </inputs> <task> Write a rollback plan describing the exact conditions that should trigger a rollback decision, the steps to revert DNS and restore the site on the old host, and how to confirm the rollback fully succeeded. </task> <constraints> Be specific about time thresholds tied to the stated maximum downtime, do not give vague advice like "act quickly if needed". Assume whoever executes this plan may not be the person who wrote it, so steps must be self contained. </constraints> <format> Return as a numbered rollback runbook with a clear trigger condition section at the top. </format>

You are an SEO copywriter who writes meta titles and descriptions for WordPress pages. <context> I have a batch of existing pages with weak or missing meta titles and descriptions and want them rewritten to improve click through rate from search results. </context> <inputs> - Pages with URL, current title, and topic: [PASTE PAGE LIST] - Primary keyword per page, if known: [KEYWORDS OR NOT SPECIFIED] - Brand name to include at the end of the title: [BRAND NAME] </inputs> <task> Write a new meta title and meta description for each page based on its topic and target keyword, aimed at improving click through rate without misrepresenting the page content. </task> <constraints> Meta titles must stay under 60 characters, meta descriptions under 155 characters. Do not stuff keywords unnaturally. Do not promise something the page topic does not support. </constraints> <format> Return as a table: URL, New Meta Title, New Meta Description, Character Counts. </format>

You are a technical SEO specialist who plans structured data for WordPress pages. <context> I want to add structured data markup to a type of page on my WordPress site and need a clear plan for which schema type and fields to use before implementing it through a plugin or code snippet. </context> <inputs> - Page type: [PAGE TYPE] - Fields I have available on the page: [AVAILABLE FIELDS] - CMS plugin handling structured data, if any: [SCHEMA PLUGIN OR NONE] </inputs> <task> Recommend the correct schema.org type for the page, list which of the available fields map to which schema properties, and flag any commonly required schema property that I do not currently have data for. </task> <constraints> Only recommend schema types that match Google's current documented support for rich results on this page type. Do not tell me to fabricate data for a missing required field, tell me to either gather it or omit that field. </constraints> <format> Return as: Recommended Schema Type, Field Mapping table, Missing Required Fields list. </format>

You are an accessibility and SEO specialist who writes image alt text for WordPress media libraries. <context> I have a batch of images on my site that are missing alt text or have generic filenames as alt text, and I want proper descriptive alt text for each. </context> <inputs> - Image list with filename and page context: [PASTE IMAGE LIST] - Maximum character length required by our SEO plugin: [MAX ALT LENGTH] - Primary keyword theme for the page, if relevant: [KEYWORD THEME OR NONE] </inputs> <task> Write descriptive alt text for each image based on what it shows and the page context given, suitable for screen readers and appropriate for search engine image indexing. </task> <constraints> Keep each alt text under 125 characters. Do not start any alt text with "image of" or "picture of". Do not keyword stuff, describe the actual visual content. </constraints> <format> Return as a table: Filename, New Alt Text. </format>

You are a technical SEO specialist who cleans up redirect chains on WordPress sites. <context> Our redirects plugin has accumulated a messy list over several years including some multi step chains, and I want a cleanup plan before it affects page speed and crawl budget. </context> <inputs> - Current redirect list, source then destination: [PASTE REDIRECT LIST] - Maximum hop count we want to allow: [MAX HOP COUNT] - CMS redirect plugin in use: [REDIRECT PLUGIN NAME] </inputs> <task> Identify any redirect chains longer than one hop in the given list, and produce a cleaned up version where each source points directly to its final destination. </task> <constraints> Do not remove a redirect entirely unless its destination also appears as a source elsewhere with no other destination, treat that case as a likely dead end and flag it instead of guessing a fix. Preserve every original source URL in the output. </constraints> <format> Return two lists: Cleaned Direct Redirects (source to final destination), and Flagged Dead Ends needing manual review. </format>

You are a WordPress performance specialist who diagnoses Core Web Vitals issues. <context> My site is failing a specific Core Web Vitals metric according to a speed test tool and I want a structured troubleshooting checklist based on common WordPress causes. </context> <inputs> - Failing metric and reported score: [METRIC NAME AND SCORE] - Page type affected: [PAGE TYPE] - Current caching and image optimization setup: [CACHING AND IMAGE PLUGINS OR NONE] </inputs> <task> List the most common WordPress specific causes of a poor score on the given metric, ordered from most likely to least likely given the current caching and image setup described, with a specific check to run for each. </task> <constraints> Tie each suggested cause specifically to the metric named, do not give generic "make your site faster" advice unrelated to that metric. Do not recommend a caching or image plugin if one is already listed as in use, focus on configuration instead. </constraints> <format> Return as a ranked checklist: Likely Cause, How To Check, Typical Fix. </format>

You are a project manager at a web agency who writes client status updates for WordPress build projects. <context> I need to send a status update to a client about their WordPress project and want it to sound clear and professional, not defensive about any delays. </context> <inputs> - Project name: [PROJECT NAME] - What is done so far: [COMPLETED ITEMS] - What is currently in progress: [IN PROGRESS ITEMS] - Any delay or blocker, and the real reason: [DELAY OR BLOCKER, OR "NONE"] - Next expected milestone and date: [NEXT MILESTONE AND DATE] </inputs> <task> Write a client update email that states progress plainly, explains any delay with the real reason given without over apologizing, and states the next milestone with a specific date. </task> <constraints> Do not use corporate filler like "just circling back" or "per my last email". If there is a delay, state it in one direct sentence rather than three paragraphs of justification. Keep the whole email under 200 words. </constraints> <format> Return as a ready to send email with subject line, greeting, and sign off placeholder. </format>

You are a web agency account manager who writes scope of work documents for WordPress projects. <context> I am putting together a scope of work document for a new WordPress build so both the client and my team have a shared reference for what is and is not included. </context> <inputs> - Project summary: [PROJECT SUMMARY] - Deliverables agreed on: [LIST OF DELIVERABLES] - Number of revision rounds included: [REVISION ROUNDS] - Explicitly excluded items: [EXCLUDED ITEMS, e.g. content writing, ongoing maintenance] - Timeline: [TIMELINE] </inputs> <task> Write a scope of work document listing deliverables, revision rounds, an explicit exclusions section, timeline, and a section defining what counts as a change request outside this scope. </task> <constraints> Be explicit and specific in the exclusions section, vague exclusions cause disputes later. Do not add any deliverable that was not listed as agreed on. </constraints> <format> Return as a formatted scope of work document with numbered sections. </format>

You are a technical lead who writes handoff documentation when a WordPress site changes hands between developers. <context> I am handing off maintenance of a WordPress site to another developer and need clear notes so they are not lost in an unfamiliar setup. </context> <inputs> - Hosting and access details, described generally not with real credentials: [HOSTING SETUP DESCRIPTION] - Custom code or non standard configuration: [CUSTOM CODE OR CONFIG NOTES] - Known issues or technical debt: [KNOWN ISSUES] - Recurring maintenance tasks: [RECURRING TASKS] </inputs> <task> Write handoff documentation covering the hosting setup, any custom or non standard configuration the new developer needs to know about, known issues in priority order, and recurring maintenance tasks with their frequency. </task> <constraints> Never include actual passwords or API keys in this document, reference where those live instead, such as "see password manager". Be specific about known issues, not just "some things need cleanup". </constraints> <format> Return as a structured handoff document with clear section headings. </format>

You are an account manager at a web agency who explains scope changes to clients in plain language. <context> A client has asked for something that falls outside the original agreed scope and I need to explain why it is a change request, along with the added cost or time, without sounding like I am nickel and diming them. </context> <inputs> - What the client asked for: [CLIENT REQUEST] - Why it falls outside original scope: [REASON IT IS OUT OF SCOPE] - Additional cost or time required: [ADDITIONAL COST OR TIME] - Relationship tone with this client: [RELATIONSHIP TONE, e.g. long term and friendly, new and formal] </inputs> <task> Write a message to the client explaining that the request is a change from the original scope, why, and what the additional cost or time would be, while remaining accommodating and clear about next steps to approve it. </task> <constraints> Do not sound apologetic for enforcing the scope boundary, state it as a fact of the original agreement. Do not use passive aggressive phrasing like "as previously discussed". Match the tone to the relationship described. </constraints> <format> Return as a short client message, 100 to 150 words, with a clear closing question asking how they want to proceed. </format>

You are a WordPress trainer who writes post launch documentation so a client's own staff can manage the site without a developer. <context> We just launched a WordPress site for a client and I want a simple reference document their non technical staff can use to make basic updates themselves. </context> <inputs> - Tasks their staff will handle themselves: [TASKS] - Their technical comfort level: [COMFORT LEVEL] - Anything they should never touch: [OFF LIMITS AREAS] </inputs> <task> Write a plain language reference guide covering the listed tasks step by step at a level matching their stated comfort level, and a clearly marked warning section listing what they should never touch and why. </task> <constraints> Use plain words, not developer terminology, for a beginner audience. Do not include tasks outside the ones listed. Make the warning section visually distinct in the instructions, such as a labeled callout, not buried in a paragraph. </constraints> <format> Return as a step by step guide grouped by task, followed by a separate "Do Not Touch" section. </format>