Checklist · Intellectual Property

Copyright Registration for a Website: A Practical Checklist

Type
Checklist
Jurisdiction
National
Date
2024-09-26
Topic
Intellectual Property

A website is not one copyrightable thing; it is a bundle of separate works, text, images, video, audio, and code, each with its own author, owner, and registration door. This checklist explains how to register the right parts the right way: auditing ownership, sorting content into published and unpublished, registering the crown-jewel assets individually, batching the rest through the group options (GRTX, GRUW, group photographs), registering the software as a computer program, and capturing the site's selection and arrangement as a compilation or collective work only where the claimant owns everything. It walks the publication puzzle, the constant-updating problem, the derivative-version rule, deposit format, and the timing that decides whether statutory damages and fees are ever on the table. Group caps, fees, and Copyright Office practices change; confirm current requirements at copyright.gov before filing.

Copyright Registration for a Website: A Practical Checklist

Intellectual Property > Copyright | Published 26 September 2024 - Updated 12 February 2025 | UpLaw - uplaw.us

A website is a container, not a work. Registration reaches the works inside the container, one door at a time, and only timely registration puts statutory damages and attorney's fees on the table. This checklist maps every door.

Keywords: website copyright registration, compilation, collective work, group registration, GRTX, GRUW, group photographs, derivative version, deposit copy, published versus unpublished, user-generated content, work made for hire, statutory damages, Section 412, automated database

Start Here: There Is No Copyright in "a Website"

A competitor clones your site overnight, and you call a lawyer. The first question back is not "how much do you want?" It is "which part did they take?" That question feels like a dodge until you understand the architecture of the Copyright Act, at which point it becomes the only sensible place to begin.

The subject matter of copyright is set by statute. Section 102(a) of the Copyright Act protects "original works of authorship fixed in any tangible medium of expression" and then lists eight categories: literary works; musical works; dramatic works; pantomimes and choreographic works; pictorial, graphic, and sculptural works; motion pictures and other audiovisual works; sound recordings; and architectural works. 17 U.S.C. § 102(a). Read that list again and notice what is missing. There is no category called "website." The Copyright Office will not let you type "website" on the authorship line of an application, because a website is not a work of authorship. It is a delivery mechanism, a membrane stretched over many separate works, each of which belongs somewhere on the Section 102 list and each of which is protected, owned, and registered on its own terms.

Picture a mid-size direct-to-consumer brand, call it Harborlight Provisions, running a store at a fictional domain. The homepage carries marketing copy (a literary work). The product grid is stitched together from studio photographs (pictorial works). A founder's-story page embeds a two-minute brand film (an audiovisual work) with an original score (a musical work and a sound recording). The checkout flow, the search bar, and the recommendation engine are running code (a literary work, registered as a computer program). Customer reviews pour in from strangers (works authored by third parties). And the way all of that is chosen, sequenced, and laid out, the selection and arrangement, is itself a candidate for a thin layer of protection as a compilation. That single URL is at least five distinct copyright analyses wearing a trench coat.

The practical payoff of that framing is everything. You cannot register "the website" as one thing, so the task is never a single filing. It is a portfolio decision: identify each stream of content, confirm who owns it, decide whether it is published or unpublished, and route it to the correct registration option, individual, group, or compilation, on a schedule that keeps the remedies alive. This checklist is the website-specific overlay on the general copyright registration checklist; for the narrative treatment of how the Copyright Office handles online content, see registering copyright in websites and online content. For the doctrinal foundations under all of it, the complete overview of copyright law is the hub.

Why Registration Is the Whole Ballgame

Before the mechanics, the stakes. Copyright attaches automatically the instant an original work is fixed; you do not need to register to own a copyright. 17 U.S.C. § 102(a). But ownership and enforceability are different animals, and for a U.S. work the gap between them is registration.

