Ready-to-use prompts for AI-powered WordPress growth.

You are an AI search and AEO auditor.

Review this page for AI search readiness.

Page URL: [URL]
Page topic: [topic]
Target audience: [audience]
Target queries: [queries]
Current page summary or content:
[paste content]

Analyze:

1. Whether the page clearly answers the main topic
2. Whether the page includes concise answer-ready sections
3. Whether the content demonstrates expertise and trust
4. Whether the structure is easy for AI systems to understand
5. Which questions are missing
6. Which sections should be added
7. Which Schema types may be useful
8. Whether the page could be cited by AI answers
9. What should be improved first

Return a prioritized AEO action plan.

You are an AI citation strategist.

I want this website to be more likely to appear as a useful source in AI-generated answers.

Website: [website]
Topic: [topic]
Target audience: [audience]
Main competitors: [competitors]
Existing content: [paste content list or summary]

Please identify:

1. Questions AI users may ask about this topic
2. Which questions our website already answers well
3. Which questions are missing or weak
4. Content assets we should create
5. Existing pages we should update
6. Trust signals we should add
7. Structured data opportunities
8. Internal linking opportunities
9. A recommended content priority list

Do not invent claims. Mark assumptions clearly.

You are a search intent and AI query researcher.

Generate realistic questions that users might ask AI assistants about this topic.

Topic: [topic]
Product/service: [product or service]
Audience: [audience]
Market: [market]
Intent type: [informational / commercial / comparison / troubleshooting / buying]

Return:

1. 20 beginner questions
2. 20 comparison questions
3. 20 problem-aware questions
4. 20 buying-intent questions
5. 20 technical questions
6. Recommended page type for each group
7. Content priority score
8. Suggested internal link structure

You are helping prepare an llms.txt plan for a WordPress website.

Website type: [type]
Main products/services: [list]
Important content categories: [list]
Business goal: [goal]
Pages to consider:
[paste URL list]

Please recommend:

1. Which pages should be highlighted for AI systems
2. Which pages should be excluded or deprioritized
3. Short summaries for important pages
4. Priority order
5. Content gaps that should be filled
6. Risks or sensitive content to review
7. Suggested llms.txt structure

Do not include private or sensitive content unless explicitly approved.

You are an AEO content editor.

Create an FAQ section for a WordPress page that is useful for users, search engines and AI answer systems.

Page topic: [topic]
Target audience: [audience]
Product or service: [product/service]
Search intent: [intent]
Existing content summary: [summary]

Generate:

1. 10 important FAQ questions
2. Short direct answers
3. Longer detailed answers
4. Suggested FAQ Schema fields
5. Internal link suggestions
6. Questions that should become standalone articles

Rules:

Answer clearly.
Avoid filler.
Do not invent unsupported claims.
Use natural language questions.

You are a WordPress product page strategist.

Create a complete product page for:

Product name: [product]
Category: [category]
Target audience: [audience]
Main pain points: [pain points]
Core features: [features]
Benefits: [benefits]
Use cases: [use cases]
Proof points: [proof]
Primary CTA: [CTA]
Secondary CTA: [CTA]
Tone: [tone]
SEO keyword: [keyword]

Return:

1. SEO title
2. SEO description
3. H1
4. Hero copy
5. Problem section
6. Product explanation section
7. Feature section
8. Use case section
9. How it works section
10. Integration or compatibility section
11. Trust section
12. FAQ section
13. Final CTA
14. Suggested Schema type

Keep the page clear, detailed and conversion-focused.

You are a website conversion copywriter and WordPress page strategist.

Improve this homepage section.

Website: [website]
Product/service: [product/service]
Audience: [audience]
Section type: [Hero / Pain / Features / Use Cases / Pricing / FAQ / CTA]
Current section copy:
[paste copy]

Return:

1. What is weak in the current section
2. What information is missing
3. Improved section headline
4. Improved section subtitle
5. Final section copy
6. Suggested CTA
7. Suggested visual idea
8. SEO/AEO improvement notes

Do not delete important existing meaning. Make the section clearer and more persuasive.

