Shelf-Ready Before Launch: A Metadata Audit for Indie Books Headed to Libraries
Photo: SilesianSoul, CC BY 4.0, via Wikimedia Commons
At Red Door Publishing, we spend a lot of time thinking about doorways. A cover is one. A first page is another. But for readers who discover books through their local library, the first doorway is often a catalog record—a few lines of metadata that decide whether a title shows up in a search, lands on a themed shelf, or gets recommended by a librarian who never saw the physical book.
That is not the most romantic sentence we have ever written. It may be one of the most practical. Library catalogs are an underused doorway for indie books, especially in the U.S., where public libraries buy print and e-books through vendors, consortiums, and approval plans. If your metadata is thin, late, or messy, the door stays closed. If it is clean and complete before publication, librarians can find you, evaluate you, and put you in front of readers.
Here is a field guide to the metadata work that matters most—and a checklist you can use before your next launch.
Start with the record, not the cover
A librarian often meets your book as a record in a vendor database or catalog, not as a beautiful object. That record needs to be accurate, complete, and sent early. For most indie presses, this means preparing ONIX metadata or a comparable feed for distributors and library vendors well before pub date. The exact timeline depends on your distribution setup, but four to six months ahead is a reasonable target for many titles. Late metadata is not just inconvenient; it can mean your book misses a buying cycle.
BISAC codes: choose the shelf before the shelf chooses you
BISAC codes, maintained by the Book Industry Study Group, are the categories many retailers and vendors use to shelve and search books. Pick a primary code that honestly describes the book, then add two or three secondary codes that reflect real angles—not every keyword you can imagine. A literary novel set in a small town might use a primary literary fiction code, with secondary codes for family life or a specific region if those are genuine. Avoid the giant generic codes as your only choice. “Fiction” is not a shelf strategy.
Accuracy matters more than volume. Stuffing codes can make a record look spammy to humans and muddy to systems. Choose the codes a librarian would use if they were trying to help a patron find this book.
Subject headings: speak librarian
BISAC is not the only vocabulary in the room. Library catalogs often use controlled subject headings, including Library of Congress Subject Headings. You may not control every heading a cataloger assigns, but you can supply clear, library-ready subjects in your metadata and on your press sheet. Include place names, time periods, identity terms, and themes when they are central to the book. If your novel is about a family running a diner in rural Ohio, say so in plain language. If your nonfiction book covers climate adaptation in coastal cities, make that visible.
When in doubt, ask a librarian. Not as a marketing favor, but as a professional courtesy. A reference or cataloging librarian can tell you whether your subjects are legible to the systems they use every day.
Series and volume information: do not make patrons guess
If your book is part of a series, state the series title, volume number, and reading order clearly. If it stands alone, say that too. Librarians and patrons need to know whether they can start here or whether they should begin with book one. Ambiguity creates friction at the exact moment someone is trying to decide. Include series information in your metadata, on your website, and in the book itself. Consistency across all three is the goal.
Accessibility notes are not fine print
Accessibility metadata helps libraries and readers know whether an e-book works with screen readers, whether alt text is present, and whether the title meets common accessibility standards. For print books, note large-print or dyslexia-friendly features if they exist. For e-books, include accessibility details in your ONIX feed and on your product page. Do not treat this as a compliance box. A blind reader, a dyslexic reader, or a librarian serving them is looking for the same door everyone else is.
Description formatting: write for scan and search
Your description has two jobs: help a human decide and help a system match. Lead with a one- or two-sentence hook that makes sense without the cover. Then give a clean paragraph or two of context. Keep the language concrete. Avoid HTML clutter, all-caps, and keyword soup. Include format details, publication date, page count, and ISBN where required. If you have a short description and a long description, make sure both are accurate and free of spoilers.
A pre-publication metadata checklist
- Confirm title, subtitle, author name, and imprint match the cover, copyright page, and website.
- Assign one primary BISAC code and two or three accurate secondary codes.
- Add library-ready subject headings, including place and time when relevant.
- State series title, volume number, and reading order—or clearly mark the book as standalone.
- Include accessibility notes for every format.
- Write a short hook and a fuller description in plain language.
- Check ISBNs, format, price, page count, and publication date.
- Send metadata to distributors and library vendors early.
- Ask a librarian or library-savvy friend to search for the title by subject, author, and series.
- Fix anything that makes the book hard to find before launch day.
The doorway test
Before publication, try to find your own book the way a stranger would. Search by subject. Search by the phrase a reader might use. Look for the series. Check the accessibility notes. If you cannot find it, a librarian may not either. Metadata is not glamorous, but it is a hinge. Oil it before the door opens.