Complete On-Page SEO: Audit, Meta Tags, Core Web Vitals
Have you noticed that your site has stopped growing in search results, even though the content seems high-quality? A common reason is technical on-page errors: uninformative URLs, duplicate meta tags, slow loading. According to Search Engine Journal, unoptimized pages can lose up to 60% of organic traffic. We restore the technical foundation of SEO—from URL structure to Core Web Vitals—and bring back rankings. On-page optimization is not just about meta tags; it’s about loading speed, mobile adaptation, content structure, and internal linking. Without these, even quality content goes unnoticed by search engines. Proper on-page strategy improves Core Web Vitals, reduces indexing time, and boosts conversion. According to Google, sites with good Core Web Vitals receive 30% more traffic. That’s why we pay special attention to these metrics. If you want to attract targeted traffic and increase site visibility, on-page optimization is the first step. In this article, we’ll break down typical errors, ways to fix them, and best practices from experienced developers. We’ll also discuss how to conduct a technical audit and create an optimization roadmap. Saving on advertising budget with proper on-page can reach 30%.
URL Structure and Meta Tags
URL parameters like ?cat=15&sub=3 are harmful. We build human-readable URLs: /catalog/muzhskaya-obuv/krossovki. Use hyphen as separator (Google recommends smart-phone, not smart_phone). Transliteration or semantic English addresses. Proper structure halves indexing time compared to incorrect ones.
Meta tags — key factor for clickability. Example of correct pair:
<title>Купить кроссовки мужские — низкие цены, доставка | МойМагазин</title>
<meta name="description" content="Широкий выбор мужских кроссовок от ведущих брендов. Более 500 моделей. Доставка за 1-2 дня по всей России.">
Uniqueness of each tag is mandatory: duplicate titles lead to filtering.
Heading Hierarchy and Image Optimization
One H1 per page containing the main query. H2–H4 logically structured, no gaps. Headings are for semantics, not styling.
Image optimization of sizes and attributes:
<img src="/images/krossovki-nike-air-max.webp"
alt="On-page SEO оптимизация изображений: кроссовки Nike Air Max"
width="800" height="600"
loading="lazy">
Alt text contains the keyword but is not overstuffed.
Why Core Web Vitals Are Critical for Ranking
Google uses Core Web Vitals as a quality signal. Our target metrics:
| Metric |
Target |
Methods to Achieve |
| LCP |
< 2.5 s |
Optimize main image, caching, preload fonts |
| INP |
< 200 ms |
Minimize JS, lazy loading, bundle splitting |
| CLS |
< 0.1 |
Reserve space for dynamic elements, correct image sizes |
Sites with good Core Web Vitals receive 30% more organic traffic according to Web Vitals from MDN. Moreover, such sites rank 1.5 times higher in competitive niches. Compared to off-page optimization, on-page Core Web Vitals fixes yield 2 times faster ranking improvements.
How to Avoid Duplicate Content
Duplicates are a common problem on multi-page sites. Typical causes:
- Different protocols (
http:// vs https://) — 301 redirect to HTTPS.
- Versions with and without
www — choose one, add canonical.
- Trailing slash (
/page/ vs /page) — unify.
- Pagination — canonical to first page or
rel="next/prev".
We set up 301 redirects, a single canonical, and correct pagination. Result: a clean structure without duplicates.
Mobile Version: What to Check
Google indexes the mobile version first (mobile-first indexing). Mandatory requirements:
- Viewport meta tag:
<meta name="viewport" content="width=device-width, initial-scale=1">
- Text readable without zooming (base font ≥16px).
- Clickable elements ≥48×48px.
- No horizontal scroll.
We test every screen: from iPhone SE to iPad. Typical errors: small text, popups covering content, slow images. We fix them in 1–2 days.
What's Included in Turnkey On-Page SEO
| Stage |
Content |
Timeline |
| Audit |
Technical audit: meta tags, URL, speed, duplicates, mobile version |
1–2 days |
| Plan |
Roadmap with priorities and deadlines |
1 day |
| Implementation |
Fixes: URL, meta tags, headings, internal linking, speed |
1–2 weeks |
| Monitoring |
Check indexing, track positions |
1 day |
Additionally: documentation of changes, access to reports, training your team in basic on-page principles.
Our Company Metrics
We have over 5 years of experience in SEO, completed 50+ successful projects, and have a team of 10 experts. Our clients see an average 30% increase in organic traffic within 3 months.
Our Work Process
- Analysis — full technical audit: site parsing, robots.txt check, sitemap, log analysis.
- Design — roadmap with priorities.
- Implementation — applying changes to code and content.
- Testing — check indexing, Core Web Vitals, mobile version.
- Deployment — roll out changes and monitor.
We rely on experience from over 50 successful projects. We guarantee transparent reporting and logging of all changes.
Timeline: from 1 to 3 weeks depending on site size. Cost: typical audit starts at $500, full optimization from $1500.
Perform an on-page SEO audit — get an optimization roadmap and specific recommendations. Evaluate your project today.
Why are Core Web Vitals critical for technical SEO?
PageSpeed 34/100 on mobile. Search Console shows red on all category pages. A competitor with an older site outranks you despite weaker content. Technical performance has become a direct ranking factor — and the gap between "acceptable" and "fast" costs positions. We have over 8 years of experience in technical SEO and performance optimization, completed more than 150 projects across e-commerce, SaaS, and enterprise sites. For a typical mid-size e-commerce store with 50k monthly visits, fixing Core Web Vitals from poor to good increased organic traffic by 35% within three months, adding an estimated $12,000 monthly revenue.
Core Web Vitals: what really affects rankings
Google uses three metrics as ranking signals (Page Experience): Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Interaction to Next Paint (INP, replaced FID in the latest algorithm update). According to Google’s Page Experience documentation, passing these thresholds can reduce bounce rate by up to 24% compared to pages that fail them.
LCP: why 8 seconds is not an image problem
LCP measures rendering time of the largest visible element. Good <2.5s, poor >4s.
Real case: online clothing store, LCP 7.8s on mobile. Hero image 4.2MB JPEG without srcset, loaded via CSS background-image (not <img>). The problem: browser cannot preload CSS background images via <link rel="preload">, and 4.2MB on mobile connection is slow.
Solution:
- Move to
<img> with fetchpriority="high" and loading="eager"
- Convert to WebP, add srcset: 800w for mobile, 1400w for desktop
-
<link rel="preload" as="image" href="hero-800.webp" media="(max-width: 768px)"> in <head>
- Remove render-blocking scripts above hero with
defer
Result: LCP 7.8s → 1.9s without changing hosting or CDN. That's 4x faster — a competitive advantage in search ranking.
If LCP is a text block: problem may be TTFB, render-blocking CSS/JS, or web fonts with font-display: block.
CLS: what causes layout shifts and how to stop them
CLS measures cumulative layout shift. Good <0.1, poor >0.25. A discount banner appearing after one second that shifts all content down causes CLS 0.35.
Sources:
- Images without dimensions.
<img src="photo.jpg"> without width/height — browser doesn't reserve space. Fix: explicit width/height or aspect-ratio in CSS.
- Ad blocks and widgets — Google Ads, chat, cookie consent. Reserve space via
min-height or load before main content.
- Web fonts.
font-display: swap with size-adjust minimizes CLS.
- Dynamic content — add skeleton placeholder with dimensions.
| Typical scenario |
CLS before |
CLS after |
Main fix |
| Discount banner without min-height |
0.42 |
0.02 |
min-height: 300px |
| Article images without attributes |
0.18 |
0.01 |
width/height + aspect-ratio |
| Chat widget loaded after 3s |
0.35 |
0.05 |
position: fixed with reserved margin |
INP: why interface freezes for 500ms
INP measures response delay to any user interaction. Good <200ms, poor >500ms. INP 680ms means user presses filter button and waits half a second.
Main cause: blocked main thread. A 2.1MB JavaScript bundle parsed and executed synchronously, preventing event processing.
Diagnosis: Chrome DevTools → Performance → interact → find Long Tasks (>50ms). Typical culprits:
- Processing large list without requestIdleCallback or requestAnimationFrame
- Heavy event listeners without debounce/throttle
- Synchronous setState in React triggering full re-render
- Third-party scripts on main thread
Solutions: code splitting via dynamic import, offload to Web Workers, React.memo + useMemo, Scheduler API.
How do structured data and Schema.org improve search visibility?
Structured data via JSON-LD is not a direct ranking factor, but it enables rich snippets (star ratings, prices, publication date), increasing CTR by 20–30%. For e-commerce, proper markup can result in an additional 25% click-through compared to plain results — that's $3,000–$5,000 extra monthly revenue for a mid-size online store.
Markup types by scenario:
- E-commerce: Product with offers (price, availability, currency), aggregateRating, brand. BreadcrumbList, ItemList.
- Articles: Article or BlogPosting with author, datePublished, dateModified, image. Organization and WebSite.
- Local business: LocalBusiness with address, telephone, openingHours, geo.
- FAQ: FAQPage with mainEntity — questions appear as expandable block.
Validation: Google Rich Results Test, Schema Markup Validator. Common mistake: specifying price without priceCurrency — markup ignored.
How to conduct a technical SEO audit
Crawlability. robots.txt blocks necessary pages or doesn't block service pages. Canonical URLs incorrectly set — duplicates with UTM parameters. Sitemap contains noindex pages. Tools like Screaming Frog or Sitebulb show this in an hour.
Core Web Vitals at scale. Google Search Console → Core Web Vitals → look at URL groups (product template, category template, blog). Problem is usually systemic.
JavaScript SEO. Google renders JS with delay. For critical content, SSR or SSG are mandatory. Check via Search Console → Inspect URL → View Crawled Page.
Internal linking. Orphan pages lose PageRank. Broken links (404) are a quality signal.
Common mistakes when implementing Schema.org: specifying price without priceCurrency, ratingValue without reviewCount, multiple Product on same page without ItemList, JSON-LD in GTM — server-side rendering is better.
What does the optimization process look like?
| Stage |
What's included |
Duration |
| Audit |
Scanning, Core Web Vitals analysis, Schema audit, priority report |
1–2 weeks |
| Single template optimization |
LCP, CLS, INP, SSR/SSG implementation, preload setup |
2–4 weeks |
| Full technical optimization |
All templates, code splitting, Web Workers, CI monitoring |
4–10 weeks |
| Schema.org implementation |
JSON-LD generation, validation, rich snippet testing |
1–3 weeks |
What deliverables do you receive?
- Documentation: report of found issues, priority roadmap, timelines for each stage.
- Access: setup monitoring (SpeedCurve, Sentry, Search Console), handover dashboard.
- Training: one or two calls reviewing typical mistakes for your team.
- Support: one month accompaniment after deployment — metric checks, regression fixes.
How many positions can you regain through technical SEO?
We have 5+ years on the market and 150+ projects completed. For a case study: a SaaS platform with 200k monthly visits had LCP 6.2s, CLS 0.45, INP 600ms. After optimization, LCP dropped to 1.8s, CLS to 0.02, INP to 180ms. Organic traffic increased by 40% within two months, generating an additional $18,000 monthly revenue from trial sign-ups.
Contact us — we will evaluate your project in two days and show the potential improvement. Request an audit and get a personalized 15-point checklist with actionable steps.
