The half of SEO that has a definite answer

We treat SEO as an engineering problem, because the half of it that actually moves is engineering.

Start a conversation→ Content writing→

Discipline: Technical SEO
and content
Checklist: Nearly eight hundred
line items
Measured on: Real page loads,
not a lab score
Location: Cape Coral, FL
Working remotely

What we can control, and what nobody can

Starting with the honest part

No one can promise you a ranking. Anyone who does is either guessing or counting on you not to check.

What can be controlled is whether a search engine can crawl your site quickly, render it correctly, understand what each page is about, and find a reason to prefer it. That is technical work with a definite answer, and it is where we start.

A ranking is an outcome. Crawlable, fast and understood are decisions.

The technical pass

Finding out which line items apply

Our internal technical SEO checklist runs to nearly eight hundred individual line items. Not all of them apply to any one site; the audit is the process of finding out which do.

Crawl → render → understand → preferAudit stages

Each stage has to hold before the next one is worth working on. The tracks below are measured on real page loads, not a lab score.

Crawl and index

Robots directives, sitemaps, canonicals, pagination, redirect chains, orphaned and duplicate pages

Core Web Vitals

Largest contentful paint, interaction latency and layout shift, measured on real page loads rather than a lab score

Structured data

Schema for organisation, local business, services, articles, breadcrumbs and FAQs, validated rather than assumed

Internal linking

Making sure the pages you care about are the pages the site itself points at most

Machine-readable surfaces

Including an llms.txt, because a growing share of discovery now happens through AI assistants rather than a results page

Then the part that is not technical

A crawlable page about nothing ranks for nothing

A perfectly crawlable page about nothing still ranks for nothing. Once the technical floor is in place, the work moves to pages that answer a real question a real buyer has — which is content writing and blogs as a service.

We are a software firm that also does this, which has one practical advantage: when the fix is in the theme, the template or the server, we make it rather than filing a ticket with whoever built the site.

787line items on the internal technical checklist

12+industries the work has run in

20+client engagements delivered

Asked before every engagement

Answered the same way every time

/01Can you guarantee a first-page ranking?

No, and neither can anyone else. What we can commit to is the technical floor: that the site can be crawled quickly, renders correctly, is understood by a machine, and gives a search engine a reason to prefer it. Those have definite answers and we report against them.

/02Do you fix what you find, or hand us a report?

We fix it. Being a software firm is the practical difference — when the problem is in the theme, the template or the server, we make the change rather than filing a ticket with whoever built the site.

/03Does any of this matter now that people ask an AI instead?

It matters more. The same things that make a page crawlable and unambiguous to a search engine make it usable to an assistant, which is why we ship machine-readable surfaces including an llms.txt as part of the technical pass.

/04What if the honest answer is that our site is fine?

Then that is what we will tell you, and we will say where we think the problem actually is. It is usually the cheaper conversation.

Want to know what is actually wrong with your site?

We will run the technical pass and tell you what we find, including if the honest answer is that your site is fine and the problem is elsewhere.

Start a conversation→ Blogs as a service→