Technical SEO
Crawling, indexing, rendering and speed. If these are broken, every page, link and campaign you pay for performs below what it could.
Is this for you?
A good fit if
- Large or growing sites: stores, publishers, directories
- Pages that should rank are missing from Google or flagged in Search Console
- A migration, a platform change or a new JavaScript framework is coming
Not the right fit if
- A five-page company site with no indexing problems
- You want a report from a scanning tool and nobody to fix anything
- You can't give access to a developer or the server
How I do it.
-
Crawl and logs
A full crawl, plus server logs if you have them, to see where Googlebot actually spends its time.
-
Index control
Canonicals, URL parameters, filter pages, sitemaps and robots rules set so Google indexes the right pages.
-
Rendering and speed
JavaScript rendering checks, and Core Web Vitals work based on real user data instead of lab scores.
-
Check
Every fix tested again and watched in Search Console until Google picks it up.
What you get.
- Technical audit ranked by impact
- Developer tickets with clear pass/fail checks
- Indexing and crawl budget plan
- Structured data
- Core Web Vitals plan
- Report confirming the fixes worked
The details.
Technical SEO is the least exciting part of the job, and usually the part that pays back the most. Every content plan, every link and every campaign is limited by how easily a search engine can crawl, render and understand your site.
What I check
- Crawl budget and crawl efficiency, using server logs when you have them
- Indexing: what’s indexed, what should be, and what’s wasting crawl
- Site structure and how internal links spread authority
- JavaScript rendering, and what Googlebot actually sees
- Core Web Vitals (LCP, INP, CLS) from real user data, not lab scores
- Canonical tags, redirects and redirect chains
- XML sitemaps and robots.txt rules
- Structured data: whether it’s correct, complete and eligible for rich results
- Filter pages and URL parameters
- Pagination and infinite scroll
- Duplicate and near-duplicate pages
- hreflang on sites with Arabic and English versions
- Mobile usability
- Broken internal links and pages nothing links to
Problems this usually solves
“We publish all the time and nothing ranks”
This is usually an indexing or internal linking problem. The pages exist, but Google either can’t reach them or doesn’t think they’re important enough to keep.
“Most of our products don’t show up in Google”
Almost always filter navigation creating millions of crawlable URL combinations, so Google spends its time on pages nobody will ever search for.
“We dropped after a core update”
Sometimes it’s content quality. Often it’s a technical issue Google used to tolerate and now doesn’t. The diagnosis is different in each case, and so is the fix.
“Our site is a JavaScript app”
Then rendering is the main question. Whether your important content and links are in the first HTML the server sends changes the whole plan.
Will a technical audit explain a traffic drop?
It will tell you whether the drop is technical. Roughly half the drops I look into turn out not to be, and finding that out quickly matters as much as a fix, because it stops you spending three months on the wrong problem.
In their words.
Clients asked not to be named. Each quote links to the case study with the numbers behind it.
See the numbers (Editor, Arabic lifestyle publisher)Our monthly clicks from Google went from about 113 thousand to more than 190 thousand in three months.
See the numbers (Owner, online store, Egypt)Much more of our catalogue shows up in Google now. Impressions went up by more than a third, and clicks followed.
See the numbers (Manager, services company, Saudi Arabia)We started with almost no visits from Google. Now people find us every month when they search for our services.
Common questions.
Which platforms do you work with?
WordPress, WooCommerce, Shopify, Salla, Zid, Magento and custom JavaScript sites.
Do you fix the issues yourself?
On WordPress, often yes. On other platforms I write exact tickets and review your developer's work.
Can you audit a site before it launches?
Yes. Checking the staging site catches the most expensive mistakes, especially during migrations.
Do you use server logs?
Whenever you can share them. Logs show what Google really crawls, which crawling tools can't show you.
Your next move.
Tell me where things are now and where you want them to be. I reply within one business day, in Arabic or English. If I'm not the right person for it, I'll say so.