SEO Blog Post Rules

A blog post that ranks but doesn't satisfy the reader who clicked it fails just as hard as one that reads well but never gets found — write for the actual search intent first, then structure that answer so both a skimming human and a crawler can follow it.

Match search intent before writing

• Identify what the searcher actually wants before drafting: a definition (informational), a comparison or "best X" list (commercial investigation), a specific product page (transactional), or a specific known site (navigational). Match the post's format to that intent — a listicle for "best X," a how-to for "how to X," a direct answer for a question query.
• Check what's currently ranking for the target query before writing. If every top result is a listicle and the plan is a narrative essay, the format is fighting the established intent for that query regardless of writing quality.
• Write for a specific searcher's actual problem, not for the keyword as an abstract string — content written to satisfy a person ranks better and converts better than content written to satisfy an algorithm.

One primary keyword, natural variants

• Pick one primary keyword or phrase per post and build the post around it; use natural semantic variants and related terms throughout (synonyms, plural/singular, related questions) rather than repeating the exact phrase mechanically.
• Never keyword-stuff — repeating the exact phrase unnaturally to hit a density target reads badly to humans and is treated as a spam signal, not a ranking boost, by modern search engines.
• Include the primary keyword naturally in the title, the first ~100 words, at least one H2, and the URL slug — not forced into every paragraph.

Title and heading structure

• Write one clear, specific H1-equivalent title under ~60 characters where possible so it doesn't truncate in search results; front-load the keyword and the specific value (a number, a timeframe, a concrete outcome) rather than a vague topic label.
• Use H2s to break the post into its actual logical sections, each one descriptive enough to be understood out of context (useful for both skimmers and featured-snippet extraction) — not generic labels like "More Info" or "Details."
• Use H3s only for genuine subsections under an H2, never to fake visual hierarchy where a plain paragraph would do.
• Keep heading structure strictly nested (H2 then H3 under it, not H2 then H4) — broken hierarchy confuses both readers scanning the outline and crawlers parsing document structure.

Intro that answers the query fast

• Answer the core query directly within the first 100 words — don't preamble with throat-clearing ("In today's fast-paced world...") or a long windup before getting to the point. A reader who doesn't find their answer signal in the first few lines leaves.
• State clearly and early what the post covers so both the reader and a search snippet extraction get an accurate, immediate summary.

Scannability

• Write short paragraphs — two to four sentences — with white space between them; a wall of text gets abandoned on mobile regardless of content quality.
• Use bullet lists and numbered lists for genuinely list-shaped content (steps, comparisons, options) rather than burying list content inside prose paragraphs.
• Use bold sparingly to mark the genuinely most important phrase in a paragraph, not every sentence — over-bolding defeats its own purpose.
• Break up long sections with descriptive subheadings often enough that a reader scanning only the H2/H3 outline still gets the shape of the whole answer.

Linking discipline

• Link internally to genuinely related pages using descriptive anchor text (not "click here") — internal links help both crawlers discover related content and readers find what they need next.
• Link externally to authoritative, relevant sources when citing a claim, a statistic, or a study — uncited specific claims read as less trustworthy, and search engines use outbound link quality as a signal.
• Never link for its own sake; every link should be the single most relevant destination for that anchor text, not an arbitrary insertion to hit a link count.

Meta description

• Write a unique meta description per post, roughly 120–158 characters, that summarizes the specific value of the post and includes the primary keyword naturally — this is ad copy for the search results page, not a content summary for the crawler.
• Write it to earn the click: state the specific outcome or answer the post delivers, not a vague teaser.

Helpful vs. thin content

• A post is "helpful" when it answers the query completely enough that the reader doesn't need to click back to search again — thin content covers the topic superficially and sends the reader looking elsewhere.
• Add genuine specificity that generic content lacks: real examples, actual numbers, direct experience, an opinion with reasoning — not just a longer restatement of what every other top-ranking post already says.
• Length is a byproduct of thoroughness, not a target — padding a thin answer to hit a word count doesn't make it more helpful and is easy for both readers and ranking systems to detect.

Updating old posts

• Refresh posts on topics that change (tools, statistics, best practices, pricing) on a regular cadence rather than leaving them to go stale — a post with outdated information actively damages trust even if it still ranks.
• When updating, verify every fact and link still holds, add genuinely new information rather than cosmetic rewording, and update the published/modified date only when the update is substantive.
• Preserve the URL when refreshing a post rather than republishing at a new URL — a URL change discards any accumulated ranking signal the original page had built up.