Browser-local website tools: choose the right one
Choose by result: Website Audit checks public HTML, AI Crawler Check reads robots rules, Sitemap Generator converts a URL list, JSON Formatter checks syntax, Word Counter measures text and QR Generator makes a static URL image.
Updated 7 October 2026. Choose the tool that can show the evidence you need.
Compare the options
| Task | Use | What it does not do |
|---|---|---|
| Review several public pages | Website Audit | It does not predict rankings or verify indexing |
| Check named crawler rules | AI Crawler Check | It does not prove visits, citations or firewall access |
| Turn a URL list into XML | Sitemap Generator | It does not crawl or choose canonical URLs |
| Inspect pasted JSON | JSON Formatter | It does not validate an API schema or send the data |
| Check text length | Word Counter | It does not judge writing quality or ranking potential |
| Make a static URL code | QR Code Generator | It does not provide redirects, analytics or subscriptions |
Direct answer
Choose by result: Website Audit checks public HTML, AI Crawler Check reads robots rules, Sitemap Generator converts a URL list, JSON Formatter checks syntax, Word Counter measures text and QR Generator makes a static URL image.
Start with the input
A website audit reads public URLs. The crawler checker reads robots.txt rules for an exact page. The sitemap generator accepts a list that you provide. JSON and word tools work on text you paste, while the QR tool encodes a URL in the browser. The input determines what the result can prove.
Local processing has a narrow meaning
Browser-local means the selected text, list, or generated image is processed in the browser for that action. The page still makes normal website requests and anonymous analytics requests. Local processing does not remove confidential data or decide whether a URL is safe to publish.
When an online AI chat is a poor fit
A general chat assistant can explain concepts and draft a checklist, but it may not fetch the current robots.txt file, reproduce an HTML response or validate every URL in your list. A purpose-built tool can show the input and output for the narrow check it actually performs. Use both when each answers a different question.
Keep human review in the loop
Every tool reports a bounded result. Open the page, compare the output with the source and record the decision. A valid JSON document can still have the wrong fields. A well-formed sitemap can still contain URLs you should not publish. A permitted crawler can still be blocked by a firewall.
Use the tools as a short chain
A common sequence is: audit a sample of pages, check crawler access for the important path, build or review the sitemap, validate any JSON-LD, and use a word count when a brief has a limit. The order is flexible. The evidence from one step should inform the next step.
Limits are part of the product
The tools do not claim an access score, ranking forecast, AI citation guarantee or security certification. They are small utilities for public checks and local transformations. A larger audit may need Search Console, analytics, logs, source code or a specialist review.
Choose a page, not a keyword list
A useful resource page sends a reader to one relevant tool with a clear expectation. Avoid creating a page for every synonym of the same task. Keep one canonical explanation and add a related link when the next action is genuinely different.
International use
The website tools are available to users in the US and Europe and do not depend on a particular industry's data. The page language is English, so teams can adapt the checklists to their own market, language and privacy requirements.
A practical handoff
When a tool result is going to another person, include the input, the date, the output and the next decision. For an audit, that might be the starting URL, pages checked, observed issue and owner. For a crawler check, include the exact user agent and path. For a sitemap, include the reviewed URL source and the published file address.
Do not send a green label without the evidence behind it. A recipient may need to know that the audit sampled ten pages, that the crawler check only read robots.txt or that the sitemap generator did not crawl the site. Those details prevent a small utility from being treated as a wider guarantee.
A local tool is often a good first step because it reduces unnecessary data sharing and gives a deterministic result for a narrow task. It is not a complete privacy or security review. Keep the same human review step you would use after a chat answer, especially when a public page contains customer information, a legal claim or an irreversible deployment change.
When to choose a different tool
Use Search Console when you need indexing and search performance evidence, server logs when you need request evidence, a browser test when you need visual interaction evidence and a schema validator when you need a formal structured-data check. The free website tools are deliberately small. Choosing the narrowest tool that can answer the question keeps the report honest and the next action clear.
Keep the result reproducible
A short URL, a date and the tool name are enough for another person to repeat many public checks. Save a copy of a generated sitemap or a redacted JSON sample when the output affects a release. For text and images, keep the source in the team's normal system rather than relying on a browser download as the only record. A tool is useful when the next person can understand what it saw and what it did not see.
Avoid tool-shaped content
A page should exist because a reader has a distinct question, not because a tool has another synonym. If two resources produce the same decision and link to the same action, merge them. A smaller set of clear pages gives internal links more meaning and gives the measurement plan fewer ambiguous events to interpret.
A useful stop condition
Stop using a tool when the question it can answer has been answered and the output is recorded. More clicks do not make a narrow check more certain. Move to the next evidence source or ask a specialist when the tool's stated limit is reached.
Questions
Do these tools require an account?
The linked public tools are available without an account or email. Saving an audited site to a dashboard is a separate action.
Are files and text uploaded for local tools?
The browser-local transformations do not upload the selected content for processing. Normal page and anonymous analytics requests still occur.
Can a tool replace an SEO specialist?
No. It supplies bounded evidence for a small task. Interpretation, prioritisation and wider technical checks still need human judgement.