You launched an e-commerce store on Laravel with a thousand products. A month later, you notice Google indexed only the homepage and a couple of categories, while new products wait weeks for their turn. This familiar scenario: without a properly configured XML sitemap, search engine robots wander blindly, missing important pages. We help automate sitemap generation so every page gets indexed on time.
What problems we solve
Poor indexing of new pages
If a sitemap isn't updated, new pages can stay unindexed for a long time. Dynamic generation solves this: the sitemap is regenerated with every content update—immediately after a product or article is published.
Incorrect priorities and frequencies
Many set priority="1.0" for all pages, confusing robots. The homepage should be priority 1.0, categories 0.8, products 0.6, blog 0.5. For changefreq, use weekly for blog, daily or hourly for products, never for contacts.
Sitemap size limits
One sitemap file holds up to 50,000 URLs. For large sites, use an index sitemap: it combines multiple files (pages, products, blog). Otherwise, part of the pages remains unnoticed.
How to set priorities correctly in a sitemap?
Priorities help search engines understand which pages are most important. Use a scale from 0.0 to 1.0. Homepage — 1.0, categories — 0.8, products — 0.6, blog articles — 0.5, contacts — 0.3. Update frequency (changefreq) defines dynamics: daily for products, weekly for blog, monthly for static pages.
How we do it: a case study on Laravel
Recently we configured a sitemap for an electronics e-commerce store running Laravel 11 with PostgreSQL. The database contains 15,000 products, 500 categories, and 300 blog articles. We implemented dynamic generation via a controller:
// routes/web.php
Route::get('/sitemap.xml', [SitemapController::class, 'index']);
// SitemapController.php
public function index()
{
$pages = Page::where('is_published', true)->get(['slug', 'updated_at']);
$products = Product::where('is_active', true)->get(['slug', 'updated_at']);
return response()
->view('sitemap.index', compact('pages', 'products'))
->header('Content-Type', 'text/xml');
}
The sitemap.index.blade.php template builds the file with correct tags, priorities, and frequencies, and adds product images for Google Images. The result is a fully functional sitemap.xml that automatically updates with every database change.
Work process
| Stage |
Duration |
Result |
| Site structure analysis |
1–2 hours |
List of all page types and their priorities |
| Generation setup |
3–6 hours |
Working sitemap, auto-updating |
| Index sitemap creation (if needed) |
2–4 hours |
Split into files by content type |
| Registration and testing |
1–2 hours |
Validation in Google Search Console and Yandex.Webmaster |
| Final documentation |
1 hour |
Update guide and recommendations |
Timeline: from 1 day for sites up to 5,000 URLs, up to 3 days for large projects (over 50,000 URLs). Pricing is determined individually after audit.
Why choose dynamic generation?
Dynamic sitemap updates 3 times faster than a static one. According to the Sitemaps protocol, a sitemap file can hold up to 50,000 URLs. For large projects we use an index sitemap—it simplifies management and speeds up parallel processing by search engines.
| Criterion |
Static |
Dynamic |
| Freshness |
Only at creation |
Always up-to-date |
| Update effort |
Manual editing |
Automatic |
| Suitable for |
Sites with rare changes |
E-commerce, blogs, news |
| Error risk |
High (misses, duplicates) |
Low |
How an index sitemap works
For sites with more than 50,000 URLs, create an index file that references multiple sitemap files:
<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<sitemap>
<loc>https://example.ru/sitemap-pages.xml</loc>
</sitemap>
<sitemap>
<loc>https://example.ru/sitemap-products.xml</loc>
</sitemap>
<sitemap>
<loc>https://example.ru/sitemap-blog.xml</loc>
</sitemap>
</sitemapindex>
This approach simplifies management, and search engines process each file in parallel.
Registration in robots.txt
Add a single line:
Sitemap: https://example.ru/sitemap.xml
After that, manually submit the sitemap in Google Search Console and Yandex.Webmaster—this speeds up initial indexing by 2–3 times.
How to create a sitemap manually for a small site
- Collect all page URLs that should be indexed.
- Determine priority and update frequency for each.
- Create an XML file using any editor, following the template from Google's sitemap guidelines.
- Upload the file to the site root.
- Add the line to robots.txt.
What's included in the work
- Analysis of current site structure and detection of issues
- Setup of automatic sitemap generation (Laravel, WordPress, any framework)
- Creation of index sitemap if necessary
- Registration in robots.txt and submission to Google Search Console / Yandex.Webmaster
- Error testing (format, dates, accessibility)
- Documentation and recommendations for ongoing maintenance
Guarantee: if the sitemap is not accepted by search engines, we will fix it free of charge within 2 days.
Contact us for a consultation. Order a turnkey sitemap setup and get results in 1–3 days. Our experience: 7+ years of hands-on work, 50+ successful projects.
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.
