Your content isn't the problem. Google can't read the site.
The plumbing that decides whether your content ever gets a chance to rank — crawling, indexing, speed and schema, on WordPress.
Most small business sites have a technical problem nobody has ever told them about. A canonical tag pointing at the wrong page. A noindex left on after a redesign. A homepage that takes six seconds on a phone. A plugin quietly redirecting a URL in a loop.
None of these produce an error message. The site looks fine. It just doesn’t rank, and nobody can explain why — so the usual advice is “write more content”, which costs money and fixes nothing.
I find those problems and fix them. Everything I check, I’ve had to fix on my own site first, and I’ve published what happened including the parts where I was wrong.
Everything in the programme.
Full crawl and index audit
What Google can actually reach, what it's ignoring, and what it's indexed that should never have been public. Most sites have pages in the index nobody knew existed.
Canonical and redirect check
The two things that silently remove a page from search. A canonical pointing at the wrong URL tells Google to ignore that page entirely — and nothing on the site looks broken.
Core Web Vitals and speed
Real measurement on a phone connection, then the fixes: image compression, render-blocking scripts, and the plugins costing you more than they're worth.
Schema markup, written properly
LocalBusiness, FAQ, Article, Breadcrumb — hand-written and validated, not generated by a plugin that guesses. This is what wins the extra space in search results.
Plugin and theme audit
Which plugins are slowing you down, which are duplicating each other, and which are fighting your SEO plugin. Two plugins writing the same meta tags is worse than none.
A written fix list, in priority order
Every issue found, ranked by what it costs you, with the fix explained in plain language. Yours to keep — you can hand it to any developer, including one who isn't me.
How the work actually runs.
Measure before touching anything
Current indexed pages, Core Web Vitals, and where you rank for your main terms. Without a baseline nobody can prove the work did anything — including me.
Find what's blocking, not what's imperfect
Every site fails some audit tool check. I'm looking for the handful of issues actually costing you visibility, not a 200-item report that makes you feel bad.
Fix, on a staging copy first
Technical changes break things. I test on a copy, then apply to the live site, so the worst case is a wasted afternoon rather than a site that's down.
Re-measure and hand over the list
Same numbers, same format, four weeks later. Plus the written fix list, so you know what was done and what's still outstanding.
Results from this service.
No case study for this service yet.
Honest answer: I haven’t run this for a paying client yet. What I do have is the work on my own site — hypothesis, method and numbers, published in full.
Priced before we start, not after.
You get a written scope and a fixed number before any work begins, so there is no invoice at the end that surprises you. If the job turns out to be bigger than we thought, I tell you at the point I find out — not when the bill arrives.
Common questions about WordPress + Technical SEO.
What counts as a technical problem, exactly?
Anything that stops Google reading, understanding or trusting your site — separate from what the site actually says. Wrong canonical tags, accidental noindex, slow loading, broken redirects, missing or invalid schema, pages that can't be crawled. The common thread is that none of them show an error. The site looks fine to you and to your visitors. It just quietly doesn't rank.
Will you break my site?
That's the right question to ask, and the honest answer is that technical SEO work carries real risk — which is why I test on a staging copy before touching anything live, and take a full backup first. I've broken my own site more than once while learning. That's exactly why I don't experiment on yours.
How much of this can I see for myself?
More than you'd think. Right-click any page, choose View Source, and search for "canonical" — that one line tells you which URL your page claims to be. I'll show you how to check the basics yourself, because a client who can spot a problem early is worth more to me than one who depends on me for everything.
Do you do this for anything other than WordPress?
The principles are the same anywhere, but I work fastest on WordPress and that's where most small businesses are. If you're on Shopify, Wix or something custom, I'll tell you honestly whether I'm the right person before we start rather than after.
What are you not able to do yet?
Log file analysis at scale, JavaScript rendering problems on large single-page applications, and enterprise crawl budget work on sites with hundreds of thousands of URLs. If your problem is one of those, I'd be learning on your money, and I'd rather say so. For a small business site on WordPress, I can do all of it.
Articles on WordPress + Technical SEO.
First articles publishing this week.