Guides

Write ups of things that actually broke, and what fixed them.

There is no shortage of general SEO advice on the internet and we have no intention of adding to it. What goes here are problems we have genuinely diagnosed on live sites, written up properly, including the parts where the first two theories were wrong.

Written from real fixesIncludes the wrong turnsNo affiliate links

Currently being written

One guide is published so far, and we would rather show you an honest short list than pad it out with filler. The rest below are actually being written. If one of them would be useful to you sooner, say so and we will bump it up the list.

Planned

Five more in progress.

In progress

How to test whether the problem is the file or the cache

A short, practical method. Hit the origin directly with a cache buster and compare. It takes two minutes and it decides which half of the stack you spend the next two days in.

A method we use on nearly every diagnosis

In progress

Stopping a wp-login brute force at the Cloudflare edge

The Managed Challenge and admin allowlist setup, and just as importantly, how to check whether the attack is actually slowing your site before anyone suggests a bigger server.

From the 21,626 hits a day case

In progress

Designing a schema entity graph that does not fight itself

Getting @id relationships right, when to consolidate duplicate organisation entities, and which markup to remove rather than fix. Includes why we no longer add FAQPage markup at all.

From the Search Console entity work

In progress

Hub and spoke with split intent, and why your pages compete

Separating commercial and informational intent so your own pages stop cannibalising each other, plus a governance rule that stops a tidy internal link structure decaying back into a 25 link block.

From the DR 72 rebuild

In progress

The canonical that quietly points at a redirect

How to find it, why it is so easy to miss in an audit, and why it can hold down a page that looks perfectly healthy in every other respect.

A recurring find

Approach

How these get written.

Every guide here comes from a problem that appeared on a real site, was diagnosed properly and was fixed. That constraint rules out a lot of topics, which is the point.

They include the wrong turns. When a problem has four plausible explanations and the first two are wrong, that process is the genuinely useful part, and it is the part that usually gets edited out of tidy write ups. Knowing which check ruled out which theory is worth more than the final answer.

Where a fix carries a risk or a trade off, it says so. Some of these changes are ones we would not make on every site, and a guide that does not tell you when not to do something is not much of a guide.

No affiliate links, no tool sponsorships, and no padding to hit a word count.

Book me

Would one of these solve your problem?

If you are sitting on the exact issue one of these covers, do not wait for us to write it up. Send us the URL and we will just tell you.

Reply within one working day No obligation Your details stay with us

Takes about 60 seconds. No newsletter and no CRM sequence. Your details are used to reply to this enquiry and nothing else.