Skip to content

Service

Technical SEO

Crawlability, indexation, site architecture, speed and everything between the server and the search result.

Most sites that underperform are not losing to better content. They are losing to duplicate URLs, crawl budget spent on parameters, pagination that hides half the catalogue, slow templates, or a rendering setup search engines quietly disagree with. I find the mechanism and fix it, either hands-on or with a precise specification for your team.

Mobile PageSpeed scoreSee the case study
61 → 93
Site errors in the auditSee the case study
2,339 → 2
Top-three rankings in two monthsSee the case study
17 → 99

Why it matters

What is at stake.

Content and links can only work on pages search engines are able to crawl, render and keep in their index. When the technical layer is wrong, every other investment in SEO is quietly discounted, and the loss rarely shows up as a single obvious error.

Technical problems also compound with size. A template-level fault on a site with thousands of pages is thousands of faults, which is why fixing one well-chosen issue can move a whole site at once.

Workflow

How the work runs.

Each step builds on the evidence from the one before, and every finding is checked against the live site before it becomes a recommendation.

  1. 01

    Crawl and access

    Crawl the site with the settings the later checks actually need, and test robots rules, response codes and real search and AI crawler access at the server, not only in robots.txt.

  2. 02

    Indexation and canonicals

    Reconcile the sitemap, the crawl and what Search Console says Google has indexed. The gaps between the three are where duplicate content, canonical conflicts and orphaned pages hide.

  3. 03

    Speed and Core Web Vitals

    Separate real-user field data from lab scores, test the key templates on a real mid-range phone, and trace slow pages to their cause before choosing a fix.

  4. 04

    Structure and linking

    Audit URL structure, navigation, internal links and structured data from the page markup itself, so authority flows to the pages meant to earn money.

  5. 05

    Fix, verify, measure

    Implement the changes or specify them for your team, confirm each one against the live page, and track indexation, rankings and speed against the baseline.

Results

What it can bring.

  • More of the right pages indexed, and fewer wasted URLs competing with them.
  • Faster pages that pass Core Web Vitals for real users.
  • Rankings that recover or grow once the technical ceiling is removed.
  • A site that search engines and AI crawlers can read without guessing.

Typically includes

  • Crawl, index and log analysis
  • Indexation and canonicalization
  • Redirects and migrations
  • Site architecture and URL design
  • Core Web Vitals diagnosis and fixes
  • Structured data implementation

In practice

How this worked on a large listing site

A New York commercial listings site: mobile PageSpeed from 61 to 93, site errors from 2,339 to 2, and #1 rankings back above where they started.

Common questions

Questions about Technical SEO.

How quickly do technical SEO fixes show results?
Changes that affect what Google indexes usually show in Search Console within two to six weeks. On one coupon site, top-three rankings went from 17 to 99 within two months of the fixes going live.
Do you need developer access to fix technical issues?
Not always. Many fixes can be made directly in the CMS, the SEO plugin, the markup or the CDN, and I can do those myself. Where a change needs code or server work, I specify it precisely for whoever owns that part of the stack.
What is included in a technical SEO audit?
Crawlability and crawler access, indexation, canonicals and redirects, site architecture and internal linking, page speed and Core Web Vitals, structured data, and mobile usability. Every finding is checked against the live page and ranked by its impact on search visibility.
What is crawl budget, and does it matter for my site?
Crawl budget is how much of your site search engines are willing to crawl in a given period. It matters most on large sites with filters, pagination or many near-duplicate URLs, where crawlers can spend their time on pages that should never rank instead of the ones that should.
Do Core Web Vitals affect rankings?
They are a ranking signal, but rarely the deciding one on their own. Their bigger effect is on users: slow, unstable pages lose visitors and conversions. Real-user data from Chrome matters more than a lab score, which is why both are measured separately.
Can you help with a website migration?
Yes. A migration is planned before launch with a full URL map, redirects, and checks on canonicals, internal links and structured data, then monitored afterwards. If a migration has already caused a traffic drop, the same checks identify what went wrong.

Need help with Technical SEO?

Describe what is happening on your site. You will get a direct answer about what I think is going on, how I would approach it, and whether it is work I should be doing.