EXPERIENCE

Technical SEO Audit

We analyse the technical foundation of the website to identify issues that may prevent search engines from discovering, interpreting or indexing content correctly.

Google Search Console

Technical SEO Audit

technical SEO auditindexation checkcrawl auditsite structure audit

EUR 50 / hour

Request a Technical SEO Audit

Complementary products

Technical SEO SEO Services Website Speed Optimization Website Maintenance & Development Website Migration

what is wrong -> why it matters -> how important it is -> what should be done

implementation -> testing -> recrawl -> validation

The audit does not automatically include remediation.

01PRODUCT READER

First screen

We do not start with:

“What else can we optimize?”

We start with:

“Is there anything in the technical architecture preventing the website from working correctly in search?”

We audit crawling, indexing, URLs, canonicals, redirects, internal linking and other relevant technical signals.

The amount of work depends on website size, number of URLs, platform and architecture complexity.

CTA support text:

Send us the website and tell us what issue you are seeing, if any. We analyse the technical foundation and document the priorities.

02PRODUCT READER

What problem does it solve?

A website may have technical SEO problems without them being obvious to users.

It may:

look correct;

appear to function normally;

contain good content;

receive traffic;

while still having issues such as:

important pages not indexed;

pages indexed that should not be;

duplicate URLs;

incorrect canonicals;

uncontrolled redirects;

orphan pages;

weak internal linking;

inconsistent sitemap;

incorrect robots rules;

incorrect HTTP status codes;

invalid structured data;

incorrect hreflang implementation;

important content depending on problematic rendering;

unnecessary URLs generated by filters or parameters.

The audit establishes whether these problems exist, how important they are and what should be addressed first.

03PRODUCT READER

What does the product do?

Technical SEO Audit builds a documented view of how the website is:

discovered;

crawled;

indexed;

structured;

internally connected;

technically interpreted.

We analyse the relationship between:

crawl -> indexability -> URL -> canonical -> redirects -> internal links -> structured data -> rendering

The primary output is diagnosis.

We do not change the website simply to increase the number of “issues resolved” in a tool.

04PRODUCT READER

What you receive

Depending on the project, the audit may include:

technical crawl;

URL inventory;

indexability review;

robots.txt analysis;

meta robots analysis;

X-Robots-Tag analysis where relevant;

XML sitemap analysis;

URL-structure review;

canonical analysis;

redirect analysis;

HTTP status-code review;

duplicate-URL identification;

orphan-page identification;

internal-linking analysis;

site-architecture analysis;

structured-data analysis;

schema-markup analysis;

hreflang analysis;

HTML-semantics analysis;

rendering analysis;

identification of relevant JavaScript issues;

review of selected performance signals relevant to SEO;

post-migration configuration analysis where applicable;

Search Console review where access exists;

issue prioritization;

remediation recommendations;

final report.

Implementation is separate.

05PRODUCT READER

What we need from you

To begin, it helps to have:

website URL;

issue observed, if any;

platform;

Search Console access where available;

sitemap;

information about recent migrations;

language versions;

important pages;

areas that should not be indexed;

information about recent changes;

any previous audit if available.

You do not need to identify the cause yourself.

That is the role of the audit.

06PRODUCT READER

What we do not promise

The audit does not promise:

better Google rankings;

traffic growth;

more sales;

indexing of every page;

immediate removal of every Search Console message;

a specific number of “errors” discovered.

A strong audit may also conclude that some areas are implemented correctly.

We do not invent problems to justify later projects.

07PRODUCT READER

Frequently asked questions

How much does a Technical SEO Audit cost?

The service costs EUR 50 / hour.

We estimate the work after understanding the size and complexity of the site.

What is the difference between Technical SEO Audit and Technical SEO?

The audit identifies and documents the issues.

Technical SEO implements the fixes and validates the result.

Do you audit indexing problems?

Yes.

Indexation checking is one of the central intents of the product.

Do you audit crawling?

Yes.

We analyse how pages are discovered and accessed.

Do you audit site structure?

Yes.

We analyse relationships between URLs, levels and internal linking.

Do you check canonicals?

Yes.

We analyse consistency between canonical, URL, sitemap, redirects and internal linking.

Do you check robots.txt and sitemap?

Yes.

