Technical SEO — paid against free

Paid against free › Marketing & Growth › SEO & Organic Search › Technical SEO · Getting found on Repo Radar

Paid 0 reviewed

Prices and free tiers as checked, dated on each review.

Paid tools for this job are being added. The free alternatives below are ready to use.

Free to use. You run it on your own server.

They do this job.

One page of about forty public facts about any web address.

It loads one web page in a real browser, runs about a hundred checks, and prints a scored report.

A log reader that turns a web server access log into a terminal dashboard or an HTML report.

It measures a site's speed with real browsers and keeps the history.

Runs Google's page-auditing tool across a whole site and collects the scores into one report.

A frequently updated list of AI scrapers, ready to paste into a web server.

It reads the title, description and picture out of any web page.

A proposal for one Markdown file at `/llms.txt` that tells a language model what a site is, plus two tools for working with it.

A Python toolkit that turns site crawls, site maps and word lists into plain tables.

Seven search-engine and answer-engine modules for Nuxt sites, installed as one package.

Typed JSON-LD for the Schema.org vocabulary — structured data the compiler can check.

An audit that scores how readable and quotable a site is to AI answer engines.

A command-line crawler that audits a whole site and writes one HTML report.

Crawls a whole site and lists the technical problems it found.

A second choice: they cover part of this job or are a building block for it.

A command-line tool that runs a quality checklist over font files and reports the failures.

One job at a time: the paid tools worth paying for, the free ones you can run yourself, and who should pick which.

No tracking pixels. One click to leave. We use your address to send Stack Radar and nothing else. Privacy.