SEO is not dead. Bad technical SEO is.

E-commerce technical SEO consultant.

I help online stores and marketplaces fix the technical blockers — crawl waste, faceted-nav index bloat, duplicate PDPs, slow templates — that stop category and product pages from growing organic revenue.

Ex-GroupM (Extra Stores GCC). Currently Cresen Growth. Proven on platforms doing 150M+ monthly impressions.

Eslam Saker — E-commerce Technical SEO Consultant
Live crawl diagnostic

Googlebot is crawling 97,400 URLs on your store that will never make you money.

Faceted navigation and duplicate PDPs spawn tens of thousands of near-identical URLs. Googlebot burns its crawl budget on the junk and starves the category and product pages that drive organic revenue. Here's what reclaiming that budget looks like.

crawl target: store.example · 142,800 URLs discovered
indexing bloat
Crawl budget on revenue pages
18% 74%
Indexable / discovered ratio
31% 89%
Junk URLs pruned
0
Category / PDP — revenue page Crawl waste — faceted params, duplicate PDPs, thin Canonical consolidation
01

Crawl waste

Googlebot spends its budget on filters, sort parameters, and session URLs instead of your money pages.

02

Index bloat

Tens of thousands of weak faceted-nav URLs dilute your site's overall quality signal.

03

Duplicate PDPs

Variants, tracking parameters, and canonical conflicts split ranking signal across near-identical products.

04

Weak categories

Money templates lack content depth, internal linking, and the architecture to rank for commercial terms.

05

Slow templates

Category and product templates failing Core Web Vitals on the pages that drive 80% of organic sessions.

06

Broken signals

Canonicals, pagination, hreflang, and internal links sending mixed instructions to Google's crawler.

Simulation based on typical mid-market catalogs. Real numbers come from a crawl + log-file analysis of your store — that's the first thing I run on every engagement.

Inside the workflow

Not a PDF. A working repair system.

Every engagement runs through six instrumented stages — from raw log-file analysis to shipped tickets your team can deploy. This is what an audit actually looks like before it becomes a roadmap.

~/eslamsaker/audits/store.example_ 00:00:00
log_analysis stdout · googlebot · 7d window
$ python log_analysis.py --bot=googlebot --days=7
[INFO] parsed 8,412,397 hits from access.log.gz
[INFO] grouped by URL pattern...

