Skip to main content

Guides

Robots.txt, explained for business owners

A robots.txt file is a plain text file that sits at the root of your domain and tells search engine crawlers which parts of your site they are allowed to request. For a business owner, it matters because one wrong line in that file can quietly keep Google from reading your entire website, and nothing on the page itself will warn you.

Understanding robots txt for business owners does not require you to write code. It requires knowing what the file controls, what it cannot control, and the handful of mistakes that turn a harmless housekeeping file into a traffic leak. This guide walks through all three.

What robots.txt actually controls

The file speaks to automated crawlers, also called bots or user agents. When a crawler arrives at your domain, it checks yourdomain.com/robots.txt first, reads the rules, and decides which URLs it is permitted to fetch. Think of it as a posted notice at the front door, not a lock. Well behaved crawlers like Googlebot obey it. Malicious scrapers often ignore it entirely, which is why robots.txt is a crawl management tool and never a security tool.

Here is the part most people get backwards. The file controls crawling, not indexing. If you Disallow a page, Google will not fetch it, but it can still list that URL in search results when other sites link to it, because the crawler never opens the page to read instructions telling it to stay out. To keep a page out of the index, you let it be crawled and add a noindex tag. To stop a crawler from wasting effort on junk URLs, you Disallow it. Those are two different jobs, and confusing them is where most trouble starts.

In plain terms, robots.txt is good at:

  • Keeping crawlers out of sections that waste their time, like internal search results, filtered product lists, or cart and checkout pages.
  • Pointing crawlers to your sitemap so they discover your real pages faster.
  • Reducing load from aggressive bots hitting low value URLs.
  • It is the wrong tool for:

  • Hiding private or sensitive pages. A Disallow line is public, and it actually advertises the exact path you are trying to hide.
  • Removing a page from Google. That needs a noindex tag or password protection, not a crawl block.
  • The anatomy of the file

    Every robots.txt file is built from a few simple directives. You do not need to memorize them, but recognizing them makes the file far less intimidating when a developer shows it to you.

    User-agent

    This names the crawler a rule block applies to. User-agent: * means the rules apply to every crawler. You can also target a specific one, such as Googlebot, when you want different rules for different bots.

    Disallow and Allow

    Disallow lists a path crawlers should not request. Disallow: /cart/ blocks everything under the cart folder. Allow carves an exception back out, letting a crawler into one path inside an otherwise blocked folder. A blank Disallow line means nothing is blocked at all. Paths are case sensitive and match from the start of the URL, so small typos have real consequences.

    Sitemap

    A Sitemap line gives crawlers the full web address of your XML sitemap. It is optional, but worth including, because it hands search engines a clean map of the pages you actually want found rather than making them guess.

    The mistakes that cost businesses traffic

    Most robots.txt damage comes from a small set of errors, and the worst of them stay invisible until organic traffic drops weeks later.

  • The staging block that shipped live. Development sites usually carry Disallow: / to keep them out of search. If that single line survives the move to production, it tells every crawler to ignore your entire site.
  • Blocking CSS and JavaScript. Google renders pages the way a browser does. If you block the files that control layout and behavior, it may see a broken version of your site and judge it on that.
  • Using Disallow to hide data. A disallowed path is published in plain text for anyone to read, and the page can still be indexed through inbound links anyway.
  • Assuming a change is instant. Crawlers cache robots.txt, so edits take time to register. Removing a block does not trigger a full re-crawl of your site that afternoon.
  • Why the file matters more as your site grows

    On a small brochure site, crawlers can read every page without strain, so robots.txt does little either way. The file earns its keep as a site grows. Large catalogs, event calendars, and filtered listing pages can generate countless thin, near duplicate URLs that pull crawlers away from the pages that actually sell. A tight Disallow rule steers crawlers toward the content that matters and away from the combinatorial sprawl. This is the same problem that drives index bloat, and the two are worth reading together.

    How to check your robots.txt

    You can inspect your own file in under a minute, with no tools and no login.

  • Type yourdomain.com/robots.txt into any browser. Whatever appears there is exactly what crawlers see.
  • Scan for a lone Disallow: / under User-agent: *. That single line blocks everything and should almost never be on a live site.
  • Confirm your sitemap is listed and that its address loads.
  • Use the robots.txt report inside Google Search Console to see how Google last read the file and whether it flagged any errors.
  • If the file looks wrong, or pages are missing from search and you are not sure why, a crawl block is one of the first things to rule out. Our guide to indexation troubleshooting walks through the rest of that chain.

    How we handle it

    Ninetyfifth Marketing performs SEO only on sites we build, which means the robots.txt file is something we write and own from the first day rather than inherit and guess at. We keep the crawl rules deliberately narrow: block the URLs that waste crawl effort, expose everything meant to be found, and reach for a noindex tag when a page needs to stay out of the index instead of just out of sight. You can see how that fits into a full engagement on the SEO services page, and the published terms on the pricing page.

    Questions

    Does robots.txt keep a page out of Google?

    Not reliably. robots.txt stops crawlers from fetching a page, but a blocked URL can still appear in results if other sites link to it. To remove a page from the index, allow it to be crawled and add a noindex tag, or protect it behind a login.

    Where is my robots.txt file?

    It always lives at the root of your domain, at yourdomain.com/robots.txt. If nothing loads there, you simply do not have one. That is fine for many small sites, because crawlers then assume everything is open to crawl.

    Do I even need a robots.txt file?

    A small site with nothing to keep crawlers out of can run without one. You want one once you have sections worth blocking, like internal search or faceted filters, or when you want to point crawlers at your sitemap.

    Why does robots txt for business owners get treated as a developer only topic?

    Because it lives in code and looks cryptic. In practice the risk is a business risk, not a technical one. A single stray line can hide your whole site from search, so knowing how to read the file protects revenue even when a developer is the one editing it.

    Related

    By Marco Consuelo, Ninetyfifth Marketing. Last reviewed .

    Downtown Phoenix, by appointment only. contact@ninetyfifthmktg.com

    Ninetyfifth Marketing

    Let's talk.

    Take 90 seconds to tell us about your business. If we're a fit, we'll reach out to set up a call.

    Ninetyfifth Marketing
    Ninetyfifth Marketing
    Live chat · Replies in minutes
    Ask a question and someone from our team will jump in.