Technical SEO

When the content is fine and nothing ranks anyway.

There is a particular kind of stuck where you have done the work, published the pages, earned some links, and the graph stays flat. Often the problem is not what is on the site. It is whether search engines can reach it, read it, and trust it enough to serve it. Finding and fixing that is work we do for clients, and if the problem turns out to be something else we will say so.

Get it looked at
The layer underneath

What technical SEO actually covers

Content and links get the attention. This is the part that decides whether either of them counts.

Crawling and indexing

Whether Google can find your pages and whether it chooses to keep them. A broken robots.txt is rarer than the internet suggests. A stray noindex is not, and it is what we most often find on sites that arrive already knowing something is wrong.

Site structure and internal links

How pages connect tells search engines what matters. Pages nobody links to get crawled less and rank worse, which is a problem we find on a lot of sites that have grown one page at a time.

Core Web Vitals, honestly

The score itself is not a ranking factor. It is a baseline. A painfully slow or unstable site will hold you back, but going from acceptable to excellent rarely moves rankings on its own. We have written about why, because teams do the work, watch the scores improve, and are then disappointed when nothing happens.

JavaScript rendering

We prefer server-side rendering, and we have written about why. If your pages assemble themselves in the browser after load, we check what a crawler actually receives rather than what you see on screen.

Structured data

Schema markup that describes your business, products, articles and FAQs in a form machines read directly. It shapes how your result looks, and increasingly how AI assistants summarise you.

Page builder bloat

The single biggest speed problem we see on WordPress is Elementor, and bloated page builders generally. They are pleasant to work in and they ship an enormous amount of markup and script to do things that need very little of either. Sometimes the fix is configuration. Sometimes it is getting off the builder.

Hosting

We do not refuse to work with any host. We do prefer a fast dedicated cloud host, shared hosting is fine when it is good enough, and when it is not we move people. Slow hosting is one of the few problems you cannot optimise your way around.

How it goes

Diagnose first, then fix

Technical SEO goes wrong when people apply a checklist without checking what is actually broken. We work the other way round.

  1. Crawl the site the way a search engine wouldNot a spot check on the homepage. A full crawl that surfaces redirect chains, orphaned pages, broken canonicals, blocked resources and everything returning a status code it should not.
  2. Compare that against what Google has actually indexedSearch Console tells you which pages Google chose to keep and which it silently dropped, along with why. That gap between what you published and what got indexed is usually where the answer is.
  3. Check what a crawler receives, not what you seeEspecially on JavaScript-heavy sites. If the important content only appears after scripts run, we find out whether it is being indexed at all.
  4. Measure speed on real page templatesYour homepage is rarely the problem. We test the templates that carry your money pages, on the connections your customers actually use, and trace slowness back to its cause rather than its symptom.
  5. Prioritise by what it will changeEvery audit produces a long list. Most of it does not matter. We sort by likely impact against effort, and say plainly which items are housekeeping and which are the ones that will move something.
  6. Fix it, or hand it overWe can implement directly, or write it up for your developers with enough detail that nobody has to guess. Either way you get the reasoning, not just the instruction.
Straight answer

Who this is for

Technical SEO is not always the bottleneck, and we will tell you if it is not yours.

Worth doing if

  • You publish good content and rankings do not respond
  • Search Console shows far fewer indexed pages than you have
  • Your site is large, or generates pages automatically
  • It is built on a JavaScript framework and you are unsure what gets indexed
  • Traffic dropped after a redesign or a platform change

Something else first if

  • You have very few pages and none of them target anything searched for
  • You are moving platforms, where migration comes first
  • Your problem is local visibility, which is local SEO
  • You do not yet know what is wrong, in which case start with an audit
  • The site converts badly rather than ranks badly, which is CRO
Related

The rest of our SEO work

Technical work usually runs alongside one of these rather than on its own.

Questions

Technical SEO, answered

Important Notice

We are aware of a scam involving emails claiming to be from The 215 Guys about Website Accessibility or Maintenance. That’s not us! Always verify that emails come from our official domain: @the215guys.com