Two statutory rules do the heavy lifting. First, registration is a precondition to suit. Section 411(a) provides that "no civil action for infringement of the copyright in any United States work shall be instituted until preregistration or registration of the copyright claim has been made." 17 U.S.C. § 411(a). For years, courts split over whether filing an application was enough or whether the Office had to act on it. The Supreme Court closed that split in Fourth Estate Public Benefit Corp. v. Wall-Street.com, LLC, 586 U.S. 296 (2019), holding that "registration . . . has been made" when the Register of Copyrights actually registers the claim, not when the applicant mails the paperwork. Id. at 302; see also Fourth Estate, 139 S. Ct. 881, 889 (2019). Translation: if you wait until you are infringed to file, you sit in the Office's queue, often many months, while the infringement runs, before you can even get into the courthouse.

Second, and this is the one that changes behavior, the timing of registration decides whether the two most valuable remedies exist at all. Section 412 bars an award of statutory damages or attorney's fees for any infringement that began before the effective date of registration, unless the work was registered within three months of its first publication. 17 U.S.C. § 412. Statutory damages under Section 504(c) run from $750 to $30,000 per work as the court considers just, and up to $150,000 per work for willful infringement, without the plaintiff proving a dime of actual loss. 17 U.S.C. § 504(c). Attorney's fees come through Section 505. Miss the Section 412 window and you keep only actual damages and the infringer's profits, which for a stolen blog post or product photo is frequently a rounding error that no contingency lawyer will touch. Register in time and the same theft carries a five- or six-figure statutory exposure and a fee-shift, which is why timely registration is less a formality than the entire economic engine of copyright enforcement. For how those numbers actually get computed and awarded, see what an IP case is worth.

Registration also buys a rebuttable presumption of validity and of the facts in the certificate if made before or within five years of first publication, 17 U.S.C. § 410(c), and it is the ticket to the Copyright Claims Board, the small-claims tribunal created by the CASE Act, 17 U.S.C. §§ 1501-1511, where a claimant needs at least a pending application to proceed. Put the pieces together and the strategy writes itself: register the most valuable, most-copyable content early and on a cadence, so that on the day it is stolen the full remedial toolkit is already loaded.

There is a corollary that trips up many first-time registrants. The Section 412 window is measured against first publication of the specific work, not against the site's launch, not against the day you happened to notice the theft, and not against some general sense that the material has "been up for a while." Each work carries its own clock. A product photograph published in March and a blog post published in July have independent three-month grace periods, and a single group registration that sweeps both in does not reset either one; it merely registers each as of the group's effective date. That is why cadence beats volume. Filing one enormous batch once a year feels efficient, but it guarantees that most of the year's content spends months unregistered and outside the grace period, exposed to exactly the pre-registration infringement that Section 412 punishes. A smaller, more frequent filing rhythm keeps a far higher fraction of the catalog inside the window at any given moment. The arithmetic of that tradeoff, and the broader menu of specialized registration tools, is developed in the comprehensive guide to copyright registration and, at the roadmap level, in the toolkit for registering copyrights with the U.S. Copyright Office.

Phase 1 - Audit Ownership of Every Content Stream

You can register only what you own. The single most common and most painful surprise in website registration is discovering, at the moment of enforcement, that you do not own your own site, because the person who built it never signed the copyright over to you. So the audit comes first, before any application.

  • [ ] Inventory every category of content. Walk the site page by page and list each stream: marketing and editorial copy, product and lifestyle photography, illustrations and icons, the logo and brand graphics, video, audio, downloadable resources (PDFs, white papers, templates), the front-end and back-end code, and any user-generated content such as reviews, comments, or forum posts.
  • [ ] Confirm employee-created content as work made for hire. A work "prepared by an employee within the scope of his or her employment" is a work made for hire, and the employer is the author and owner from the moment of creation. 17 U.S.C. §§ 101, 201(b). No assignment paper is needed for genuine employee work; the statute vests title in the company by operation of law.
  • [ ] Get a signed assignment from every contractor. This is the trap. A freelance designer, photographer, or developer is an independent contractor, and independent-contractor work is not work made for hire merely because you paid for it.
  • [ ] Classify user-generated content as licensed or actually transferred. Read your own terms of service. Most grant the site a broad license to display UGC. A license is not ownership.
  • [ ] Close every ownership gap before filing. Fix the chain of title first; register second.