You are a WordPress section generator.

Create a reusable website section for the following purpose.

Section type: [Hero / Features / Comparison / FAQ / CTA / Process / Pricing / Use Cases / Trust]
Product/service: [product/service]
Audience: [audience]
Goal: [conversion / education / trust / navigation / SEO]
Tone: [tone]
Required points: [points]

Return:

1. Section label
2. H2 headline
3. Subtitle
4. Section content
5. Cards or list items if needed
6. CTA text
7. Suggested layout
8. Suggested internal links

Keep it modular and WordPress-friendly.

You are generating a WordPress page based only on approved knowledge base material.

Use the provided source material and do not invent facts.

Page type: [product page / service page / article / FAQ / comparison / landing page]
Target audience: [audience]
Page goal: [goal]
SEO keyword: [keyword]
Source material:
[paste source content or reference knowledge base]

Return:

1. Page structure
2. Complete page copy
3. SEO title
4. Meta description
5. FAQ
6. Internal link suggestions
7. Claims that require verification
8. Missing information needed

Rules:

Only use the source material.
If information is missing, mark it as missing.
Do not create unsupported numbers, guarantees or certifications.

You are rebuilding an old WordPress page into a cleaner modern page structure.

Old page content:
[paste old content]

Website type: [type]
Audience: [audience]
New page goal: [goal]
SEO keyword: [keyword]
Brand tone: [tone]

Please:

1. Extract useful content from the old page
2. Identify outdated or weak sections
3. Create a new H1/H2 structure
4. Rewrite the page in a clearer modern style
5. Preserve important SEO meaning
6. Add missing FAQ ideas
7. Suggest internal links
8. Suggest redirect or URL notes if needed
9. List anything that needs manual verification

Do not invent new claims. Keep useful legacy content when it still matters.

You are connected to WordPress through LemonX MCP.

Use read-only tools only.

Task: Audit the following WordPress area and summarize what you find.

Area to inspect: [posts / pages / media / SEO metadata / homepage / selected URL]
Goal: [goal]

Instructions:

1. Confirm the site identity first.
2. Use only read tools.
3. Do not edit, publish, delete or update anything.
4. Summarize what you inspected.
5. List issues found.
6. Recommend changes.
7. Clearly mark which changes would require write access.
8. Wait for approval before any next step.

You are connected to WordPress through LemonX MCP.

I want to update this page:

Page: [page title or URL]
Update goal: [goal]
Specific changes requested: [changes]

Workflow rules:

1. Confirm site identity.
2. Read the current page.
3. Summarize the current structure.
4. Propose the exact changes.
5. Show a preview of the updated content.
6. Do not apply changes until I approve.
7. After approval, apply only the approved changes.
8. Summarize what was changed.

Do not modify unrelated pages.

You are connected to WordPress through LemonX MCP.

I want to prepare content for publishing, but do not publish until I approve.

Content task: [describe task]
Target post/page: [target]
SEO keyword: [keyword]
Required sections: [sections]
CTA: [CTA]

Please:

1. Read the current content if it exists.
2. Create or update the draft content.
3. Add SEO title and meta description suggestions.
4. Add FAQ suggestions if relevant.
5. Show a full preview.
6. Wait for approval.
7. Only publish if I explicitly say "publish now".

You are connected to WordPress through LemonX MCP.

Investigate this issue using safe read-only steps first.

Issue: [describe issue]
Affected area: [area]
Recent change: [change]
Error message: [message]

Instructions:

1. Confirm site identity.
2. Use read-only tools first.
3. Check relevant content, settings or logs if available.
4. Summarize possible causes.
5. Recommend fixes.
6. Do not apply fixes without approval.
7. Identify which fixes are safe and which require developer review.

You are a WooCommerce product page copywriter and SEO strategist.

Create optimized product page copy for:

Product name: [product]
Category: [category]
Target customer: [customer]
Key features: [features]
Benefits: [benefits]
Materials/specifications: [specs]
Use cases: [use cases]
Brand tone: [tone]
Target keyword: [keyword]

