What is technical SEO in plain words?

Order on the site: speed, mobile usability, indexing, and structure — plus Schema markup when useful. So customers are comfortable and Google can find and understand pages.

Do business owners need to know Core Web Vitals?

You do not need to memorise reports. Enough that the page shows meaning quickly, buttons respond, and blocks do not jump. The rest is the contractor’s job. Check the result on your own phone on normal mobile data.

What is Schema and why does it matter?

Schema is machine markup on a page (organisation, FAQ, product, and so on). It helps search understand the content and can sometimes show a richer snippet. If the facts are not on the page, there is nothing honest to mark up — and Schema alone does not guarantee rankings.

How much does a technical SEO fix cost?

Softly for the Uzbekistan market: point fixes often about 1.5–6 million UZS; an audit plus fix pack about 5–18 million UZS; rebuilding a key section from ~12 million UZS. Market range, not a UZNEO price list.

Will FAQ markup alone push the site to the top?

Rarely by itself. It can improve how the result looks if useful answers are already on the page. Without strong copy and decent speed, the effect is weak.

Where should I start if the site already exists?

Walk the checklist on a phone, open Search Console, strengthen 3–5 main service pages (above-the-fold speed, structure, FAQ). Do not start with a full rebuild “for the technology”.

Is Next.js required for technical SEO?

No. You can bring technical order on different platforms. Next.js is convenient when you need speed, control, and long-term growth — a fit for the task, not a Google requirement.

SEO19 minJuly 5, 2026

Technical SEO for your website: Core Web Vitals, Schema, and Next.js — without the jargon

Robert MirovUpdated Jul 5, 2026

Business owners in Tashkent and across Uzbekistan often hear: “the site is slow”, “no markup”, “you need Next.js”, “Core Web Vitals are red”. It sounds like a developer-only problem. In practice it is about leads: if the page opens slowly on a phone, blocks jump, and Google barely understands what you offer — your copy and ads work weaker than they should. Technical SEO is order on the site: speed, a usable phone experience, indexing (so search can find the right pages), clear structure, and when useful Schema (special markup for search engines). Core Web Vitals are three Google metrics about how a page *feels*. Next.js is a modern way to build a site when speed, control, and growth matter. Below is a calm guide for business owners in Uzbekistan: what to check yourself, what to ask a contractor, soft timelines and budgets. No code walls and no promise of ranking #1. At UZNEO we keep the focus on leads — not on a pretty report.

01What technical SEO means for business

Technical SEO is not a separate “magic package” and not a replacement for copy and offer. It is the foundation: the customer is comfortable, Google can find and understand the page, and you do not lose leads to lag and messy URLs.

Layer	In plain words	Why an owner cares
Speed / Core Web Vitals	The page shows meaning and buttons quickly, without jumping	Fewer exits before the request
Mobile	Readable and tappable on a phone without pain	Most traffic in Uzbekistan is mobile
Indexing	The right URLs are in search; private areas are closed	A beautiful unindexed site is useless
Page structure	One page — one job, clear blocks	Search and people understand the offer
Schema (markup)	A machine “passport”: FAQ, organisation, product	Sometimes a richer search snippet

Tech alone does not push you to the top. It removes blockers so SEO promotion and ads are not fighting a slow above-the-fold or pages Google cannot see.

Before	After
“Technical SEO = opaque acronyms”	Order: speed, phone, indexing, structure, markup
We only polish design	First fix what blocks leads and search
Waiting for “Next.js magic”	Checklist first, platform second

02Core Web Vitals in plain words

Core Web Vitals are three Google metrics about how a person *experiences* a page. You do not need to memorise formulas. Enough to understand three questions and check the result on your own phone.

Metric	What it measures	How to feel it without a report
LCP (Largest Contentful Paint)	How fast the main meaning of the screen appears (often a headline or large image)	Do you stare at emptiness before the offer shows?
INP (Interaction to Next Paint)	How fast the site reacts to a tap	Do “Call” / the form freeze after you tap?
CLS (Cumulative Layout Shift)	Whether blocks jump while loading	Does the button slide away when a banner loads?

