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.
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.
Input to analyse
Website pages, content and context
Output
SEO summary and action plan
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.
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.
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 engine records pages and their HTTP responses, redirects, sitemaps and SEO elements. Browser rendering checks and Lighthouse measurements can supplement this collection.
The site's structure, content, objectives and CMS capabilities guide the analysis. Observations remain distinct from hypotheses about their causes.
The action plan links issues to the affected pages, priorities, suggested owners and verification criteria. The draft is reviewed and expanded before delivery.
HTTP records, page elements and observed internal links help organise the analysis by content type and locate evidence for each finding.
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.
Search Console and GA4 exports can supplement public observations. Their date ranges and scope are retained to interpret results in context.
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.
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.
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.
In development
Structure the recovery of a hacked WordPress website, from analysis to relaunch.
In development
Bring technical evidence together to guide a Magento diagnosis.
Your project
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.