Eve Dijital

Technical
SEO

If Google cannot crawl or index a page, or cannot offer users a good experience because it finds the page slow, content work will not pay off. We audit your site's infrastructure, rank the issues by importance and follow them through until they are fixed.

Live demo · Core Web Vitals

Three metrics, three different fixes

Google measures page experience with three metrics: how fast the main content loads (LCP), how quickly the page responds to input (INP) and how much it shifts (CLS). Each has its own cause and fix — switch the fixes on one by one and watch the gauges.

↳ Toggle the fixes — each one moves its gauge

LCP

4.6 s

Largest content

INP

420 ms

Interaction response

CLS

0.28

Layout shift

GoodNeeds improvementPoor

Thresholds are Google’s official values (LCP 2.5 s · INP 200 ms · CLS 0.1). Gauge readings are examples.

Indexing and Search Console

We go through statuses in the Page Indexing report, such as "Crawled – currently not indexed," "Discovered" and "Excluded by noindex tag," one by one and find the cause.

Crawl Analysis

We crawl the site the way a search engine does to surface broken links, redirect chains, orphan pages and parameter URLs that are being crawled unnecessarily.

Core Web Vitals

We measure LCP, INP and CLS with real-user field data and fix the causes, such as oversized images, render-blocking files and shifting layouts.

Redirects and Canonicals

We check how 301/302 redirects are used, along with redirect chains and canonical tags, to prevent the same content from being indexed at multiple URLs.

Structured Data

JSON-LD markup for Organization, LocalBusiness, Product, Article, Breadcrumb and other suitable page types, validated with the Rich Results Test.

Hreflang and Multilingual Setup

Reciprocal hreflang tags, x-default and language-specific sitemaps for hotel, exporter and tourism sites with Turkish and foreign-language versions.

robots.txt and XML Sitemap

Correctly written files that tell search engines what to crawl and what not to, with only the pages you want indexed included in the sitemap.

JavaScript and Rendering Checks

On sites built with React, Next.js or page builders, we use the URL Inspection tool to check whether content reaches Google in the initial HTML.

Site Migrations and Redesigns

When the domain, platform or URL structure changes: an old-to-new URL mapping table, 301 redirects and post-migration Search Console monitoring.

Core Web Vitals

Google's page experience metrics and thresholds

The assessment is based on 75 percent of real users' page loads. We read the data from the Core Web Vitals report in Search Console and the field data in PageSpeed Insights.

examplecompany.com · mobile loadExample
Cookie notice
Get a quote
0.0 s
LCPCLSINP
0 s5 s

Metric

LCP (Largest Contentful Paint)

What it measures

How long it takes for the largest image or text block on the page to load

Threshold

Good: ≤ 2.5 sPoor: > 4 s

Common causes

  • Large uncompressed hero image
  • slow server response
  • render-blocking CSS/JS

INP replaced FID in March 2024. Values between the two thresholds are classified by Google as "needs improvement."

Notes from the Field

The Issues We Find Most Often in Audits

Watch an example crawl output for each issue to see where the problem is caught and how it gets fixed.

crawl outputExample

$ crawl https://examplecompany.com/services

GET /services → 200 OK

robots.txt → Allow: /

<meta name="robots" content="noindex"> found (left over from staging)

Search Console: "Excluded by 'noindex' tag"

01 / 04

Pages Blocked by Mistake

A leftover "noindex" tag from a staging environment or a single line in robots.txt can keep important pages out of Google for months. It is one of the first things we check.

Issues rotate automatically; pick one to stop the tour.

Deliverables

What You Receive at the End of the Audit

Open the files in the delivery folder to see an example preview of what each document looks like.

technical-audit-delivery/

Files open one by one; tap one to pin it.

findings.xlsxExample

01 · Report

Findings Table

For each issue: a description, the affected URLs, its priority and who will do the work (you, your developer or us).

IssuePriorityOwner
noindex on service pagesHighDeveloper
Redirect chainsMediumEve Dijital
Missing image alt textLowContent team
Choosing the Right Service

Technical SEO or a different SEO service?

