Does Blogging Help SEO? Measured, Not Claimed

Three dedicated blog posts hold first-page organic positions for the query "does blogging help seo". Ahrefs estimates their monthly US organic traffic at 133, 100 and 21 visits, from 18, 23 and 8 ranking keywords. The snapshot is dated 2026-10-09, the day this article was written.

The page with the most backlinks of the three, on the strongest domain, is the one earning 21.

That spread is the real answer to the question, and it is the answer every page in that result set skips. Blogging is not a switch that turns search traffic on. It is a way to own queries, and it pays exactly as much as the queries you manage to own are worth. This article shows the measurement, gives you the one you can run on your own site in Search Console, and names the cases where the honest answer is that a blog is the wrong place to spend your next ten hours.

The short answer, and the condition that comes with it

A blog helps SEO when it earns queries your product, service or category pages cannot earn. That is the whole condition, and it is testable.

A software page cannot rank for "does blogging help seo" without becoming an article. A pest control service page cannot rank for "how often should you spray for ants" without becoming an article. Those queries exist, they have demand, and the only way to answer them on your domain is a post.

What a blog does not do is add generic strength to your domain by existing. There is no publishing counter in Google's systems that lifts the rest of your site. The mechanisms that do operate are narrower than the listicles suggest, and we go through them below with Google's own documentation next to each one.

So the question to ask is never "should I have a blog". It is "which queries can only be answered by a post, and are they worth the hours". If you cannot name three of them for your business, you do not need a blog yet. You need better product pages.

What one blog post actually earns: three pages, measured

Here are the three dedicated articles ranking for the query, with Ahrefs estimates pulled on 2026-10-09 for the US market. Domain Rating and backlink counts come from the same SERP snapshot.

Three readings matter here.

The first is that one post is not one keyword. The two small-site posts rank for 18 and 23 queries each, and 11 of studiocotton's 18 sit in the top three. That multiplier is the mechanism of blogging that holds up under measurement: a post written for one question gets found through a family of phrasings.

The second is that domain strength did not decide the outcome. The HOTH post sits on a DR 75 domain with 58 backlinks pointing at that single URL, and it places eighth with zero top-three keywords. A DR 55 studio blog with nine backlinks beats it by a factor of six on estimated traffic.

The third is the number founders actually want. Ahrefs puts the equivalent paid value of studiocotton's post at about $241 a month. One post, written once. That is the honest frame for the arithmetic, and it is the same frame we use when asking whether SEO is worth the hours at all.

All three figures are third-party estimates for one country on one day, not server logs. They are good enough to compare pages against each other and useless as a forecast for yours.

Where the blog sits in the whole site's traffic

The per-post numbers say what a post earns. They do not say what a blog is worth to a business. For that, compare the whole domain against its blog subfolder. Same tool, same day, same market, prefix mode on the blog path and subdomains mode on the domain.

On the two small sites, the blog is not a supplement to organic traffic. It is most of it. Take the posts away from studiocotton and roughly four fifths of its search visibility goes with them.

The powermarketinginternational row carries the sharper lesson. Its blog earns 143 visits, and 100 of those come from the single post ranking for this query. One article is 70% of that blog's traffic and about 31% of the entire site's organic traffic.

That concentration is normal, and it is why averages lie. A blog does not deliver a steady yield per post. A small number of posts hit a query family that pays, and the rest cost you the hours. Which means the useful question before writing is which family you are aiming at, not how many posts you will publish per month.

The HOTH row shows the other shape. At 34,426 visits a month the site has plenty of non-blog visibility, and the blog's 15% share is a large absolute number on a small relative one. Share alone tells you nothing without the absolute next to it.

The four mechanisms, and which ones survive contact with Google's docs

Every article in this result set lists the same four reasons blogging helps. Here is what each one looks like when you check it against Google's documentation instead of against another blog post.

