Generators / GEN-01 Runs in your browser
Custom Robots.txt Generator for Blogger: Free Online Blogspot Builder
A robots.txt generator for Blogger and Blogspot: pick what crawlers should leave alone, point them at your sitemap, and copy a finished file straight into Blogger's Search preferences. Nothing is uploaded — the file is assembled in this page.
Builder GEN-01 Output updates as you type
With or without https:// — either is fine.
Changes which paths are offered below.
Google ignores this directive. Some smaller crawlers honour it.
What this custom robots.txt generator for Blogger actually writes
A custom robots.txt generator for blogger blogs has one job, and it is worth being precise about what that job is. A robots.txt file is a plain-text list of instructions sitting at the root of your domain. Every well-behaved crawler asks for it before it asks for anything else, which makes it the single most frequently read file on any blog. It is also unforgiving: it has no syntax checker, no error message, and no way of telling you that a rule you were counting on has been quietly ignored for eight months.
This builder writes three kinds of line and nothing else. A User-agent line naming
who the rules apply to, one Disallow line per path you asked to protect, and a
Sitemap line pointing at your URL list. That last one is the only line that adds
reach rather than removing it, and it is the one most hand-written files leave out.
The defaults are deliberately cautious. On Blogger the tool blocks the internal search results and the mobile duplicate parameter, because those genuinely produce endless near-identical URLs. It leaves your label and archive pages open, since on most blogs those are the internal links holding older posts together. Any custom robots.txt generator for blogger sites that blocks those by default is costing you crawl coverage you probably wanted.
Free, and what that word covers here
There is no account, no quota and no watermark on the output. It is free because the whole tool is a few lines of JavaScript running in the tab you have open, so there is no cost per use to recover, and free with no signup is easier to build than a metered tier would be. Type a domain, read the file online, close the tab. Nothing was transmitted, because there is nothing on the other end to transmit to.
That also sets the honest limit. A custom robots txt generator for blogger blogs can only assemble text; it cannot see your blog. It does not know whether you have 40 posts or 4,000, whether your labels are load-bearing, or whether some plugin is already serving a competing file. Those judgements stay with you, which is why the sections below explain what each rule does rather than just handing you a file.
Using the online output on a Blogspot blog
Working online has one consequence worth knowing about here. Blogger does not let you upload a
file to the domain root, so the platform reads a copy you paste into its settings instead. Open Settings, find the Crawlers and indexing block, enable the
custom robots.txt switch, and paste the whole block including the sitemap line. Save, then open
yourblog.blogspot.com/robots.txt in a fresh tab.
That last step is not optional. Blogger will happily accept a file, serve its own default instead, and never mention the discrepancy. If the live file does not match what you pasted, the switch did not save. This is the most common failure and it is invisible unless you look.
A Blogspot blog on a custom domain behaves the same way, but check the file on the domain you actually rank on. The robots.txt at the blogspot.com address governs the blogspot.com address, and the two are separate as far as crawlers are concerned.
The four rules worth understanding before you copy anything
A disallow is not a removal. Blocking a URL prevents crawling. If other pages link to it, that URL can still show up in results as a bare link with no description. To remove a page, leave it crawlable and add a noindex tag to the page itself, so Google can read the instruction it is meant to obey.
Trailing slashes decide the match. Disallow: /search matches every
path beginning with those characters. Disallow: /search/ matches only the folder. On
Blogger the search URLs carry a query string rather than a slash, so the slashed form protects
nothing at all. The output here uses the form that matches real Blogger URLs.
Blocking a resource can break rendering. Disallowing your CSS or image directories stops Google seeing the page the way a visitor does, which affects how it judges the layout. Block content you do not want crawled, not the files that draw it.
Order does not create precedence, specificity does. With two conflicting rules,
the longer, more specific path wins, regardless of which line comes first. That is why an
Allow line for one file can safely sit under a broad Disallow for its
folder.
What to check a week later
Open Search Console and look at the page indexing report. A rule that did what you intended shows up as a slow decline in "Indexed, though blocked by robots.txt" or in crawled-but-not-indexed URLs. A rule that overreached shows up as valid pages dropping out, and that is the pattern to react to quickly. This is the only feedback loop a custom robots.txt generator for blogger blogs cannot give you, because it runs before the crawler has seen anything.
The URL inspection tool answers the specific question directly: paste any address and it will tell you whether the live file currently permits crawling. When a page you care about is affected, that report is more reliable than re-reading your own rules and hoping.
Rerun this free custom robots txt generator for blogger and Blogspot blogs whenever the shape of your blog changes — a new section, a shop, a members area. A file written for a 30-post blog is rarely still the right file two years later, and the version in your settings is the one being obeyed, not the one you remember writing.
Questions people ask
Where do I paste the file once it is generated?
On Blogger, open Settings, scroll to the Crawlers and indexing block, switch on "Enable custom robots.txt" and paste the whole file into the box that appears. Save, then load yourdomain.com/robots.txt in a new tab to confirm the live file matches what you pasted.
On WordPress the file usually lives in the site root. If an SEO plugin manages it, edit it there instead of uploading a second copy, otherwise the plugin will keep overwriting your file.
Does blocking a page in robots.txt remove it from Google?
No, and this is the mistake that costs people the most traffic. A disallow rule stops crawling, not indexing. A URL that other sites link to can still appear in results, just with no snippet, because Google was never allowed to read the page and see the noindex.
If your goal is removal, leave the URL crawlable and put a noindex robots meta tag on the page itself. Block in robots.txt only what you want left alone entirely, such as internal search result pages.
Should I block the label or archive pages on a Blogger blog?
It depends on how many posts you have. On a blog with a few dozen posts the label pages are often the only route Google has into older content, so blocking them removes the internal links that keep those posts discoverable.
On a large blog where every post already sits in a sitemap and gets internal links from newer posts, the label pages mostly duplicate content, and keeping them out of the crawl is defensible. The default in this builder leaves them open, because that is the safer of the two mistakes.
Why does the sitemap line matter so much?
The Sitemap directive is the one line in robots.txt that adds something rather than taking it away. It tells every crawler where your full URL list lives without you submitting anything anywhere.
Blogger serves two useful ones: /sitemap.xml covers posts, and /sitemap-pages.xml covers static pages. Listing both is the reason a lot of Blogger pages that were never in Search Console still get found.
Is one wrong character really enough to break the file?
A malformed line is ignored rather than fatal, but ignored is not harmless. "Disallow: /search" blocks anything starting with /search; "Disallow: /search/" blocks only the folder. On Blogger the search URLs have no trailing slash, so the second version silently does nothing.
The generator writes the form that matches Blogger URLs, which is why checking the live file after you paste it is worth the ten seconds it takes.
Is anything I type sent anywhere?
No. The tool runs in this page and there is no server behind it, so nothing you type is transmitted, logged or stored. Disconnect from the network, reload from cache, and it still works.