User-agentSpecifies which search engine bots the rules apply to.
SEO Performans is a CodeStup brand. All rights reserved.
Contact UsDefine which areas of your site search engine bots may crawl. Choose your directives and generate a valid robots.txt file instantly.
Set the bot, permissions, blocks and sitemap address.
Your file updates automatically as you enter details.
File is ready to use
A free tool that prepares the directives defining which areas of your site search engine bots may crawl, in valid robots.txt format.
Define allow and block paths for all bots or a specific User-agent; the tool removes duplicate rules and generates the text output instantly.
Select all crawlers or a custom User-agent value.
Manage crawlable paths with Allow and Disallow rules.
Download the robots.txt output with the Sitemap and optional directives.
A correct robots.txt file gives search engine bots clear guidance on which areas should and should not be crawled.
By restricting access to areas that don't need crawling, such as admin, internal search, filter parameters and cart, it helps bots focus on valuable pages.
Supports crawl budget usage by limiting the crawling of unnecessary URL areas.
Lets you define separate access directives for different search engine bots.
Sets clear crawl limits for admin, search and parameterized page paths.
Supports URL discovery by stating the sitemap address in the file.
Manage bot crawling behavior with clean, clear directives while keeping your site's important pages accessible.
Limit unnecessary URL areas, make room for the discovery of valuable pages and make technical SEO management more predictable.
Reduce bots wasting time on low-value and duplicate URLs.
Guide search engine crawlers to the sections you want to be visible.
Set clear limits for areas such as filters, cart, admin and internal search.
Help search engines discover your pages by declaring the sitemap address.
A valid file shouldn't just produce directives; it should also assess the scope and consistency of the rules and their effect on critical resources.
Checks bot groups and whether the rules apply to the relevant crawler.
Makes duplicates, scope problems and contradictions in Allow and Disallow paths visible.
Helps prevent accidentally blocking required CSS and JavaScript files.
Ensures the sitemap address and directory paths are written in the correct format.
From choosing your bot to a publishable file, the whole process runs instantly and in an orderly way based on the information you enter.
Decide whether the rules apply to all bots or a specific crawler.
Add allowed and blocked directory paths, one rule per line.
If needed, define Crawl-delay, Host and the full Sitemap address.
Download the generated robots.txt file and upload it to your website's root directory.
Every change you make in the form fields is automatically reflected in the file preview.
We handle every stage, from defining the rules to post-publication checks, in a consistent and verifiable flow.
By evaluating bot access together with site structure and technical SEO needs, we reduce the risk of accidentally blocking critical pages.
We determine which bots should access which parts of the site.
We review duplicate or contradictory Allow and Disallow patterns.
We convert the rules into a standards-compliant, clean and readable text structure.
We check the format of the User-agent, path, Host, Crawl-delay and Sitemap values.
We test that the file is reachable in the root directory and readable by search engines.
Manage common robots.txt directives, from bot targeting to sitemap declaration, in a single tidy output.
User-agentSpecifies which search engine bots the rules apply to.
DisallowDefines directories or URL patterns that bots should not crawl.
AllowSpecifies crawlable exception paths within a blocked area.
Crawl-delay / HostDefines the request interval and preferred host for bots that support them.
SitemapAdds the full address of the XML sitemap to the file so bots can discover it.
Move the generated directives to your live site in a few controlled steps and verify that search engines can access the file.
Downloading the file is not enough. It must be uploaded to the root directory under the correct name and its accessibility checked.
Make sure critical pages and rendering resources are not blocked by mistake.
Copy the generated text or download it to your device with the correct file name.
Publish the file so it is reachable at yourdomain.com/robots.txt.
Open the file in your browser and test the rules with the relevant search engine tools.
Update the directives as the site structure changes and monitor crawl behavior.
The examples below are starting points for common scenarios. Adapt the paths to your own site structure and test them before publishing.
User-agent: *
Allow: /
Sitemap: https://www.ornek.com/sitemap.xmlThe simplest file, enough if you do not want to restrict any section. The Sitemap line helps bots find your sitemap; you can prepare it with the XML Sitemap Generator.
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Sitemap: https://www.ornek.com/sitemap.xmlKeeps the admin area out of crawling but still allows access to admin-ajax.php, which some themes and plugins use on the front end.
User-agent: *
Disallow: /sepet
Disallow: /odeme
Disallow: /*?siralama=
Disallow: /*?filtre=
Sitemap: https://www.ornek.com/sitemap.xmlCart, checkout and sorting/filter parameter URLs can create duplicate URLs that add no value in search results. Change the paths to match your own URL structure and make sure you do not block category and product pages.
User-agent: *
Disallow: /Used to keep a test environment from being crawled. If this file is carried over to the live site, the whole site is blocked from crawling and organic visibility can suffer badly. Robots.txt is not a security measure; also protect staging with a password.
A single wrong line can stop important pages from being crawled. Check the points below before you publish.
Robots.txt does not remove a page from the index; a blocked URL can still appear in search results because of links. A page must be crawlable for its noindex directive to be read, so do not block a page with robots.txt if you want it removed from the index.
Blocking style and script directories can make it harder for search engines to render the page the way users see it. Keep the required resource paths out of your blocks or open them with Allow.
If the file that blocks the whole test site is copied to production, bots cannot crawl your site. Add a robots.txt step to your launch checklist and open the file in the browser after going live to verify it.
The file must be published in the root directory of the domain under the lowercase name robots.txt. A location such as /blog/robots.txt or a different name may not be read by bots as expected.
* stands for any sequence of characters and $ marks the end of the URL. For example, Disallow: /*.pdf$ targets only addresses ending in .pdf; a mistyped pattern can affect more or fewer URLs than you intended. Test patterns against sample URLs.
Correct rules also depend on your site architecture. For the full range of crawling and indexing issues, see our Technical SEO Optimization service, or use the SEO Site Analysis tool to see current problems.
Read the answers to the most common questions about the file's location, the effect of directives and correct usage.
A plain text file that tells search engine bots which areas of your site they may or may not crawl.
The file must be published in the root directory of the domain, for example at https://site.com/robots.txt.
No. Disallow blocks crawling; to remove a page from the index, use noindex or appropriate removal methods.
Use an asterisk (*) in the User-agent field to apply the rules to all compliant bots.
Yes. Allow can define a crawl exception for a specific subpath within a blocked directory.
It is not required, but stating the full sitemap URL makes it easier for search engines to discover the file.
Googlebot does not support the Crawl-delay directive. Google crawl rate settings are managed through Search Console.
Usually not. Search engines need access to the required resources to render the page correctly.
Yes. You can create your directives for free, copy them and download them as robots.txt.
URL paths can be case-sensitive depending on the server setup; paths must be written exactly like the real URL structure.
Robots.txt sits in the root directory of your domain. You can check whether the file exists by opening yourdomain.com/robots.txt in a browser. Each subdomain needs its own file.
Disallow stops a bot from crawling a page; noindex is a directive telling search engines not to show the page in results, and the bot must be able to read the page to see it. If you block a page with Disallow, the noindex directive cannot be seen, and the blocked URL can still appear in the index because of links.
In Google Search Console, the reports related to your robots.txt file show how Google reads it and any errors. You can also use the URL inspection tool to check whether a specific address is blocked. Because the interface can change over time, see the Search Console help pages for the current menus.
Support your robots.txt setup with technical SEO, content and structured data work to build a more holistic optimization process.
Create markup that helps search engines understand your content more accurately.
View the serviceComprehensively fix crawling, indexing, speed and site architecture problems.
View the serviceImprove your pages according to user intent and organic visibility goals.
View the serviceSee technical risks, opportunities and priority actions in measurable reports.
View the serviceLet's fix faulty blocking rules, protect your crawl resources and make sure search engine bots access your site correctly.