Technical SEO
Technical SEO services
The engineering half of search: how fast pages render, whether crawlers can reach and understand them, and whether the signals you send about duplication, language and structure are the ones you intended.
Problems this solves
- Pages are in the index but the wrong versions of them are - with parameters, with and without www, or in the wrong language.
- The site scores badly on Core Web Vitals and the report names a metric rather than a cause.
- Content only appears after JavaScript runs, so what crawlers receive is close to an empty page.
- A multilingual site has the two language versions competing, because hreflang is missing or not reciprocal.
- The sitemap contains redirects, 404s and pages that are not canonical.
- Structured data is present, invalid, and describing things that are not on the page.
Who it is for
Sites that are slow, hard to crawl or invisible in search despite having content worth finding - and multilingual sites where canonical and hreflang need to be correct rather than approximately right.
What is included
Core Web Vitals
Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift traced to the specific asset, script or layout rule causing them, then fixed and re-measured.
Crawlability and rendering
What a crawler actually receives, checked against the rendered page: server-rendered content, real anchors rather than click handlers, correct status codes, and no important resource blocked.
Indexing signals
Self-referencing canonicals, reciprocal hreflang, redirect maps for migrations, a sitemap containing only canonical 200 URLs, and robots rules that block what should be blocked and nothing else.
Structured data
Valid JSON-LD that matches what is visible on the page, with stable identifiers connecting the entities rather than a separate disconnected block per page.
What you receive
- A written audit with findings ranked by impact and effort
- Implemented fixes, not just a list of recommendations
- Before-and-after performance measurements
- Corrected canonical, hreflang, redirect and robots configuration
- A regenerated sitemap containing only canonical, indexable, 200 URLs
- Valid structured data matching visible page content
- Automated checks added to your build where the codebase allows it
How we work
- 01
Audit
Measure performance, crawl the site, and record the current indexing signals.
- 02
Fix
Resolve the technical issues in order of impact, with each change measured.
- 03
Structure
Metadata, structured data and internal linking put in order.
- 04
Verify
Confirm against real crawls and Search Console, not just a local score.
Performance, accessibility and search
Fixes that hold
Where the codebase allows it, the rules become automated checks that fail the build - duplicate titles, missing canonicals, non-reciprocal hreflang, invalid JSON-LD - so the same problem cannot return silently.
Accessibility as a shared win
Heading order, landmarks, alt text and focus handling improve both assistive technology and how well a page can be parsed. They are treated as one job.
Honest reporting
We report what changed and what it measured, and we do not promise rankings. Anyone who does is either guessing or lying.
What we build with
- Server-side rendering
- JSON-LD structured data
- Core Web Vitals instrumentation
- XML sitemaps
- Canonical and hreflang
- Automated build-time validation
Integrations
- Google Search Console
- Analytics
- Existing CI and build pipelines
- CDN and hosting configuration
- Log file sources where available
Cost and timeline
We do not publish fixed prices or delivery times, because scope changes both by an order of magnitude. You get both in writing, specific to your project, before any commitment.
What drives the price
- Size of the site and the number of distinct templates
- Whether we implement the fixes or hand them to your team
- Whether the codebase is accessible and can be changed
- How much of the problem is rendering strategy rather than configuration
- Whether a multilingual or multi-region setup is involved
- Whether ongoing monitoring is wanted after the initial work
What drives the timeline
- Access to the code, hosting, analytics and Search Console
- How much of the fix list needs coordination with another vendor
- Whether performance problems come from third-party scripts you do not control
- How quickly changes can be deployed
- Re-crawl and re-index time, which is outside anyone's control
Related work
- Commerce
Avangard Parts - Automotive Parts Store
A completed automotive e-commerce platform with a bilingual catalogue, fast product discovery and custom administration.
Read the case study - Systems
Bookyra - Salon Scheduling Platform
Salon reservation platform for beauty professionals, with schedules, reminders, invoicing, public profiles and operator dashboards.
Read the case study
Frequently asked questions
No. This is the technical foundation - rendering, speed, markup, structured data and indexing signals. It makes good content able to rank; it does not create the content, and it will not rescue a page nobody wants to read.
No, and neither can anyone else. Rankings depend on competition, content and factors nobody controls. What we can guarantee is that the technical reasons for not ranking are removed, and that the change is measurable.
Yes. Reciprocal hreflang, a deliberate x-default, per-language canonicals and correct language attributes are a core part of this work - it is exactly the setup running on this site.
Yes, that is most of this work. We audit and fix technical SEO on existing sites regardless of the platform, including WordPress and Shopify.
Performance improvements are visible immediately in measurement. Indexing changes take as long as re-crawling takes, which varies by site and is not something we or you control.
Related services
Ready to start?
Tell us about your project and we will come back with a clear, honest plan.
Start a project