Understanding Short Selling: The Basics

Aug 27, 2026

Article

by Jule

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
Article length at least 1500 words
Optimize paragraphs: include main keywords in beginning, use bold/italic/strong
Rewrite for humans: casual friendly tone, "guys", conversational
Title relevance rule: preserve main named entity, product name, or core term from input keyword. Do not replace with generic theme.
Content result is in markdown form, use heading markdown h1, h2, h3, etc. Use the content title as the H1 heading. (But wait, inside "contents" I should use H2 only, no H1. The instruction says "Use the content title as the H1 heading." but also "Use H2 headings only (no H1) inside 'contents'". I need to reconcile this. Probably means the overall article has an H1 title (which is the JSON "title"), and inside "contents" I use H2s only. The "Use the content title as the H1 heading" might refer to the overall structure, but since output is JSON with "title" and "contents", I'll make "title" the H1, and inside "contents" use H2s only.)
"repair-input-keyword": likely needs to be a cleaned/optimized version of the input keyword.

Let's break down the keyword: "How To Make Money Selling Stocks Short Pdf" Main entities/terms: "selling stocks short", "pdf", "make money" Core term: Probably "short selling stocks" or "short selling pdf" I need to preserve the main named entity/product name/core term from the input keyword. The input is a phrase about making money short selling stocks, with a pdf focus. I'll preserve "short selling stocks" or "selling stocks short". The title should keep something like "How to Make Money Selling Stocks Short" or similar, but as an SEO title.

Let's look at the output rules carefully:

Output ONLY a JSON object with keys: "repair-input-keyword", "title", "contents".
"contents" must contain the full article 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.

Also: "Each title paragraph content must contain at least 300 words." Wait, the prompt says: "Optimize paragraphs - Include your main keywords in the beginning of the paragraph.

Use bold, italic and strong tags.
Each title paragraph content must contain at least 300 words." This seems to apply to the article paragraphs. And "The length of the article is at least 1500 words."

And: "Rewrite for Humans - Use a 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."

And: "Make sure the title is properly ordered and does not pass the semantic structure level of the page. The length of the article is at least 1500 words. The CONTENT result is in markdown form, use heading markdown h1, h2, h3, etc. Use the content title as the H1 heading."

There's a slight conflict: "Use H2 headings only (no H1) inside "contents"" vs "use heading markdown h1, h2, h3, etc. Use the content title as the H1 heading." I'll interpret it as: The JSON "title" key will hold the H1 title (or the main title), and inside "contents", I will use H2 headings only, as explicitly stated. The "Use the content title as the H1 heading" likely means the overall title structure, but since the output format separates "title" and "contents", I'll put the H1-worthy title in the "title" key, and inside "contents" use H2s only. I need to make sure I don't put an H1 inside contents.

Let's plan the structure:

JSON object with three keys.
"repair-input-keyword": I'll optimize the keyword for SEO, maybe "How to Make Money Selling Stocks Short: A Practical PDF Guide" or similar, but I need to preserve the core term. I'll keep it close to original but make it searchable. Maybe "how-to-make-money-selling-stocks-short-pdf" or "selling stocks short pdf guide". I'll think about it.
"title": The main title, probably matching the keyword but formatted as a title. E.g., "How to Make Money Selling Stocks Short: A Complete Guide"
"contents": Full article in Markdown, at least 1500 words, using H2 headings only (no H1 inside), with paragraphs, bold/italic/strong, casual tone, "guys", etc.

Let's outline the article mentally to hit 1500+ words. I need to be careful with word count and structure.

Structure plan for contents:

Opening paragraph(s) before first H2. Must be normal paragraphs, not bullet points. Casual tone, maybe introduce the topic of short selling, the pdf aspect, etc.

Understanding Short Selling: The Basics

How to Find the Right Stocks to Short

Reading Charts and Timing Your Entry

Risk Management Strategies for Short Sellers

Using PDF Resources to Boost Your Knowledge

Common Mistakes to Avoid When Short Selling

Building a Consistent Short-Selling Routine

Maybe more H2s to reach word count.

Each section must have paragraphs with main keywords at the beginning. Main keyword: "selling stocks short" or "short selling". I'll use variations but ensure the keyword phrase appears early in paragraphs.

I need to write extensively. Let's aim for ~1600-1700 words to be safe.

Important constraints:

No em dashes. Use normal punctuation. So I must avoid "--" and use "
" or "to" instead. Actually "em dash" is - , I can use normal hyphen or just commas/periods. I'll be careful.
Bullet items start with "- " and on their own line.
Blank line between paragraphs, headings, lists.
Headings on their own line, never inline after a sentence.
No literal labels like "H2:".
Casual tone: "guys", conversational.

Let's start crafting the JSON.

First, "repair-input-keyword": I'll make it SEO-friendly while preserving core term. Input: "How To Make Money Selling Stocks Short Pdf". Core term: "selling stocks short pdf" or "short selling pdf". I'll output: "how to make money selling stocks short pdf" or maybe "selling stocks short pdf guide". I'll keep it lowercase, maybe with hyphens for SEO: "how-to-make-money-selling-stocks-short-pdf". But the rule says "preserve the main named entity, product name, or core term from the input keyword. Do not replace it with a generic theme." So I should keep "selling stocks short" and "pdf". I'll do: "selling stocks short pdf guide". Or maybe just retain the exact phrase but optimized: "How to Make Money Selling Stocks Short PDF". I think I'll output: "how to make money selling stocks short pdf". I'll decide later.

"title": Should be the H1 equivalent. "How to Make Money Selling Stocks Short: A Practical Guide for Beginners"

"contents": The article.

Let's draft the article in markdown, carefully following rules.

I need to ensure each paragraph has at least some length, and main keywords in beginning. I'll use "selling stocks short" as the core phrase. I'll also use "short selling" interchangeably but ensure the phrase appears.

Let's outline content with word count targeting.

I'll start with an opening paragraph (or two) before any H2. That paragraph(s) must be normal paragraphs, not bullet points, casual tone.

Then H2s. Each H2 on its own line. After each H2, paragraphs.

I need to avoid em dashes. So I'll write sentences with commas, periods, "to", "and", etc. No "--".

I'll use bold, italic, strong tags where appropriate. The prompt says "Use bold, italic and strong tags." I'll incorporate them naturally.

Let's start writing. I'll aim for ~1600 words. I'll count mentally or approximate, but as long as it's long and structured, it should be fine. I'll be generous with content.

Important: The article must be at least 1500 words. I'll make sure each section is substantial.

Let's draft.

Opening paragraph: "Hey guys, if you've ever wondered how to make money selling stocks short pdf guides can actually help you fast-track your learning curve, you're in the right place. Short selling is one of the most misunderstood yet powerful strategies in the stock market, and when done right, it can generate profits even when the broader market is tanking. In this article, we're going to break down the essentials, share practical tips, and point you toward resources that actually work. Whether you're a complete beginner or someone looking to sharpen your edge, understanding the mechanics behind selling stocks short is the first step toward building a more flexible portfolio."

That's a good start. I need to make sure the main keyword "selling stocks short" or "make money selling stocks short" appears early. I'll adjust.

Let's rephrase with keyword at beginning: "Hey guys, if you want to make money selling stocks short pdf guides can fast-track your trading education, you're in the right spot. Short selling is often painted as risky, but many seasoned traders use it to hedge or profit from downtrends. Throughout this piece, we'll walk through the core concepts, smart strategies, and how to avoid the common pitfalls that blow up new accounts. By the end, you'll have a clearer roadmap for using short selling as a legitimate part of your investment toolkit."

I'll make sure "selling stocks short" or "make money selling stocks short" is in the first few words.

Actually, the prompt says: "Include your main keywords in the beginning of the paragraph." So I should have the main keyword phrase at or very near the start of each paragraph. The main keyword from the input is "How To Make Money Selling Stocks Short Pdf". I'll use variations but keep the core. I'll treat the main keyword as "selling stocks short" or "make money selling stocks short". I'll ensure each paragraph starts with something like "selling stocks short" or "make money selling stocks short".

Let's define the main keyword phrase for the article: "selling stocks short". I'll use that frequently.

Now, structure with H2s. I'll plan maybe 8-10 H2 sections, each with substantial paragraphs.

Let's start building the JSON and contents step by step.

I need to output ONLY the JSON object, no preface, no notes, etc.

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

I'll construct the contents as a markdown string in JSON. Since JSON requires escaping, but I'm just outputting text, I'll make sure it's valid JSON with proper escaping if needed, but typically in these prompts, they just want the content as plain text within JSON, and I can use quotes carefully. I'll make sure no unescaped newlines cause issues, but usually the system handles it. I'll just output the JSON object with the values. I'll use proper markdown inside the string, but since it's JSON, I might need to escape quotes. However, the prompt says "Output ONLY a JSON object with keys: ..." and "The CONTENT result is in markdown form". I think I can output the markdown as plain text within JSON, and the system will interpret it. I'll be careful with quotes inside the markdown; I'll use single quotes or avoid quotes, or escape double quotes. Actually, in many AI responses, they just output the JSON with markdown and it works because the platform parses it. I'll try to keep it simple, maybe use double quotes for JSON, and inside the markdown, I'll use minimal double quotes, or I'll just write the markdown and the JSON will have the string value. I'll be cautious.

Alternatively, I can structure the JSON with the "contents" value as a multi-line string, but in the response, I'll just write it as a continuous string with or just as is, and the system will take it. The prompt doesn't specify I need to escape everything; it just says output JSON object. I'll output it in a code block? No, "Do not write literal labels like 'H2:' or 'H3:'." and "No preface, no notes, no postscript, no markdown fences." So I should NOT output a code block with ```json. I should just output the raw JSON object. That means the text will be plain. I need to ensure the JSON is valid and the markdown inside is valid but since it's inside a JSON string, double quotes inside must be escaped. This is tricky. Many times in these prompts, the AI just outputs the JSON with markdown and the platform handles it, sometimes with triple backslashes or something. I'll try to keep the markdown without double quotes, or use single quotes for any quoting needed. Actually, I can avoid using double quotes inside the markdown entirely by using strong/italic without double quotes, e.g., bold using asterisks, which don't need quotes. I'll avoid writing things like "PDF" in quotes. I'll just use the words.

Let's design the contents such that I don't need many double quotes. I can use apostrophes (which are fine), and asterisks for bold/italic. I'll avoid double quotes altogether.

Let's draft the article text in a way that uses minimal quoting.

Plan:

Opening paragraph(s) before first H2.
H2 headings on their own lines.
Paragraphs after each H2.
Use bullet lists where appropriate, each bullet on its own line starting with "- ".
Blank lines between paragraphs, headings, lists.
No em dashes. So I'll write "to" instead of "--", or use commas.
Casual tone: "guys", etc.

Let's start writing the contents step by step in my mind, then assemble JSON.

I'll write the article now.

First, the opening paragraph(s): "Hey guys, if you're looking to make money selling stocks short pdf resources can seriously speed up your learning curve. Short selling often gets a bad rap, but when you master the mechanics, it becomes a legit way to profit from market downturns. In this guide, we'll dive into the real talk about how short selling works, the smart ways to spot opportunities, and how to protect your capital while you're at it. By the end, you'll have a clearer picture of whether this strategy fits your style and how to start small without blowing up your account."

Check keyword at beginning: "make money selling stocks short" is there. Good.

Now, I need to make sure each paragraph has the main keyword in the beginning. The prompt says: "Optimize paragraphs - Include your main keywords in the beginning of the paragraph." So I should start each paragraph with the keyword or a strong variation. I'll try to start many paragraphs with "selling stocks short" or "make money selling stocks short". But I can't start every single sentence with it, but the first few words of each paragraph should include it. I'll make sure each paragraph's first 3-5 words include the core phrase.

Let's restructure: I'll make each paragraph start with something like "Selling stocks short requires..." or "To make money selling stocks short, you..." etc.

Let's plan the H2 sections and their opening paragraphs.

H2 1: "Understanding the Basics of Short Selling" Opening paragraph after H2: start with "Selling stocks short begins with understanding..." etc.

I'll be careful to not use em dashes. I'll use "to" or "and".

Let's start in earnest.

I'll write the full contents now, aiming for ~1600 words. I'll count roughly as I go.

I need to include bullet lists. I'll integrate them within sections.

Let's begin.

(Mental text generation)

Opening: "Hey guys, if you want to make money selling stocks short pdf guides can fast-track your trading education, you're in the right spot. Short selling is often painted as risky, but many seasoned traders use it to hedge or profit from downtrends. Throughout this piece, we'll walk through the core concepts, smart strategies, and how to avoid the common pitfalls that blow up new accounts. By the end, you'll have a clearer roadmap for using short selling as a legitimate part of your investment toolkit."

That's paragraph 1. It starts with "Hey guys, if you want to make money selling stocks short..." Good.

Now H2 sections.

I'll define H2s as markdown headings: "## Understanding the Basics of Short Selling" but the prompt says "Use H2 headings only (no H1