Skip to main content

Search and citation guide

There is one box in the header and it answers two kinds of question. Type a citation and it goes straight there; type anything else and it searches the text. You do not have to tell it which you meant — it reads what you wrote.

Both halves can also ask about the past. A citation can name a release point and land on the provision as it stood then, and a search can name one too — though only through the URL for now, and with a limit worth reading first. See searching at a release point.

Going to a citation

Each of these forms works, and each is followed by the official identifier it resolves to. Select any example to try it.

Two things that will catch you out

Add a release point to any of these — ?release=119-99 or ?date=07/12/2026 — and you land on the provision as it stood then.

Searching the text

By default a search matches the words you typed, and every one of them has to appear. The operators below are how you loosen that deliberately — including asking for near-spellings when you are not sure how a word is written.

Strict by default

Searching for compare finds provisions containing the word compare — not compact or company. This site used to return all three, because it ran every search with a two-character-edit tolerance nobody asked for. In a body of law a different word is a different rule, so that tolerance is now something you request.

If you are unsure of a spelling, add ~1 to the word: conservation~1 finds provisions containing anything within one character edit of it.

Operators

What is searched

The text of sections and the headings above them — chapters, subchapters, parts. A search covers the law currently in force unless you name a release point, which is done from the URL and is described in the next section.

Operators combine, and grouping works the way it does in arithmetic: (forest | grassland) -timber .

Searching at a release point

You can search the Code as it stood at a past release point. This is the one place on the site where the answer is not yet complete, so both halves are set out below: how to ask, and what comes back.

The search box has no control for this yet, so you add the release point to the results URL. There are two parameters, the same two a citation URL takes: the label of a release point, or a date.

Not the whole picture yet

The search index currently holds the text in force — one document per section, as it reads today. A search at a release point therefore finds the provisions whose current text was already in force then, and it misses text that has since been replaced: a section amended in 2024 cannot be searched as it read in 2019, even though the reader will happily show you that version.

What is missing is the index, not the feature. Every superseded version is in the database and the indexer knows how to write them — python -m ingest.reindex_search --all-versions builds them, roughly 490,000 documents against the 66,000 the default search reads. It has not been run against this deployment, and until it is, a point-in-time search is answering from current text alone.

You can always tell which you got: the results page says either “In the text as of release point …” or “Searching the law currently in force.”

Asking what cites a provision

Prefix a citation with citescites 26 usc 501 — and the search looks for provisions that refer to it. This is a keyword search over the citation's text for now, not a real cross-reference index, and the results page says so rather than letting the answer pass for the finished thing.