Keyword capture holds. It is the mechanism measured in the table above: 18 and 23 queries for one post. Nothing in Google's docs is needed to support it, because it is observable in your own Search Console.

Internal linking holds, with a caveat. Google's ranking systems guide names PageRank directly: "Among these is PageRank, one of our core ranking systems used when Google first launched." Links on your own site are links. What the docs do not give you is a quantity, so treat internal linking as plumbing you control rather than a lever with a known payout. The structural decision that matters more is whether the blog lives on your domain at all, which is the subfolder versus subdomain question.

Backlinks to posts are real and uncorrelated with effort. The measurement above is blunt: 58 backlinks on the eighth-place page, nine on the sixth-place page. Posts attract links, and the count does not translate into position inside this result set.

The "fresh content" claim is the one that breaks. The beginner's guide ranking fourth attributes Google's preference for new content to a 2011 algorithm update. Google's current documentation says something narrower: "We have various 'query deserves freshness' systems designed to show fresher content for queries where it would be expected." Freshness is evaluated per query, not as a site-wide bonus for publishing. A new post about a stable topic earns nothing from being new.

Crawl budget gets invoked the same way, and it also does not apply to you. Google's own crawl budget guide addresses "Large sites (1 million+ unique pages)" and "Medium or larger sites (10,000+ unique pages) with very rapidly changing content (daily)". A forty-post blog is two orders of magnitude away from that conversation.

What does apply, and gets skipped everywhere, is that publishing is not indexing. The Page Indexing report documentation is explicit: "Google doesn't guarantee that all pages everywhere will make it into the Google index," and "Don't expect every URL on your site to be indexed." A post stuck in "Crawled - currently not indexed" ("The page was crawled by Google but not indexed") helps nothing at all. If that is where you are, start with why your pages are not showing up before writing the next one.

The measurement that settles it for your own site

Everything above is about other people's sites. Here is the twenty-minute version for yours, and it answers the real question: are the posts earning queries the rest of the site does not already own?

Open the Search Console Performance report and add a Pages filter set to Custom (regex). Google's documentation specifies the behaviour you are relying on: "The RE2 syntax is used," default matching is a "partial match," and "Default regex matching is not case-sensitive." Prepend (?-i) if you need case sensitivity.

^https://example\.com/blog/

Export the Queries tab with that filter on. Then switch the filter to "Doesn't match regex" with the same pattern and export again. You now have your blog's queries and your money pages' queries as two files.

The overlap is the number that decides it. Run this against the two exports:

// node blog-split.js blog-queries.csv other-queries.csv
import { readFileSync } from 'node:fs'

const parse = (file) =>
    readFileSync(file, 'utf8')
        .split('\n')
        .slice(1)
        .filter(Boolean)
        .map((line) => {
            const [query, clicks, impressions] = line.split(',')
            return {
                query: query.replace(/^"|"$/g, '').toLowerCase(),
                clicks: Number(clicks) || 0,
                impressions: Number(impressions) || 0,
            }
        })

const blog = parse(process.argv[2])
const other = new Set(parse(process.argv[3]).map((r) => r.query))
const exclusive = blog.filter((r) => !other.has(r.query))
const sum = (rows, key) => rows.reduce((total, row) => total + row[key], 0)

console.log('blog queries:', blog.length)
console.log('queries only the blog ranks for:', exclusive.length)
console.log('clicks from those queries:', sum(exclusive, 'clicks'))
console.log('impressions from those queries:', sum(exclusive, 'impressions'))
console.log(
    'share of blog clicks that are exclusive:',
    ((sum(exclusive, 'clicks') / (sum(blog, 'clicks') || 1)) * 100).toFixed(1) + '%',
)

The split is naive about commas inside a quoted query, which is rare enough in search data to ignore and easy to fix with a real CSV parser if your export trips it.

Read the output like this. A high exclusive share means the blog is doing the one job only a blog can do, and more posts in the same families are a reasonable bet. A low exclusive share means your posts are competing with your own pages for the same queries, which is a content audit problem rather than a publishing problem.

