Your content does not have to go viral

No, your service business doesn't need to go viral for its content to be useful. A post can answer a customer's question, explain your work, or help someone decide to contact you without reaching millions of people. I'd focus on making those answers useful and easy to find.

By Eric Yim, Protocol Text

Entertainment in your feed isn't the standard for your business

I think service providers overcomplicate social media because they overthink the content they have to make. They look at what's in their feed, and a lot of it is entertainment. Then they think that if their content doesn't have millions of views, it doesn't do anything.

But someone watching a funny video might have no reason to hire the business that posted it. Someone reading a straightforward answer about a service may be much closer to making a decision. Those are different kinds of attention.

A small audience doesn't automatically mean the post worked, either. People still need to encounter it, understand it, and have a reason to care. The point is to judge attention in relation to the work you want, rather than treating a view count as the whole result.

Low visibility can start to feel like low value. I wouldn't use one quiet post to decide that people don't care about quality or that your work isn't good.

Make content that helps someone choose

It's okay to make really dry content. It can really just be your work. You can explain what you do, what your values mean in a customer decision, or a question that comes up in conversations. It doesn't have to be this funny dance.

Start with a question that creates uncertainty before someone hires you. What do they need to understand before requesting an estimate? What information would help you answer them accurately? What differences between service options do they keep asking about?

I would keep those answers connected to one foundation: the work you want people to know you for. You can have variety, including personality, without leaving readers guessing about what the business does. An unrelated post isn't automatically harmful, but a scattered collection gives people less clear information to work with.

Try one customer question before planning a month of posts

Here's an illustrative example, not a client result. Imagine a painting business regularly hears, “Why can't you give me an accurate price from the room dimensions alone?” That question gives the owner a useful topic without needing a trend.

The owner could explain which details their estimating process requires, such as the surfaces included or preparation needs. They should use their actual process rather than copying another company's answer. A relevant photo could help explain a detail, with permission and without exposing customer information.

Try this exercise with your own business:

1. Write down a question from a real conversation. Keep the customer's everyday wording and remove identifying details.
2. Answer it directly. Put the useful answer first, then explain what the answer depends on.
3. Add one concrete detail. Use a relevant work photo, a process explanation, or a clearly labeled example.
4. Give the reader a sensible next step. That might be gathering information for an estimate rather than booking immediately.

This gives the post a job. Before publishing, ask yourself whether someone could use it to understand a choice or take the next step. If it only says that you do great work, add the explanation that helps them evaluate that claim.

Give useful answers a place people can find later

Part of why I believe this matters is that content can remain useful after its first appearance in a feed. An answer you published two years ago may still address something a customer needs today, provided it's accurate.

In the interview, I talked about crawlable content giving AI context. Crawlable means an automated system can access a page and read its content. That creates an opportunity for discovery; it doesn't guarantee indexing, an AI recommendation, or a perfectly timed introduction.

I'd keep important answers on your website as readable text, then adapt them for social posts. Use a descriptive title and link to the answer from a relevant page. Don't leave the entire explanation inside an image. Social platforms have different access rules, so don't assume every post is available to every search or AI system.

Judge the post by what it helps people do

Look beyond views to relevant website visits, inquiries that mention the answer, and conversations where the post helped explain something. These aren't interchangeable: a visit is evidence of attention, while an inquiry gives you more information about intent.

You can ask new inquiries how they found you and which information helped. Keep a simple record, while recognizing that people may encounter several posts and never mention them.

If a post gets little response, check the question, clarity, and distribution before abandoning the approach. Useful content still needs a way to reach people. It also can't repair an unclear offer or unanswered inquiries by itself.

Frequently asked questions

Should I delete an old post because it barely got any views?

Not for that reason alone. Check whether it still answers a relevant question accurately. You might improve its title, update the explanation, or link to it from a related page. Remove or correct misleading information, but don't treat age or low views as proof that an answer has no use.

Can I use video if I don't like writing?

Yes. You can talk through a question or show a relevant part of your work. Add accurate captions for viewers, then turn the explanation into readable website text if it deserves a lasting page. Review the wording so transcription mistakes don't change your advice.

How much time should I spend on this if I'm already busy?

Start with one question you already answer often and a time limit you can sustain. Reuse that explanation where it fits rather than inventing a separate topic for every platform. If content work begins interfering with serving customers or responding to inquiries, reduce the scope before increasing the posting schedule.