---
title: "Technical SEO and audits · MRC Studio"
description: "Technical SEO audits for large and multilingual sites: template issues separated from scattered ones, evidence for every finding, priorities and effort."
url: https://mrcstudio.io/services/technical-seo/
lang: en
updated: 2026-11-21
---

# Technical SEO and audits

A technical audit tells you what stops Google, Bing and AI bots from reading and indexing your site, and in what order to fix it. It is for anyone with a large or multilingual site, a migration coming up, or a drop in traffic that nobody can explain. I separate template issues from scattered ones, because template issues are fixed once for every page.

## What it solves

On a site with thousands of pages there are thousands of errors, but often only a few problems, repeated by a template. A piece of data missing from the product template is missing from every product page; a description loaded with JavaScript is missing from the raw HTML of all of them.

A page-by-page list of errors is no use to the people who have to fix them. They need to know which errors come from a template, which are scattered cases and which matter most.

### It is the right service when

- you have a large or multilingual site and do not know where to start;
- you are about to change platform, CMS or domain and do not want to lose traffic;
- organic traffic has dropped and nobody can say why;
- the site is built with a JavaScript framework and you do not know what bots read.

## How I work

I follow the [MRC method](https://mrcstudio.io/method/): I measure, fix it with your team, check it works.

I measure with a crawl of the site, the server logs, and the raw HTML compared with the page a visitor sees. I look at crawling and `robots.txt`, indexing and canonicals, page rendering and JavaScript, architecture and internal links, structured data, hreflang, performance, and what AI bots read.

I fix things with the people who develop the site, in order of priority. After release I check in the logs and in the traffic that the fixes have worked.

## What I deliver

- The audit, organised by template: every finding with its evidence (the page, the line, the log) and why it matters.
- Template issues separated from scattered ones.
- Priorities, with an estimate of the development work for each fix.
- The check after release: item by item, what is fixed and what is not.

## An example

Take an online shop with 2,140 product pages, all from the same template. The `Product` JSON-LD has no `brand` or `sku`, so search engines do not connect the product to the brand. The description arrives through JavaScript: the text is missing from the raw HTML, and GPTBot and PerplexityBot see the page without a description. The French and German versions name the Italian page as their canonical.

That is not 2,140 problems: it is three, and all of them are in the template. The estimated fix is two days of development, done once for every product.

## Frequently asked questions about technical SEO and audits

### How much does an audit cost?

The cost of an audit depends on the site: the number of templates weighs more on the work than the number of pages, and languages and domains count too. Send me the address of the site: I’ll look at how it is built and tell you how much work it is.

### What is the difference between a template issue and a scattered one?

A template issue sits in the model that many pages are built from: if the product template lacks a piece of data, every product page lacks it, and it is fixed once. A scattered issue affects individual pages, for example a wrong redirect or a duplicate title tag, and is fixed case by case.

### Does the audit cover AI bots too?

Yes. I check what bots that do not run JavaScript read, such as GPTBot, ClaudeBot and PerplexityBot, what `robots.txt` allows them, and, from the server logs, which of them actually visit the site.

### What are server logs for?

They show which bots actually visit the site, and which pages. `robots.txt` says what you allow and a crawl says what is there; only the logs say who has visited. That is why they are part of the measurement.

### Do you also handle migrations?

Yes: a change of platform, CMS or domain. I write the SEO requirements beforehand and check after release. In-house, I wrote the SEO requirements for a migration to a new platform, with rankings and traffic retained, and I oversaw the merger of an external domain into the main one with 100% of the traffic retained.

## Let’s start from your site

Send me the address of the site and what worries you: I’ll reply personally and, if needed, we’ll arrange a call. If you want a quick measurement of one page first, try [MRC Check](https://mrcstudio.io/labs/mrc-check/).

[Get in touch](https://mrcstudio.io/contact/)
