We see versions of the question “Is my DOI registered?” all the time. Because it’s such a fundamental part of the process, it’s easy to assume everyone else just “gets it,” and members have worked up all different ways to check their DOIs, some more reliable than others. But because the answer to this question is so definitive, it’s worth returning to the fundamentals. For this Ticket of the Month, we’re going back to the basics for everyone and I, as a new tech support specialist, am learning a great part of these fundamentals along with you.
Recently, a member reported that several DOI deposits “were not registered” simply because they couldn’t find them via a Google Search. Some DOIs appeared in the Google Search results, but those that didn’t led our member to doubt the success of their registration. This brings us to the big question: If Google can’t find it, is my DOI successfully registered?
Spoiler alert: Yes. A DOI can be fully registered and resolvable even if it doesn’t yet show up in Google. The DOI exists whether or not it’s been “noticed” by search engine crawlers, and really, we may be giving Google too much metaphysical power over what exists and what does not. While a Google search tells you if a page has been indexed by google, it cannot tell you if a DOI has been registered with Crossref and its metadata made openly available through our APIs.
Registration steps and verification methods at a glance
Before we go into the methods for checking a DOI status, it helps to have a working definition of what we mean by a “registered DOI.” To understand the status of a record, it helps to define registration through three specific steps.
First, you send the record to Crossref; at this stage, checking your submission logs simply tells you that the submission has been successfully processed.
Next, Crossref sends the DOI to the DOI resolver. Checking the DOI resolver proves whether a brand-new DOI is actually resolving and functioning as a link. In its simplest terms: if you click the DOI link and it takes you to the correct landing page, it’s resolving.
Finally, the associated metadata is sent to our REST API. Checking Crossref Metadata Search or the REST API proves that the metadata has made it all the way through to our APIs and is discoverable to the wider scholarly ecosystem.
These are the steps and conditions required for a DOI to be considered fully registered, and the methods of verification - submission logs, DOI resolver, Crossref Metadata Search, and REST API - allow you to check the status of your DOI at each step.
Let’s start with the submission logs.
Method 1: Submission logs
When you submit metadata to register a DOI record, your record doesn’t just appear instantly; it first enters a queue. Once the system finishes processing your submission, a submission log is generated. The record will either be successfully created, or the log will highlight specific errors that may have stopped it from being registered.
For deposits made through the web deposit form, Simple Text Query, uploads via the admin tool, or HTTPS POST, we automatically email you this log. The email goes to the email address you provided in the form or included in the <email_address> field in your XML. The subject line is “CrossRef Submission ID.” Inside, you’ll find your submission ID, a clear success or failure status, and details explaining any errors. Here is how it will look (If the XML feels overwhelming, focus on this crucial part, as it will tell you whether your submission was successful or not - either <record_diagnostic status =“success”> or <record_diagnostic status =“failure”>
If your log looks like the one below, your work is done, the DOI is registered:
If you’re registering content through the Crossref XML plugin for OJS or using the New Metadata Manager, things work a little differently. Those submissions are processed immediately and don’t enter the queue, so you won’t receive a status email. Instead, you’ll see the result directly in the tool interface.
But, keep in mind, that no matter how you register your DOI, a submission log is still created. You can view logs and their status for past deposits at any time in the admin tool. Here’s how:
- Log in to the admin tool using your account credentials
- Click the Submissions tab, then the Administration sub-tab
- Click Search at the bottom of the screen, and you’ll see a list of all past deposits for your account, from newest to oldest.
- Click on the Submission ID number to the left of any deposit to access the Submission details, including the submission log for that deposit, or click on the file icon to view the file that was submitted.
Method 2: DOI resolver
A DOI isn’t just a string of characters, it’s a permanent link. You can test yours by turning it into a URL - just add https://doi.org/ in front of the DOI string and paste it into your browser.
What a registration success looks like: If your DOI is registered and has a valid URL assigned, it will resolve to the landing page currently associated with it, in this case: https://doi.org/10.5555/987654321
Alternatively, you can do this the “official” way: go to doi.org, scroll to the bottom of the page, find the “Try resolving a DOI name” field, enter your DOI, and hit submit. If you land on the publication page, you can be sure that your DOI is registered.
What a registration failure looks like: If a DOI has never been registered, the resolver simply won’t know where to go. Instead of your article, it will resolve to an error page on doi.org that says “DOI Not Found.” You can see what that failure looks like using this unregistered DOI.
This is a very simple way to check if a DOI is registered. If you see this error for one of your own records, it means the DOI has not yet been fully registered and should be addressed as soon as possible. The best next step is to register the DOI right away or contact our support team if you need help.
As a Crossref member, maintaining your DOI records is part of the responsibility of managing your prefix. On a side note, automated reports (called DOI error reports) from the DOI Foundation may flag these issues, but they are simply notifications and are sent back to the member organization that originally registered the DOI. Because of this, it’s important to review and correct any unregistered DOIs on your side when they appear.
Method 3: Crossref Metadata Search and Crossref API
The third way to confirm a DOI registration is through our own search interface at search.crossref.org. While the DOI resolver tells you if the link is functional, Crossref Metadata Search shows you the actual bibliographic record we have on file.
It is important to note that our system requires a small window to index new information. Even after a DOI is successfully registered and resolvable, there is a lag that can take up to 24 hours before it appears in this search tool.
As mentioned, if you search for a very recently registered DOI, it may not appear yet. However, a DOI registered in the past shows up clearly with its associated metadata.
Crossref API
If you want to dive deeper and see all the metadata associated with the registered DOI, you can use the Crossref REST API. Crossref provides open metadata in structured formats that are freely accessible. While the Crossref metadata search interface is geared toward humans reading results in a browser, the REST API is designed to return metadata in a structured format (JSON) that is suitable for both systems and people to inspect. We receive over 2 billion requests to our APIs each month, and the metadata is used by thousands of tools and systems in the scholarly community. For example, many library databases and reference managers retrieve metadata from Crossref’s API (find out more here) You can check your DOI’s “machine-readable” status by pasting this into your browser: https://api.crossref.org/works/[YOUR_DOI]. As an example, here is how I was able to retrieve the DOI in the below image: https://api.crossref.org/works/10.5555/987654321.
If you see a screen full of text (JSON format) containing your article’s bibliographic metadata, the DOI is fully registered and available to any system that queries Crossref’s data. If this is your first time viewing an API response, installing a JSON formatter extension in your browser will make the metadata much easier to read and navigate.
A final note on Google
Crossref does not have any formal relationship with Google. Search engines operate independently and whether a DOI appears in Google search results depends on many factors, so it may or may not show up immediately. In fact, search engines like Google aren’t primarily looking at metadata - they are looking at the data actually findable on your web pages. If a DOI is registered but never actually appears on your landing pages or within your article PDFs, Google may never discover it. And conversely, search engines can often index “ghost” DOIs that were assigned and are included on a PDF or a webpage but were never actually registered in our system (Note on Indexing: If you’re curious about how the other side of this process works, Google provides Inclusion Guidelines for Webmasters on how their crawlers index scholarly article webpages).
The next time you can’t find a DOI in a Google search, remember that search engines are not the registry itself. If you want a definitive answer, check the DOI in the registry itself - through submission logs, the DOI resolver, Crossref Metadata Search, or the REST API. These tools tell you exactly whether the DOI is registered and active. Once registered in Crossref, a DOI exists and resolves, whether or not a search engine has discovered it yet. And keep in mind that while Google might not use the Crossref API directly, other discovery tools do. This is why providing rich, accurate metadata is so critical: it ensures that you aren’t just registering a DOI but also making your research findable by the scholarly community.