Technical SEO
Technical SEO Services That Get Your Pages Indexed and Ranking
Results · 16 months
From client Search Console accounts
From client Search Console accounts I've managed (in-house and freelance).
| Client | Clicks | Impressions | Notes |
|---|---|---|---|
| Account D | 21.9K | 2.76M | Large-scale organic visibility |
| Account A | 3.18K | 170K | Competitive high-ticket B2C niche, avg position 17.6 |
| Account B | 827 | 37.8K | 2.2% CTR, avg position 8.2, steady upward trend |
| Account C | 455 | 14.6K | 3.1% CTR, impressions up about 4x |
SEO clients and industries I’ve worked with
- Gulf Horizon Tele · Telecom · Saudi Arabia · ongoing
- Med spa clients · Aesthetics · USA
- Limo and chauffeur services · Transportation · USA and UK
Per-account Search Console numbers are shown anonymously (Accounts A–D) and are not tied to a specific client above.
Signs
When you need technical SEO
- Pages dropped out of Google after a redesign, migration or URL change
- Search Console shows “Crawled – currently not indexed” or “Discovered – not indexed”
- You moved to Next.js, React or headless and traffic fell
- Rankings stalled even though the content is good
- Core Web Vitals are failing on mobile
What I fix
The full technical stack
Indexing and migrations
Rendering and speed
Structure and internal links
Schema
Search Console-led optimisation
Content quality
Process
How an audit works
- 01
Crawl
Screaming Frog / Sitebulb, Search Console and, where available, server logs.
- 02
Prioritise
What to fix, why, and the expected impact.
- 03
Implement
Done by me on WordPress or Next.js, or as tickets for your developer.
- 04
Monitor
Indexing and traffic tracked for the following 8–12 weeks.
First-hand
A migration I fixed: this website
When I rebuilt rehanjaved.com on Next.js in September 2026, the inner URLs changed and most pages dropped out of Google. Every technical check was green, which is exactly why this kind of problem is easy to miss. The fix was a redirect map from old URLs to new ones, plus rewriting thin pages with real proof. I wrote up the full story in my core update recovery article, and the migration lessons in why technical SEO matters for large sites.
What a technical SEO audit from me includes
A technical SEO audit is only useful if it tells you what to fix first and how. Mine covers:
Indexing
Every reason in Search Console's Pages report, with the URLs behind each one and what to do about them. You can test a single URL right now with my free checker.
Crawling
A full crawl with Screaming Frog or Sitebulb: broken links, redirect chains, orphan pages, duplicate titles, canonical conflicts and pages buried too deep.
Rendering
Whether the HTML Google receives actually contains your content, links and metadata. This matters most on React, Next.js and other JavaScript sites.
Speed
Core Web Vitals from PageSpeed Insights and Lighthouse, traced back to the templates and scripts causing them.
Structured data
Whether your schema describes real things on the page, and whether it validates. Clear schema also helps Google connect a page to its author, which matters for being cited in AI Overviews.
Site structure
How authority flows through internal links, and which important pages get almost none.
You get a prioritised list, not a 90-page PDF. Each item says what's wrong, why it matters, and the exact fix. For pages that rank but don't get clicked, I rewrite titles and descriptions; the SERP preview tool shows how they'll display before they go live.
Step by step: how a technical SEO project runs
First 30 days
Crawl, Search Console review, log files if your host provides them, and the written audit. Anything blocking indexing gets fixed straight away rather than waiting for the report.
Days 31 to 60
Implementation. I make the changes myself on WordPress or Next.js, or write clear tickets for your developer and check their work afterwards. Redirect maps, canonical fixes, sitemap clean-up, template speed fixes and schema.
Days 61 to 90
Monitoring and the next layer: internal linking, thin or overlapping pages, and the pages sitting just off page one that are worth improving. Google re-crawls and re-evaluates at its own pace, so I track progress in Search Console rather than promising a date. If traffic moves suddenly, compare the date with Google's confirmed ranking updates.
Technical SEO mistakes I find again and again
- A redesign launched without redirects. It happened to this very site, and it is the most common cause of sudden traffic loss I see.
- Staging settings left live: a noindex tag or a robots.txt block copied over from the test site.
- Several URLs for the same page through parameters, trailing slashes or http and https versions, with no clear canonical.
- Important pages with no internal links, only reachable through the sitemap.
- Schema that doesn't match the page, such as review stars with no visible reviews. That is a risk, not a shortcut.
Who needs a technical SEO consultant
You'll get the most from this if your site has hundreds of pages or more, runs on a JavaScript framework, has recently been migrated or redesigned, or has good content that isn't ranking. It's also worth a one-off audit before any rebuild. If you have a small brochure site that's indexed and loading quickly, you probably need better content and local signals more than technical work, and I'll tell you that.
Results
Search Console numbers from client accounts I've worked on: one reached 21.9K clicks from 2.76M impressions over 16 months; another sits at an average position of 8.2 with 827 clicks; a third grew impressions about four times, to 14.6K, as new pages were indexed. Each SEO case study gives the period and context.
Reporting
Monthly, from Search Console and your analytics: indexed pages, impressions, clicks and average position for the pages we worked on, plus a log of every change made and when. That log matters. When something moves, we can see what caused it.
Pricing
An audit is quoted as a fixed piece of work once I know the size and platform of the site. Implementation and ongoing work are scoped separately, because a 40-page WordPress site and a 10,000-URL Next.js build need very different amounts of time.
Where this connects to the rest of my work
For industry-specific SEO see SEO for limo and chauffeur companies, med spa SEO in the USA and SEO in Saudi Arabia and the UAE. For the reasoning behind this approach, read why technical SEO pays off most on large sites and how I diagnose a traffic drop after a core update. For a worked example of location pages done without thin duplicates, see how I build airport transfer pages for limo companies.
Free technical SEO tools
Audit a page's on-page and technical basics, check whether it can be indexed, validate robots.txt and sitemaps, generate structured data, review its content for stuffing, and see whether Google is rolling out an update.
FAQ
Technical SEO questions
How long until I see changes?
Indexing fixes are often visible in 2–6 weeks. Ranking growth usually takes 3–6 months.
Do you write content too?
I plan and optimise it, so every page targets a real search and shows real expertise.
Is technical SEO worth it for a small site?
After a migration or redesign, yes, because broken redirects hurt a small site as much as a big one. Otherwise a small site usually needs a one-off audit, not ongoing technical work.
What is the difference between a technical SEO audit and a normal SEO audit?
A technical audit looks at whether Google can crawl, render and index your pages, and how fast and well structured they are. A general audit also covers content and links. I do both, but technical problems come first because they limit everything else.
Can you fix pages that are 'Crawled – currently not indexed'?
Often, yes. That status usually means Google saw the page but didn't think it was worth indexing yet: thin content, duplication or weak internal links. I find which applies to each page and fix the cause.