
An AI-assisted SEO system combines technical website signals, content analysis and prioritised recommendations in one traceable workflow. This anonymised case study focuses on architecture, data quality and human control; the product and client identity are intentionally not published.
Anonymised project study: This page documents technical product work. It is not a service offer; I am not currently accepting freelance or commercial projects.
Problem
Traditional SEO audits often produce long collections of independent warnings. They do not necessarily explain which action should come first, which finding is proven and which is only a plausible interpretation. A language model can summarise text well, but it must not invent missing measurements or replace deterministic technical rules.
The system was therefore not designed as an autonomous ranking autopilot. It structures available evidence, explains relationships and supports prioritisation. Publication and implementation remain deliberate human decisions.
System boundaries
- Technical facts must come from retrieved documents or measurements.
- Generated recommendations are stored separately from raw evidence and rule results.
- Important recommendations should link back to a concrete signal.
- Uncertainty, missing data and contradictory findings remain visible.
- The system never changes a website automatically without review.
Analysis pipeline
| Stage | Processing | Output |
|---|---|---|
| Collection | URL, status, canonical, headings, metadata, links, structured data and text | Reproducible document snapshot |
| Normalisation | Canonicalise URLs, identify duplicates, classify page type and language | Comparable records |
| Deterministic checks | Test indexability, status chains, missing fields, conflicts and internal links | Evidence-based technical findings |
| Semantic analysis | Assess intent, topic coverage, redundancy and clarity | Context for editorial decisions |
| Prioritisation | Weight impact, confidence, effort and template reach | Ordered actions rather than a warning dump |
| Human approval | Review recommendation, evidence and potential side effects | Conscious decision with an audit trail |
Deterministic rules before AI
Many SEO questions do not require a language model. A conflicting canonical, broken link, blocked page or multiple H1 elements can be tested directly. These checks provide reproducible results and become the foundation for later explanation.
AI is used where context matters: does the title and introduction fit the likely intent? Are several pages repeating the same topic? Should the same recommendation be treated differently on a profile page and an article? The model complements the rules rather than replacing them.
Explainable prioritisation
A finding is not important merely because it is easy to describe. Prioritisation uses at least four dimensions: expected impact, confidence in the evidence, implementation effort and the reach of the affected template. A defect in a global layout may deserve attention before ten small copy observations on individual pages.
Recommendations based on incomplete evidence are labelled accordingly. A reviewer can then choose further measurement, a controlled test or a direct correction.
Hallucination controls
The system must not claim rankings, search volume, conversion figures or technical states that are absent from the input. Prompts and output schemas separate observation, inference and recommendation. Evidence fields point to the analysed page fragment or deterministic result.
Additional validation checks that URLs belong to the analysed host, figures originate in the input and required fields follow the expected schema. Unsupported claims are reframed as hypotheses or removed.
Guiding principle
AI can direct attention towards relevant patterns. Reproducible measurements, source documents, search data and verified changes still determine what is true about a website.
Privacy and access
An SEO system may process public pages, unpublished content and analytics. Data sources, retention and permissions therefore need separate controls. Credentials do not belong in prompts or logs, and project data should be processed only where necessary.
Even public-page snapshots should not grow indefinitely. Clear refresh and deletion policies prevent old content from later being interpreted as the current state.
Outcome
The workflow converts heterogeneous SEO signals into an ordered and reviewable task base. Technical findings remain reproducible, semantic observations gain context and reviewers can see why a recommendation was suggested.
The primary benefit is not maximum text generation. It is better decision quality: fewer unstructured warnings, clearer evidence and prioritisation that people can challenge and correct.
Evidence demonstrated
- Architecture of an AI-assisted analysis workflow
- Combination of deterministic web checks and semantic evaluation
- Structured output, validation and source traceability
- Risk-aware use of generative models
- Prioritisation by impact, confidence, effort and reach
- Human-in-the-loop instead of automatic site changes
More architecture and SEO work
Other project studies and articles document my work across TYPO3, PrestaShop, APIs, performance and technical SEO.
Project overviewTechnology profileArticles