Do you check structured data and schema markup?

Yes, where relevant to the website.

Do you check hreflang?

Yes, for multilingual projects.

Do you audit ecommerce stores?

Yes.

We can analyse filters, variants, faceted navigation and other ecommerce-specific technical issues.

Does the audit include implementation?

No.

Implementation is separate.

Can I give the report to another team?

Yes.

The report should be clear enough to be implemented by another technical team.

Does the audit guarantee traffic growth?

No.

It identifies technical barriers and issues. Organic performance depends on additional factors.

Can the audit conclude that the site is technically fine?

Yes.

We do not invent problems simply to create another project.

08PRODUCT READER

Crawl audit

The audit checks how search engines can discover and access the website’s URLs.

We analyse:

which URLs are crawlable;

which URLs are blocked;

how pages are discovered;

whether important pages are internally linked;

whether unnecessary areas consume crawling;

redirects;

orphan pages;

automatically generated structures.

We do not evaluate crawling using the rule:

“The more pages crawled, the better.”

The objective is for relevant pages to be discovered efficiently.

09PRODUCT READER

Indexation check

We review whether important pages send coherent indexing signals.

We check:

index / noindex;

canonical;

HTTP status code;

redirects;

sitemap;

internal linking;

duplication;

rendering;

other relevant signals.

We distinguish between:

the page cannot be indexed

and:

the page can be indexed, but the search engine has chosen not to keep it in the index.

These are different situations and require different diagnosis.

10PRODUCT READER

Reviewing non-indexed pages

For important pages that do not appear in Google, we check possible causes such as:

robots blocking;

noindex;

canonical pointing to another page;

redirect;

HTTP error;

duplication;

weak internal linking;

rendering-dependent content;

conflicting technical signals.

We do not assume the cause solely from a message shown by one tool.

11PRODUCT READER

Robots.txt

The audit checks whether robots.txt:

accidentally blocks important areas;

allows access to unnecessary areas;

contains outdated rules;

reflects the current architecture;

still contains staging or development rules;

conflicts with indexing intent.

Robots.txt controls crawling.

It is not the same as noindex.

12PRODUCT READER

Meta robots and indexing directives

We review directives such as:

index;

noindex;

follow;

other relevant directives.

We look especially for situations where:

an important commercial page is noindex;

pages that should not be indexed are open;

directives conflict with other technical signals.

13PRODUCT READER

XML sitemap

The sitemap audit may review:

canonical URLs;

indexable URLs;

redirects included incorrectly;

noindex pages;

missing pages;

non-existent URLs;

language versions;

consistency with the real site structure.

The sitemap should represent the inventory we actually want to signal.

Not every URL the platform is capable of generating.

14PRODUCT READER

URL structure audit

We review whether URL architecture creates issues such as:

duplicates;

unnecessary parameters;

multiple versions;

legacy routes;

conflicting slugs;

uppercase / lowercase inconsistencies;

inconsistent trailing slash;

HTTP / HTTPS variations;

www / non-www variations;

automatically generated URLs;

overly deep architecture.

The audit does not recommend changing URLs simply for visual preference.

Any change should solve a real problem.

15PRODUCT READER

Canonical audit

We review the relationship between existing URLs and declared canonicals.

Possible issues include:

missing canonical;

incorrect canonical;

canonical pointing to a redirect;

canonical pointing to an irrelevant page;

canonical inconsistent with sitemap;

canonical inconsistent with internal linking;

canonical pointing across languages incorrectly;

important pages canonicalized elsewhere.

The objective is consistency between signals.

16PRODUCT READER

Redirect audit

We analyse:

missing redirects;

incorrect redirects;

redirect chains;

redirect loops;

historical redirects;

irrelevant redirects to Home;

routes passing through several destinations.

For a migrated website, we check whether important legacy URLs reach the most relevant new destinations.

17PRODUCT READER

Status codes

The audit may identify:

4xx errors;

5xx errors;

soft 404s;

removed pages returning 200;

incorrectly implemented redirects;

important pages returning inappropriate statuses.

The HTTP status should represent the real state of the resource.

18PRODUCT READER

Duplicate URLs

Duplicate URLs may appear through:

parameters;

filters;

sorting;

variants;

pagination;

alternative versions;