Why it matters, and the traps. The Supreme Court settled the employee-versus-contractor line in Community for Creative Non-Violence v. Reid, 490 U.S. 730 (1989), adopting the common-law agency test and holding that a sculptor commissioned to create a work was an independent contractor, so the commissioning party was not the author. The lesson for websites is blunt: unless a contractor's work fits one of the nine narrow categories of specially commissioned works in the Section 101 definition and the parties signed a writing calling it a work made for hire, the contractor owns the copyright, full stop.

That makes the written assignment the load-bearing document. Under Section 204(a), a transfer of copyright ownership "is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed." 17 U.S.C. § 204(a). Paying the invoice buys you an implied license to use the deliverable; it does not buy the copyright. If the web-design shop that built your storefront never signed an assignment, the shop, not you, owns the layout, the custom graphics, and often the templated code, and you cannot register that material as your own or sue over it. The clean fix is a present-tense assignment ("Contractor hereby assigns") in the development agreement, backed up by work-made-for-hire language as a belt-and-suspenders fallback. The mechanics of that determination live in the work-made-for-hire determination checklist.

User-generated content is its own puzzle. Say Harborlight's product pages fill with hundreds of customer photos and reviews. Those are original works authored by the customers, and Harborlight owns none of them by default. A typical terms-of-service clause grants the company a "worldwide, royalty-free, perpetual license" to use that content, which is plenty for display and marketing but is not a transfer of copyright, so Harborlight cannot register the reviews as its own works. Only an actual assignment in the terms (rare, and often unenforceable as to any single low-value post) would let the company register UGC in its own name. The platform-liability side of hosting third-party content, and why you generally should not want to own it, is covered in Section 230 and the IP carve-out. And if your worry runs the other direction, that outsiders are scraping your content, the interaction of contract, the CFAA, and copyright is mapped in web scraping after hiQ v. LinkedIn.

Worked example. Harborlight's audit turns up four ownership tiers. The blog posts and product descriptions were written by W-2 marketing staff: work made for hire, company owns them, ready to register. The hero photography was shot by a freelance photographer who invoiced per shoot and never signed anything: the photographer owns those images, and Harborlight holds, at most, an implied license, so those photos are quarantined until an assignment is signed. The e-commerce theme was bought from a template marketplace under a license that expressly reserves the developer's copyright: not registrable by Harborlight, and excluded from any compilation claim. The customer reviews are UGC under a display license only: never registrable as Harborlight's. The audit's real output is not a filing; it is a punch list of assignments to collect before the filings can be trusted.

Phase 2 - Classify Each Work as Published or Unpublished

Publication status is a hinge that controls three downstream decisions: which deposit rules apply, which group options you may use, and, through the three-month grace period, exactly when the Section 412 statutory-damages clock starts. Get it wrong and you can misfile a group, botch a deposit, or forfeit the grace period.

  • [ ] Apply the statutory definition, not intuition. Publication is "the distribution of copies or phonorecords of a work to the public by sale or other transfer of ownership, or by rental, lease, or lending," and it includes offering to distribute copies to a group for further distribution or public display. 17 U.S.C. § 101. The hidden key is the phrase "copies," a public performance or display, standing alone, does not constitute publication.
  • [ ] Treat display-only and stream-only material as presumptively unpublished. If users can view or stream content but are not authorized to download and keep a copy, and your terms prohibit downloading, the Copyright Office generally treats that content as unpublished.
  • [ ] Treat downloadable material as published. Content behind a "Download" button, files the public is authorized to retain, or material that also exists in distributed tangible copies, is generally published.
  • [ ] Document your reasoning and align your terms. Record why you classified each work as you did, and make sure your terms of service match the status you claim.

Why it matters, and the traps. "It's on the internet, so it's published" is a folk rule, not the law. The statutory definition turns on distribution of copies the public may retain, which is why a video that only streams may be unpublished while the same video offered as a download is published. The Copyright Office's Compendium of U.S. Copyright Office Practices (3d ed.) devotes extended discussion to the difficulty of pinning down publication for online material and counsels applicants to make a reasonable, documented determination. That ambiguity is real and longstanding; some courts have found that launching a website is itself a publication of its contents, treating the live posting as a distribution to the public, while other content, especially display-only media, resists that characterization. The safe practice is to decide deliberately, keep a note explaining the call, and make your posted terms consistent with it rather than letting a "published" claim collide with a terms-of-service ban on downloading.

