How to Copyright a Website's Design and Content

The first thing every freelance web designer learns the hard way: a website isn’t one copyrighted work. It’s at least three. The visual design is one work. The written content is another. The underlying code is a third. Each gets registered separately, each gets enforced separately, and missing one means your protection has a gap exactly where someone is going to copy you.

Here’s how working web designers and site owners handle this in practice.

The three (or four) copyrights inside a website

What’s actually on a typical website:

1. The visual design. Layouts, color schemes, typography choices, custom illustrations, photography, logo work. Protected by copyright as visual art.

2. The written content. Page copy, blog posts, product descriptions, FAQs. Protected by copyright as literary work.

3. The code. HTML, CSS, JavaScript, server-side languages. Protected by copyright as a computer program.

4. Compiled databases (sometimes). Structured content like product catalogs, member directories, custom data sets. Protected by database rights in the EU and copyright in some forms in the US.

A site copied from another site usually involves multiple of these. The infringer might lift the design (visual), the content (literary), and the structure (code) in a single act. Your enforcement is stronger when each component is separately registered.

What’s actually copyrightable

A common misunderstanding: “I’ll copyright my website.” That’s like saying “I’ll copyright my office.” The website itself is a container; the protectable creative work is inside it.

Specifically protectable:

• Original visual design (your custom artwork, illustrations, photography on the site)
• Original written content (your articles, copy, descriptions in your own words)
• Original source code that you wrote
• Original sound or video content

Not directly copyrightable:

• The general layout pattern of a website (header, sidebar, content, footer)
• Common navigation patterns
• Standard CSS techniques used by everyone
• HTML structure that’s industry-standard
• Templates you bought from a third party (those are licensed; you didn’t author them)
• WordPress themes you customized (the underlying theme is its author’s; only your customizations are yours)
• Content licensed from stock photography or stock content services

This distinction matters for enforcement. You can claim copyright on your original photography on the homepage. You can’t claim copyright on the fact that the homepage has a hero image with a centered headline below it.

What to register, exactly

Three separate registrations for a typical site:

Registration 1: Visual design

Register the master design files (Figma exports, Sketch files, AI files) plus high-resolution rendered images of the major page templates.

What to include:

• Final design files for major page types (homepage, product page, blog template, etc.)
• Custom illustrations and graphic assets
• Brand artwork (logo and variants)
• Custom typography or letterforms if any
• Color palette specification (as part of a style guide document)

Register as a single work under your name (or your client’s, if it’s a work-for-hire arrangement).

Registration 2: Written content

Register the body of original written content on the site. For substantial sites, this might be 50,000+ words across pages, blog posts, and dynamic content.

What to include:

• Page copy for non-templated pages (About, Services, Approach, etc.)
• Blog posts you’ve published
• Email sequences and downloadable content
• Product descriptions you’ve written
• Knowledge base or help center content

A practical approach: a single PDF export of all your original copy as one document. Register the PDF as one work, with the file hash establishing what’s covered.

Update the registration periodically as you add new content. Quarterly is reasonable for active sites.

Registration 3: Source code

Register the codebase. For the specifics of how source code registration works, see our developer guide.

What to include:

• The complete codebase as a Git bundle or ZIP archive
• Any custom plugins or modules you’ve written
• Custom templates and theme files
• Server-side scripts you’ve authored

Register on launch and on major updates. Open-source dependencies don’t need to be registered (they’re not yours); your registration covers only your original contributions.

Registration 4: Database (if applicable)

If your site has substantial original structured data (a custom directory, a curated catalog, an editorial database), the database itself may warrant separate protection. In the EU, database rights are a distinct protection separate from copyright. In the US, database rights are limited but the creative arrangement of facts can be copyrightable.

For most websites, this isn’t needed. For sites whose core value is their data (research portals, directories, structured indexes), it’s worth registering separately.

The 30-minute workflow

For a typical site launch:

Step 1: Lock the launch version

Determine the exact version going live. Same files, same content, same code. Future updates need fresh registrations under version tracking.

Step 2: Package each component

• Design package: ZIP of master design files + rendered page mockups
• Content package: PDF export of all original copy
• Code package: Git bundle of the repository

Each package becomes a separate registration.

Step 3: Register each component

Sign up for an online copyright service, register each of the three packages as separate works under version tracking with the same project name (e.g., “MyClientCo Website 2026-05 - Design”, ”…Content”, ”…Code”). Cost: $3 in tokens.

Save the verification URLs.

Step 4: US Copyright Office for substantial projects

For US-based sites that are commercially significant, file US Copyright Office registrations:

• Form VA for the design
• Form TX for the content
• Form TX for the code (registered as a literary work)

Each filing is $45-$65. Processing takes 3-9 months.

Step 5: Document in the site itself

