The Shift Around Cialdini, R. B. (2001). Influence

Article
by Jule
The Shift Around Cialdini, R. B. (2001). Influence

or "H3:". The opening before the first H2 must be normal paragraphs, not bullet points. Put each heading on its own line, never inline after a sentence. Put each bullet item on its own line starting with "- ". Leave a blank line between paragraphs, headings, and lists. Avoid em dashes. Use normal punctuation instead. No preface, no notes, no postscript, no markdown fences.

  1. Identify the Core Task:

  • The input is a book citation: "Cialdini, R. B. (2001). Influence: Science And Practice (4th Ed.). Allyn &"

  • The user wants an SEO article based on this, but the output must be a JSON object with specific keys and formatting rules.

  • I need to "repair" the input keyword, come up with a title, and generate the article content in markdown format within the JSON.

  • The article must be at least 1500 words (implied by "The length of the article is at least 1500 words" in the initial prompt, but the output rules override some of that; I need to reconcile).

  • Actually, the initial prompt says: "The length of the article is at least 1500 words." But the output rules say: "Output ONLY a JSON object with keys: "repair-input-keyword", "title", "contents". "contents" must contain the full article in Markdown." and "Use H2 headings only (no H1) inside "contents"." and other formatting rules.

  • I need to generate a JSON object. The article inside "contents" must be in markdown, at least 1500 words, using H2 headings only (no H1 inside contents, but the overall article uses h1 as the content title as H1 heading? Wait: "Use the content title as the H1 heading." and "Make sure the title is properly ordered and does not pass the semantic structure level of the page." and "Use heading markdown h1, h2, h3, etc. Use the content title as the H1 heading." But then output rules say: "Use H2 headings only (no H1) inside "contents"." This is a bit contradictory. I need to interpret: The JSON has a "title" key and a "contents" key. The "contents" should be the article body, which should start with H2 headings only, but the overall structure might have an H1? Actually, the prompt says: "Use heading markdown h1, h2, h3, etc. Use the content title as the H1 heading. But then output rules: "Use H2 headings only (no H1) inside "contents". And "Do not write literal labels like "H2:" etc. And: "The opening before the first H2 must be normal paragraphs, not bullet points. So I think the intent is: The JSON keys: "title" will be the main H1 title. The "contents" will be the markdown article body, which should start with paragraphs, then H2s, but no H1 inside contents. The overall article has an H1 which is the title. But the output is just JSON with title and contents. I'll make the "title" key have the article title (which would be H1 on the page), and "contents" have the body starting with paragraphs then H2s, no H1 inside. That satisfies "Use H2 headings only (no H1) inside "contents"." and "Use the content title as the H1 heading." (the title key is the H1).

  • Now, the input keyword/reference is "Cialdini, R. B. (2001). Influence: Science And Practice (4th Ed.). Allyn &". The "main named entity" is Robert Cialdini's book "Influence: Science and Practice". I need to "preserve the main named entity, product name, or core term from the input keyword. Do not replace it with a generic theme." So the article should be about Cialdini's Influence, specifically the 4th edition or the principles.

  • I need to "repair-input-keyword". What does that mean? Probably clean up the keyword, maybe extract the core term. The input is a citation. I'll set "repair-input-keyword" to something like "Cialdini Influence Science Practice 4th Edition" or similar.

  • Now, I need to generate a unique, SEO-optimized article about Cialdini's Influence: Science and Practice (4th Edition), at least 1500 words in the contents markdown, using H2 headings only (no H1 inside), with proper formatting, casual tone, etc. But the output must be JSON only, no preface.

  • Let's outline the article structure mentally:

  • Title: Something like "Mastering Persuasion: A Deep Dive into Cialdini's Influence (4th Edition)"

  • Contents: Start with a paragraph introducing the topic. Then H2 sections. I need at least enough H2s to reach 1500 words. I'll aim for maybe 8-10 H2 sections, each with substantial paragraphs (~150-200 words each, total ~1500+). I need to be careful with word count.

  • Constraints check:

  • JSON output only with keys: "repair-input-keyword", "title", "contents"

  • "contents" in Markdown

  • Use H2 headings only (no H1) inside contents

  • Do not write literal labels like "H2:" or "H3:"

  • The opening before the first H2 must be normal paragraphs, not bullet points

  • Put each heading on its own line, never inline after a sentence

  • Put each bullet item on its own line starting with "- "

  • Leave a blank line between paragraphs, headings, and lists

  • Avoid em dashes. Use normal punctuation instead.

  • No preface, no notes, no postscript, no markdown fences.

  • Casual and friendly tone, like saying "guys" or other slang, so it feels natural and conversational.

  • Focus on creating high-quality content and providing value to readers.

  • Optimize paragraphs: Include main keywords in the beginning of the paragraph.

  • Each title paragraph content must contain at least 300 words. (This might mean each section's paragraph? Or the overall? I'll interpret as each major paragraph or section should be substantial, but the rule says "Each title paragraph content must contain at least 300 words." Might be a mistranslate; I'll make sure each H2 section has substantial content, maybe 300+ words per section? That would be too long for 1500 total if 5 sections. I'll aim for the whole article 1500+ words, and each section reasonably long.)

  • Actually, re-read: "Each title paragraph content must contain at least 300 words." Maybe it means the content under each title/heading should be at least 300 words. I'll try to make each H2 section ~300 words, but with maybe 5 sections that's 1500. I'll do 5 H2 sections, each with ~300 words. That fits 1500+.

  • Use bold, italic and strong tags. (In markdown, bold, italic, strong). I'll use ** and *.

  • Optimize paragraphs: Include main keywords in the beginning of the paragraph. I'll start each paragraph with "Cialdini" or "Influence" etc.

  • Let's plan the JSON:

  • "repair-input-keyword": "Cialdini Influence Science Practice 4th Edition"

  • "title": "Mastering the Psychology of Persuasion: A Deep Dive into Cialdini's Influence (4th Edition)"

  • "contents": markdown string with opening paragraph, then H2 sections. No H1 inside. Each H2 on its own line. Blank lines between sections. Paragraphs with keywords at start. Casual tone.

  • Now, I need to actually write the content. This is the heavy part. I need to generate ~1500 words in markdown, with H2s, following all formatting rules. I'll structure it carefully.

  • Let's outline the H2 sections. I'll pick 5 core principles from Cialdini's Influence: Reciprocity, Commitment and Consistency, Social Proof, Authority, Liking, Scarcity. Maybe 6 sections. Each ~250-300 words to hit 1500.

  • Rules reminder:

  • Avoid em dashes ( - ). Use normal punctuation (-- or just commas/phrases). I'll be careful.

  • No bullet points before first H2. Opening must be normal paragraphs.

  • Each heading on its own line, never inline after sentence.

  • Bullets if any on own line starting with "- ". I might use bullets for lists, but careful.

  • Leave blank line between paragraphs, headings, and lists.

  • Casual tone: "guys", slang naturally. I'll incorporate "hey", "okay", "so", etc., but keep it readable.

  • Main keywords at beginning of paragraphs. The main keyword/entity is "Cialdini" and "Influence". I'll start paragraphs with "Cialdini's" or "Influence".

  • Let's start drafting the contents in mind, then format to JSON.

  • I'll write the opening paragraph: ~150-200 words, starting with "Cialdini" or "Influence". Then H2 sections.

  • Section H2s:

  1. "The Six Universal Principles of Persuasion"
  2. "Reciprocity: Giving to Get"
  3. "Commitment and Consistency: The Power of Our Word"
  4. "Social Proof: Why We Follow the Crowd"
  5. "Authority: Following the Leader"
  6. "Liking: We Say Yes to People We Like"
  7. "Scarcity: The Fear of Missing Out" That's 7 sections. Each ~215 words to hit 1500. I'll aim for ~220-240 each.
  • I need to ensure each paragraph starts with main keyword. I'll use "Cialdini" or "Influence" at the start of paragraphs.
  • Tone: casual, friendly. "Hey everyone", "okay", "so here's the thing", etc.
  • I'll write the content now mentally, then output JSON.
  • One tricky part: "Avoid em dashes. Use normal punctuation instead." So I'll avoid "
  • " entirely. Use "
  • " or commas.
  • "Put each bullet item on its own line starting with "- "." I might not use bullets, but if I do, format correctly.
  • "Leave a blank line between paragraphs, headings, and lists." I'll ensure that.
  • "The opening before the first H2 must be normal paragraphs, not bullet points." So after the opening paragraph(s), then first H2.
  • "Do not write literal labels like "H2:" or "H3:"." So just the heading text, e.g., "The Six Universal Principles of Persuasion" on its own line.
  • "Use H2 headings only (no H1) inside "contents"." So inside the contents string, I'll have H2 headings like "The Six Universal Principles of Persuasion" but not

H1. In markdown, H2 is "## Heading". But the rule says "Use H2 headings only (no H1) inside "contents"." And "Put each heading on its own line, never inline after a sentence." It might mean the markdown heading syntax "## Heading" or just the text. Usually, in such prompts, "H2" refers to the markdown level. I'll use "## Heading" syntax, as that's standard markdown for H2. But the rule says "Do not write literal labels like "H2:" or "H3:"." That means don't write "H2: Heading", just "## Heading" is fine, as it's not a label. I'll use "## Heading" on its own line. The prompt: "Use heading markdown h1, h2, h3, etc. Use the content title as the H1 heading." and "Use H2 headings only (no H1) inside "contents"." So I'll use "##" for H2. That's standard. And the overall title will be the H1, which is the "title" key. So contents will have "## Heading" lines.

  • Let's confirm: Output JSON has "title" and "contents". "contents" is markdown. I'll put "## The Six Universal Principles of Persuasion" as H2. That's fine.

  • Now, word count: I need at least 1500 words in contents. I'll write seriously. Let's estimate: 7 sections * ~220 words = 1540. Plus opening paragraph ~100 words. Total ~1640. Good.

  • I'll start drafting the opening paragraph: "Hey folks! If you’ve ever wondered why we cave in to a sales pitch, nod along to a friend’s recommendation, or feel that tug to donate when we see a charity ad, you’re not alone. The science of persuasion is a wild ride, and Robert Cialdini has spent decades mapping out exactly how it works. His classic book, Influence: Science and Practice, especially the 4th edition, is like a treasure map for anyone curious about the hidden forces that shape our decisions. In this post, we’re going to break down the core principles, sprinkle in some real-world examples, and maybe even spot these tactics the next time they pop up in your own life. So grab a coffee, get comfy, and let’s dive into the psychology of saying 'yes' without even realizing it."

  • That's about 140 words. I'll make it a bit longer to maybe 150-160. But the rule says "Each title paragraph content must contain at least 300 words." Hmm, maybe it means each section's paragraph? Or the whole content? I'll interpret "Each title paragraph content" as maybe each heading's paragraph should be at least 300 words? That would be 7*300 = 2100, plus opening. But the prompt also says "The length of the article is at least 1500 words." I think the "Each title paragraph content must contain at least 300 words" might be a generic instruction from the template, but I'll try to make each H2 section's content at least ~300 words to be safe. That would make the article ~2100+ words, which is fine as long as it's at least 1500. I'll aim for each section ~300 words. That's doable.

  • Let's plan: 5 sections at 300 words each = 1500. I'll do 5 H2 sections. That simplifies. I'll choose 5 key principles: Reciprocity, Commitment and Consistency, Social Proof, Authority, Scarcity. I'll omit Liking or merge. 5 sections * 300 = 1500 exactly. I'll make each section ~300 words.

  • Let's draft Section 1: "Reciprocity: Giving to Get"

  • Start with "Cialdini" or "Influence" at beginning of first paragraph.

  • Casual tone.

  • ~300 words.

  • I need to be careful with word count and not accidentally use em dashes. I'll proofread mentally for "

  • ". I'll use "--" only if needed, but better to avoid even that, use commas or "and".

  • Let's start writing the actual content in the JSON structure. I'll build the JSON step by step.

  • JSON keys: "repair-input-keyword", "title", "contents"

  • "repair-input-keyword": I'll set to "Cialdini Influence Science Practice 4th Edition"

  • "title": "Mastering Persuasion: Cialdini's Influence Science and Practice (4th Edition) Explained"

  • "contents": the markdown string.

  • Now, the markdown contents. I need to output it as a JSON string value. So I'll need to escape quotes, but since I'm outputting JSON, I'll just write the markdown as a string with proper escaping. The prompt says "Output ONLY a JSON object with keys: "repair-input-keyword", "title", "contents"." and "The CONTENT result is in markdown form". I'll output the JSON with the contents value as a markdown string. I'll make sure to not use actual markdown fences (like ```) in the output, just the raw markdown inside the JSON string.

  • I'll write the contents string with line breaks. In JSON, I can use for newlines, but typically in these prompts, they expect the markdown text directly, maybe with actual newlines. I'll output the JSON with the contents value containing the markdown text, likely with actual newlines represented as or just raw. To be safe, I'll format it as a raw string with line breaks, but in JSON that means I need to escape them or just write them if the system handles it.