Technical SEO Services for Sites Where the Content Is Fine and the Rankings Are Not
Content SEO decides whether a page deserves to rank. Technical SEO decides whether it ever gets the chance. When good pages sit at position forty, the problem is usually somewhere between the crawler finding the URL and the index keeping it.
What is technical SEO?
Technical SEO is the work of making sure a search engine can find, crawl, render, index and serve your pages quickly and without ambiguity. It covers site architecture, crawl control, indexation rules, page speed, mobile rendering, structured data and the health of the underlying code — everything that determines whether a page is eligible to rank, as distinct from whether it deserves to.
That paragraph is the whole distinction. Content quality is a ranking question. Technical SEO is an eligibility question, and eligibility comes first. You can write the best page on the internet about commercial signage, and if it is behind a crawl block, rendered only in JavaScript that times out, or canonicalised to a different URL, it will never compete — and nothing in your content report will explain why.
It is invisible in content reporting
A page that was never indexed produces no impressions, so it never shows up as a loss. It simply is not there, and absence is the hardest thing to notice in a dashboard.
It compounds against you
Every new page inherits the same template, the same render path and the same schema gap. Technical debt in search is the only kind that grows while you sleep.
It gates AI search too
Answer engines crawl and render before they cite. A page an engine cannot parse cannot be quoted, so technical problems now cost you citations as well as clicks.
The fixes are usually cheap
Most of what we find is a configuration line, a redirect rule or a missing block of markup. The expensive part is the months spent not knowing it was there.
Technical, on-page, content and local SEO — what each one actually covers.
These four get used interchangeably and they are not interchangeable. They break differently, they are fixed by different people, and buying the wrong one is the most common way an SEO budget gets wasted.
| Discipline | What it governs | What it looks like when this is the problem | Who actually fixes it |
|---|---|---|---|
| Technical SEO | Whether a page can be discovered, crawled, rendered, indexed and served fast enough to compete. | Pages missing from the index entirely, or indexed but ranking far below pages that are plainly worse. | Developers and infrastructure. Almost every fix is a config change, a template change or a deploy. |
| On-Page SEO | What a single page says it is about — title, headings, internal links, markup, keyword targeting. | Pages indexed and ranking, but for the wrong query, or cannibalising each other for the right one. | An SEO working in the CMS. Usually no developer involvement at all. |
| Content SEO | Whether the page answers the question better than the ten results above it, and covers the topic completely. | Pages indexed, correctly targeted, ranking on page two, and not moving no matter how many links point at them. | Writers and subject experts. The slowest of the four to show results and the hardest to fake. |
| Local SEO | Whether you appear for searches with a place attached, and in the map pack rather than the blue links. | Strong national rankings, invisible within five miles of your own premises. | Whoever owns the business listings, reviews and location data — often not the website team. |
The practical test: if the page is not in the index, nothing on the other three rows can help you. That is why technical work is sequenced first, and why an audit that starts anywhere else is starting in the wrong place.
Range of technical SEO services we deliver.
Scoped to what your crawl actually shows, not to a standard package.
Technical SEO Audit
A full crawl with rendering enabled, reconciled against Search Console and your sitemaps, so every finding is tied to a URL count rather than a severity label.
Crawl & Index Control
Robots rules, canonicals, parameters, pagination and noindex logic — deciding what search engines are allowed to spend time on, and what they should ignore.
Site Speed & Core Web Vitals
Real-user metrics first, lab scores second. We fix what moves the seventy-fifth percentile, not what moves a synthetic number in a report.
JavaScript & Rendering
What the crawler sees after rendering, versus what your visitors see. On modern frameworks this gap is where most invisible traffic loss lives.
Structured Data & Schema
Valid markup for the entities you actually have, kept in sync with the page. Increasingly this is what decides whether an AI engine can quote you at all.
Site Architecture & Internal Links
Depth, hierarchy and link paths, so that the pages that earn money are not five clicks from the homepage and orphaned from everything else.
Redirects & Migrations
URL mapping, redirect chains, staged QA and a rollback plan. The single highest-risk technical event any site goes through.
Log File Analysis
What the crawler actually requested, how often, and where it gave up. The only source that tells you the truth rather than an estimate of it.
Five stages between publishing a page and ranking it.
A page has to survive all five. It only takes one to fail, and the symptom at the end looks identical whichever stage caused it — which is why technical problems get misdiagnosed as content problems so often.
The engine has to learn the URL exists — from a sitemap, an internal link or an external one.
What breaksOrphaned pages with no internal links, sitemaps that list URLs which redirect, and pages only reachable through a search box or a filter.
The URL is requested. How often depends on how much crawl capacity your site has earned and how much is being wasted.
What breaksRobots rules blocking the wrong paths, faceted and parameter URLs consuming the budget, slow responses reducing crawl rate, and long redirect chains.
The page is executed, JavaScript included, to produce the version the engine will actually read.
What breaksContent injected client-side after a timeout, links built as click handlers rather than anchors, and blocked scripts that leave the main content empty.
The rendered page is assessed and either stored as a candidate for queries, or discarded.
What breaksCanonicals pointing elsewhere, stray noindex tags left from staging, near-duplicate pages collapsing into one, and thin templated pages judged not worth keeping.
The page competes for queries, and what appears in the result is assembled from your markup.
What breaksSlow real-world load at the seventy-fifth percentile, layout shifting on mobile, and missing or invalid schema that costs you the enhanced result.
This is also the order the work has to happen in. Fixing schema on a page that is blocked in robots.txt is effort spent on stage five while stage two is still failing — and it is remarkably common, because stage five is the one the tools report on most loudly.
The technical SEO checklist we run, in full.
Published rather than summarised, because there is no advantage in keeping it vague. If you want to run it yourself, run it — most of it needs a crawler and an afternoon.
- Robots.txt — every rule tested against a sample of real URLs, not read by eye
- XML sitemaps — present, current, and free of redirected or non-indexable URLs
- Orphan pages — anything in the sitemap or logs with no internal link pointing at it
- Crawl depth — how many clicks from the homepage your revenue pages actually sit
- Redirect chains — hops, loops, and any chain longer than one
- Parameter & facet handling — what is crawlable that should not be
- Server response codes — real 404s, soft 404s, and 5xx under crawl load
- Log file sample — what the crawler requested, how often, and where it stopped
- Rendered vs raw HTML — what survives execution, and what only exists client-side
- Canonical logic — self-referencing where it should be, and consistent with the sitemap
- Indexation reconciliation — crawl against Search Console, URL by URL
- Duplicate & near-duplicate — templated pages that differ by one noun
- Core Web Vitals — field data at p75, split by template and by device
- Mobile rendering — parity of content and links, not just a responsive layout
- Structured data — validity, coverage, and whether it matches the visible page
- HTTPS & hreflang — mixed content, certificate chain, and language targeting errors
Technical SEO fixes what is wrong. Enterprise SEO fixes what nobody can change.
If you know roughly what is broken and the blocker is finding time and expertise, this is a technical engagement and it is the cheaper, faster one. If the problems are already understood and the real difficulty is getting anything shipped across templates, teams and release cycles, that is enterprise work. Plenty of sites need the first and are quoted for the second.
Send us one URL.
We will run it through all five pipeline stages and send back where it drops out, with the raw crawl output. No call, no deck, no obligation.
Get the Five-Stage CheckInvisible for its own products, then first for all three.
Seaborn Manufacturing’s pages existed and earned nothing, because nothing that mattered was eligible to rank. The terms below are the ones its buyers actually search.
- “laser pipe cutting”— → #1
- “laser tube cutting”— → #1
- “cnc tube bending service”— → #1
- Impressions per month9,412 → 49,573
Technical work rarely gets its own case study, because it does not look like anything — nobody photographs a corrected canonical. What it looks like is this: pages that were always good enough finally being allowed to compete.
Five steps from crawl to verified fix.
Crawl with rendering on
A full crawl that executes JavaScript, plus a log file sample where we can get one, so we are looking at what the engine sees rather than what the CMS claims.
Reconcile against the index
Crawl output matched URL by URL against Search Console and your sitemaps. The gap between what exists, what is eligible and what is indexed is the audit.
Sequence by pipeline stage
Findings ordered discovery first, serving last, so nothing gets fixed on a page that is still blocked two stages earlier. Each one carries its affected URL count.
Implement or hand over
We make the changes ourselves where we have access, or write them as tickets your developers can take into a sprint without translating anything first.
Re-crawl and verify
The same crawl run again against the same URLs. A fix is not done because it was deployed; it is done when the pipeline shows the page surviving the stage it used to fail.
$ mdg crawl --compare baseline
✓ 2,232 orphans now linked
✓ 273 render timeouts resolved
✓ 2,863 canonicals corrected
✓ p75 first byte 1.9s → 0.6s
✓ schema valid on 8 templates
_
Do you need an agency for this?
Often not. Technical SEO is the most self-serviceable part of search, and we would rather say so than sell you a retainer you do not need.
Do it yourself
Small site, one person with site access, and you are willing to learn a crawler. The checklist above is the whole job. Free tiers of the common tools will cover a few hundred URLs, which is plenty.
Buy an audit once
You have a developer who can implement but nobody who can diagnose. A one-off audit with ticket-ready findings gets you the list; your team ships it. This is the most common engagement we run.
Bring someone in
Rendering problems on a JavaScript framework, a migration coming, or a site where the same issues keep returning after every release. Those need someone in the release cycle, not a PDF.
Start with where pages drop out.
Send us your domain and read access to Search Console. We will come back with how many URLs we found, how many survive each of the five pipeline stages, which template accounts for the biggest drop, and what the first three fixes are worth in pages recovered. If the honest answer is that you can do this yourself, that is what we will tell you.
Technical SEO, explained plainly.
What is technical SEO?
Technical SEO is the work of making sure a search engine can find, crawl, render, index and serve your pages quickly and without ambiguity. It covers site architecture, crawl control, indexation rules, page speed, mobile rendering, structured data and code health — everything that determines whether a page is eligible to rank, as distinct from whether it deserves to.
What is the difference between technical SEO and on-page SEO?
Technical SEO decides whether a page can be indexed and served at all. On-page SEO decides what an already-indexed page is understood to be about — its title, headings, internal links and keyword targeting. The simplest test: if the page is missing from the index, it is a technical problem; if it is indexed but ranking for the wrong query, it is an on-page one. Technical work is also usually done by developers, on-page work by an SEO in the CMS.
What is the difference between technical SEO and content SEO?
Technical SEO is an eligibility question and content SEO is a quality question. Technical determines whether the page reaches the index; content determines whether it beats the ten results above it once it is there. They fail in different ways — a technical failure shows up as absence, with no impressions and no errors, while a content failure shows up as a page that is indexed, correctly targeted and stuck on page two.
How often should you run a technical SEO audit?
A full audit once a year for a stable site, and always before and after a migration, a replatform or a redesign. Between those, a monthly crawl comparing against the previous one catches most regressions early — technical problems are usually introduced by a release rather than appearing on their own, so the useful cadence follows your deploy schedule rather than the calendar.
Can I do technical SEO myself?
A lot of it, yes. If you have one site, access to change it and the patience to learn a crawler, the checklist on this page is genuinely the job, and the free tiers of the common tools cover a few hundred URLs. It gets harder when JavaScript rendering is involved, when the fixes need a developer who is not you, or when the same problems keep coming back after every release — at that point the constraint stops being knowledge and starts being access.
How long does technical SEO take to show results?
Faster than content work and slower than people hope. Indexation fixes can move within days of a re-crawl because you are removing a block rather than earning anything. Speed and Core Web Vitals improvements need about a month of field data before they register. Anything that depends on the engine re-crawling a large number of URLs is governed by your crawl rate, which is itself one of the things being fixed.
Does technical SEO matter for AI search?
More than it did for traditional search, not less. Answer engines crawl and render pages before they quote them, so a page that fails at rendering or indexation cannot be cited no matter how well it answers the question. Structured data and clean, parseable markup carry additional weight because they make the content unambiguous to a model that is extracting an answer rather than ranking a list.
The pages costing you most are the ones that were never indexed.
They generate no impressions, trigger no errors and appear in no report. The only way to find them is to crawl the site and compare what exists against what the index actually holds.
REPLY WITHIN ONE BUSINESS DAY · NO SPAM, EVER