The stakes of the call are concrete. Group registration of unpublished works (GRUW) requires that every work in the batch be unpublished; slip one published item into that group and the registration is defective as to that item. The published and unpublished photograph groups are separate options with separate rules. And the three-month grace period in Section 412 runs from first publication, so if you want the grace period you need a defensible publication date. When in doubt on a mixed batch, split the filing: unpublished works down one path, published works down another.

Phase 3 - Register the Crown Jewels Individually and Now

Not everything on a site deserves its own application, but the highest-value, most-copyable assets do. The signature photograph that anchors your brand, the long-form article that ranks and gets scraped, the explainer video competitors would love to lift, register each of those on a dedicated application, immediately, so the remedies clock starts the day the work goes live.

  • [ ] Identify the assets most likely to be copied and most valuable if they are. These are your crown jewels: the marquee visuals, the flagship written content, the key video.
  • [ ] File a standard application for each, individually. A single-work registration gives that asset the cleanest possible certificate and the earliest possible Section 412 clock.
  • [ ] File before infringement, or within three months of first publication. Either condition preserves statutory damages and fees under Section 412.

Why it matters, and the traps. A dedicated registration is insurance you buy before the fire. If Harborlight's signature product photo is registered the week it publishes, then the day a competitor rips it into their own store, statutory damages of up to $150,000 (for willful infringement) and a fee-shift are already on the table, and the case is worth bringing. If instead that photo is sitting in an unfiled quarterly batch when it is stolen, and the batch has not yet been submitted, the theft "began" before registration, Section 412 slams the door on statutory damages and fees, and the claim collapses to actual damages that rarely justify litigation. The whole point of singling out the crown jewels is to guarantee the remedy is loaded for the assets most likely to be taken. Note that the "single application" option (one work, one author, one owner, not made for hire) will rarely fit a business website, whose content is usually work made for hire owned by an entity; most crown-jewel filings will use the standard application. 37 C.F.R. § 202.3(b)(2). For the full registration walkthrough across work types, see the comprehensive guide to copyright registration.

Phase 4 - Batch the Rest Through the Group Options

Individual registration is right for the crown jewels and hopelessly impractical for the long tail: hundreds of blog posts, thousands of catalog images. Congress and the Copyright Office built group registration for exactly this, letting a claimant register many related works on one application with one fee under Section 408(c). 17 U.S.C. § 408(c); 37 C.F.R. § 202.4(a). The trick is matching each content stream to the right group option, because the eligibility conditions and caps are strict and non-negotiable.

  • [ ] GRTX for short online text. Group Registration of Short Online Literary Works covers 2 to 50 short online works, each between 50 and 17,500 words, by the same individual author (or the same joint authors), with the same claimant, all first published online within the same calendar year. 37 C.F.R. § 202.4(j). Blog posts, articles, and columns are the paradigm case.
  • [ ] GRUW for unpublished works. Group Registration of Unpublished Works covers up to 10 unpublished works by the same author with the same claimant. 37 C.F.R. § 202.4(c). Useful for draft content or display-only material not yet published.
  • [ ] Group photographs for image-heavy sites. Published photographs go through GRPPH and unpublished through GRUPH, each accommodating up to 750 photographs per application, subject to the option's specific conditions. 37 C.F.R. § 202.4(h)-(i). This is the workhorse for catalogs and galleries.
  • [ ] Serials, newspapers, and newsletters only if you truly operate as one. The periodical group options exist, but use them only if the site genuinely publishes on a periodical cadence with the required issue structure. 37 C.F.R. § 202.4(e)-(g).
  • [ ] Set a cadence, not a one-time filing. No single group option captures a perpetually changing multi-author site, so register on a recurring schedule.