Add appropriate copyright notices:

• Footer: ”© 2026 [Your Name/Company]. All rights reserved.”
• Optionally: link to your registration verification URL for credibility
• Terms of Service page: explicit copyright reservation

The notices themselves don’t create copyright (you already have it automatically). They put visitors on notice and create a clear record of your assertion.

Designer-client situations

Most websites are built by a designer for a client. Who owns what gets confusing fast.

The default rules:

The designer owns the copyright in everything they create, unless there’s a written assignment or work-for-hire agreement. This includes the design files, the custom code, and any content they personally wrote.

The client owns the copyright in any content they provided to the designer (their own product photos, their own copy, their own video).

Third parties own any licensed stock content, themes, templates, fonts, and plugins used in the build.

For a clean ownership structure, the design contract should specify:

• That on receipt of final payment, the designer assigns all copyright in the deliverables to the client
• That the designer retains the right to use the work in their portfolio and case studies
• That the client must respect any third-party licenses for stock content used in the build
• That ownership of pre-existing assets the designer brought (their own custom code library, for example) doesn’t transfer

Without these clarifications, you end up with messy ownership questions years later when something needs to be enforced.

Common copying patterns

Sites get copied in specific recognizable ways. Each has a different enforcement approach.

Pattern 1: Direct clone

Someone copies your site essentially wholesale. New domain, slightly different colors, same structure, same content, same code patterns. The site is sometimes hosted in a jurisdiction where enforcement is difficult.

Enforcement: DMCA notices to the hosting provider. If hosted in cooperative jurisdictions, removal within days. If hosted in non-cooperative jurisdictions, much harder.

Pattern 2: Content scraping

A “content farm” scrapes your blog posts and republishes them, sometimes paraphrased, often verbatim. Sometimes monetized with ads, sometimes used to drive SEO to other content.

Enforcement: DMCA notices to the platform. Google’s removal of search results for clearly-scraped content (via google.com/copyright). Cease and desist if the scraper is identifiable.

Pattern 3: Design lift

A competitor or peer takes your visual design but uses different content and code. They’re more sophisticated than direct cloners.

Enforcement: Document the design similarities specifically (color codes, typography choices, layout proportions, distinctive design elements). A C&D works when the copying is clear. Going public sometimes helps.

Pattern 4: Code copying

Someone uses your custom code, often without realizing they should. Common in JavaScript and CSS where techniques are visible. Less common for server-side code.

Enforcement: Source code comparisons. DMCA notices to GitHub if hosted there. Repository removal can be fast when copying is direct.

Pattern 5: AI training without consent

Site content used to train language models or generative AI. This is an active legal area in 2026.

Enforcement: The legal landscape is evolving rapidly. Major lawsuits are underway. For now, the practical options include robots.txt opt-out signals, opt-out registries, and joining class actions where applicable.

Updating registrations over time

Websites evolve continuously. New posts, redesigns, code updates. Your registration approach should match:

Quarterly content registrations. Every quarter, export your accumulated original content and register as a new version. Covers all the new blog posts, page updates, and added pages from the quarter.

Per-redesign visual registration. Each major design refresh gets a new registration. The old registration still covers the old version of the site; the new one covers the redesigned version.

Per-release code registration. Major code updates get new registrations under version tracking.

This rolling approach keeps your protection current without requiring registration of every minor change.

The honest cost analysis

For a typical small business website:

Initial registration on launch:

• 3 online registrations (design + content + code): $3
• US Copyright Office filings (optional, 3 forms): $135-$195
• Total: $3 to $200

Ongoing maintenance:

• Quarterly content registration: $4/year
• Annual code refresh: $1/year
• Annual design refresh (if applicable): $1/year
• Total: about $6/year

For a creator-driven content site (a blog, a portfolio, an online publication), the math is even better because the content registration is the most valuable and the code and design are simpler.

For the broader analysis of why copyright registration matters at all, see our piece on automatic copyright vs registration.

The minimum viable strategy

If you’re launching a website this month:

1. Pre-launch: Register the design, the content, and the code each as separate works. Save the verification URLs.

2. In your terms of service: Reserve all rights and reference your registrations.

3. In your site footer: Standard copyright notice.

4. Quarterly: Register new content additions.

5. At major updates: Register the new versions.

6. When you find copying: DMCA notice to the host. Cease and desist if identifiable. Each handled separately.

This is the foundation that protects against the common patterns. The unusual patterns require more specialized response, but the foundation handles the cases that come up most often.

A website is a substantial creative work. Protecting it requires the same discipline as protecting any other creative work, with the added wrinkle that it’s actually multiple creative works in one package. Register each one. Update as the site evolves. Enforce promptly when copying appears. The infrastructure cost is minimal. The protection is real and immediate.