Technical SEO

Technical SEO and site recovery

We find out why Google does not see part of your pages and remove the causes: duplicates, unnecessary redirects, markup errors, a slow or vulnerable server. Every URL change gets a 301 redirect, we record a baseline before the work, and compare the result in a before/after report built on Search Console data.

Discuss your siteAll services

What we do

The technical base content depends on

Copy and links will not help if a search engine cannot read the site correctly. This is what we check and fix.

Indexing audit

We work out which pages Google has indexed, which it has dropped and why, and produce a list of the specific causes.

  • Search Console “Pages” report
  • Duplicates and canonicals
  • Redirect chains
  • Sitemap and robots.txt

Structure and URLs

A logical catalogue and section structure, readable URLs, and every URL change backed by a redirect, aimed at keeping what the old address has built up.

  • Catalogue and section structure
  • Transliterated page URLs
  • 301 redirects from a map

Markup and languages

Structured data that search and AI assistants take company facts from, and language versions that do not compete with each other.

  • JSON-LD with schema.org
  • hreflang for language versions
  • A self-canonical URL per language
  • Open Graph for social networks and messengers

Visibility in AI search

Answers from ChatGPT, Perplexity or Google AI also come from websites. We make sure AI crawlers can read yours and get the facts without guessing.

  • llms.txt and llms-full.txt
  • AI crawler rules in robots.txt
  • IndexNow for fast updates in Bing

Speed

A slow page is indexed worse and converts worse. We strip excess weight and excess requests, especially on mobile.

  • WebP and image optimisation
  • Fonts and caching without extra requests on Cloudflare and Nginx

WordPress updates and hardening

An outdated core and plugins are a break-in risk, and after a break-in someone else's spam pages end up in the index. We update, close vulnerabilities and set up analytics.

  • Core, theme and plugin updates
  • Protection against attacks and intrusions
  • GA4, GTM, Search Console

Careful with rankings

How we work on a site that already has something

The main rule for a site with history is not to break anything. So every change has a baseline and a check.

1

Baseline snapshot

We export Search Console data and crawl the site before any change. Without this baseline the result cannot be proven.

2

URL map

No URL disappears without a 301 redirect to its new counterpart. The map is drawn up before any change.

3

Changes in batches

Fixes go out in batches, and each one is checked in Search Console before we move on to the next.

4

Before and after report

We compare indexing, page exclusion reasons and speed against the baseline and show the difference in numbers.

Experience

Where this already works

We do not disclose client names — only the problem and the technology.

Media

Publishing platform with an SEO layer

A news platform on FastAPI and PostgreSQL with several themes and an editorial moderation queue. SEO layer: sitemaps, AMP, JSON-LD and transliterated page URLs. Deployed with Docker, Nginx, Cloudflare and GitHub Actions.

FastAPIPostgreSQLJSON-LDAMPCloudflare
Media

WordPress news website

Development and maintenance of a WordPress news website, with the server and the site secured against attacks.

WordPressNginxAttack protection
SAIRAS

This website

Two language versions with self-canonical URLs and hreflang, a JSON-LD graph with the organisation, services and FAQ, a sitemap with change dates, llms.txt for AI crawlers and IndexNow. Pages in both languages and their markup are generated by one build from a single set of source files.

JSON-LDhreflangllms.txtIndexNow

Technology

Tools and platforms

Only what we work with on real websites.

SEO and analytics

Technical SEOJSON-LDhreflangSitemapllms.txtIndexNowSearch ConsoleBing WebmasterGA4 / GTM

CMS and backend

WordPressWooCommerceLaravelDjangoFastAPI

Speed and delivery

CloudflareNginxWebPAMP

Protection

DDoS protectionServer securityAccess controlSSL

Questions

Technical SEO in short

Why does Google not index some of our pages?

Most often: duplicates without a proper canonical URL, a forgotten noindex, redirect chains, pages with no internal links, or a slow server. The audit shows which of these is yours, and on how many pages.

We want to change our page URLs. Is that safe?

It is, as long as every old URL leads with a 301 redirect to its new counterpart and the sitemap and internal links are updated. We draw up the redirect map before the change.

Do you work with WordPress and WooCommerce?

Yes: core, theme and plugin updates, protection against attacks, speed, catalogue structure, markup and analytics.

What is llms.txt and why does it matter?

A text file at the site root from which AI crawlers quickly learn what the company does and find links to the details. We use it on our own site together with the full plain-text version, llms-full.txt.

How do we know the work paid off?

We compare Search Console reports before and after: how many pages are indexed, why the others are excluded, how speed has changed.

Do you set up analytics?

Yes: GA4, GTM, Search Console and Bing Webmaster, and form leads can go into the CRM together with UTM source tags.

Contacts

Tell us about the task

Tell us in two paragraphs what's not working. We will tell you whether we take it on and where we suggest starting. Meetings online, or in person in Uzhhorod or Kyiv.

We reply within one business day.

Email info@sairas.com.ua Phone +380 98 907 03 18 Telegram Open a chat LinkedIn Founder profile
Location Uzhhorod, Kyiv and remote across Ukraine
Telegram