Why it matters, and the traps. The caps and conditions are jurisdictional facts, not suggestions. GRTX will reject a 20,000-word treatise (over the 17,500-word ceiling) and cannot mix two authors' individual works into one claim. GRUW's ten-work limit and its all-unpublished requirement mean you cannot quietly fold a published piece into the batch. The photograph groups top out at 750 images each and demand a title list and specific metadata. The Copyright Office's Compendium Chapter 1000 governs the scope of these group registrations, and Section 1105.4 explains how far each group claim reaches. The deep dive on photo batching, including the DMCA metadata protections that pair naturally with it, lives in the copyright registration for photographs checklist.

Because no single option swallows an entire evolving website, the operative concept is cadence. A workable rhythm for a content-heavy site might be: a GRTX filing each quarter for that quarter's blog posts; a GRPPH batch each quarter for newly published product and lifestyle photography; individual filings for crown-jewel assets as they publish; and a software re-registration whenever a major release ships. Run on that schedule, and at any given moment the vast majority of the site's protectable content is registered within the Section 412 window rather than languishing unregistered until the day it is stolen.

The constantly-updated site and the automated-database option. For a site that behaves less like a magazine and more like a database updated continuously, a news aggregator, a listings platform, a reference site refreshed daily, there is a specialized path: group registration for a database and its revisions. The Copyright Office has long treated automated databases and their frequent updates as registrable as a group under its database rules (see U.S. Copyright Office, Circular 65, Copyright Registration of Automated Databases), which can cover a defined span of updates in one filing. Whether your site qualifies turns on whether it is genuinely a database of separately identifiable data, so treat this as a specialist option to evaluate with counsel rather than a default. It is, however, the most honest answer to the "my site changes every day" problem short of the derivative-version approach discussed in Phase 7.

Phase 5 - Register the Software Separately

The code that runs the site is a work of authorship in its own right, a literary work registered as a computer program, and it travels through a different door with its own deposit rules. Do not try to fold it into a content registration; register it as software.

  • [ ] Register the site's code as a computer program. The front-end and back-end code you own is protectable expression and registers as software, not as part of the "website."
  • [ ] Use the source-code deposit rule and redact trade secrets. The Office's identifying-portion rule generally calls for the first 25 and last 25 pages of source code, and it permits redaction of trade-secret material under its blackout and special-relief practices. 37 C.F.R. § 202.20(c).
  • [ ] Re-register major versions as derivative works. Each materially new release is a new version, registered as a derivative work claiming only the new or revised code.

Why it matters, and the traps. Copyright in code protects the expression, the way the program is written, not the functionality, algorithms, or ideas, and clearing open-source components before you deposit is essential because a copyleft dependency can complicate what you can claim. The full mechanics, including the source-code deposit rule, the trade-secret redaction options, and the "Rule of Doubt," are set out in the copyright registration for software checklist and, in narrative form, in registering copyright in software and source code. One conceptual point worth holding onto: registering the code protects the code; it does not protect the visual look of the rendered pages, the photographs, or the text. Those are separate works with separate registrations, which is exactly why a website is never one filing.

A subtler line separates the code from the rendered interface. When a browser executes your code, it paints a screen, and that screen has a look: a color scheme, a typographic system, a layout grid, iconography. Some of those elements are protectable and some are not, and the boundary is one of the most misunderstood in the field. Copyright does not protect functional layout choices, standard interface conventions, or, by itself, a typeface or "style"; the line runs between uncopyrightable functional or stock elements and the original expression layered on top. The distinction is worked through, with the fonts-as-software wrinkle, in the fine line between copyright protection for style, typefaces, and fonts. For the site, the practical takeaway is to register the protectable expression that actually exists, the original graphics, the original text, the original arrangement, through the correct doors, rather than to imagine that one "user interface" registration will lock up the whole look and feel. If the interface amounts to an audiovisual experience, as with an interactive game embedded in the page, that is yet another door; the audiovisual and code layers of interactive works are treated in registering copyright in board games and video games.

Phase 6 - Capture the Arrangement as a Compilation or Collective Work

