Technical SEO
Technical SEO fixes your site can actually ship.
We audit crawling, rendering, indexation, canonicalization, structured data and Core Web Vitals—then work with the codebase to implement the highest-impact fixes.
Technical SEO fails in practice for a predictable reason: the findings are correct and the implementation never happens. The person who wrote the recommendation cannot change a template, and the developer who can was never given the context to understand why it mattered.
ALCA runs both halves. The audit is written by people who can read your repository, and the fixes are shipped as ordinary engineering work — in a branch, reviewed, deployed and verified against Search Console afterwards.
Scope
What a technical engagement covers
Crawl and indexation
What search engines can reach, what they choose to index, and which of your valuable pages are excluded. Robots rules, orphan pages, faceted parameters, pagination and crawl-budget waste on large sites.
JavaScript rendering
Whether your content exists in the initial HTML or depends on client-side execution. We compare rendered and raw output, then move critical copy, links and metadata into server-rendered markup where they belong.
Canonicals and redirects
Self-referencing canonicals, conflicting signals between canonical tags, internal links and sitemaps, redirect chains and loops, and parameter handling that quietly splits one page into a dozen.
XML sitemaps
Sitemaps that contain only canonical URLs returning 200, segmented by page type on large sites, with lastmod values that reflect real modifications rather than the date of the last deploy.
Structured data
Schema that matches what is visible on the page — Organization, Service, Article, Product, LocalBusiness, FAQ and Breadcrumb — generated server-side and validated, not injected by a tag manager.
Core Web Vitals
LCP, INP and CLS traced to their causes: render-blocking resources, unoptimized images, layout shift from late-loading elements, hydration cost and third-party scripts. Measured at the 75th percentile on real users, not on a lab score.
Migrations and replatforms
URL mapping, redirect specification, parity checks and a post-launch monitoring plan, so a redesign or platform change does not become an unplanned traffic reset.
Log analysis when available
When server logs are accessible, we look at what crawlers actually request and how often — the only direct evidence of how a search engine spends its budget on your site.
What you receive
Every finding lands in one place, ranked, with enough specification that either team can implement it.
- A prioritized implementation backlog scored on impact, effort and risk
- Reproduction steps and the specific URLs affected by each issue
- Implementation of the agreed items, in your codebase or as reviewed pull requests
- Structured-data templates that render server-side and validate cleanly
- A Core Web Vitals baseline and the changes made against it
- Verification after deployment against Search Console and field data
What this does not promise
- No ranking or traffic guarantees. Fixing technical debt removes obstacles; it does not create demand that was never there.
- Indexation is Google’s decision. We can make a page eligible and worth indexing — we cannot force it into the index.
- Core Web Vitals targets depend on hosting, third-party scripts and marketing tags outside our control. We will tell you which of those is the binding constraint.
Frequently asked questions
Do you implement the fixes or just report them?
We implement. Our engineers work in your repository or open reviewed pull requests against it. If your team prefers to own the implementation, the backlog is specified well enough to be built from, and we review the result before it ships.
Will you work in our existing codebase?
Yes. We work in the stack you already have, on a branch, following your review process. We do not require a rebuild or a migration to our preferred framework as a condition of the engagement.
How do you handle a site that renders content with JavaScript?
We compare the raw HTML against the rendered DOM to find what a crawler sees on the first pass, then move critical content, internal links and metadata into server-rendered output. Client-side enhancement is fine; client-side-only content is a risk we remove.
Can you help with a replatform or redesign?
Yes, and the earlier we are involved the cheaper it is. We produce the URL map and redirect specification before launch, check parity between old and new templates, and monitor indexation and Core Web Vitals through the first weeks afterwards.
Related SEO services
Each of these can be scoped on its own or run as part of one program.
- Local & multi-location SEOProfiles, location pages, citations and review workflows governed consistently across every location.
- Content strategyIntent research, topic and entity mapping, briefs, expert review and the internal links that convert.
- Programmatic SEOData models, templates, quality thresholds and indexation rules for large page estates.
- Digital PR & authorityOriginal research, linkable assets, editorial outreach and legitimate citations. No paid ranking links.
- SEO audit & roadmapPrioritized findings, a 90-day roadmap and an implementation estimate — a diagnosis with a plan attached.
Find out what is actually blocking crawling and indexation
Send the site and we will tell you what we would investigate first and what an implementation engagement would involve.