12 Rules for Writing an SEO-Friendly Blog Post

An SEO-friendly blog post is not one that repeats a keyword a certain number of times. Google's helpful content documentation asks whether content is created primarily to help people; technical rules are built on top of that purpose.
In this article I collected the 12 rules I apply in my own posts and on client sites, in order from writing to publishing and updating. Deciding which topics to write about is a separate job, which I cover in the content strategy guide.
Short answer: An SEO-friendly blog post answers one search intent, gives a clear answer in the intro, builds a scannable structure with h2 and h3 headings and links to related pages with descriptive anchor text. Author information, honest dates and regular updates support its credibility.
Before you start writing
1. Identify the search intent
Search for the target query on Google and look at what type of content ranks on page one: a guide, a list, a comparison or a product page? A post written without understanding whether the user wants information or is trying to make a decision answers the wrong question, however good it is. I explain the intent types with examples in what is search intent.
2. Give each post one main topic
A post should target one main query and its close variations. Two posts answering the same question compete with each other. Group main and secondary queries with the method in the keyword research guide and assign each group to a single URL.
How to write the title and intro
3. Make the title state the main topic clearly
The title tag and the h1 on the page should tell at a glance what the post answers. Put the main phrase near the start, do not repeat the keyword, and write in the same language and script as the page. Detailed rules are in rules for meta titles and descriptions.
4. Give the answer in the intro
Readers and search engines should find an answer to the post's question in the first paragraphs. Intros that open with a long story or a generic definition lose readers. I start every post with a 2 to 3 sentence “short answer”, which also works as a summary that AI answers can quote.
- The answer within the first two sentences
- A short plan of what the post covers
- A concrete example or criterion
- Generic sentences about why the topic matters
- The keyword repeated over and over
- The answer hidden at the end of the post
Body structure and content quality
5. Build a scannable structure with h2 and h3 headings
Each h2 should answer a sub-question, and h3s should break that answer into steps or examples. Someone reading only the headings should be able to summarise the post. Keep paragraphs to 2 to 4 sentences; use lists for steps and tables for comparisons.
6. Add first-hand experience and original information
Content that adds nothing beyond a summary of other articles gives no reason to rank. Add your own tests, client questions, screenshots and decision criteria. I explain how I make this visible in content for E-E-A-T. If you use AI while writing, it is worth knowing Google's policy on AI content.
Links, images and the meta description
7. Add internal links with descriptive anchor text
Link the post to the main page on the same topic and to related articles, and link to the post from the main page too. The anchor text should describe the target page; avoid phrases like “click here”. I cover the structure in internal linking and topical authority.
8. Use images where they add meaning, with the right settings
A screenshot, diagram or original photo carries more information than a stock image. Use alt text that describes the image, a descriptive file name and compressed modern formats. Technical details are in image SEO.
9. Write a meta description that summarises the page
Google builds snippets mostly from page content, but it may use the meta description when it describes the page more accurately. Write a natural, unique sentence for each post that summarises the whole post. You can check how it looks in search results with the SERP preview tool.
Trust and freshness signals
10. Make author information visible
Google explicitly encourages accurate authorship information, such as bylines, on content where readers would expect it. Add the author's name, a short note on their expertise and a link to an author page; never use misleading author information.
11. Show dates honestly and actually update the content
Google's byline date documentation recommends a user-visible publication or update date that matches the date in structured data. Refreshing the date without substantial changes to the content is listed as a negative example in the helpful content documentation.
12. Use a short URL and Article structured data
Choose a short URL that describes the topic, without dates; on Turkish sites transliterating characters such as ş to s is usually more practical; the principles are in URL structure. Add headline, author, datePublished and dateModified to your Article or BlogPosting markup. You can build the markup with the schema generator and find the rules in the schema and structured data guide.
Pre-publish SEO checklist
I run through this list quickly before publishing any post. The table shows where each rule is checked.
- Target query and search intent are clear and do not overlap with another post
- Title and h1 state the main topic clearly
- The intro contains a clear 2 to 3 sentence answer
- Reading the h2 headings in order summarises the post
- There is at least one original example, data point or screenshot
- Internal links point to related posts and the main topic page
- Images have alt text and descriptive file names
- Author name, visible date and structured data are consistent
| Rule | Where to check | When |
|---|---|---|
| Search intent, single topic | Google results, Search Console queries | Before writing |
| Title and meta description | SERP preview, Search Console CTR | Before and after publishing |
| Internal links | Site crawler, CMS | At publishing |
| Structured data | Rich Results Test | Before publishing |
| Freshness | Search Console performance trend | At regular intervals |
- ResearchIntent, query group and competing pages.
- WriteShort answer, h2 outline, original examples.
- ConnectInternal links, images, structured data.
- Publish and measureImpressions and CTR in Search Console.
- UpdateRefresh outdated facts and close gaps.
Let's plan your blog content together
These rules strengthen a single post; what grows traffic is writing the right topics in the right order. If you want a topic map and a writing standard for your blog, see content strategy services or book an intro call.
Frequently Asked Questions
How many times should a keyword appear in a blog post?
There is no set number or density ratio. It is enough for the main phrase to appear naturally in the title, the intro and a relevant subheading. Forcing repetition hurts readability and gets close to the keyword stuffing example in Google's spam policies.
Should I delete old blog posts?
For posts that bring no traffic, links or conversions and are not worth updating, deleting them or merging them into a similar post with a redirect can make sense. Check each post's data before deciding; deleting a post that brings traffic creates a loss.
Is adding an FAQ section to blog posts still useful?
Google has not shown FAQ rich results in search since May 2026. An FAQ section that answers questions readers really ask still has value as content, and FAQPage markup remains valid, but it will not earn a rich result.
How often should I publish blog posts?
Publishing frequency on its own is not a ranking criterion. Choose a pace your team can sustain without losing quality; two good posts a month are worth more than five shallow ones a week. Add updates to existing posts to the calendar too.
How do I tell Google about a post after publishing it?
If your sitemap is up to date, Google will discover the new URL over time. For an important post you can request indexing with the URL Inspection tool in Search Console. Internal links from the home page or related posts also speed up discovery.

8+ years of hands-on SEO and GEO experience across 150+ projects in e-commerce, SaaS, healthcare and local business sectors. Writes based on real client data, not theory.





