Every good professor keeps a well-worn folder of lesson plans. Every smart site owner should keep a folder of reliable AI prompts. Below are 30 copy-ready prompts, organized by task, that you can paste into your favorite AI assistant. Just replace anything in [BRACKETS] with your own details.
These prompts are starting points. The more context you give (audience, tone, goals, constraints), the better the results. And as always in Professor Press’s classroom: you review, edit, and fact-check before anything goes live.
Heads up: Never paste passwords, API keys, database credentials, or private customer data into a prompt. Swap them for placeholders like [API_KEY] or [CUSTOMER_NAME] first.
Content Prompts
1. Blog post outline
Create a detailed outline for a blog post titled “[TITLE]” for [AUDIENCE]. The goal is to help readers [GOAL]. Include an intro hook, 5–7 H2 sections with H3 subpoints, and the key questions each section should answer. Flag any claims that will need a source.
2. Clarity rewrite
Rewrite the following text so a beginner can understand it. Keep my friendly tone, use short sentences, and don’t add new facts: [PASTE TEXT]
3. Intro hooks
Write five different opening paragraphs (2–3 sentences each) for a post about [TOPIC] aimed at [AUDIENCE]. Use a different approach for each: a question, a relatable problem, a surprising angle, a short story, and a bold promise I can actually deliver.
4. FAQ section
Based on this article, list 6 questions a reader might still have, with a 2–3 sentence answer each. Only use information in the article; mark anything that needs outside verification: [PASTE ARTICLE]
5. Content refresh
Review this older post about [TOPIC] and suggest what to update: outdated sections, missing subtopics, weak headings, and places to add examples. Return a prioritized list, not a rewrite: [PASTE POST]
SEO Prompts
6. Meta descriptions
Write three meta descriptions under 155 characters for a page about [TOPIC]. Lead with the reader’s benefit and include the phrase “[KEYWORD]” naturally.
7. SEO titles
Suggest 8 SEO title options under 60 characters for a post about [TOPIC] targeting “[KEYWORD]”. Make them specific and click-worthy without clickbait.
8. Search intent check
For the search query “[KEYWORD]”, describe the most likely search intent (informational, commercial, transactional, or navigational), what format the ideal page should take, and which subtopics it must cover.
9. Internal links
Here is a list of my existing posts with URLs: [PASTE LIST]. Here is my new article: [PASTE ARTICLE]. Suggest up to 6 internal links, showing the exact sentence where each link fits and the anchor text to use.
10. Alt text
Write concise alt text (under 125 characters) for an image showing [DESCRIBE IMAGE], used in a post about [TOPIC]. Describe what matters in context; don’t start with “image of.”
11. FAQ schema draft
Convert these on-page questions and answers into valid FAQPage JSON-LD. Don’t add any questions that aren’t in the text: [PASTE Q&A]
Design Prompts
12. Block pattern
Create WordPress block editor markup (core blocks only) for a [SECTION TYPE, e.g. “three-column features section”] with a heading, short text, and a button in each column. Use theme.json preset colors and spacing instead of hard-coded values.
13. CSS tweak
Write minimal CSS to [DESIRED CHANGE] on my WordPress site. The element’s selector is [SELECTOR]. Explain where to add it and make sure it doesn’t affect [AREA TO LEAVE ALONE].
14. Color palette
Suggest a 5-color palette for a [INDUSTRY] website with a [MOOD] feel, based on the brand color [HEX]. Give hex codes, suggested roles (background, text, accent, etc.), and check text/background pairs against WCAG AA contrast.
15. Accessibility review
Review this HTML for accessibility problems: heading order, missing labels, alt text, link text, focus visibility, and ARIA misuse. List issues by severity with a suggested fix for each: [PASTE HTML]
16. Featured image brief
Write an image-generation prompt for a featured image for a post titled “[TITLE]”. Style: [STYLE, e.g. “flat illustration, friendly, bright”]. Aspect ratio 16:9, no text in the image, no real people or trademarks.
Code Prompts
17. Secure snippet
Write a WordPress code snippet that [FEATURE]. Follow WordPress coding standards: prefix functions with [PREFIX]_, sanitize all input, escape all output, use nonces and current_user_can() for any form or action, and explain each part briefly.
18. Explain this code
Explain what this WordPress code does, line by line, in plain English. Point out any hooks it uses and anything that could cause conflicts or security issues: [PASTE CODE]
19. Debug an error
I’m getting this WordPress error (paths and secrets redacted): [PASTE ERROR]. It started after [RECENT CHANGE]. Explain the likely cause and give me a step-by-step way to investigate safely on a staging site.
20. Security review
Review this WordPress plugin code for security issues: missing sanitization, unescaped output, missing nonces, missing capability checks, SQL injection risk, and unprefixed names. List each problem with the fixed code: [PASTE CODE]
21. Custom post type
Write the code to register a custom post type called “[NAME]” with support for title, editor, thumbnail, and excerpt, visible in the block editor (show_in_rest), with an archive at /[SLUG]/. Use the prefix [PREFIX]_ and translatable labels.
Marketing Prompts
22. Newsletter digest
Write a friendly weekly newsletter for [SITE NAME] featuring these posts: [PASTE TITLES + SUMMARIES]. Include a short personal intro, one line per post on why it’s worth reading, and a single call to action. Suggest 3 subject lines.
23. Welcome email
Write a welcome email for new subscribers to [SITE NAME], which helps [AUDIENCE] with [TOPIC]. Thank them, deliver [LEAD MAGNET] with a link placeholder, say what they’ll receive and how often, and invite them to reply with their biggest question.
24. Social repurposing
Turn this blog post into [NUMBER] social posts for [PLATFORM]. Each should stand on its own, share one useful idea, and end with a soft invitation to read the full post: [PASTE POST]
25. Lead magnet ideas
Suggest 10 lead magnet ideas for a site about [TOPIC] aimed at [AUDIENCE]. Each should be quick to create, genuinely useful, and closely related to my most popular post, “[POST TITLE]”.
26. Honest product review structure
Create an outline for an honest review of [PRODUCT] based on my experience using it for [USE CASE]. Include sections for who it’s for, who should skip it, pros, cons, alternatives, and a place for my affiliate disclosure near the top.
Maintenance Prompts
27. Maintenance checklist
Create a monthly WordPress maintenance checklist for a [SITE TYPE, e.g. “small WooCommerce store”]. Cover backups, updates, security, performance, broken links, and content review, with an estimated time for each task.
28. Plugin audit
Here is my list of active plugins: [PASTE LIST]. Group them by purpose, flag any that seem to overlap, and list questions I should ask before removing any of them.
29. Speed troubleshooting
My WordPress site’s PageSpeed Insights report shows these issues: [PASTE ISSUES]. Explain each in plain English and suggest fixes in order of likely impact, noting which need a developer.
30. Update plan
I need to update WordPress core, my theme [THEME], and these plugins: [LIST]. Write a safe step-by-step update plan, including backups, staging tests, what to check afterward, and how to roll back if something breaks.
Tip: Save your favorites in a notes app or text expander, and refine them each time you use them. Your best prompts will slowly become tailored to your exact site and voice.
Professor’s note: AI can state wrong facts with total confidence. Treat every answer like a student’s first draft: promising, but it needs your red pen.
Want to go deeper? Browse practical workflows in AI + WordPress, try building a plugin in our vibe coding section, and find more handy utilities on the tools page.
Homework
- Copy your five most useful prompts from this list into a saved note.
- Use one of them on real work this week and edit the result into your own voice.
- Improve one prompt by adding more context, and compare the before and after output.