After the individual works and the code are handled, one layer remains: the site itself, considered as an original selection, coordination, and arrangement of material. That layer can be registered, but only under tightly limited conditions, and its protection is famously thin.

  • [ ] Register the site as a compilation only if you fully own everything in it. A compilation registration protects the original selection, coordination, and arrangement of the underlying material and can reach the underlying components, but only if the claimant owns all of them.
  • [ ] Or as a collective work where separate contributions are assembled. A collective work, a work "in which a number of contributions, constituting separate and independent works in themselves, are assembled into a collective whole," is the right frame when independently authored pieces are gathered together. 17 U.S.C. § 101.
  • [ ] Exclude everything you do not own. Freelance photos without an assignment, licensed templates, customer reviews, and anything merely linked from elsewhere must be excluded from the claim.
  • [ ] Consider the "unit of publication" option for a launch. Where a set of works you own is first published together as a single unit, the Office permits registering them together on one application. 37 C.F.R. § 202.3(b)(4).

Why it matters, and the traps. The governing case is Feist Publications, Inc. v. Rural Telephone Service Co., 499 U.S. 340 (1991), which held that a compilation earns copyright only through original selection, coordination, or arrangement, and that even then the protection is "thin," reaching the arrangement itself but not the underlying facts or pre-existing materials. Id. at 348-51. Section 103(b) makes the same point statutorily: copyright in a compilation "extends only to the material contributed by the author of such work, as distinguished from the preexisting material employed in the work, and does not imply any exclusive right in the preexisting material." 17 U.S.C. § 103(b). For a website, that means a compilation registration protects the way you chose and arranged your pages and elements, and it reaches the individual works inside the arrangement only if you own all of them. Slip a freelance photo you never licensed for this purpose, or a batch of customer reviews, into a compilation claim, and you have both overclaimed and weakened the registration.

The compilation-versus-collective-work distinction matters for who owns the pieces inside the container. A collective work assembles separately authored contributions, a magazine, an anthology, a journal, and the default rule under Section 201(c) is that the collective-work author acquires only the privilege of reproducing the contribution as part of that collective work and revisions of it, while each contributor retains copyright in their own piece. That allocation, and the Tasini line of cases that shaped it for the digital era, is the subject of contributions to a collective work. The upshot for websites: registering the site as a collective work protects your assembly, not the contributors' underlying copyrights, unless those were separately transferred to you.

Phase 7 - The Constant-Updating Problem and the Derivative-Version Rule

Websites are not printed once; they change hourly. That reality collides with a registration system built around fixed copies, and the collision is resolved by treating each materially changed version as a derivative work.

  • [ ] Treat each materially revised version as a derivative work. A "derivative work" is one "based upon one or more preexisting works," including any form in which a work is "recast, transformed, or adapted." 17 U.S.C. § 101.
  • [ ] Claim only the new material in each version. By statute, the copyright in a derivative work covers only the new authorship, not the preexisting material. 17 U.S.C. § 103(b).
  • [ ] Exclude previously published, previously registered, public-domain, and third-party material. The application's "material excluded" and "new material added" fields must accurately carve out what is not new.
  • [ ] Keep a version log. Track what was registered, when, and which snapshot, so future derivative filings can exclude prior material precisely.

Why it matters, and the traps. No registration captures a website that will look different tomorrow; a registration captures the version you deposited. The honest way to protect an evolving site is to re-register meaningfully updated versions as derivative works, each claiming only what is new. That requires discipline: when you register the Q2 version of a page, you must exclude the Q1 content already published and registered, or you overclaim. The doctrine of thin protection, the originality threshold for the new material, and the overclaiming risk are worked through in registering derivative works. The database option from Phase 4 is the alternative frame for sites that update so continuously that a version-by-version approach is unworkable; between the two, most content sites are better served by scheduled derivative-version and group filings, while true databases lean on the database group.

Worked example. Harborlight overhauls its homepage in the spring. The prior version was registered in January. The new version keeps the old logo and two old photographs (previously registered), swaps in fresh marketing copy and three new photographs, and rearranges the layout. The correct spring filing is a derivative-work registration that claims the new copy, the three new photographs, and the revised arrangement, while expressly excluding the logo and the two carried-over photographs as previously registered material. Claim the whole page as new and you have made a material misstatement about content you did not newly author, which brings us to the accuracy rule.

Phase 8 - Prepare Deposits That Actually Match the Claim