Technical SEO deals with the site's infrastructure; it does not write content or earn links. If you are not sure where your problem lies, a short preliminary review lets us tell you which service you need.

This page is for you if

  • Your pages are not getting indexed by Google, or you see errors in Search Console
  • The site is slow, shifts around on mobile, or the Core Web Vitals report is red
  • You are planning a redesign, a domain change or a platform migration
  • Your site has several language versions and the right one does not show up in the right country

What we need to start the audit

Most of a technical audit can be done from the outside, but Search Console data is essential to fully understand how Google sees your site. We start with the following access.

Let's talk about your project

Book a call ↗

At least read access to Google Search Console, ideally full access

GA4 access and, if available, traffic data from previous periods

Access to the site's admin panel or hosting, or a line to your developer

If a migration or redesign is planned, the staging URL of the new site

How we work

How we run
a technical audit

Our goal is not a long list of warnings, but fixes that have been implemented and verified.

About us →
01
Findings ranked by importance
We do not forward the hundreds of lines of warnings that tools generate as they are. We rank every finding by its impact and how hard it is to implement.
02
In terms a developer understands
For each item, we list the affected URLs, how to reproduce the issue and the recommended fix; if needed, we talk to your developer directly.
03
Field data, not lab scores
A PageSpeed score is not a goal on its own. We look at the Core Web Vitals data collected from real users, which is what Google evaluates.
04
We verify the changes
Once a fix is in place, we recrawl the page, start validation in Search Console and follow up on the result.
05
Under one roof with the web team
If we built your site or are going to rebuild it, our web team can implement the technical fixes directly.
How we work

Our Process

01

Data collection

We gather Search Console, GA4 and server-side information and run a full crawl of the site.

02

Audit report

Findings are listed with the affected URLs, prioritized and reviewed together with you.

03

Implementation

Fixes are made with your developer, or directly by us if we are given access; critical items come first.

04

Verification

Results are checked through recrawls, Search Console validations and Core Web Vitals monitoring.

FAQ

Frequently Asked
Questions

Technical SEO is about whether Google can crawl, understand and index your site: indexing, speed, redirects, structured data and so on. Our general SEO service also includes keyword research, content creation, local SEO and monthly management. You can also take technical SEO on its own as a one-off audit and fix project.

The values Google considers "good" are: Largest Contentful Paint (LCP) of 2.5 seconds or less, Interaction to Next Paint (INP) of 200 milliseconds or less, and Cumulative Layout Shift (CLS) of 0.1 or less. The assessment is based on whether these thresholds are met for 75 percent of real users' page loads. INP replaced FID in March 2024.

On its own, most likely not. The 0–100 score in PageSpeed Insights comes from a lab test; for rankings, Google uses real-user data as part of page experience. Speed matters, but how well the content matches the search is far more decisive. We tackle speed issues for both user experience and conversions, and set expectations accordingly.

Some fixes (meta tags, redirects, sitemaps) can be made from most admin panels, and we will apply them if you give us access. Template, server or code-level changes require a developer. We give your site's developer a clear task list and do the post-implementation check ourselves.

Before launch, you need a mapping table that lists every important URL on the old site and links each one to its counterpart on the new site with a 301 redirect. Title tags, internal links and structured data should also be preserved. For several weeks after launch, errors and traffic in Search Console should be monitored closely. We manage this process from start to finish.

It is needed when your site offers the same content in different languages or for different countries; for example, a Cappadocia hotel with Turkish and English versions, or a manufacturer that exports. Each language version must point to the others reciprocally; one-way or incorrect tags may be ignored by Google.

No. Structured data makes a page eligible for rich results; Google decides whether to show them. Some types also come with Google's own restrictions; for example, FAQ rich results are now shown only for certain authoritative sites. That is why we apply markup according to Google's current guidelines and only for types that will actually help.

Unless there is a major change, one or two comprehensive audits a year are enough for most sites. However, a site redesign, a platform change, a new language version or an unexplained drop in traffic calls for an interim audit. For sites on our monthly SEO service, we monitor Search Console continuously.