Loading
User-agent: * Disallow: /admin Disallow: /api Sitemap: https://example.com/sitemap.xml
robots.txt controls crawling, not indexing — a disallowed page can still appear in results if something links to it, and blocking a page you also want de-indexed prevents the crawler from seeing the noindex that would remove it. It is also public: anyone can read yours, so it is not a way to hide anything. Test the result in Search Console before deploying it, because a wrong rule here can remove a site from search entirely.
Produces a robots.txt from the paths you enter, leaving out any rule you left empty.
Everything happens in the page — nothing is uploaded, nothing is stored, and no address is required.
Replace the example with your own text. The counts update as you type, and the panel shows the result rather than a score.
The defaults are examples chosen to make the shape obvious. They are not recommendations.
robots.txt controls crawling, not indexing — a disallowed page can still appear in results if something links to it, and blocking a page you also want de-indexed prevents the crawler from seeing the noindex that would remove it. It is also public: anyone can read yours, so it is not a way to hide anything. Test the result in Search Console before deploying it, because a wrong rule here can remove a site from search entirely.
The ranges are conventions rather than rules, and being outside one is not automatically wrong.
What matters is whether the meaning survives truncation — check that the opening still says what the page is about, because that part always survives.
No. It runs in the page, nothing is sent anywhere, and there is no follow-up.
They are character counts. Truncation happens on rendered pixel width, so treat them as an approximation.
No. It works on the text you paste, and makes no requests.
Half an hour on your own figures, and an honest answer about the parts Treepie does not improve.