Are Online Blog Posts Protected By Copyright? The Real Rules (and What They Get You)

The short version: Yes, your blog post is protected by copyright automatically, the second it's fixed in a readable form online, no registration or copyright notice needed in the UK, US, or most of the world. What copyright doesn't give you is an easy, free, or fast way to stop someone taking it. That gap between "legally protected" and "practically protected" is where most bloggers get caught out, and it's the bit nobody tells you when you first start publishing.

What copyright covers the moment you hit publish

Under the Berne Convention, which the UK, US, and 180-odd other countries have signed, copyright attaches automatically to any "original literary work" the instant it's created and fixed in a tangible form. A blog post counts. You don't need to register it, stamp a © on it, or send yourself a copy in the post (that old "poor man's copyright" trick does nothing legally, by the way, it's a myth that refuses to die).

What's protected is your specific expression: your wording, your structure, your examples, your turn of phrase. What's not protected is the idea itself. If I write a post about "five ways to grow an email list," nobody owns that concept. Anyone can write their own five ways. What they can't do is copy my sentences, my specific examples, or lift my post wholesale and republish it under their own name.

In UK law this sits under the Copyright, Designs and Patents Act 1988. In the US it's Title 17 of the US Code. Both give the creator (that's you, the person who typed the words) exclusive rights to reproduce, distribute, and adapt the work, and both make copyright automatic on creation, not on publication.

The bit that trips people up: who owns the post

This matters more than most bloggers realise. If you write posts as an employee, in the course of your job, your employer usually owns the copyright, not you, under UK law's "work made for hire" style rules (in the US it's literally called work for hire). If you're a freelance writer and you sign a contract that transfers rights, the client owns it once they've paid, not you, even though you typed every word.

I've seen this go wrong both ways. A client of mine once assumed a freelancer's posts belonged to the business by default because they'd paid for them. They hadn't specified anything in the brief. Legally, without a written assignment of rights, the freelancer technically still held copyright and could, in theory, have republished those exact posts elsewhere. It didn't turn into a fight, but it easily could have. If you want to know what a proper working relationship with a freelance writer should look like on paper, including who owns what, this breakdown of what a real freelance writing job looks like is worth reading before you hire anyone or take on a gig yourself.

The fix is one paragraph in a contract: "All rights, including copyright, in the work produced under this agreement transfer to [Client] upon full payment." That's it. I put a version of that clause in every freelance and ghostwriting agreement I sign, on both sides of the table.

What copyright doesn't do (and this is the part people don't want to hear)

Here's the uncomfortable truth that most posts on this topic skate past: having copyright doesn't stop anyone from stealing your content. It gives you the legal right to make them stop, but enforcing that right costs time, money, and energy that most solo bloggers and small business owners simply don't have.

Say someone in Vietnam copies your 1,500-word blog post word for word and republishes it on their site with ads on it. You technically have a case. Practically, you're not flying to Vietnam or hiring an international lawyer over one blog post that made you no direct revenue. Copyright law protects the big fights, the ones worth money, like a publisher stealing a book manuscript or a company lifting an entire course. For the everyday scraper who copies your "how to write a LinkedIn headline" post, your only realistic tool is a DMCA takedown, and even that only works if the thief's host is based somewhere that respects DMCA requests, which not all of them are.

I say this as someone it's happened to. A few years back I found an entire post of mine, one on LinkedIn outreach strategy, sitting on a random marketing blog with my name quietly removed and someone else's byline added. Same structure, same examples, even the same slightly odd phrase I use about "warm outreach not cold spam." I sent one email to the site's hosting provider (found through a quick WHOIS lookup) with a formal DMCA notice attached, screenshots dated and everything. The post came down within four days. No lawyer, no fee, just the right email to the right inbox. That's usually how these things get resolved, quietly and without drama, not through court.

Step by step: what to do if someone copies your post

• Screenshot everything first. Date-stamped screenshots of both your original post and the copy, before you contact anyone, because pages get edited or pulled once people realise they've been caught.
• Check your original publish date. Google's cache, the Wayback Machine (web.archive.org), or your own CMS timestamp all count as evidence of when you published first.
• Find the host, not just the site. Run the offending URL through a WHOIS lookup tool to find who hosts it. That's who you send the takedown to, not the site owner, who'll usually ignore you.
• Send a DMCA takedown notice. Most major hosts (GoDaddy, Bluehost, SiteGround, Cloudflare) have a dedicated abuse or DMCA email address. Templates for these notices are free and easy to find; you don't need a lawyer to write one.
• Report to Google directly. Google's own DMCA tool at their Search Console removal request page will delist the copied page from search results even faster than waiting on a host, often within days.
• Escalate only if there's real money at stake. If it's a competitor lifting your entire lead magnet or course content, that's when a solicitor's letter or, in the US, statutory damages of up to 150,000 dollars for wilful infringement (if the work is registered with the US Copyright Office) become worth pursuing.

