Technical SEO audit tool · 2025
Technical checks after a template change
ShippedIndependent engineer
A template change required a technical review, but a recurring SEO subscription was the wrong fit for a job that simply needs to run again after each release.
The constraint
Local, repeatable, no third-party account. Eleven focused checks, sized to the job.
Built with
PythonBeautifulSoupJSON
How it works
Fetch the site. Run the checks. Write a prioritized JSON list. Run it again after the template moves.
The calls that shaped it
Each decision with the pressure that forced it and the price it keeps costing.
A script you can rerun
A subscription reports on a schedule. The actual trigger here was a template change, which has no schedule.
Run it against the site, get JSON, fix in priority order. The client can run it again without me.
The cost: It has to be run deliberately, so a site that changes often means running it often.
On-page and crawl, not rankings
Rank data needs a third-party service and an account. The checks that caught the template problems were structural and needed no external source.
The tool reports technical and structural issues; it does not claim to track rankings.
The cost: The output says nothing about search position, which is often the first number a client asks for.
Eleven checks produce a prioritized list you can act on, and the run repeats whenever the template moves. Run it once after a release or on every deploy. The checks stay the same.
Where it stands
Shipped. A repeatable technical pass that runs again after each template change, without a monthly SEO product.
- Eleven on-page and crawl checks, ranked into a prioritised fix list.
- Runs locally with no third-party account.
- Output is JSON the client can act on in order and run again after the next release.
- Shipped. It does not track rankings.
What was handed over
- How to run it
- What each check means
- That it reports technical and structural issues only