How to register DOIs for proceedings
without a publisher

What a DOI actually is

A DOI is a registered redirect plus metadata: doi.org/10.XXXX/suffix resolves to a URL you control, and the registration agency (for scholarly content, almost always Crossref) holds the paper's metadata (title, authors, publication date), which is what citation databases, reference managers, and Google Scholar consume. Papers with DOIs get cited more reliably because the link never rots and the metadata is machine-readable.

Step 1: Join Crossref

Crossref membership is open to any organization that publishes scholarly content; a university department or a conference-organizing association qualifies. As of 2026, the smallest membership tier is a few hundred dollars per year plus roughly one dollar per registered paper (check crossref.org/fees for current numbers). On joining you receive a DOI prefix (the 10.XXXX part) under which all your DOIs live.

If yearly membership does not fit a one-off event, some organizations sponsor deposits for third parties; your university library may already be a member and able to deposit on your behalf. Ask before buying a membership.

Step 2: Choose a suffix scheme

The suffix (everything after the slash) is yours to design. Rules of thumb:

• Make it opaque or semi-structured, not meaningful: 10.XXXX/acme2026.042 works; encoding the paper title does not: titles get revised, and a DOI can never change.
• Keep one scheme across conference years, with the year in the suffix, so your 2027 volume reads as a sibling of the 2026 one.
• Decide up front whether the volume itself gets a DOI in addition to the papers. It should, because the volume DOI is what libraries catalog.

Step 3: Landing pages, the requirement people miss

A DOI must resolve to a landing page: a human-readable page showing the paper's title, authors, abstract, and a link to the PDF. Pointing the DOI directly at the PDF violates Crossref's rules: the landing page is where the metadata lives when the PDF moves. This is the piece most first-time depositors discover late, because it means your conference needs a small per-paper web page, generated and hosted somewhere stable, before deposit.

Step 4: Build and submit the deposit XML

Crossref deposits are XML files against their deposit schema (5.3.1 at the time of writing), using the conference content type: one conference_paper element per paper with contributors (given name, surname, affiliation, ORCID iD where you have it), title, pages within the volume, publication date, and the DOI + landing-page URL pair. The volume-level element carries the proceedings title, ISBN if you have one, and the conference name, location, and dates.

For a handful of papers, Crossref's web deposit form works. Past about twenty, generate the XML from the same metadata spreadsheet you use for the volume's table of contents. With one source, the TOC, the stamped DOIs, and the deposit metadata can never disagree. Submit through the admin interface or the HTTPS deposit API, then read the confirmation log: Crossref validates against the schema and rejects individual records with reasons, and a 95%-accepted deposit is a normal first outcome.

Step 5: After the deposit

• Test resolution. Every DOI should resolve within a few hours. Click a sample.
• Stamp the DOIs on the papers. Each paper's first page should carry its DOI, because readers cite from the PDF in hand, not from the landing page.
• Google Scholar indexing follows from the landing pages, not from Crossref itself: Scholar wants per-paper pages with citation meta tags (citation_title, citation_author, citation_pdf_url). If your landing pages carry those tags, indexing typically follows without any submission step.

The spreadsheet is the hard part

None of the steps are conceptually difficult. The real work is metadata hygiene across a hundred papers: author name spellings, affiliation strings, ORCID iDs collected at submission rather than begged for afterwards. Ready.Pub keeps that metadata in one editable table, collects ORCID iDs from contributors at upload, stamps DOIs onto the papers, and exports valid deposit XML (schema 5.3.1) plus JATS XML for digital-library ingestion. The workflow is on the proceedings page.