HomeMCP SEO → Technical SEO
Module

Technical SEO Audit in Continuous Operation – The Technical SEO Module

A technical SEO audit shows you where your website stumbles – on the day of the check. This module turns the snapshot date into a permanent state: continuous monitoring of crawling, status codes and Core Web Vitals, implementation in the CMS only after your approval.

What it is

Eight areas in continuous operation

The Technical SEO module is automated, continuous monitoring. It crawls your website regularly, reconciles the results with Google Search Console and checks eight areas: crawling and indexing, status codes and redirect chains, Core Web Vitals (LCP, INP, CLS from field data), sitemap and robots.txt, canonicals and duplicate content, HTTPS, mobile usability and structured data.

Sitemap and robots.txt at a glance Both files schematically control what search engines capture from a website. Sitemap (tree) Home / /services/ /blog/ /about-me/ /contact/ robots.txt (example) robots.txt User-agent: * Disallow: /wp-admin/ Sitemap: https://example.com/sitemap.xml viktorpasztor.de · MCP SEO · Technical SEO module
Schematic example of sitemap and robots.txt – a simplified model, not a real website structure or actual analysis.

Important for context: I also offer technical SEO as a manual service. . The dividing line: the module checks continuously and reports deviations. The manual service steps in where judgement and hands-on work are needed – at a relaunch, with grown legacy issues, on architecture questions. One doesn’t replace the other.

Why it’s a problem

A website doesn’t stand still

Errors arise between two check dates – and that’s exactly where they sit, because nobody’s looking. An audit PDF ages badly.

Silent plugin error

An update overwrites the robots.txt – nobody notices until traffic drops.

Disappeared pages

A category disappears from the shop, along with its subpages – and with them their rankings.

New script, new load

A theme change loads one script more than the old one – and pushes load time down.

Gap between two dates

Exactly where nobody’s looking, errors sit for weeks.

Core Web Vitals tip over

LCP over 2.5 seconds, INP over 200 milliseconds or CLS over 0.1 cost visibility – often unnoticed until the next audit.

“Across around 15 parallel client projects I keep seeing the same sequence: the error arises on a Tuesday through an update – and is only found at the next big audit. The time in between costs visibility, and you don’t win that back overnight.”

— Viktor Pásztor, SEO freelancer in Berlin
When an error is discovered The same error, two points of discovery. Snapshot audit Visibility lost Error arises Tuesday Next audit 6 weeks later Continuous monitoring (MCP SEO) Error arises Tuesday Alert a few days viktorpasztor.de · MCP SEO · Technical SEO module
With a snapshot audit, weeks often pass between an error arising and being discovered; with continuous monitoring, only days.
How to solve it

Four steps, always in the same order

The process in five steps 1 2 3 4 5 Finding Prioritisationby impact Implementationin the CMS Briefing todevelopers Approval
Step 5 is always the approval – only what you sign off gets automated.
1

Finding

Regular crawl plus reconciliation with Search Console – with the same tools that also run in the manual audit, including Screaming Frog and PageSpeed Insights.

2

Prioritisation by impact

A redirect chain on a revenue-relevant page weighs more than a missing canonical in the archive. You get a short, sorted list.

3

Implementation in the CMS

Whatever can be fixed in WordPress, Shopify, Shopware or TYPO3, I fix there directly.

4

Briefing to developers

Where the system can’t intervene itself, your developer gets a precise task: finding, affected URLs, target state. No server interventions, no theme rebuilds, no architecture decisions – that stays hands-on work.

5

Approval

Nothing goes live without your approval. The module proposes, you decide.

Four-way comparison

DIY / pro / agency / automated

CriterionDo it yourselfSEO pro (manual)AgencyHow I do it
Coststool costs plus your working timeaudit from €1,200, support from €1,000/monthmonthly flat fee depending on contract€99–399 per month, depending on module scope, plus credit usage as consumed
Check rhythmwhen there’s timeat the agreed appointmentdepending on contract, often monthlycontinuous
Reaction to new errorswhen you notice themat the next appointmentby ticket and workloadalert on deviation, reply within 24h on weekdays
Expertise neededhigh – you have to be able to read crawlsnonenonenone
Implementing the fixesyou do it yourselfas an action list, implementation by effortdepending on contractin the CMS after approval, the rest as a developer briefing
Traceabilityyour notesdetailed audit reportreporting depending on agencyalert per finding plus quarterly report
To be honest: before a relaunch or with a problem structure grown over years, you need a manual SEO audit with judgement and a concept; for server and theme work, your developer or an agency with a dev team – and anyone who can read crawls themselves and has time to spare is cheapest going it alone.
What’s in it for you

Five effects of continuous monitoring

There’s no ranking guarantee – not from me, and from no one serious. What the module delivers:

01

Discovered early

Errors are found when they arise – not months later at the next audit.

02

Prioritised by impact

You see first what affects your revenue pages.

03

Implementation included

After approval, directly in the CMS, without you having to coordinate a service provider.

04

Quarterly report

What was found, what was fixed, what’s open.

05

Cancellable monthly

Access and content belong to you, even after it ends.

What technical SEO costs relative to other measures is on the SEO costs.

Frequently asked questions

Questions about the technical SEO audit

Is the module worthwhile for a small website too?

Depends on the frequency of changes. A handful of static pages that never change don’t need continuous operation – a manual check is enough there. As soon as content, products or plugins are added regularly, new sources of error keep arising, and then monitoring pays off.

What happens with errors the module can’t fix itself?

Your developer gets a briefing: finding, affected URLs, desired target state. They don’t have to search, just implement. Server interventions, theme rebuilds and architecture decisions stay with humans on principle.

What access do you need?

CMS and Google Search Console. Both remain yours – I work with my own user accounts, which you can revoke at any time.

Can I book the module individually?

Yes. The MCP SEO modules can be booked individually and are cancellable monthly. The price depends on scope and ranges from €99 to €399 per month plus credits.

Context

Back to the pillar

The Technical SEO module is part of MCP SEO, my system for automated SEO routine work. Three neighbouring modules pick up where this one leaves off: PageSpeed goes deep on load times, Redirects decides per URL between 301, 410 or keep, and Internal Linking distributes relevance to the pages meant to sell.

Need a one-off, deep audit with a concept instead? The technical SEO optimisation as a manual service covers that. What each route costs is on the SEO costs page. SEO costs.

Have your website’s technical health checked

Want to know how your website is doing technically? Write to me. You’ll get a reply within 24 hours on weekdays – and an honest assessment of whether the module is worthwhile or a one-off audit would be the better entry point.

→ Book your free consultation