The deposit is the fixed copy of the work you are registering, and it defines the outer boundary of what your registration protects. A claim in "an entire website" does not extend to anything a reviewer cannot see in the deposit. Deposits are where careful registrations quietly fail.

  • [ ] Deposit the content as it actually appears to users. The Office's preferred format is PDF, and a PDF "package" can capture a site's pages while preserving navigation and layout. 37 C.F.R. § 202.20.
  • [ ] Never submit a live URL as the deposit. A hyperlink is not a fixed copy. The Office requires a stable, submitted copy of the material; a live link that can change or vanish will not do.
  • [ ] Match the deposit to your claimed publication date. The snapshot should reflect the site as it existed on the date you claim, not a later or earlier version.
  • [ ] Register embedded audio and video separately. Media that streams from a player often will not render inside a static PDF capture, so a claim resting only on a page capture may not actually reach the embedded film or track; register those as their own works with their own deposits.
  • [ ] Preserve dated snapshots as evidence. A contemporaneous, dated deposit is clean proof of what the site looked like on a given day, useful far beyond the registration itself.

Why it matters, and the traps. Because the deposit defines the claim, the two classic failures are depositing too little and depositing a link. If your capture shows the page frame but the embedded product video is just a gray box, your registration does not reach the video, no matter what the application says. And a URL submitted "as" a deposit is not a deposit at all; the Office needs a fixed copy in hand. The evidentiary bonus is real and underappreciated: a registration deposit is a notarized-in-effect record of the site on a date certain, which can matter enormously when you later need to prove what was where and when, an authentication problem explored in getting website evidence admitted. Pair the registration with a proper copyright notice on the site, which is no longer mandatory but still defeats an innocent-infringer defense; the mechanics are in the copyright notice checklist.

Phase 9 - Keep the Claim Accurate: Section 411(b) and Unicolors

Everything above assumes your applications tell the truth. The final discipline is accuracy, because a registration built on a knowing material misstatement can be challenged, and the Supreme Court has recently defined exactly when that challenge succeeds.

  • [ ] State authorship, ownership, publication status, and dates accurately. Every material fact on the application, and especially the new-material and excluded-material fields on derivative and compilation claims, must be correct.
  • [ ] Do not claim third-party or previously registered material as new. Overclaiming in a compilation or derivative filing is the most common source of website registration inaccuracy.
  • [ ] Keep records that let you defend each certificate. Version logs, assignment files, and publication-date notes are your defense if a registration is questioned.

Why it matters, and the traps. Section 411(b) provides that a certificate satisfies the registration requirement even if it contains inaccurate information, unless the inaccuracy was included with knowledge that it was inaccurate and the inaccuracy, if known, would have caused the Register to refuse registration. 17 U.S.C. § 411(b)(1). In Unicolors, Inc. v. H&M Hennes & Mauritz, L.P., 595 U.S. 178 (2022), the Court held that this knowledge element extends to mistakes of law as well as fact, so a good-faith but mistaken belief about a legal requirement (there, the "single unit of publication" rule) does not invalidate a registration. Id. at 185-86. That is a meaningful safe harbor for honest applicants, and it is emphatically not a license to be careless. The protection turns on the absence of knowing inaccuracy, so the practitioner's job is to make each claim accurate in the first place and to keep the records that show any error was innocent. For a website registrant filing serial derivative versions and compilation claims, the exposure to inaccuracy is above average precisely because the claims are complex, which is why the version log in Phase 7 is not busywork.

Putting It Together: A Filing Cadence

Doctrine is easier to hold when it runs on a calendar. Here is how the phases collapse into an operating rhythm for our hypothetical Harborlight Provisions, a mid-size content-and-commerce site with a blog, a large photo catalog, embedded brand video, and custom code.

At launch, Harborlight collects assignments from its developer and photographers (Phase 1), classifies its content (Phase 2), and files three things: a standard registration for its two crown-jewel photographs and its flagship founder's-story video (Phase 3), a computer-program registration for the site's custom code (Phase 5), and, because it owns the launched content as a package, a unit-of-publication registration for the initial site as a compilation (Phase 6), carefully excluding the licensed template and the customer reviews it does not own.

