Tools I built.
Free forever.
I build tools constantly — it's how I think through problems. Every one of these started as something I needed for my own work. If I'm going to build it anyway, I may as well share it. No sign-up, no paywall, no email capture. Just open and use.
SEO Meta Analyzer
Enter any URL and instantly get a breakdown of your title tag, meta description, OG tags, canonical, robots directives, and structured data. No Chrome extension needed.
Keyword Density Checker
Paste any text and see keyword frequency, density percentage, and over-optimisation warnings. Useful for checking your own content before you publish — and checking competitors' pages too.
Schema Markup Validator
Paste your JSON-LD schema and instantly validate against Google's rich result types. Identifies errors, warnings, and missing recommended properties that testing tools miss.
Robots.txt Tester
Test whether a given URL is allowed or blocked by a site's robots.txt — for any user-agent. Useful when you're debugging indexation issues and need to quickly rule out robots.txt as the cause.
AI Prompt Generator
Describe what you want to do and get a structured, well-formed prompt ready to use with ChatGPT, Claude, Gemini, or any LLM. Includes role-setting, context, format instructions, and output constraints.
AI Readability Scorer
Goes beyond Flesch-Kincaid. Uses an AI layer to assess sentence variety, passive voice overuse, jargon density, and whether your text actually sounds human — not just readable by a metric.
Content Brief Generator
Enter a keyword and target URL. Get a content brief with suggested headings, semantic keywords, word count benchmark, and questions to answer — built from real SERP analysis, not templates.
JSON Schema Generator
Paste any JSON object and instantly generate a JSON Schema draft. Infers types, detects optional fields, and produces clean schema ready to use in API validation, form generation, or LLM output structuring.
API Response Diff Tool
Compare two API responses side-by-side, with deep diff highlighting of structural changes, type mismatches, and added or removed fields. Useful for catching breaking changes during migrations.
Why is this all free?
Genuinely asked. Here's the honest answer. I build tools to solve my own problems. The ones on this page all started as scripts, snippets, or quick hacks in my own workflow. At some point they became polished enough that other people might find them useful.
Making them public costs me almost nothing. And they tend to introduce me to people who find something useful here, read a blog post, and eventually want to work together. That's the entire business logic — transparent and unsexy. No growth hacking, no email funnel. Just useful things attracting good people.
- //No account needed. I hate being forced to sign up for something before I can evaluate whether it's worth my time. I won't do that to you.
- //No usage limits. Run the SEO meta analyzer 500 times today if you need to. The tools are there to be used.
- //No data stored. What you paste in stays in your browser session. I'm not building a training dataset from your content.
- //Open to feedback. If a tool is broken, wrong, or could be better — tell me. I actively maintain these.
Missing something?
If there's a tool you wish existed — something that would genuinely make your SEO, dev, or AI workflow easier — I'd love to hear it. I build things that solve real problems, and you might just have the right one.
Email hello@yourdomain.com with your idea.
FAQs
Are these tools really free?
Yes. There is no paywall or account wall for the utilities on this hub. They exist to be used in real workflows—meta checks, robots debugging, readability passes, and quick structured-data validation.
Do you store what I paste or type?
The hub is built so inputs are handled for the request and not retained as a product feature. Treat anything sensitive as you would on any third-party site: avoid secrets, credentials, or personal data in fields.
Can I use results for client work?
Yes. Outputs are meant to support audits, QA, and shipping. Always corroborate high-stakes decisions (for example, indexation and rendering) with Search Console, server logs, and your own policies.
Will you add a tool for X?
Maybe. The best requests include the workflow pain, an example input/output, and how you would judge “done.” I prioritize tools that reduce repeated manual work for many readers.
Something looks wrong—how do I report it?
Send a short email with the tool name, what you entered (redacted), and what you expected versus what you saw. Screenshots help. I fix real breakage and misleading UX as time allows.