If you've got a draft sitting unpublished because a voice keeps asking "who am I to write about this?", you're dealing with what most people call imposter syndrome. It's a normal reaction to putting your name on something public, and it doesn't mean you should stop.
The short answer: you don't have to feel like an expert before you publish, and you shouldn't pretend to be one. Write about what you've actually done or learned, say plainly what you have and haven't tested, and let the feeling shrink as your published work and your readers' replies pile up. Trying to argue yourself into confidence first rarely works, because there's nothing yet for the confidence to rest on.
What imposter syndrome is, and what it isn't
The idea has a specific origin. Psychologists Pauline Clance and Suzanne Imes described the "impostor phenomenon" in a 1978 paper about high-achieving women who, despite real accomplishments, believed they weren't actually capable and had fooled the people around them. The term has since been used far more broadly than that original group.
Two things are worth knowing about it. First, it isn't a clinical diagnosis. It's not listed as a disorder in the DSM-5 or the ICD-10, the manuals clinicians use; it's a name for a pattern of thoughts. Second, the original idea describes people whose doubt doesn't match their track record. A new blogger is in a slightly different spot: you don't have a track record yet, so some of your doubt is simply accurate. That's fine, and it changes what you should do about it.
Check whether the doubt is pointing at something real
Before you treat the feeling as noise, ask what, specifically, you'd need to do to feel ready to publish this post.
If you can name it, do it. Maybe there's a claim you haven't checked, a step you described but never tried, or a section you paraphrased from someone else without really understanding it. That kind of doubt is useful. It's your judgment telling you the post isn't finished.
If you can't name anything, and the post is accurate and honest about what you know, then more research won't help. You'll just keep polishing a draft that was ready a week ago. Publish it.
"Who am I to write about this?" has a practical answer
Most advice treats this question as a confidence problem. I think it's better treated as a question about what you're claiming.
You feel like a fraud when the post implies more than you can back up. So close that gap from the other side: claim only what's true.
- Write from what you've done or learned. "Here's how I set up my first blog and what confused me" is a post you're fully qualified to write. "The definitive guide to blogging" isn't, yet.
- Say what you have and haven't tested. If you compared two tools by reading their documentation rather than using both, say so. Readers can work with that. What they can't work with is a confident recommendation that turns out to be a guess.
- Document instead of posing. A record of what you tried, what happened and what you'd do differently is useful to the person one step behind you, and it doesn't require you to be an authority.
- Be honest about your level. One line is enough: how long you've been doing this and where your information comes from. Don't inflate it, and don't bury the post in apologies either.
This is the ethical way to write, and it also lines up with what Google asks for. Its guidance on helpful, people-first content asks whether a page shows "first-hand expertise and a depth of knowledge", giving the example of having actually used a product or visited a place, and says that of experience, expertise, authoritativeness and trust, "trust is most important." A modest post that's accurate about its own limits fits that better than one that performs expertise. It's also harder to copy, which matters more now that generic articles are cheap to produce; the guide to what makes a site hard to replace with AI-written content goes into that.