Run the same export monthly and the question stops being an opinion. That cadence is also what turns writing into a repeatable workflow instead of a series of guesses.

The AI Overview sitting on top of this exact query

The result set for "does blogging help seo" opens with an AI Overview carrying four sitelinks, then a Reddit thread, then a Quora page. The first dedicated article is in fourth position.

Ahrefs puts US volume for the query at 322 a month. The Reddit thread alone is credited with about 414 visits, more than the three dedicated articles put together. For an informational query phrased as a yes-or-no question, that is the shape to expect: a generated answer on top, community pages underneath, and the articles competing for what is left.

Google's documentation on AI features is refreshingly short on requirements. To be eligible as a supporting link, "a page must be indexed," and "There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary." It goes further: "You don't need to create new machine readable files, AI text files, or markup to appear in these features. There's also no special schema.org structured data that you need to add."

Measurement is thinner than it looks. Pages shown in AI features are "reported on in the Performance report, within the 'Web' search type," and the dedicated generative AI report gives impressions only, defined as "how many times links to your site were shown to a user in a generative AI feature on Google Search," broken down by pages, countries, dates and devices, with a search type filter offering "Web: text-based" and "Web: multimodal".

The practical consequence for topic choice is not to avoid informational queries. It is to prefer the ones where a summary cannot finish the job: a decision with a tradeoff, a procedure with a result to verify, a number someone had to measure. Getting quoted in those answers is its own discipline, which we cover under answer engine optimization.

When a blog is the wrong investment

Three cases, and in all three the better move is not a post.

Your demand is local and transactional. Google's local ranking guidance names three factors: relevance is "how well a Business Profile matches what someone is searching for," distance is "how far each business is from the customer who's searching," and prominence "means how well-known a business is." The same page states plainly that "There's no way to request or pay for a better local ranking on Google." A blog post cannot change your distance from the searcher. If most of your customers type a trade plus a place, the hours go into your Business Profile and your reviews first.

Your catalogue pages are not finished. If your collection and product pages do not yet target the queries buyers type, a blog sends traffic to the wrong doors. Fix the pages that take the money, then write the posts that feed them. For stores, the sequence is the one in our ecommerce checklist.

You cannot name the query families. A blog is a bet on query coverage. If you cannot write down the three families you intend to own, the posts will scatter across unrelated topics, which Google's helpful-content guidance explicitly flags: it asks whether you are "producing lots of content on many different topics in hopes that some of it might perform well in search results".

None of this is an argument against blogging in general. It is an argument against blogging as a default, which is what the result set for this query sells. The alternative framing, where content and SEO budgets compete for the same hours, is covered in SEO versus content marketing.

Cadence and length: what Google says, and what nobody can source

The beginner's guide ranking fourth for this query recommends posting "2-4 per month" and writing "500+ words", with no source for either. Those numbers have circulated for a decade, and they are not in Google's documentation.

Google's guidance on creating helpful content addresses the length question directly, as one of its self-assessment questions: "Are you writing to a particular word count because you've heard or read that Google has a preferred word count?" The list in that document, updated 2026-10-05, is worth reading next to your own drafts. It asks whether content "provide[s] original information, reporting, research, or analysis", whether it is "primarily made to attract visits from search engines", and whether you are "mainly summarizing what others have to say without adding much value".

On volume, the binding document is the spam policy. Scaled content abuse is defined as "when many pages are generated for the primary purpose of manipulating search rankings and not helping users", typically "creating large amounts of unoriginal content that provides little to no value to users, no matter how it's created". That last clause is the one to notice. The policy is indifferent to whether a human or a model wrote the page.

So the cadence that matters is not a number per month. It is whether each post answers a query family you can cover better than what currently ranks. On the query this article targets, the bar was a 900-word agency post with a service CTA at the end, and a 3,500-word vendor piece whose statistics link to image files and secondary aggregators. That bar is reachable with one well-researched post, and unreachable with eight thin ones.

