An official website of the United States government

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS
A lock () or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Related Services
Provided By

URLs and Filenames

Creating URLs

A good URL is:

  • Short
  • Easy to remember
  • Easy to type
  • Well-organized

Even if you can’t control the whole URL, use the parts you can to make it better.

Every page on your site should have its own unique URL so users can bookmark or share it.

Tips for Writing URLs

  • Use hyphens to separate words (this is called kebab case).
  • Leave out small words like a, an, and the.
  • Use the base form of verbs (like /make-thing/ instead of /making-thing/).
  • Avoid extra or unnecessary words.

Domains

  • Domains should be short and user-friendly.
  • Don’t include deep department names unless they matter to users.
  • You don’t need “www.” at the beginning.
  • Use lowercase letters only.
  • Use abbreviations if users will understand them.

Example improvements:

Paths

Paths are the parts after the domain, like /content-guide/urls-and-filenames/.

  • Keep them short, but it’s okay if they’re longer than the domain.
  • Use hyphens to separate words.
  • Use lowercase only.
  • Avoid showing file types like .php or .html.
  • Make sure users can remove part of the path and still find useful content.

Example improvements:

  • /services/default/php/forms/longnamecreationservice/index.php?action=create
    → /make-long-names/

Keeping URLs Working

People bookmark and share links, so it’s important that URLs don’t break.

  • Try to keep original URLs working.
  • If you change a URL, set up a redirect from the old one to the new one.
  • Plan ahead to make URLs last a long time.

Creating Filenames

Good filenames are:

  • Lowercase
  • Use hyphens instead of spaces
  • Descriptive but not too long
  • Easy to understand

Examples:

  • Correct: summary-of-pay-gap-findings.pdf
  • Not the best way: smmrypgpfnds.pdf

If the file is tied to a date, include it in this format: YYYY-MM-DD.

Examples:

  • pay-gap-report-2024.pdf
  • newsletter-2025-08.pdf

Avoid special characters (like #, &, %) and don’t use spaces.

How to Show URLs and Filenames in Text

URLs

  • Always write URLs in lowercase, even if they start a sentence.
  • Paths (the part after the domain) are case-sensitive, so keep their original capitalization.

On Web Pages (Interactive)

  • Make URLs clickable links.
  • Don’t include the beginning part like https:// in the link text.

    Correct: Visit gsa.gov for more information.
    Not the best way: Visit https://gsa.gov for more information.

In Print or Non-Clickable Text

  • You can leave out http:// or https:// if both work.
  • If the URL is long or awkward, put it in angle brackets

This is especially helpful in emails, where the email program might not turn the URL into a link.

Filenames

  • Filenames are case-sensitive. Keep the original capitalization.
  • If a filename starts with a lowercase letter, don’t capitalize it—even at the beginning of a sentence.
  • You can also use angle brackets for filenames if needed:
    <summary-of-pay-gap-findings.pdf>

Parts of a URL

A full URL might look like this:
https://pages.bia.gov/content-guide/specific-words-and-phrases/#main

Here’s what each part means:

  1. Protocol – https:// (use this unless you must use http://)
  2. Domain – pages.bia.gov (the main site)
  3. Path – /content-guide/specific-words-and-phrases/ (the page location)
  4. Query string – ?q=18f+content+guide (optional, usually for searches)
  5. Fragment – #main (optional, jumps to a section on the page)

Avoid using query strings and ports in URLs when possible. Fragments are okay if they help users, but don’t rely on them to find content.

Screen reader users often skip from link to link, so link text should make sense on its own.

Don't Use:

  • Click here
  • Learn more
  • Here

Use instead:

  • See the IA Code of Conduct for more information.
  • Download the 2025 Pay Gap Report.

This also helps with search engine results and makes your content easier to scan.


Why We Do Not Use URL Shortening Services

Do not use third-party URL shortening services (like Bitly, TinyURL, or Ow.ly) on official websites or in digital communications.

While short links are convenient, they create serious security and trust issues for government websites.

1. It Hides the Official Government Link

The .gov at the end of our web addresses proves to visitors that they are on a real, official government website. When you use a service like Bitly, the .gov disappears. Visitors only see a link like bit.ly/3xY7z9. Because the official name is hidden, people cannot tell if the link is safe or fake.

2. It Breaks Good Security Habits

We teach the public to be careful online by hovering over links to see where they go before clicking. URL shorteners completely break this safety rule. A shortened link hides the final destination, forcing users to click blindly. This goes against federal cybersecurity training.

3. Scammers Use Them for Phishing

Cybercriminals frequently use URL shorteners to hide malicious links. If government agencies use these services regularly, it becomes much easier for scammers to trick people. A bad actor could create a fake shortened link that looks just like ours, but takes users to a dangerous website designed to steal their personal information.

4. They Rely on Outside Companies

When you use a commercial shortening service, you lose control of the link. If that company's website goes down or gets hacked, our links will stop working. This can cut the public off from critical information.

Additionally, these companies often track the people who click their links. Passing citizen web traffic through a private company can violate government privacy rules.

Best Practice Alternatives

Instead of using a shortener service, use these options to keep links clean and safe:

  • Use Clean URLs (Descriptive Slugs): Create short, easy-to-read web addresses using our own domain (for example, bia.gov/service-request instead of a long string of numbers).
  • Write Clear Link Text: Instead of pasting a long URL directly onto a page, attach the link to descriptive text (for example: Read the SCIP Service Request Guide).

Bureau of Indian Affairs (BIA) websites can link to websites outside of the federal government. These external links must support our mission and provide useful information to the public. We cannot link to websites that promote hate, bias, or discrimination. If we link to a private business website, we must treat all similar businesses equally to prevent unfair favoritism.

When users click a link to leave a secure .gov website, we must clearly show them that they are leaving our platform. We do this by using an external link icon or showing a quick disclaimer message. The BIA does not control or guarantee the privacy, security, or accuracy of any outside websites.

Compliance Resources

  • Links to Non-Federal Web Sites: Review the complete Department of the Interior (DOI) guidelines for choosing and managing external links.
  • Links to External Sites: Access the formal DOI privacy policy notices concerning third-party website tracking and data rules.
  • External Links: Learn federal web standards for displaying required notification icons and exit disclaimers

Additional Information

indianaffairs.gov

An official website of the U.S. Department of the Interior

Looking for U.S. government information and services?
Visit USA.gov