Technical SEO specialist

I find why good pages aren't crawled, indexed or shown, then fix the cause at template level. I got JerseyGram's Google manual penalty lifted in four weeks.

Illustration for technical seo/2003014041.2sLCP

What I do

01

Crawl and index diagnosis

I compare the URLs Google can find with the URLs you meant to publish, using Search Console and a Screaming Frog crawl. A large gap usually means a template, plugin or importer is creating URLs nobody planned.

02

Speed and rendering

I fix Largest Contentful Paint and layout shift at template level. JerseyGram's LCP fell from 4.8 to 1.2 seconds, helped by lazy loading and WebP images.

03

Migrations and redirects

I map every URL, redirect it with a 301 and carry over metadata, canonicals and schema. JerseyGram moved domains with every URL redirected, and Grey moved 850+ pages to a new CMS.

04

Recovery and penalties

I work out whether a drop is technical, a penalty or an update, then fix it in order. At JerseyGram that meant closing backdoors first, then a disavow file covering 92% of harmful links.

How I work

  1. 1

    Crawl

    Crawl the site and pull Search Console coverage to compare discovered, indexed and intended URLs.

  2. 2

    Diagnose

    Trace each gap to a cause: template, plugin, redirect, rendering or server. Check dates against Google's Search Status Dashboard before blaming an update.

  3. 3

    Specify

    Write each fix as a ticket a developer or no-code builder can ship once, with acceptance criteria.

  4. 4

    Verify

    Re-crawl after release and watch the indexing trend, not only the status label.

  5. 5

    Monitor

    Set a regular crawl and a Search Console check, so small dips are caught before they become cliffs.

Proof

Who I help

Sites with a sudden traffic drop that need the cause found before the next update.

Teams planning a migration to a new CMS, domain or URL structure.

Large or template-built sites where plugins and importers can quietly create new URLs.

Lean teams without SEO engineers who need fixes written so they can be shipped once.

Tools and stack

  • Google Search Console
  • Screaming Frog
  • Ahrefs
  • Semrush
  • GA4
  • PageSpeed Insights
  • Schema.org validator
  • Webflow
  • Strapi

Related skills

All skills
Illustration for seosearch#1#2#3AI answercited: you+2 sources

Marketing skill

SEO, AEO & GEO expert

Afeez AdebayoSkill

Related case studies

All case studies

Questions

How do you tell a technical problem from an algorithm update?

I compare the URLs Google can find with the URLs you meant to publish, then check the drop's date against Google's Search Status Dashboard. On a site I run, discovered URLs far exceeded published pages, and a crawl found more than 12,000 indexable URLs against about 4,000 expected. The updates exposed that fault. They did not create it.

What does a technical SEO audit cover?

Crawlability, indexation, rendering, canonicals, redirects, sitemaps, internal links, structured data and Core Web Vitals, plus the CMS and plugins that generate URLs. I rank findings by what blocks revenue pages first, and write each fix as a template-level ticket so one release helps every page. You get a ranked list, not a long export.

How do you prioritise technical fixes?

By what stops important pages being found, then by how many pages a fix touches. Security and indexing faults come before speed work. At JerseyGram we closed the malware backdoors before asking Google to lift the penalty. Cosmetic issues go last, however many a crawler reports.

How long do technical fixes take to show in rankings?

It depends on how quickly Google recrawls and reassesses the site. JerseyGram's penalty was lifted within four weeks. On a content site I run, clicks stayed flat for four months after the clean-up before recovering in late September 2026. I cannot promise a date, so I track the indexing trend and report it.

Do you work with our developers or in a no-code stack?

Both. At Grey I delivered the SEO programme without an engineering team, through no-code tools and automation, and I moved 850+ pages from Webflow to Strapi. With developers, I write acceptance criteria and check each release. Either way, a fix should be specified once so that it applies to every page using the template.

Need to know why your pages are not being indexed?

Tell me what you are working on. I reply within two working days.

Book a free call