URL pattern                              hits      % budget
─────────────────────────────────────────────────────────
/category/*?filter_color=*&sort=*     2,847,201    33.8%
/category/*?p=*&filter_*            1,612,038    19.2%
/product/*?variant=*&utm_*          1,302,544    15.5%
/category/*                             612,887     7.3%
/product/*                              498,720     5.9%
/* (other low-value)                       1,539,007    18.3%

[WARN] 68.5% of crawl budget on parametrized URLs
[WARN] top 3 parameter patterns: filter_color, sort, variant
[OK]   recommendation written to findings/01-crawl.md
gsc.coverage searchconsole · property
StatusURLsΔ 28dAction
Crawled — not indexed97,412+12,840noindex + canonical
Duplicate, alt canonical41,228+3,902consolidate variants
Discovered — not indexed18,067+1,114strengthen internal links
Indexed (revenue pages)14,884+312protect & expand
Blocked by robots.txt2,401audit blocklist
Diagnosis: ratio of indexable revenue pages to discovered URLs is 8.5%. Target after consolidation: 62%+.
architecture.diff crawl depth · before → after
depth 0 — home
1
depth 1 — categories
42
depth 2 — subcategories
218
depth 3 — PDPs (revenue)
14,884
depth 4 — faceted bloat
97,412
depth 5+ — orphan / dead
28,107
Money pages live at depth 3. 92% of bloat lives at depth 4+ behind faceted filters — that's where Google's crawl budget is dying.
canonical.diff templates/product.liquid
@@ /templates/product.liquid @@
- <link rel="canonical" href="{{ canonical_url }}">
- {% if product.selected_variant %}
-   <link rel="alternate" href="{{ variant.url }}">
- {% endif %}
+ <link rel="canonical" href="{{ product.url | absolute }}">
+ {%- comment -%} variants consolidated to parent PDP {%- endcomment -%}

@@ /robots.txt @@
+ Disallow: /*?filter_*
+ Disallow: /*?sort=*
+ Disallow: /*?utm_*
+ Disallow: /*?variant=*

@@ ticket #ECM-1042 @@
title:   Consolidate PDP variants to parent canonical
impact:  ~41,228 duplicate URLs → 1 canonical per product
effort:  M (template edit + robots + 1 sitemap regenerate)
cwv.audit category template · mobile · p75
LCP
4.2s
2.1s
INP
312ms
180ms
CLS
0.28
0.04
TTFB
820ms
340ms
html
css blocking
js bundle
hero image
font swap
third-party tags
Three render-blocking layers stacked. Fix order: unblock CSS → defer third-party → preload LCP image. ~2.1s recovered on category template.
validation weekly delta · 12 weeks post-fix
MetricBaselineWk 12Δ
Indexed revenue pages14,88418,402+23.6%
Crawl budget on /category/ + /product/13.2%71.4%+58.2pt
Top-10 commercial keywords284487+71.5%
Organic clicks (revenue pages)118k/mo196k/mo+66.1%
Avg LCP (category, mobile)4.2s2.0s−52.4%
Every fix is tracked against the pre-engagement baseline in GSC + GA4. If it didn't move the metric, it goes back on the roadmap.
stage 1/6 crawl intelligence
auto · ⏵

These artifacts are anonymized composites from real engagements. On your store, every stage produces a working file your developers can ship from — not a deck.

Trusted on platforms doing 150M+ monthly impressions — agency & in-house
Engagement modes

Choose your technical SEO intervention.

Every store fails differently. Some need a clean diagnosis. Some need a developer-ready roadmap. Some need an experienced operator inside their sprint reviewing and validating every fix before it ships. Pick the right altitude.

01 Diagnose

Technical SEO Audit

For stores that need to know exactly what is blocking organic growth.

  • Crawl waste & log-file analysis
  • Indexation & canonical audit
  • Faceted-nav / parameter strategy
  • Category & PDP template review
  • Internal linking & crawl depth
  • Prioritized issue map
Best for Stalled organic traffic, suspected index bloat, replatform fallout.
Audit my store →
03 Deploy

Implementation Support

For teams with internal developers but no technical SEO owner in the room.

  • Sprint-attached SEO review
  • Pre- & post-deploy QA
  • GSC + crawl validation
  • Canonical / robots / noindex checks
  • Performance & CWV regression guard
  • Weekly impact monitoring
Best for Engineering teams shipping fast who can't afford SEO regressions.
Support my team →
SCOPE

Built for stores doing 100k+ monthly organic sessions or 10k+ SKUs. Smaller catalogs usually don't have enough surface area to justify a specialist — happy to point you to who can help.

Not sure which fits? Book a 15-minute technical SEO call and I'll tell you what your store actually needs — even if that means doing less.

// objections

The questions nobody asks on the call.

The things that quietly stop people from booking. Direct answers, no hedging — if I can't answer it honestly here, I shouldn't be in the engagement.

Still have a question? Just ask →
Q-01 Will changing canonicals or pruning faceted-nav URLs hurt my current rankings?
No — done right, it does the opposite. The URLs being consolidated are weak duplicates that were splitting your ranking signal, not driving it. Every change is staged: I model the impact on a crawl sample first, ship in waves (robots → canonical → noindex), and watch GSC's "Crawled — not indexed" bucket weekly. If a wave moves a metric the wrong way, it's reversible in 24h. I've never had a fix that needed a rollback at scale.
Q-02 Do you implement the fixes yourself, or just hand my devs a list and disappear?
I don't push code to production environments I don't own — but I don't disappear either. Every finding becomes a developer-ready ticket with acceptance criteria, sample code, and the exact GSC/crawl signal that verifies it shipped. On Implementation Support engagements I sit in your sprint reviews and QA every release before it hits prod. The hand-off is the most expensive part of most SEO projects — that's the part I refuse to half-do.
Q-03 What platforms do you work on?
Shopify Plus, Magento (Adobe Commerce), Salesforce Commerce Cloud, custom headless / React / Next.js storefronts, and large WordPress + WooCommerce catalogs. The biggest pain is usually not the platform — it's a recent replatform or theme update that left canonical conflicts and parameter bloat behind. That's a niche I've shipped fixes on repeatedly.
Q-04 How fast will I see anything move?
Crawl signals (Googlebot hit distribution, "Crawled — not indexed" trend) move in 2–4 weeks after the first wave ships. Indexation cleanup is visible in GSC by week 6–8. Ranking and organic-clicks impact on category templates typically lands in weeks 8–12. I don't promise 30-day miracles — anyone who does is selling you a story.
Q-05 What's the investment?
Audit starts at $3,500 (small-to-mid catalogs) and scales by SKU count + access depth. Audit + Roadmap with developer tickets typically lands $6,500–$12,000 depending on templates and platform. Implementation Support is monthly, usually $3,500–$6,000/mo for a defined sprint involvement. Every engagement is scoped on the call — no surprise invoices.
Q-06 Do you work with agencies, or only direct to brand?
Both. I've been the senior SEO inside agencies (GroupM on the Extra Stores GCC account) and I'm currently leading SEO at Cresen Growth. White-label engagements are fine — pricing the same, reporting attributed to the agency, NDAs respected. I just won't ghost-write a deliverable I wouldn't put my name on.
Q-07 What if my store isn't big enough?
I'll tell you on the call. Stores under ~100k monthly organic sessions or ~10k SKUs usually don't have enough technical surface area to justify what I charge — you'd get more value from a generalist SEO or platform-specific specialist. I'd rather refer you out than take a fee I can't 10× return.

Right now, on your store

Googlebot is wasting most of your crawl budget on URLs that will never make you money.

Let's find out exactly how much — and the three changes that would recover the most revenue. One call. No pitch deck.

15 min free diagnostic call
48 hrs to first response
No retainer until value is proven