Free Utility Tools

Generators write text. You publish it.

Meta tags, robots.txt, an XML sitemap, UTM parameters, a SERP preview, and URL encoding all stay in the browser until you copy them. Read the canonical and robots values before you paste a meta snippet into a template. A generated sitemap contains only the URLs you pasted. Keep a single file within the sitemap protocol limits of 50,000 URLs and 50 MB uncompressed. If the list is longer, split it. Priority and changefreq are fields you store in the file. They are not ranking instructions.

Check the output on the live URL after you deploy, not only in the generator. Preview the title and description, then fetch the URL with the title and meta checkers. Test a new robots.txt in the robots.txt tester before you rely on a Disallow. Validate a generated sitemap with the XML sitemap validator. The diff checker compares two URLs, or a URL against text you paste. It does not keep a history, so save your own baseline if you want a later comparison. The UTM builder does not create the campaign in Analytics. It only assembles the query string.

Encoding is the small one people skip. Percent-encoding is for characters in a URL or a query value. It is not HTML escaping. Encode the value, not the https:// or the ? and & that already structure the URL. If you encode a string that already contains %20, the percent sign itself gets encoded and the link breaks. Decode once and see whether a % is still there before you encode again.

The SERP previewer is a pixel mock, not the snippet in the index. Google rewrites titles and builds snippets from the body when it wants to. Use the preview to avoid shipping a title that is already cut off in the mock, then check the live tags with the title and meta checkers after deploy. A generator that never gets fetched against the live URL is how a canonical from staging stays in production.