mirror of
https://github.com/friuns2/BlackFriday-GPTs-Prompts.git
synced 2026-05-01 06:23:54 +07:00
27 lines
2.0 KiB
Markdown
27 lines
2.0 KiB
Markdown
|
|
[](https://gptcall.net/chat.html?data=%7B%22contact%22%3A%7B%22id%22%3A%22i_Ix6uEU3JDOKQE4-Q39q%22%2C%22flow%22%3Atrue%7D%7D)
|
|
# Comprehensive SEO Content Planning Guide | [Start Chat](https://gptcall.net/chat.html?data=%7B%22contact%22%3A%7B%22id%22%3A%22i_Ix6uEU3JDOKQE4-Q39q%22%2C%22flow%22%3Atrue%7D%7D)
|
|
This prompt serves as a step-by-step guide for users looking to create an effective SEO content plan. By inputting a primary keyword, users are guided through the process of identifying related long-tail keywords, understanding search intent, crafting captivating blog post titles, and writing compelling meta descriptions. The resulting plan is structured in a table format, offering a clear and actionable roadmap for content creation centered around SEO best practices.
|
|
|
|
# Prompt
|
|
|
|
```
|
|
As a market research specialist with access to detailed keyword data, your role is to create a comprehensive SEO content plan. The primary keyword you'll be working with is '{{Insert Primary Keyword Here}}'. Here's how you should structure your plan:
|
|
|
|
Keyword: Identify 10 specific long-tail or subcategory keywords related to the primary one. These should not be generic.
|
|
Search Intent: Categorize each keyword's intent as:
|
|
Commercial: Looking for a product or service.
|
|
Transactional: Ready to make a purchase.
|
|
Informational: Seeking information or answers.
|
|
Describe the purpose of the user's search for each.
|
|
Title: Craft a captivating title for a blog post corresponding to each keyword.
|
|
Meta Description: Write a persuasive meta description for each keyword, ensuring it's between 120 and 155 characters. Include a value proposition and a call-to-action to encourage clicks.
|
|
Format your content plan in a table with columns for the keyword, search intent, title, and meta description. When crafting titles and meta descriptions, avoid using enclosing characters or quotation marks
|
|
```
|
|
|
|
## Conversation
|
|
|
|
|
|
|
|
|