Should you register your blog posts?

In the UK, there's no formal copyright register, so there's nothing to file, your protection is automatic and that's simply how it stays. In the US, registration with the US Copyright Office is optional but does something useful: it's the difference between suing for actual damages (which for a blog post might be a few hundred pounds of lost traffic value) and suing for statutory damages of up to 150,000 dollars if the infringement was wilful, plus attorney's fees.

Registration costs 65 dollars per work through the eCO online system, or you can register a group of unpublished or published works together for a lower per-piece cost, which is what most serious bloggers and course creators do, registering a batch of posts every quarter or so rather than one at a time. For most UK-based bloggers this is irrelevant since UK courts don't work the same way, but if you sell primarily to a US audience or publish through a US-based site, it's worth knowing the option exists.

The AI training question nobody has a clean answer to yet

This is the part that unsettles a lot of writers I talk to, and I won't pretend there's a tidy resolution. Large language models have been trained on enormous scrapes of public web content, and a lot of blog posts, including plenty of mine, almost certainly sat in that training data without permission or payment. Copyright law says you own your expression. It says nothing clear yet about whether training a model on that expression, without reproducing it verbatim, counts as infringement. Courts in the US and UK are actively working through cases on exactly this right now (the New York Times versus OpenAI case is the one to watch, and it's unresolved as of writing).

My honest take: you can add a robots.txt disallow for AI crawlers like GPTBot, and some publishers do, but it won't retroactively remove what's already been scraped, and it won't stop crawlers that ignore the file anyway. This is one area where the law is running behind the technology, and no amount of copyright notice at the bottom of your post changes that reality today.

Practical protection that works, beyond the law

Given all of the above, here's what I'd spend time on rather than worrying about legal enforcement you'll rarely use:

• Run your own key posts through Copyscape or a similar plagiarism checker every few months. It takes ten minutes and shows you copies you'd never find by searching yourself.
• Set up a Google Alert for a distinctive phrase from your best posts. If someone copies you word for word, that phrase surfaces the theft within days.
• Put a visible copyright line in your footer: "© 2026 [Your Name]. All rights reserved." It changes nothing legally, since protection is already automatic, but it does put honest people off and it makes your case look more serious to a host reviewing a takedown request.
• Watermark or brand your original graphics and screenshots specifically, since images get lifted even more often than text and are just as protected.

If you're building a business around your content, whether that's blog traffic feeding an email list or content supporting a paid service, this is exactly the kind of operational detail worth building into your workflow from day one rather than firefighting later. It's a small part of the wider picture of how AI and automation are reshaping content work generally, which is where a lot of my own consulting conversations end up going with clients who ask me to help them get their content, tools, and processes set up.

To get your name in front of a new audience, look at law blogs that accept guest posts. If you run a content site, read SEO for publishers.

Related: guest post examples.

Frequently asked questions

Do I need to add a copyright notice to my blog posts?

No, copyright protection is automatic under the Berne Convention the moment you publish, in both the UK and US. A visible copyright notice adds no extra legal protection, but it's a useful, cheap deterrent and it strengthens your case when reporting theft to a host or to Google.

Can someone legally quote part of my blog post?

Yes, short quotes used for commentary, criticism, review, or education are usually covered by fair dealing in the UK or fair use in the US, provided they credit you and don't reproduce the substantial or "heart" of your work. Copying an entire post, or the bulk of it, goes well beyond that protection.

What can I do if a competitor copies my blog post word for word?

Screenshot the copy with a date stamp, find their web host through a WHOIS lookup, and send a formal DMCA takedown notice to that host's abuse or legal email address. Most takedowns resolve within a week without needing a solicitor, and Google's own removal tool will delist the copied page from search results separately.

Does copyright stop AI companies from training on my blog content?

Not clearly, and not yet. Copyright protects your specific wording, but whether training an AI model on scraped web text counts as infringement is still being argued in active court cases in the US and UK, so there's no settled legal answer as of 2026.