Skip to content

Writing an SEO-Friendly Blog Post: From Topic to Publish

Stop counting keyword density. How to build a blog post that starts from a real customer question, answers it in the first paragraph and links through to your services.

KodyvaSeptember 20, 20266 min readSEO and Google Visibility
Writing an SEO-Friendly Blog Post: From Topic to Publish

SEO advice that starts with “your keyword should appear at 2 percent density” is still going around. Fixed-ratio rules like that don't do much today. What makes a blog post stand out in search is answering someone's question more clearly and credibly than other pages. AI-assisted search looks for something similar: a short, accurate answer it can quote.

Below is the flow we follow when writing our own posts and content for our clients.

Topic selection: the questions customers ask

The best blog topics are the questions your customers already ask you. For a painter: “Why does a bathroom ceiling turn black, and will painting fix it?” For an accountant: “Sole proprietorship or limited company, which suits whom?” These come from a real need, and the person asking is likely to become your customer.

To build a topic list, look at a few sources: your phone and WhatsApp conversations, incoming emails, the “People also ask” box that appears when you search your topic on Google, and queries in Search Console where your site appears but doesn't get clicked. That last source is especially valuable; Google already associates you with the topic, you just lack a good answer.

Then check one thing for each question: Could the person asking it need our service at some point? The answer to “why does a bathroom ceiling turn black” is moisture and ventilation, and some readers will end up needing a painter. “How to paint your home yourself” is written for the opposite audience. We covered keyword research in detail in a separate post.

Title and opening paragraph

The title should clearly contain the searched question or need. Witty or mysterious titles may work on social media but generally not in search; people want to see their own question in the results.

“Black Spots on the Ceiling: Through a Painter's Eyes” is weaker than “Why Does a Bathroom Ceiling Turn Black? Causes of Mold and a Lasting Fix.” Try to keep it around 60 characters so it isn't cut off in results.

The opening paragraph is the most important part of the post. Two mistakes are common. The first is a long warm-up: three paragraphs about how important the topic is and how many people face it. The second is hiding the answer at the end. Readers and Google both want the answer in the first paragraph.

Short answer, then detail

The structure that works is simple: give a direct answer in the first 2 to 4 sentences. Then go into detail.

For example: “A darkening bathroom ceiling is usually mold caused by moisture building up on the surface. Painting hides the stain for a while, but without better ventilation the mold can come back. A lasting fix means cleaning the surface with an anti-mold solution, letting it dry, applying a moisture-resistant paint and improving the bathroom's ventilation.”

That paragraph can be quoted on its own. An AI assistant or Google's featured answer box can lift it as is and cite you. Readers who want detail after getting the answer keep reading: which solution, how many coats, which ventilation options, when to call a professional.

In the detail section, your own experience is the most valuable thing. Anyone can write general information. Something you've genuinely observed in the field, for example that the problem keeps coming back in bathrooms where the extractor fan is never switched on, only comes from someone who does the work, and it sets the post apart. Write your own observations; don't use made-up statistics or unsourced quotes like “experts say.”

A note on length: a post should be as long as the question requires. Some questions are fully answered in 600 words; others need 2,000. Padding the word count with repetitive paragraphs can hurt both readers and rankings.

Heading hierarchy and lists

A page has one H1, the post title. Main sections are H2s and their subsections H3s. This isn't just visual; Google and screen readers understand the post's structure from these headings.

Shaping subheadings like questions also helps. “Why does mold form on a bathroom ceiling?” instead of “Causes,” “How do you paint a moldy ceiling?” instead of “Solution.” That way each section can answer a search query on its own.

Lists and step-by-step instructions should be used when content is genuinely sequential or itemized. If you're describing a process, numbered steps make the reader's job easier. But turning every paragraph into a list fragments the text and loses context. As a rule, reasoning and explanation go in paragraphs; sequential tasks and comparisons go in lists.

Internal linking

No blog post should stand alone on your site. It should link in two directions: to related posts and to the relevant service page.

From the bathroom ceiling post, link to “Which paint to choose for bathrooms” and to your “Bathroom and wet area painting” service page. The link text should describe the destination; instead of “click here,” use something like “our painting service for wet areas.”

Do the reverse too. When you publish a new post, add links to it from older posts that touch on the same topic. The new page can get discovered faster, and your site's depth on that topic becomes more visible.

There's no magic number of links per post. Link where the reader would genuinely want to click; rather than sprinkling a link into every paragraph, two or three strong links at the relevant points are usually enough.

Final check before publishing

Before you hit publish, ask:

  • Is the question answered in the first paragraph?
  • Is the title short enough not to be cut off, and does it contain the question?
  • Does the meta description explain what the post promises in 150 to 160 characters?
  • Do the images have file names and alt text?
  • Does the post link to at least one service page and one related post?
  • Is there information showing the author or the business?
  • Do you have the right to use the images and quotes in the post?

Updating after publishing

A blog post isn't finished on the day it goes live. Posts age and can lose rankings, especially on topics that change, like prices, regulations or technology.

Two or three months after publishing, check in Search Console which queries the post appears for. Unexpected queries often show up. If a post written for “bathroom ceiling mold” also appears for “is ceiling mold harmful to health” and doesn't answer that, add a section. That usually gets results faster than writing a new post from scratch.

When you update, change the date in the post too, and actually change the content; refreshing only the date misleads readers. To plan which post to review when, you can use the simple table in our post on content update schedules.

For many small businesses, writing 20 posts and updating each once a year works better than publishing 50 a year and never going back to any of them.

#blog #içerik #seo #yazım

Frequently Asked Questions

How many words should a blog post be?

There's no fixed number. A post should be as long as it takes to answer the question fully. Some questions are covered in 600 words, others need 2,000. Padding with repetitive paragraphs doesn't help.

How often should I publish blog posts?

Consistency matters more than frequency. For a small business, one or two good posts a month plus a yearly review of older posts is usually enough. Publishing weekly at the expense of quality usually doesn't deliver.

Blog posts are for general information only and are not a substitute for legal, financial or technical advice.

Want a quote for your project?

Browse our services or request a quote directly.

View Services