AI crawler robots.txt checker for GPTBot, ClaudeBot and more
Paste a robots.txt to see which AI crawlers it blocks: GPTBot, ClaudeBot, Google-Extended, PerplexityBot and more. Free, runs in your browser.
Bulk meta title and description length checker: paste many pages and see which titles and descriptions truncate, in pixels. Free, runs in your browser.
Runs entirely in your browser. Nothing you enter is uploaded, logged or stored.
Google does not publish a character limit for titles or meta descriptions. Its documentation says there is no limit on how long either can be, and that both are truncated in search results as needed to fit the device width. Width, not character count, is what gets cut, and it is usually a template, not a person, that produces the text. This checker measures a whole export at once so a template-wide problem is visible as a cluster of flagged rows.
Each line is split on the pipe character into URL, title and description. The title and the description are each drawn in Arial on a hidden canvas and their width is compared with a fixed budget.
| Device | Title font | Title budget | Description font | Description budget |
|---|---|---|---|---|
| Desktop | 20px Arial | 580px | 14px Arial | 990px |
| Mobile | 18px Arial | 470px | 14px Arial | 860px |
These budgets are the site’s working estimate of the visible width, shared with the SERP snippet preview so the two tools never disagree. They are not numbers Google publishes. A line with fewer than three fields is shown as a warning row reading “Expected URL | Title | Description” instead of being dropped.
Each row shows the URL, the title as it would display (cut at the last whole word with ” …” when it overflows), the measured width against the budget with a Fits or Truncated label, then the same for the description. Any row where either field truncates gets a tinted background. The summary above the table reads, for example, “5 row(s) checked, 1 would truncate on desktop”.
Switch to mobile before you trust a clean result. The mobile title budget is 110px narrower, so a title that fits on desktop can fail on mobile. If a row truncates only on mobile, decide whether the words that survive still carry the meaning; if they do, the cut may be acceptable.
The tool loads with five sample rows. On desktop, measured in Arial:
The summary reads 5 rows checked, 1 would truncate on desktop. Switch to mobile and the same row is still the only one flagged, but now twice over: the title measures about 660px against 470px and the description about 945px against 860px. Exact pixel values vary slightly with the fonts installed on your machine.
For a single page you are still writing, the Meta title and description checker with SERP preview shows the rendered result and is faster. Use this tool after a crawl or export, to audit what already shipped.
Google publishes none. Its documentation says there is no limit on how long a title or meta description can be, but both are truncated in results as needed to fit the device width. This tool checks against pixel budgets of 580 and 470 for titles and 990 and 860 for descriptions, on desktop and mobile, as a working estimate of that width.
Most truncation problems are not one bad title, they are a template that produces the same too-long pattern on every product page or every blog post. Checking a batch is the only way to see that pattern rather than one symptom of it.
Each string is drawn with the browser's canvas text API in Arial, 20px for desktop titles, 18px for mobile titles and 14px for descriptions, and the rendered width is read back. The same widths and fonts drive the single-page SERP snippet preview, so the two tools agree.
Yes. The pipe is the field separator, so a title like "Shoes | Brand" is read as the title "Shoes" with the rest pushed into the description. Replace pipes inside titles with another character before pasting, or check those rows in the single-page preview.
No. Google generates title links automatically from the page content and references to it on the web, and it sometimes uses page content instead of the meta description. Fitting the width only removes one reason for a rewrite.
Paste a robots.txt to see which AI crawlers it blocks: GPTBot, ClaudeBot, Google-Extended, PerplexityBot and more. Free, runs in your browser.
RSS feed validator: paste feed XML to check RSS 2.0 and Atom 1.0 for parse errors, required elements, dates, guids, enclosures and URLs. Runs in-browser.
humans.txt generator: build a humans.txt file with TEAM, THANKS and SITE sections from the humanstxt.org template. Free, runs in your browser.
Image lazy loading checker: paste HTML to test every img tag for width and height, lazy loading on the likely LCP image. Free, runs in your browser.