CMS-generated routes;

multiple paths to the same content.

The audit determines whether duplication represents a problem and what mechanism should be used:

consolidation;

canonical;

redirect;

removal;

another relevant configuration.

19PRODUCT READER

Orphan pages

We review pages that exist but are not properly connected through the internal site structure.

A page may be discoverable through:

sitemap;

Search Console;

analytics;

backlink;

old URL;

without being linked from the site.

The audit determines whether the page should be:

reintegrated;

redirected;

preserved;

removed.

20PRODUCT READER

Internal linking audit

We analyse relationships between pages.

We may identify:

important pages with too few links;

pages buried too deeply;

broken links;

links to redirects;

unclear anchor text;

missing connections;

pages receiving excessive links without a clear reason;

fragmented architecture.

Internal linking should express the relationship between information.

Not simply increase the number of links.

21PRODUCT READER

Site structure audit

The audit also considers overall architecture.

We may analyse:

levels;

categories;

commercial pages;

products;

informational content;

hubs;

page relationships;

click depth;

URLs;

internal linking.

A structural problem cannot always be solved by changing one meta tag.

22PRODUCT READER

Structured data

The audit may review existing markup for types such as:

Organization;

WebSite;

WebPage;

Service;

Product;

BreadcrumbList;

Article;

other relevant types.

We review:

validity;

type;

fields;

duplication;

consistency with real content;

automatically generated markup.

We do not recommend schema that declares information that does not exist on the page.

23PRODUCT READER

Schema markup

Schema issues may include:

inappropriate type;

missing fields;

contradictory data;

duplicate entities;

outdated markup;

markup added by multiple plugins;

structures that do not reflect the page.

The audit explains what should be retained, corrected or removed.

24PRODUCT READER

Hreflang

For multilingual websites, we review:

declared languages;

URLs;

self-reference;

reciprocity;

canonicals;

missing pages;

links to incorrect versions.

A RO / EN website needs to communicate the relationship between the two versions without treating them as competing duplicates.

25PRODUCT READER

HTML semantics

We may review whether the HTML structure supports the content coherently.

Examples include:

H1;

H2/H3;

links;

images;

alt text;

content existing in HTML;

components hiding information;

interactive elements failing to expose critical content.

We do not turn the SEO audit into a complete accessibility audit.

We flag only the elements relevant to the technical SEO scope.

26PRODUCT READER

JavaScript and rendering

For JavaScript-dependent websites, we review whether:

important content is available;

links can be accessed;

rendering works correctly;

errors occur;

information exists only after interaction;

certain components are unavailable to crawlers.

We do not treat JavaScript as a problem by default.

We evaluate the actual implementation.

27PRODUCT READER

Important content hidden behind interaction

The audit checks whether essential information depends exclusively on:

tabs;

accordions that do not render the content;

sliders;

hover;

clicks;

JavaScript;

broken lazy rendering.

Interaction may organize information.

It should not be the only condition under which important content exists.

28PRODUCT READER

International versions

For international projects, we may review:

RO and EN relationships;

regional versions;

canonicals;

sitemaps;

reciprocity;

missing URLs;

translations without true equivalents.

We do not force hreflang relationships between pages that are not semantically equivalent.

29PRODUCT READER

Technical SEO Audit for a new website

The audit can also be performed before launch.

We may validate:

architecture;

URLs;

robots;

canonicals;

sitemap;

internal linking;

hreflang;

structured data;

redirects required from the previous website;

indexability.

Pre-launch is one of the best times to identify issues without the cost of fixing them after indexing.

30PRODUCT READER

Post-migration Technical SEO Audit

After a migration, we may review:

old vs new URLs;

redirects;

canonicals;

sitemap;

robots;

internal linking;

hreflang;

status codes;

indexing;

newly introduced errors.

A post-migration audit does not replace SEO planning before the migration.

It can identify execution problems after launch.

31PRODUCT READER

Ecommerce

For ecommerce stores, we may additionally analyse:

categories;

collections;

products;

variants;

filters;

sorting;

pagination;

discontinued products;

unavailable products;

faceted navigation;

Product schema;

internal linking;

ecommerce sitemap.

Stores can generate many URLs automatically.

The audit checks whether that generation is controlled.

32PRODUCT READER