Why this matters in Uzbekistan: mobile networks can be uneven, and customers compare you with a competitor in seconds. A slow ad landing burns budget before anyone reads the price. More on measurement — in our site speed and PageSpeed guide. What most often breaks the scores on real sites: • phone photos at 3–5 MB on the first screen; • heavy sliders, autoplay video, and chat widgets before the offer; • fonts and scripts that block text from showing; • cookie banners and chat that shove buttons after load.

Before	After
“PageSpeed 42 — rebuild everything”	Look at LCP / INP / CLS and what blocks the lead
Fancy slider above the fold	Light first screen: offer + CTA
Chat covers “Send request”	Lead buttons always reachable
We only test office Wi‑Fi	We test normal mobile data

03Mobile: how customers really arrive

Most traffic in Uzbekistan comes from phones. If the laptop version looks fine but buttons are tiny or the page “thinks” for more than a couple of seconds, you lose customers quietly. A five-minute self-check: 1. Open the site on normal mobile data (not only office Wi‑Fi). 2. Can you read the text without sideways scrolling or pinching to zoom? 3. Is “Call”, “Telegram”, or “Send request” easy to tap with a thumb? 4. Do chat and cookie banners cover key buttons? 5. Do photos load normally — or do you get grey boxes for half the screen? For an ad landing page the rule is simple: phone first, computer second. Ads send people to the first screen — if it lags, you pay for a click with little chance of a lead.

Before	After
We only review the site on a laptop	Main test = the customer’s phone
Tiny buttons “like on desktop”	Large CTA, tappable phone number
Cookie and chat on top of the form	Form and call always visible

04Indexing: so Google finds the right pages

Indexing is when a search engine finds a page and can show it in results. A beautiful site is useless if key services never enter the index while old duplicates still hang in search. Basics an owner should understand: • Sitemap — a list of important URLs for the crawler. • robots.txt and noindex — rules for where to go / where not to go. Close private areas; keep services and articles open. • Clear addresses — without messy parameters and obvious duplicates of the same service. • Google Search Console — the cabinet where coverage and mobile errors show up. After a redesign or a move from a website builder, update the sitemap and check that old URLs are not left empty (you need redirects). For growth order in search, see how to rank in Google.

Before	After
“We have a site — so we are in Google”	Check Search Console and `site:domain`
Sitemap has old URLs; new services missing	Sitemap = current sales pages
noindex “just in case” on services	Index only the URLs you need
Two live http/https or www versions	One canonical address + redirects

05Page structure: one job — one URL

Speed and markup will not save a page where it is unclear what you sell and what to do next. Structure is UX for people and a signal for search. A strong service page usually has: • what you offer and for whom — immediately; • how it works — short blocks; • a “from” price or a range, when it fits; • examples / cases / facts about you; • FAQ from real customer questions; • contacts and a clear next step (form, call, Telegram). One page — one job. Do not mix “website design”, “ads”, and “promotion” into one long unstructured text. Title and description on key services should be unique — not one phrase for the whole site.

Before	After
One “Services” page for everything	Separate URLs for money services
H1 “Welcome”	H1 = service + clear context (often the city)
“Ask for prices” everywhere	At least a “from …” range on key pages
Text without sections or FAQ	Logical sections + answers to common questions

06Schema markup: why it matters for business

Schema (structured data) is special markup in the page code. People barely see it. Search engines use it to understand: this is an organisation, a service, a product, an FAQ, breadcrumbs. Sometimes Google shows a richer snippet: Q&A under the result, rating, price, address. That is not a guarantee of ranking #1 and not a “growth button”. It is a chance to make the result clearer — *if* those facts are really on the page. What is usually marked up: • Organization / LocalBusiness — name, address, phone, hours (especially useful for local businesses in Tashkent together with maps). • FAQPage — a Q&A block on a service page. • Product / Offer — for a shop: product, price, availability. • BreadcrumbList — the path “Home → Services → …”. Honest limits: • do not mark up what is not on the page; • fake reviews and inflated ratings are a bad idea and a risk; • markup without strong copy and decent speed has a weak effect. As an owner you only need the *why*: markup is a clarity layer for search. A developer sets it up. Meaning and structure first — Schema second.

