Should my business website have a blog? Not for its own sake. A blog is not the point, answering real customer questions in your own words is. Twelve genuinely useful posts a year beat fifty-two scheduled ones nobody asked for.
Updated August 2026.
We get some version of this question from almost every contractor we onboard. Someone told them a blog is good for SEO, or they saw a competitor's blog, and now there's a /blog page with three posts from 2023 sitting on their site like a half-finished renovation. That page does them more harm than good. An abandoned blog is a visible signal, to a human and to Google, that nobody is home.
So here's the answer we actually give clients, including the part where the honest answer is sometimes no. We build blogs into most client sites and run them on retainer, so this isn't an argument against the service we sell. It's an argument against doing it badly, which is what happens to almost every contractor blog without a real system behind it.
Does a blog actually help, or is being the answer the real goal?
A blog does not help by existing. It helps when it turns your site into the answer to a specific question a real customer typed into Google or asked an AI assistant, and most contractor blogs never get there. The old goal was "rank for keywords." The current one is "be the source that gets cited, quoted, or read out loud," because a growing share of traffic that used to land on a ranked page never leaves the search result or the chat window now. The user gets their answer from a snippet or an AI summary and moves on.
That reframes what a post is for. It's not a container you fill with trade-related words so Google notices the page exists. It's a direct, complete answer to one question, written well enough that a search engine, an AI assistant, or a human skimming on a phone gets the actual answer without digging for it. A post that dances around the question for four paragraphs before answering it fails this job even at 2,000 keyword-optimized words.
What do service pages do well, and what can't they do?
Service pages do the buying-decision job: "do you do roof replacements, do you serve our town, what does it cost, how do we reach you." They're built to convert someone who already knows they need a roofer and is deciding which one. A strong service page has your trade, your service area, your process, your proof, and a clear next step. That's the page that turns traffic into a phone call.
What a service page structurally cannot do is answer the questions a customer has before they're ready to compare contractors. "Is the roof damaged or just aged?" "Will insurance cover this?" "Architectural or three-tab shingles?" Cramming those into a service page buries its real job, and it still won't rank for the specific question, because Google and AI assistants both reward a page that is about one question, not one that mentions it on the way to a quote form.
- Service pages convert people who already know what they need. One page per service, built to sell.
- Blog posts capture people who are still asking questions, researching, or comparing. One post per question, built to answer.
- Neither replaces the other. A site with only service pages misses everyone who is still in the "is this even necessary" stage. A site with only a blog and thin service pages loses the person who's ready to book right now.
Why does "post twice a week" advice fail almost every contractor who tries it?
Because the advice was written for a content agency's staffing model, not for an owner who is also running crews and answering the phone. Twice-a-week posting needs a dedicated writer or four hours a week most owners don't have. Almost every contractor who commits off a checklist article produces four or five posts in month one, watches nothing happen yet (SEO takes months, not weeks), and quietly stops. The site is left with a burst from one month and silence after, which reads worse than never starting.
The failure isn't discipline. The target cadence was set by what looks impressive in a marketing pitch, not by what a five-person crew can sustain for a year. A blog that ships one real post a month for eighteen months straight will out-rank a blog that shipped twelve posts in one enthusiastic month and went dark, every time. Google and AI systems both read consistency over a sprint, the same way a bank reads a steady paycheck over one good quarter.
Does answering real customer questions beat posting on a schedule?
Yes, and it isn't close. A calendar that says "post every Tuesday" produces posts written to fill a slot. A list of actual customer questions produces posts written to solve a problem, and those are the ones that get cited by AI assistants, ranked for long-tail searches, and actually read to the end. The schedule buys consistency. The question list is the content.
The fastest way to build that list is to pull it from three places you already have:
- Your Google Business Profile Q&A and reviews. The questions that come up more than once are worth a full post.
- Whatever your estimator or front desk gets asked on the phone every week. The single richest source, and it's free.
- The autocomplete and "People also ask" results for your service plus your town. Ranked by how often they're actually searched.
A post built from that list has a real person's question as its title and a specific answer as its body. That's a different piece of content than "5 Signs You Need a New Roof," written to hit a keyword instead of answer anything.
What changes now that AI assistants read your site instead of just listing it?
The mechanics changed, and most contractor sites haven't caught up. A Google search used to return ten blue links and let the user pick one. Now a growing share of searches, and nearly every ChatGPT or Perplexity query, return a synthesized answer with the source cited underneath, or not cited at all if the source page never gave the AI a clean answer to lift. Ranked and cited are two different outcomes now, and a blog built the old way, long, meandering, keyword-stuffed, tends to rank fine and get cited never.
There's a slightly humbling data point here, and we'd rather give it to you straight than oversell it. A structured-data study by SE Ranking found 71% of pages ChatGPT cites carry some form of structured data, which sounds like a strong argument for stacking schema on every post. But the same study found pages with FAQ schema specifically got fewer average citations than pages without it (3.6 vs. 4.2), and concluded no single schema type reliably moves citation counts on its own. The markup correlates with getting cited, but a schema tag on a vague, evasive answer doesn't make the AI cite the vague answer. What gets cited is a page that contains a direct, complete answer near the top, in plain language, whether or not it's wrapped in JSON-LD. Schema is the wrapper. A real answer is the thing being wrapped, and that's the part contractors skip because it takes more thought than a keyword-stuffed intro.
Practically, every post now needs the direct answer in the first sentence or two, not buried after three paragraphs of throat-clearing. That's the one habit that actually moves the needle on being the answer instead of just being indexed. We covered the broader mechanics of this shift in what AEO and GEO actually mean for a small business.
What's the realistic minimum: cadence, length, who writes it?
Here's the version we actually run for clients, stripped of the padding most "content strategy" guides add to look comprehensive:
| Element | Realistic minimum | Why | |---|---|---| | Cadence | 1 post per month, non-negotiable | Sustainable for a solo owner or small crew; still reads as "active" to Google and to a human visitor | | Length | 800–1,200 words | Long enough to fully answer the question with real specifics; short enough to actually finish writing | | Topic source | Real customer questions only | Anything else is guessing at what someone will search | | Structure | Direct answer in the first sentence, detail after | Matches how both search engines and AI assistants extract answers | | Who writes it | The person who actually knows the answer, or someone who interviews them | A generic writer producing generic contractor content is worse than no post that month | | Update cadence | Revisit and refresh 4–6 posts per year | A stale post with outdated pricing or code references costs you more credibility than it earns |
One post a month is twelve real answers a year, a useful resource after two or three years, and far more sustainable than the twice-weekly cadence most checklists recommend. More is fine if you have the bandwidth, as long as it's still built from a real question.
The "who writes it" row matters more than owners think. A contractor explaining why a chimney flashing fails after fifteen years reads as credible because it is. A generic writer paraphrasing a competitor's post reads as generic, because it is. If you hand this off, hand it to someone who will talk to your estimator first, not someone producing 800 words from a keyword list.
When is the honest answer no?
Sometimes it's genuinely no, and we'd rather tell a prospect that up front than sell a service that sits unused. A blog is the wrong move right now if any of these are true:
- You cannot commit to monthly, even loosely, for at least a year. Four posts and a stop is worse than no blog, because an abandoned page is a visible dead-end.
- Your service pages are still thin or missing. If someone can't find your service area, your process, or a way to reach you in thirty seconds, fix that first. A blog on a weak core site is decoration on an unfinished house.
- You have no way to source real questions. If nobody on your team can name five things customers ask most, you have a blank page and a deadline, not content. Fix the sourcing problem first.
- You're already getting enough qualified traffic and have nothing left to give it. Some businesses run near capacity on referrals and Google Business Profile alone. That's not a mistake, it's just not the best use of the next twenty hours.
If none of those apply and you can commit to one real, question-driven post a month, a blog is worth building. It compounds. A post written in month one is still answering someone's question in month thirty, at zero additional cost.
We build a blog into most client sites because, run correctly, it's one of the few marketing assets that gets more valuable the longer it sits there instead of decaying once you stop paying for it. "Run correctly" means everything above: real customer questions, a direct answer up top, a sustainable monthly cadence, and enough structure that a search engine and an AI assistant can both extract the answer cleanly. Not twice-weekly posting. Not a blog nobody remembers to update.
If you're not sure whether your site can support this, or whether your service pages are strong enough that a blog is even the next move, run it through our free AI-visibility and site grader. The SEO, AEO, and GEO service page covers what we build into every client site from day one, or reach out and we'll tell you straight whether a blog is worth building right now, or whether your twenty hours a month are better spent elsewhere first.
FAQ
Should your business website have a blog?
Only if you can commit to answering real customer questions on a real cadence, not because a checklist told you to add one. A blog with three posts from two years ago hurts more than no blog, because it signals the site is abandoned. If you can't post at least monthly with content that answers something a customer actually asked, skip it and put that time into your service pages instead.
How often does a contractor need to post to a business blog?
Once a month is the realistic minimum that still counts as active. Weekly is better with a genuine system behind it, but most contractors who commit to weekly quit within two months and end up worse off than if they'd picked a sustainable monthly cadence from the start. Consistency at a lower frequency beats a burst of ten posts followed by silence.
What is the difference between a blog post and a service page for SEO?
A service page answers "do you do this, and can you do it near me" with your service area and a way to contact you. A blog post answers one specific question in enough depth that the answer is actually useful. They rank for different searches and do different jobs. A site with strong service pages and no blog ranks for what you do; it won't rank for the questions people ask before they know what you do.
What should a contractor actually write blog posts about?
The exact questions customers already ask on the phone, in your inbox, and in your Google Business Profile Q&A, before they book. Cost questions, timeline questions, "is this actually necessary" questions, and material comparisons. If you can't name five things customers ask every month, sit with your estimator for an hour and write them down. That list is your entire content calendar.
Do AI assistants like ChatGPT actually read blog content to answer questions?
Yes, and that's the real shift. Google indexes your page and ranks it. ChatGPT, Perplexity, and Gemini go further: they read the page and hand the direct answer to the user, often without a click. A page has to contain a clear, complete answer near the top. A vague post optimized for keyword density gets skipped by the AI even if it ranks fine on Google.
Can a contractor write their own blog posts, or do they need to hire it out?
A contractor who genuinely knows the material can write a rougher, more specific post than most agencies will, because the specifics are what make it useful. The realistic failure mode isn't skill, it's time and consistency. If you can give thirty minutes a month to answering one real question in your own words, do it yourself. If that thirty minutes never happens two months running, that's the honest signal to hand it to someone who will make it happen on a schedule.