SEO / Web: free online tools
4 free tools, processed locally in your browser.
Four tools matching four distinct moments: diagnosing a page that already exists, writing the tags it lacks, declaring the full list of the site’s addresses, and checking that an old address still lands where it should. The logical order runs from the finding to the fix, and then to publication.
Two of them leave the browser by nature. The audit and the redirect checker have to go and read the address you type in; when the remote site refuses a direct read, the request goes back out through a public relay, api.allorigins.win, and the interface then states that the page was read through a proxy. The meta tag generator and the sitemap generator, for their part, do nothing but format what you type.
Tools in the SEO / Web category
- Page SEO audit — Title, meta, headings, images and links analysed in seconds.
- Meta tags generator — Title, description and Open Graph at the right lengths.
- Sitemap generator — Compliant XML sitemap, ready for Google.
- Redirect checker — See where a URL ends up and whether it redirects.
What the audit really looks at
The audit fetches the page’s HTML, parses it and applies ten checks: presence and length of the title tag, meta description, number of H1 headings, alt attributes on images, the viewport tag, the lang attribute on the html element, the canonical URL, the Open Graph trio, the volume of visible text, and the split between internal and external links. Each point scores one, a half or zero, and the average gives the score out of one hundred shown at the top of the result.
The limit follows from what it reads: the HTML the server returns. A page whose content is built by JavaScript after loading will look thinner than it really is. The score is not a Google ranking either, but a check on the technical fundamentals of a page. Some sites, finally, block any automated read, including through the public relay, and the analysis then fails outright rather than guessing.
Fixing it with the meta tag generator
The audit points out what is missing; the meta tag generator produces it. Two gauges follow what you type, set at sixty characters for the title and a hundred and sixty for the description, turning red beyond that. The audit’s own thresholds are slightly wider, fifteen to sixty-five characters for the title and sixty to a hundred and sixty-five for the description, so aiming at the gauges keeps you inside the range of both tools.
The block generated contains the title, the meta description, the viewport tag and the canonical URL, together with the Open Graph properties that social networks and messaging apps pick up. The twitter:card value adapts itself: summary_large_image as soon as a share image is filled in, summary otherwise. The whole block is pasted into the head section of your page template.
Declaring pages, tracking addresses
The sitemap generator expects one address per line and rejects the entire batch if one of them is invalid, displaying the offenders. The file you get back follows the sitemaps.org schema, with a loc and a lastmod block per address, and an optional changefreq. Two reservations are worth knowing about: the last-modified date written in is today’s, which amounts to declaring every one of your pages modified today, and the frequency announced remains a hint that search engines are free to ignore. The standard also caps a single file at fifty thousand addresses.
The redirect checker answers a different question: does this address still respond, and where does it lead? It displays the address tested, the final address, the HTTP status obtained and the read method used. Since the browser follows a redirect chain in one go, the intermediate hops of a 301 into a 302 are not visible here; observing those needs a server-side tool.
A sequence that holds up
On an existing page, audit first, then fix the items flagged in red with the tag generator, then run the audit again to see the effect. During a redesign the order flips: check every old address with the redirect checker before publishing the new sitemap, otherwise you are handing search engines a list of pages that return an error.
None of this replaces server logs or Search Console. These four tools work on what a page says about itself, at the moment you ask it. That makes them useful just before publishing, and just after a change of address or template, rather than as a report you run once and file away.