Skip to content

Guides on technical SEO, accessibility, and site structure

Every article on this blog starts from a real finding in a real audit — a rule that fired against an actual site, a fix that actually worked, and enough detail that you could apply it to your own pages this afternoon. We write about the same categories Fixture Scanner checks: technical SEO, on-page signals, structured data, accessibility, content depth, and how well a page holds up for an AI crawler trying to extract an answer from it.

We keep the list short on purpose. Rather than publishing often for its own sake, each author writes when they have something specific worth explaining — usually after fixing the same issue for the third or fourth client and realizing it deserved a proper writeup instead of another one-off Slack message. That’s also why each post carries a named author with their own background: the advice here comes from people who have actually done the work, not an anonymous editorial voice.

Latest articles

Why we write about our own audit findings

Most technical-SEO content on the web is written to rank for a keyword, not because the author fixed the problem themselves last week. We write the opposite way: someone on our team hits a real issue while auditing a client site or dogfooding Fixture Scanner against our own pages, fixes it, and only then decides whether the fix generalizes well enough to be worth a full writeup. That’s a slower publishing cadence than most engineering blogs, but it means every recommendation here has actually shipped somewhere.

The two categories we return to most are structured data and Core Web Vitals, because they share a property that makes them easy to get subtly wrong: the markup or the image tag looks correct at a glance, and the mistake only shows up once you check it against the actual validator or the actual field-measured metric. Our structured data checklist and responsive images guide both walk through exactly that kind of quiet failure.

What to expect from a post here

Every article follows the same shape: a short introduction stating the problem, a breakdown of the specific mistakes that cause it, a working pattern you can copy directly, and a short FAQ addressing the follow-up questions we actually get asked. We’d rather publish four thorough guides a year than forty shallow ones, so the list above will stay short — check back periodically, or read the resource hub in the meantime for the external standards we reference most.

Who writes these

Every post here carries a named author with their own background in the field, rather than an anonymous house voice. That’s a deliberate choice: when an article says a particular fix worked, we want you to be able to see who made that claim and what they actually do day to day. Our current author roster works directly on the crawler and rule engine behind Fixture Scanner, so the guidance here reflects the same logic the product checks for automatically — nothing in a post here contradicts what the scanner itself would flag on your own site.

Looking for external standards instead of our own writing? The resource hub links out to the W3C, MDN, and Google Search Central documentation we reference most often.