Faceted navigation

Filters may generate very large numbers of URL combinations.

The audit may determine:

which URLs exist;

which are crawlable;

which are indexable;

which have canonicals;

which appear in internal linking;

which enter the sitemap;

whether low-value combinations exist.

We do not recommend indexing every filter simply because it can generate a URL.

33PRODUCT READER

Large websites and crawl budget

For large websites, the way crawling resources are consumed may become relevant.

We review possible sources of unnecessary volume:

parameters;

filters;

duplicate pages;

automatically generated URLs;

redirects;

calendar pages;

indexable internal-search pages.

We do not use crawl budget as an artificial concern for small websites where it is not relevant.

34PRODUCT READER

Search Console

Where access exists, Search Console may complement the audit with information about:

indexing;

sitemaps;

pages;

errors;

Core Web Vitals;

search performance;

issues detected by Google.

But Search Console is not the audit.

It is one of the sources we analyse.

35PRODUCT READER

Crawling tools

The audit may use specialist tools to analyse the site.

These can help identify:

URLs;

status codes;

canonicals;

metadata;

links;

duplicates;

structured data;

other signals.

The report is not the raw export from the tool.

Our role is to interpret what actually matters for the website.

36PRODUCT READER

Prioritizing issues

Not every technical issue has the same impact.

We prioritize using criteria such as:

blocking crawling;

blocking indexing;

number of affected URLs;

commercial importance;

risk;

duplication;

dependencies;

remediation difficulty.

The output should distinguish between:

critical

important

improvement

37PRODUCT READER

The final report

The report may include:

context;

methodology;

scope;

issue inventory;

examples;

affected URLs;

impact;

severity;

priority;

recommendation;

dependencies;

next steps.

For important issues, we explain:

what is happening

why it matters

what should be done

We do not deliver only a spreadsheet full of error codes.

38PRODUCT READER

Technical SEO Audit vs Technical SEO

Technical SEO Audit

Primarily delivers:

diagnosis;

documentation;

prioritization;

remediation plan.

Technical SEO

Continues through:

implementation;

recrawl;

testing;

validation.

You can purchase the audit without giving us the implementation work.

The report should also be usable by another technical team.

39PRODUCT READER

Technical SEO Audit vs SEO Services

The Technical SEO Audit is not a complete SEO strategy.

It does not automatically include:

keyword strategy;

content planning;

content production;

backlink strategy;

ongoing editorial optimization;

continuous competitor analysis.

It may identify needs that later belong to SEO Services.

40PRODUCT READER

Technical SEO Audit vs Website Speed Optimization

The audit may flag:

Core Web Vitals issues;

heavy resources;

rendering problems;

performance signals.

But it is not a complete website-speed project.

Where performance requires deeper analysis and remediation, we use Website Speed Optimization.

41PRODUCT READER

What the audit is not

Technical SEO Audit is not:

free implementation;

a ranking guarantee;

an automated tool export;

a list of 500 warnings with no prioritization;

complete keyword research;

editorial planning;

a complete UX audit;

a tracking audit;

full speed optimization.

The audit should provide useful and actionable technical diagnosis.

42PRODUCT READER

How much does a Technical SEO Audit cost?

EUR 50 / hour

The cost depends on:

website size;

number of URLs;

platform;

ecommerce complexity;

languages;

architecture;

JavaScript;

migration history;

data sources reviewed;

Search Console;

number of issues;

required documentation depth.

Once the scope is defined, we estimate the required number of hours.

43PRODUCT READER

Technical SEO Audit as an individual product or together with other components

Technical SEO Audit is a Component within Experience.

It can be purchased independently.

After the audit, the following may become relevant:

Technical SEO;

SEO Services;

Website Speed Optimization;

Website Maintenance & Development;

Website Migration;

Ecommerce Migration.

These services are not automatically included.

The audit may also recommend:

No major intervention is required at this time.

44PRODUCT READER

How long does it take?

The timeframe depends on:

website size;

number of URLs;

architecture;

platform;

number of languages;

ecommerce complexity;

JavaScript;

data sources;

documentation depth.

A simple website may require a much smaller audit than a large ecommerce platform with thousands of URLs.

The timeframe is estimated after defining the scope.

Technical SEO Audit

Your privacy matters