Then it settles into quarters. Each quarter it files a GRTX group for that quarter's blog posts and a GRPPH group for newly published catalog and lifestyle photography (Phase 4). Whenever a major code release ships, it re-registers the software as a derivative work claiming the new code (Phase 5). When it overhauls a major page, it files a derivative-version registration claiming only the new material and excluding what was registered before (Phase 7). Every filing uses a PDF deposit that matches the page as it appeared on the claimed date, with embedded media registered separately (Phase 8), and every claim is logged so the next derivative filing can exclude prior material accurately (Phases 7 and 9).

The result is not perfect coverage, no registration scheme perfectly captures a living website, but it is coverage where it counts: the valuable, copyable content is registered inside the Section 412 window, the code is protected and re-protected as it evolves, the arrangement is claimed where ownership is clean, and the deposits and records will hold up if a competitor ever does clone the site overnight. And when that call comes and the lawyer asks "which part?", Harborlight has an answer, a certificate, and a live statutory-damages claim for each piece worth fighting over.

Common Mistakes to Avoid

  • Trying to register "the website" as a single work. There is no such category; register the components.
  • Assuming you own contractor-built design or code. Paying an invoice buys a license, not the copyright. Get the Section 204(a) assignment.
  • Treating all online content as "published." Publication turns on distribution of copies the public may retain, not on mere posting.
  • Dropping a published item into an unpublished group (GRUW), or exceeding a group cap. The eligibility conditions are strict; a single mismatch defeats the group as to that item.
  • Registering a compilation that sweeps in content you do not own. Exclude freelance photos, licensed templates, UGC, and linked material.
  • Claiming an entire updated page as "new." Each version is a derivative work; claim only the new material and exclude the rest.
  • Depositing a live URL, or a capture that omits embedded media. The deposit must be a fixed copy, and the claim reaches only what the deposit shows.
  • Filing once and forgetting. A living site needs a registration cadence, not a one-and-done.
  • Waiting until you are infringed to file. By then Section 412 has usually foreclosed statutory damages and fees.

The Consolidated Checklist

Phase 1 - Ownership audit. Inventory every content stream; confirm employee work as work made for hire (17 U.S.C. §§ 101, 201(b)); obtain written assignments from all contractors (§ 204(a)); classify UGC as licensed or transferred; close all gaps before filing.

Phase 2 - Published or unpublished. Apply the Section 101 definition; treat stream-only material as presumptively unpublished and downloadable material as published; document and align terms of service.

Phase 3 - Crown jewels. Register the most valuable, most-copyable assets individually and immediately; file before infringement or within three months of first publication (§ 412).

Phase 4 - Group the long tail. GRTX for short online text (§ 202.4(j)); GRUW for unpublished works (§ 202.4(c)); GRPPH/GRUPH for photographs (§ 202.4(h)-(i)); serials/newspapers/newsletters only if truly periodical (§ 202.4(e)-(g)); the database option for continuously updated sites; set a cadence.

Phase 5 - Software. Register the code as a computer program; use the source-code deposit and trade-secret redaction rules (§ 202.20(c)); re-register major versions as derivative works.

Phase 6 - Arrangement. Register the site as a compilation or collective work only where you own everything; exclude what you do not own; consider the unit-of-publication option for a launch (§ 202.3(b)(4)).

Phase 7 - Updates. Treat each material revision as a derivative work; claim only new material; exclude prior, public-domain, and third-party material (§ 103(b)); keep a version log.

Phase 8 - Deposits. Deposit the content as it appears (PDF preferred); never submit a live URL; match the deposit to the claimed date; register embedded media separately; keep dated snapshots.

Phase 9 - Accuracy. State every material fact correctly; do not overclaim; keep records that show any error was innocent (§ 411(b); Unicolors).

Primary Authority

Related UpLaw Resources

Related Checklists

Related Guides

Related Articles

Related Toolkits

This checklist provides general legal information from UpLaw (uplaw.us) and is not legal advice. Copyright Office practices, group caps, and fees change; confirm current requirements at copyright.gov and consult qualified counsel before filing.