Free SEO tools are small web utilities that check or generate one specific part of a website, such as a title tag, a redirect, a robots.txt file or a schema block. The tools on this site cover on-page, technical, schema, content, speed, local, domain and analytics tasks, and none of them needs paid data.
Search visibility is hard to earn: Ahrefs found that 96.55% of the roughly 14 billion pages in its index get zero organic traffic from Google. Getting the basics of each page right is the cheapest way to avoid being one of them.
Why I built these tools
I am Saad Raza, a Holistic SEO consultant in Karachi. In day to day work I keep reaching for the same small checks: is this redirect a chain, does this page have one H1, can GPTBot crawl this URL, does the sitemap contain a noindex page. Most online tools for those jobs are buried under adverts, ask for an email address, or bolt a paid upsell onto a simple answer.
So I built my own set. Each tool does one job, explains the result in plain language and tells you what to fix next. They are meant for business owners, writers, developers and marketers who want a fast answer without learning a dashboard. They are also what I use myself before I start a deeper audit.
The collections and what each one is for
The tools are grouped into collections. Start with the one that matches the question you have today.
On-page SEO tools
These check and write page-level elements: titles, meta descriptions, headings, canonical and robots tags, Open Graph data and URL slugs. If you are asking “is this page set up properly?”, begin with the free on-page SEO tools.
Technical SEO tools
These cover crawlability and indexability: status codes and redirects, HTTP headers, robots.txt, sitemaps, hreflang, broken links and AI crawler access. If you are asking “can search engines reach and index this?”, use the free technical SEO tools.
Schema markup generators
This collection produces valid JSON-LD for common types and explains how to add it to a site, how to test it and which rich results each type can support today. Open the schema markup generator collection when you want structured data without hand-writing code.
Content and writing tools
Word and character counts, readability scoring, keyword density and case conversion live here, along with a plain explanation of what those numbers mean for SEO and what they do not. See the content and writing tools.
Image and website speed tools
Image compression, WebP conversion, resizing, page weight and Core Web Vitals checks sit together because images are so often the heaviest part of a page. Start with the image and website speed tools.
Local SEO tools
Google review links and QR codes, WhatsApp click-to-chat links and a NAP consistency check are aimed at businesses that serve customers in a specific area. Find them in the local SEO tools collection.
Domain and website lookup tools
DNS records, SSL certificate details and registration data through RDAP, with notes on what each record means for SEO, email and trust. Use the domain and website lookup tools when something looks wrong at the infrastructure level.
Marketing and analytics tools
A UTM link builder for GA4 and an SEO ROI calculator help you measure where traffic comes from and what it might be worth. They live in the marketing and analytics tools collection.
Browser-only tools and server-checked tools
Every tool is one of two kinds, and the difference matters for both privacy and accuracy.
Browser-only tools
These run entirely in your browser. The text, images or settings you enter are processed on your own device and are not uploaded to my server. Generators, counters, converters and previews work this way. The image compressor is the clearest example: your files never leave your device.
Server-checked tools
Some jobs cannot be done from inside a browser. A page on another website will not normally let your browser read it, and redirects, headers and DNS records are not visible to page scripts. For those, you enter a URL or domain, and my server fetches the public page or record and reports back. Only public information is requested, and the URL you type has to reach my server for the check to work.
Server-checked tools see what the server receives when it asks for the page. That is the HTML the site returns, not content that a visitor’s browser adds afterwards with JavaScript. If a page builds its main content on the client, the tool may report a thin page that people actually see in full. Some sites also block automated requests, and in that case the tool can only tell you it was refused. A refusal is a result worth noting, but it does not prove the page is broken.
Privacy and rate limits
For browser-only tools, privacy is simple: nothing you paste or drop in is sent to me. For server-checked tools, treat the URL as something you are sending to a service. Do not enter private addresses, staging links containing secrets, or anything you would not want fetched.
Server tools do real work for each request, because they fetch a live page or record. To keep them available for everyone, they may limit how often a visitor can run them. If you see a message that you have hit a limit, wait a little and try again, and batch your checks by page type rather than running the same URL repeatedly. A check against a large site is better done as a sample of key templates than as every URL.
Why there are no keyword volume, rank or backlink tools
You will not find a keyword search volume tool, a rank tracker or a backlink checker here. That is deliberate. Those numbers come from large paid datasets built from clickstream panels, crawlers and scraped result pages. Without that data, any tool that showed you a volume, a position or a link count would be inventing it, and a confident but made-up number is worse than none because people make decisions from it.
For those jobs, use Google Search Console for your own impressions, clicks and average positions, and use a reputable paid platform when you need market-wide keyword or link data. I would rather offer fewer tools that tell the truth than many that look impressive.
A simple workflow across the collections
You do not need to run every tool. A sensible order for a single important page looks like this.
- Run the on-page checker to see the basics: title, description, headings, canonical and robots tags.
- Check the redirect path and response headers to confirm the page returns a clean status and is not blocked by an X-Robots-Tag directive.
- Test the page against robots.txt for the crawlers you care about, including AI crawlers.
- Look at page size and Core Web Vitals, and compress the heaviest images.
- Add or fix structured data, then re-check the page.
- Build UTM links for any campaign that points to the page so you can read the traffic in GA4 later.
Take the first two steps from the on-page collection and the technical collection and you already have a sound picture of whether a page can be found and understood.
When a free tool is not enough
A tool answers a narrow question about one URL. It cannot weigh your competitors, judge whether your content deserves to rank, spot patterns across ten thousand pages or tell you which fix is worth doing first. Results can also be misread: a green tick on a title length does not mean the title is good.
If you have checked the basics and still see problems you cannot explain, such as pages dropping out of the index, traffic falling after a migration or a site that is slow in ways the numbers do not capture, a professional audit finds the cause faster than more tools do. You can read how that has played out in my case studies.
Questions about the free SEO tools
Are these SEO tools really free?
Yes. You can use them without paying. I can offer that because I only built tools that work without paid data.
Which collection should I start with?
Start with on-page tools if you are checking a single page, and technical tools if you suspect a page is not being crawled or indexed. Both collections give you a quick read of the fundamentals.
Do the tools store or upload what I enter?
Browser-only tools process your input on your own device. Server-checked tools must send the URL or domain you enter to my server so it can fetch the public page or record.
Why does a tool show a different result from what I see in my browser?
Server-checked tools read the HTML the server returns. If your site adds content with JavaScript, or blocks automated requests, the tool will not see exactly what a visitor sees.
If you would like someone to look at the results with you and turn them into a prioritised plan, ask for a free audit through the contact page.