Technical SEO is what's wrong when nothing else is wrong.

You've published great content, you've earned legitimate backlinks, you've optimised your title tags — and rankings still aren't moving. Eight times out of ten, the cause is technical: pages Google can't crawl efficiently, JavaScript rendering that hides content from the bot, structured data errors that make rich results ineligible, slow Core Web Vitals that quietly demote you, hreflang gone wrong, or a site architecture that buries important pages five clicks deep.

Technical SEO is the layer that decides whether everything else you do has a chance to work. When it's broken, every piece of content you publish performs below its potential. When it's right, content earns rankings faster, schema unlocks rich results, and AI assistants can actually parse your pages confidently enough to cite them.

For complex platforms — Magento, Shopify Plus, Salesforce Commerce, headless CMS setups, multi-region sites with hreflang — technical SEO is genuinely difficult and most generalists get it wrong. I work directly with development teams (or your hosting provider) to ship fixes properly: tickets in your tracker, code-level specs where needed, validation in staging, and rollout plans that don't break production.

What's included

The full technical SEO stack.

  • Crawl audit using Screaming Frog and Sitebulb — identifying every URL state issue (4xx, 5xx, redirect chains, canonical conflicts)
  • Indexation analysis — what's indexed vs what should be, removing index bloat and fixing exclusions
  • JavaScript rendering review — making sure Googlebot sees what users see, especially on React/Vue/Next.js sites
  • Core Web Vitals optimisation — LCP, INP, CLS — with concrete fixes prioritised by impact
  • Structured data (JSON-LD) implementation and validation in the Rich Results Test
  • XML sitemap review and rebuild if needed; submitted to Search Console
  • robots.txt audit and fixes — including AI crawler directives (GPTBot, ClaudeBot, PerplexityBot)
  • hreflang setup and validation for multi-region/multi-language sites
  • Canonical strategy — duplicate content, parameter handling, pagination
  • HTTPS, redirects, and migration support when needed
  • Site architecture — internal linking topology, click-depth, taxonomy review
  • Server log analysis for large sites — what Googlebot actually crawls vs what you want it to
Pricing & Terms

Services start at $499 USD per month.

Identical pricing across every service. No tiered upsells, no hidden fees, no surprise contract terms.

Starting price

$499 USD / month

Our $499/month plans cover 15 to 20 hours of dedicated work per month.

Choose your commitment.

To ensure measurable results and protect your investment, we require a minimum commitment period. There is no month-to-month option.

3-Month Plan

Testing your industry

Ideal for new clients exploring what SEO can do for their sector. Lower commitment, faster decision.

12-Month Plan

Best value, maximum ROI

Full campaign lifecycle, locked-in monthly rate, deepest results. Recommended for long-term partners.

We onboard a maximum of 5 clients per service category at a time.

Capacity

Currently Active Clients

We limit to 5 per service to protect result quality. Available slots open as engagements complete or graduate to in-house.

Slot Industry / Niche Service Status Start Date
1 Vertical Institute (Education, Singapore) Active retainer Active April 2022
2 Open Available Available Apply Now
3 Open Available Available Apply Now
4 Open Available Available Apply Now
5 Open Available Available Apply Now

We do not accept two clients from the same industry for the same service. This protects your competitive advantage.

FAQ

Common technical SEO questions.

My site is on a JavaScript framework (React, Next.js, Vue). Can you handle that?

Yes. JS frameworks are where most generalists get burned because Googlebot's rendering pipeline has quirks — content loaded after first paint can be invisible, hydration mismatches break canonicals, and dynamic routes can produce indexation chaos. I check render diff (what HTML the bot sees vs what users see), recommend SSR or pre-rendering where needed, and validate in URL Inspection.

What are Core Web Vitals and do they really affect rankings?

Core Web Vitals are Google's three page experience metrics: LCP (Largest Contentful Paint, how fast the main content appears), INP (Interaction to Next Paint, how responsive the page feels to input), and CLS (Cumulative Layout Shift, how much things jump around). They're a ranking factor, but not a strong one in isolation — they matter mostly as a tiebreaker in competitive niches and as a sustained user-experience signal. I optimise them as part of a broader technical SEO program.

Do I need to migrate to a faster CMS to fix performance?

Almost never. Most performance issues on WordPress, Shopify, Magento, Squarespace, etc. are fixable without migration: image compression, lazy loading, caching, eliminating render-blocking JS, preconnecting fonts, removing bloated themes/plugins. Migration is expensive and risky, and should only happen when the platform genuinely can't deliver acceptable Core Web Vitals — which is rare.

How do I know if my site has a crawl budget problem?

For most sites under ~10,000 URLs, crawl budget isn't a real concern. For large ecommerce, news, or marketplace sites, it's critical: Googlebot has a limited budget per day, and if it spends that budget crawling parameter URLs, faceted nav loops, or thin pages, important content gets crawled less often. Server log analysis tells the truth — Search Console "Crawl Stats" gives a hint. I run server log analysis on large-site engagements.

Can technical SEO fix a Google penalty?

Manual penalties (notified in Search Console) require a separate cleanup process plus a reconsideration request. Algorithmic demotions (Helpful Content, Spam Updates, Reviews Updates) require fixing the underlying root cause — which is sometimes technical (e.g., index bloat from low-quality pages) but usually content or link-related. The first step is always diagnosis through an audit; recovery follows.

Do you handle site migrations (HTTPS, domain change, replatforming)?

Yes — and migrations are one of the highest-stakes technical projects. A bad migration can erase years of SEO equity in a week. The playbook I run includes a pre-migration audit, redirect map (every URL accounted for), staging validation, launch monitoring, post-launch fixes within 48 hours, and a 90-day stability review. Don't migrate without one.

How do you work with my dev team?

However works for them. I prefer Linear or Jira tickets with clear acceptance criteria, code snippets where useful, and links to validation tools. I'll join standups if needed, review PRs for SEO-impacting changes, and validate every fix in staging before approving. The goal is making your devs more effective at SEO, not creating extra work for them.

What tools do you use for technical SEO?

Screaming Frog and Sitebulb for crawling, Search Console for ground-truth Google data, Lighthouse and PageSpeed Insights for Core Web Vitals, Schema markup validators and Rich Results Test for structured data, server log analysers for crawl budget work, and custom scripts for things off-the-shelf tools can't do. The tool stack matters less than knowing what to look for.

Ready to fix your technical SEO foundation?

Start with a technical audit — single deliverable, deep analysis, prioritised fix list.