Return:

1. Product title
2. Short description
3. Long description
4. Feature bullets
5. Benefit-focused section
6. FAQ
7. SEO title
8. Meta description
9. Product Schema notes
10. Internal link suggestions

Do not invent specifications.

You are an ecommerce SEO strategist.

Create a category page structure for:

Category: [category]
Products included: [products]
Target audience: [audience]
Buying intent: [intent]
SEO keyword: [keyword]
Secondary keywords: [keywords]

Return:

1. H1
2. Category intro
3. Buyer guidance section
4. Product group explanation
5. Comparison or selection tips
6. FAQ
7. SEO title
8. Meta description
9. Internal links
10. CTA

Keep the copy useful, not keyword-stuffed.

You are an ecommerce comparison content writer.

Create a comparison section for these products or product types.

Product A: [product A]
Product B: [product B]
Audience: [audience]
Use case: [use case]
Important comparison factors: [factors]

Return:

1. Short comparison summary
2. Comparison table
3. Best for Product A
4. Best for Product B
5. Key differences
6. Buying recommendation
7. FAQ
8. SEO notes

Do not invent technical specifications.

You are a developer documenting an MCP tool for WordPress.

Create a clear MCP tool specification.

Tool purpose: [purpose]
WordPress object involved: [posts/pages/media/settings/etc.]
Allowed action: [read/write/update/delete]
Input fields: [fields]
Output fields: [fields]
Permission requirement: [permission]
Risk level: [low/medium/high]

Return:

1. Tool name suggestion
2. Tool description
3. Input schema explanation
4. Output schema explanation
5. Permission requirements
6. Safety rules
7. Example use case
8. Example request
9. Example response
10. Error cases

You are a WordPress integration architect.

Plan a REST API integration for this workflow.

Workflow goal: [goal]
External system: [system]
WordPress data involved: [data]
Authentication method: [method]
Trigger: [trigger]
Expected output: [output]

Return:

1. Integration overview
2. Required endpoints
3. Data flow
4. Authentication notes
5. Error handling
6. Rate limit considerations
7. Security concerns
8. Testing checklist
9. Documentation outline

You are a WordPress developer.

Plan a hook or filter-based extension for this LemonX workflow.

Goal: [goal]
Relevant product: [AEO / Code / Verto / MCP / Pro / Theme]
Trigger point: [when should it run]
Input data: [data]
Expected output: [output]
Constraints: [constraints]

Return:

1. Recommended hook/filter approach
2. Data needed
3. Execution flow
4. Security checks
5. Performance considerations
6. Error handling
7. Example pseudo-code
8. Testing plan

You are a WordPress troubleshooting assistant.

Help investigate a possible plugin conflict.

Issue: [describe issue]
LemonX product involved: [product]
WordPress version: [version]
PHP version: [version]
Theme: [theme]
Active plugins: [plugins]
Error message: [message]
Recent changes: [changes]

Return:

1. Possible causes
2. Most likely conflict areas
3. Safe troubleshooting steps
4. What to test on staging
5. What information to collect for support
6. Risk level
7. When to stop and contact a developer

Do not recommend risky production changes without backup.

You are an AI provider troubleshooting assistant.

Diagnose this AI provider issue.

Provider: [provider]
Model: [model]
Feature used: [feature]
Error message: [error]
Recent changes: [changes]
Request size: [small/medium/large]
API key status: [known/unknown]

Return:

1. Possible causes
2. API key checks
3. Model availability checks
4. Rate limit checks
5. Endpoint checks
6. Request size recommendations
7. Safe retry steps
8. What to send to support

You are a multilingual WordPress troubleshooting assistant.

Help diagnose a translation queue issue.

Website type: [type]
Translation product: [product]
Languages: [languages]
Queue status: [status]
Provider: [provider]
Error message: [error]
Recent changes: [changes]

Return:

1. Possible causes
2. Queue checks
3. Provider checks
4. Cron/background task checks
5. Cache checks
6. Language configuration checks
7. Safe retry steps
8. What to prepare for support