As for how long any of it takes, Google's own page on hiring an SEO is blunt: "No one can guarantee a #1 ranking on Google." We have written separately about how long SEO takes, and the honest version of that answer is a range with conditions, never a date.

The technical floor: a blog Google can actually index

None of the above matters if the posts are not indexable. The floor is small, and on Next.js it is three files. The examples below are for the App Router on Next.js 16, which is what this site runs.

Your posts belong in the sitemap, with a real modification date per post rather than the build date for all of them.

// app/sitemap.ts
import type { MetadataRoute } from 'next'
import { getAllPosts } from '@/lib/blog'

const SITE = 'https://example.com'

export default function sitemap(): MetadataRoute.Sitemap {
    return [
        { url: SITE, lastModified: new Date(), priority: 1 },
        { url: `${SITE}/blog`, lastModified: new Date(), priority: 0.8 },
        ...getAllPosts().map((post) => ({
            url: `${SITE}/blog/${post.slug}`,
            lastModified: new Date(post.updatedAt ?? post.date),
            changeFrequency: 'monthly' as const,
            priority: 0.7,
        })),
    ]
}

Every post declares its own canonical, so that a tag page or a paginated index never competes with the article for the same content.

// app/blog/[slug]/page.tsx
export async function generateMetadata({
    params,
}: {
    params: Promise<{ slug: string }>
}): Promise<Metadata> {
    const { slug } = await params
    const post = getPost(slug)
    if (!post) return {}

    return {
        title: post.title,
        description: post.description,
        alternates: { canonical: `/blog/${slug}` },
    }
}

The params promise is not a stylistic choice. Dynamic route params are asynchronous in current Next.js majors, and copying an older synchronous example is the most common way these files break on upgrade. The rest of the setup, including robots and the metadata base, is in our Next.js SEO walkthrough.

The last piece is not a file. Each post needs at least one link from a page that already has visibility, and at least one link out to the page you want the reader to reach. A post nobody links to, including you, is a page you have asked Google to find on faith.

FAQ

Is blogging still good for SEO?

Yes, for queries your other pages cannot answer, and the measurement above shows what that is worth: 18 to 23 ranking keywords per post on two small sites, and roughly $241 a month in equivalent paid traffic for the best of the three. It is not good for queries a generated answer finishes on the spot, and it is not good as a substitute for pages that convert.

Is SEO still worth it in 2026?

It depends on arithmetic you can do before writing anything: the volume of the queries you can realistically reach, their commercial value, and the hours you can sustain. We walk through that calculation, including the cases where the answer is no, in is SEO worth it. Nobody can promise an outcome, and Google says so itself.

How many blog posts do I need before anything ranks?

There is no count that triggers ranking, and anyone quoting one is guessing. What the data in this article suggests is a different expectation: traffic concentrates in a few posts, so the useful target is covering one query family properly rather than reaching a number of posts.

What is the 80/20 rule for blogging?

It is marketing folklore rather than a Google rule, and the circulating versions contradict each other: 80% of effort on promotion, or 80% of posts with no selling. Google publishes nothing of the kind. The measurable version is the exclusive-query share from the script above: if 80% of your blog clicks come from queries no other page on your site ranks for, the blog is doing its job.

Do blog posts help the rest of my site rank?

Partly, and less than the listicles claim. Internal links from posts pass signals Google's own documentation describes through PageRank, so a post linking to a service page is doing something real. What does not exist is a site-wide bonus for publishing frequency, and freshness is assessed per query, not per site.

Does the blog platform matter for SEO?

Less than the structure around it. What matters is that posts render indexable HTML, live in a subfolder on your main domain, appear in your sitemap, declare their own canonical, and are reachable by links. A platform that makes those five things hard is a bad platform, whatever its marketing says.