Technical SEO services from a development team
We find what is holding your site back, then we fix it ourselves. The review is free and the deliverable is merged code, not a document handed to a developer who is already busy.
const canonical = resolveCanonical(product);- <link rel="canonical" href={Astro.url.href} />+ <link rel="canonical" href={canonical} />- {variants.map(v => <link rel="canonical" href={v.url} />)}+ {variants.map(v => <link rel="alternate" href={v.url} />)}
- 1,840 product URLs now resolve to a single canonical
- Structured data revalidated on the rendered output
- Indexation tracked against the pre change baseline
Works on
- WordPress
- WooCommerce
- Shopify
- Webflow
- Custom and headless
Does any of this sound familiar?
These are the six complaints we hear most often. All of them are technical, and none of them look technical from the outside.
- Indexation
New pages take weeks to appear, or never do
Usually crawl budget spent on parameters and filters, or an internal link structure that never reaches the page.
- Rendering
The content is on the page, but Google does not seem to see it
The page assembles in the browser and not in the response. A parser gets an empty shell and moves on.
- Schema
Rich results stopped showing and nobody knows when
Structured data was pasted into a template that has since been updated, so the markup no longer matches what renders.
- Duplication
Two of our own pages compete for the same query
Canonical logic that points every page at itself, and a category tree that generates the same content under several paths.
- Performance
Our speed score is fine, but the site feels slow
Lab scores measure a simulation. Field data measures your actual visitors on their actual phones, and the two rarely agree.
- Backlog
We have an audit, and nothing on it has been built
The findings were never the bottleneck. The queue was. Somebody has to write the code, and it keeps not being anyone.
If more than one of these is true, the problem is below the content layer.
Talk to usContent sits on top of something
Everything you invest in above the base is capped by the base. That is why a content programme can run for a year and move nothing.
Most of what gets called an SEO problem is a plumbing problem. A page that is never crawled cannot rank no matter how good it is. A page whose content only exists after JavaScript runs is, to a parser, an empty page with a title.
This is also why the same fixes decide whether AI systems can cite you. They fetch, they parse, they extract. A site that is hard for a crawler to read is hard for any machine to read, and the remedy is identical.
The work is invisible when it is right, which is precisely why it keeps losing to whatever is louder on the roadmap.
The six layers we audit and fix
Each one is invisible when it works. When it fails, the symptom rarely looks technical, which is how it gets misdiagnosed.
| Layer | What it decides | What you see when it breaks |
|---|---|---|
| Crawlability | Which URLs a bot can reach, and how much of your site it bothers with | Deep pages never show up in coverage, and new pages take weeks to appear |
| Indexation | Which reachable URLs are eligible to appear at all | Pages get crawled, sit as discovered, then quietly drop out |
| Rendering | Whether a machine sees the same page a person does | Content is visible in the browser but missing from the fetched HTML |
| Structured data | What a machine understands the page to be about | Rich results disappear after a theme update and nobody connects the two |
| Performance | Whether the page loads fast enough to be used and measured well | Field data fails Core Web Vitals while the lab score looks perfectly healthy |
| Internationalisation | Which language or region version is served to whom | The wrong country's page ranks, or two versions compete with each other |
What we find, and what we ship
An audit describes an outcome. Implementation is a hundred decisions about how to reach it on your specific stack. This is where technical SEO is won or lost.
Structured data missing on product and article pages
What we do
Schema generated by the template
Built from the real page fields rather than pasted in, validated against the rendered output, and written so it survives the next theme update instead of vanishing with it.
Duplicate content and self referencing canonicals
What we do
Canonical logic corrected at the root
Fixed once in the template so every page created afterwards inherits the right behaviour, rather than forty individual corrections that come back the moment somebody adds page forty one.
Crawl budget wasted on faceted and parameter URLs
What we do
Facets, robots and linking changed together
Parameter handling, crawl directives, canonical behaviour and internal links are one system. Changed separately they contradict each other, which is how a crawl fix ends up deindexing a category.
Content not visible to crawlers or AI systems
What we do
Server rendered, semantically honest markup
Headings in order, tables as tables, key content present in the response rather than assembled later by script. A parser and a person end up with the same page, which is the whole requirement.
Audit and fix, in the same engagement
We do not hand you a list and wish you luck. Finding the problem and building the fix are the same job, done by the same people.
We find it, free
Crawl, rendered output, field performance data and Search Console if you grant access. You get the findings that are actually costing you something, ordered by impact, with the evidence attached. No charge, no obligation, and you keep the findings either way.
We build it
In your repository, on a branch, through your review process. Anything correctable at template or application level is corrected there, because a page level fix is a ticket waiting to come back the next time content is added.
We prove it
Every change ships with a baseline recorded before it and a comparison after. Indexation counts, rendered output, field data. If something did not move, we say so rather than closing the ticket and moving on.
Technical SEO in full. Not the rest of SEO
We own the technical layer end to end, finding and fixing. We are not a full service SEO agency and have no ambition to become one.
We do
- Technical audits, with evidence your team can check independently
- The implementation, in your codebase, reviewed by whoever you want
- Work to your SEO team's recommendations when you already have one
- Say plainly when a requested change would cost you something
We don't
- Keyword research or content strategy
- Link building or digital PR
- Promise positions, or sell a ranking report
- Replace the agency or consultant you already trust
Two ways to work with us
Every Developtify plan already covers technical SEO, at the level of the plan. When you want a specific problem fixed now, a one-off project gives it our full focus, quoted from the free review.
- One off
From $2,100
A defined piece of work, quoted from the free review so the number is based on your site rather than a guess. Useful when you have a specific problem and a deadline.
- Included in every plan
From $1,200 a month
Issues found in health checks are fixed on every plan. Bigger plans add a quarterly technical audit or an ongoing optimization plan. Development, maintenance and performance come in the same plan.
See pricing
Website maintenance
Ongoing care on a monthly retainer, where every update and content change is checked for search impact before it ships.
Learn moreSEO migrations
Platform changes, redesigns and domain moves planned and verified so rankings, tracking and checkout all survive the move.
Learn moreWebsite speed optimization
Core Web Vitals, render blocking, image and script weight, fixed in the code as a dedicated project or kept in check on a monthly plan.
Learn moreTechnical SEO questions
What teams usually want settled before handing over a site.
How much do technical SEO services cost?
Technical SEO is included in every Developtify plan, from $1,200 a month, at the level of the plan. A one-off project for a specific problem starts at $2,100, quoted from the free review. We publish our plans rather than making you ask for them.
Do you produce the audit, or only implement it?
Both. We find the problems and we build the fixes, which is the point of hiring developers who understand search rather than one team to diagnose and another to implement. If you already have an SEO team producing recommendations, we work to theirs instead.
If you audit your own work, who checks it?
You do, or your SEO team does. Every finding ships with the evidence behind it and every fix ships with a before and after, in a form anyone can verify independently. The alternative, an agency whose findings you have to take on faith, is the thing worth avoiding.
Our audit is a year old. Is it still worth anything?
Partly. Some findings will have been fixed by accident, some will have got worse, and some no longer apply after platform updates. We go through it with you and separate what is still real from what is not, rather than quoting to rebuild the entire list.
Can you work inside our existing development process?
Yes. Your repository, branching model, review process and ticket tracker. If your team wants to review every pull request before it merges, that is a normal way to work with us rather than an obstacle.
Does any of this help with AI search?
The same foundation decides it. A system that cannot fetch, render or parse your page cannot cite it either. Server rendered content, honest heading structure, real tables and valid structured data are what make a page machine readable, whichever machine is reading. See our AI search optimization service.
Is the review really free, and what is the catch?
It is free and the scope is fixed: a crawl, a check of what actually renders, your Search Console data if you grant access, and the findings that are costing you something. You keep those findings whether or not you hire us. We do it because it is the fastest way for both of us to know if there is real work here, and because a site with nothing wrong is not a client we want to bill.
We don't have a repository or a developer. Can you still work on our site?
Yes, and that is the most common situation. Most sites we work on run on WordPress, WooCommerce, Shopify or Webflow with nobody technical in the building. You give us access, we work on staging, and you see the before and after. The engineering detail is ours to worry about.
Which platforms do you work on?
WordPress, WooCommerce, Shopify, Webflow and custom or headless stacks. Each constrains what is possible differently, and knowing those limits up front is most of the job. If something cannot be implemented cleanly on your platform, we say so and propose what can.
Start with the free review
Send us the URL. We will tell you what is actually costing you something and what it takes to fix it, whether or not you hire us for the fix.