Before	After
“Add Schema — instant top rankings”	Markup amplifies a clear page
FAQ only in code; nothing on the page	Questions and answers visible to people
Marked up everything	Only what really exists on the URL

07Technical SEO checklist: 14 points

Walk the list yourself — on a phone and in Search Console. Yes / no / not sure already gives you a picture for the contractor talk. 1. The site opens on a phone in a couple of seconds on normal mobile data. 2. Buttons and the form respond at once — no freeze after tap (INP in practice). 3. Blocks do not jump while images and banners load (CLS). 4. Text reads without sideways scrolling; buttons are easy to tap. 5. Chat and cookie banners do not cover “Call” and “Send request”. 6. HTTPS is on — padlock in the address bar, no browser warning. 7. Google Search Console is connected — coverage errors are visible. 8. There is a sitemap and it is updated after major changes. 9. Private areas are closed to search; services and articles stay open. 10. URLs are clear, without obvious duplicates of the same service. 11. Important pages have one main heading and logical sections below. 12. Title and description are unique on key services. 13. Service pages have FAQ when customers really ask those questions — and FAQ markup when it fits. 14. If there are several languages — versions are complete, each has its own URL, and search understands the link between them. If half the list is “no” or “not sure” — fix the base before publishing new articles “for SEO”. Typical launch traps — in top 10 website mistakes.

08What to ask your developer: timelines and budget

You do not need the insides of the code. You need clear questions and clear answers. A short question list: • How do you check mobile speed — and what is a normal target for our landing (LCP / above the fold)? • Are important pages in Search Console without critical errors? • Is there a sitemap? What is closed to search and why? • Are there duplicate service pages or broken old URLs after edits? • Do we need Schema (Organization, FAQ) — and are those facts on the page? • If there are several languages — are versions complete and linked correctly? • How long will critical checklist fixes take, and what is in the quote? • What do we get at the end: a fix list, a Search Console check, a speed retest? Timelines (soft guide for the Uzbekistan market):

Type of work	Timeline	What usually sits inside
Quick fixes	2–7 days	Images, HTTPS, form, meta tags, sitemap
Mid tech pack	1–3 weeks	Mobile fixes, indexing, structure for 3–5 services, FAQ / basic Schema
Serious rebuild	2–6 weeks	Landing or a move off a heavy builder

Budget (soft range, not a UZNEO price list): • Point fixes — often about 1.5–6 million UZS (~$120–500). • Tech audit + fix pack — often about 5–18 million UZS (~$400–1,500). • Landing / key section rebuild — often from 12+ million UZS (~$1,000+); the top depends on the brief. First fix what blocks leads and indexing. Beauty for its own sake can wait if the base is still red. On platforms — WordPress, Tilda, or a modern stack.

09When Next.js fits — and when it does not

Next.js is a modern framework (scaffold) for React sites. For a business owner it is not an “SEO checkbox”. It is a way to build a site when speed, structure control, several languages, and integrations (CRM, bot, payments) matter. It often fits if: • the site is a long-term sales and ads tool, not a one-off test; • you need solid mobile speed, a clean SEO base, and room to grow pages; • you plan CRM, a Telegram bot, payments, or several languages with a proper link between them. Another platform is often enough if: • you need a quick one-page test for a few weeks; • content is rare, ads are almost none, and the job is a simple brochure site.

Before	After
“Buy Next.js — SEO will follow”	Checklist and landings first; stack follows the task
Builder lags under ads	Light landing or rebuild of the critical URL
Platform chosen by fashion	Speed, support, integrations, project lifespan

The checklist result matters more to you than the technology name in the quote. Platform comparison — WordPress, Tilda, or Next.js.

Summary

Technical SEO for business is speed (including Core Web Vitals), a usable phone experience, solid indexing, clear structure, and Schema markup when it fits. Next.js is useful when the site lives long and you need control and integrations — but it is a fit for the task, not a requirement “for SEO”. Simple order: walk the checklist → ask the contractor clearly → first fix what blocks leads and indexing → then add platform complexity and markup. UZNEO designs websites and online stores so tech works for leads from day one. To discuss a task — via Telegram.

Search Console