Skip to main content
Tools & automation projects
Tools & automation

SEO audit toolkit

Turn SEO findings into an action plan tailored to the website.

I am developing a toolkit that brings together technical observations, page content and evidence from an SEO audit. It prepares detailed reports and an action plan, with guidance tailored to the website's CMS or technology.

How the tool works

Input to analyse

Website pages, content and context

  1. Observe
  2. Assess
  3. Prioritise

Output

SEO summary and action plan

My role
Design and development
Status
Tool in development
Technologies and scope
PythonSEOAnalysis across different CMS platformsHTML / JSON reports
The need

An audit that remains useful through to implementing fixes

The aim is to connect observed problems to the pages affected, then explain how to address them in the website's environment. The tool structures data collection and prepares the deliverables; the analysis and priorities are reviewed before delivery.

Findings scattered across different tools

A crawl, a browser check and content analysis answer different questions. I wanted to bring them together in a shared method, with evidence that can be located and checked again.

From the collection engine to the client report

I design the Python scripts, audit workflow and reporting templates. The work also covers separating internal evidence from deliverables, and guidance specific to CMS platforms and JavaScript-rendered websites.

The workflow

Observe the website, understand the causes, prepare the actions

  1. Bring observations together

    The engine records pages and their HTTP responses, redirects, sitemaps and SEO elements. Browser rendering checks and Lighthouse measurements can supplement this collection.

  2. Assess findings in context

    The site's structure, content, objectives and CMS capabilities guide the analysis. Observations remain distinct from hypotheses about their causes.

  3. Prepare actionable deliverables

    The action plan links issues to the affected pages, priorities, suggested owners and verification criteria. The draft is reviewed and expanded before delivery.

Features being developed

From technical evidence to remediation guidance

Crawling and structural analysis

HTTP records, page elements and observed internal links help organise the analysis by content type and locate evidence for each finding.

A method adapted to the CMS

The guidance accounts for WordPress, Magento, PrestaShop, Shopify or JavaScript rendering: fixes are planned at the level of the configuration, theme or template actually involved.

Additional measurement data

Search Console and GA4 exports can supplement public observations. Their date ranges and scope are retained to interpret results in context.

Reports to review and share

The HTML summary and JSON action plan are prepared from a selection of findings. Detailed evidence and private data remain in the audit's internal workspace.

Design decisions

An audit that can be revisited and verified

Keep a record of the work

Each website has its brief, business answers, decisions and successive records. A new collection preserves the history and allows observations to be compared over time.

Keep a review step before delivery

The report prepared by the scripts is a working draft. Assessing causes, analysing content and making business decisions remain part of the audit before delivery.

The output

Findings that can become concrete work

  • Technical records and dated evidence
  • An HTML summary prepared for review and delivery
  • An action plan with the affected pages and verification criteria

In development

WordPress recovery toolkit

Structure the recovery of a hacked WordPress website, from analysis to relaunch.

PythonWordPressAutomation

In development

Magento Black Box

Bring technical evidence together to guide a Magento diagnosis.

PythonMagento 2Diagnosis

Your project

Let's build the tool missing from your workflow.

Start with a concrete example: a repetitive task, a file or an analysis to produce. We will look at the available data and the expected result to define a custom tool.