Crawl and indexability audit
Status codes, redirect chains, canonicals, robots, sitemap, internal links, language signals, duplicate routes, and initial HTML.
Performance and technical SEO / Release rescue
Make the release fast, crawlable, and explainable.
Opportunity Relay investigates the delivery path from HTTP response to rendered interface: status codes, canonical signals, initial HTML, routes, assets, interaction cost, accessibility, and measurement. Fixes are prioritized by user and search impact.
When this service fits
Start with the delivery condition, not the technology.
A verified release with fewer crawl traps, clearer ownership of canonical URLs, and concrete evidence for the highest-impact performance fixes.
- A redesign or migration introduced indexing, redirect, canonical, or metadata uncertainty.
- A Next.js or JavaScript-heavy site is slow or incomplete in the initial HTML.
- A team needs a bounded technical SEO and performance rescue before broader content work.
Delivery scope
The release is made of reviewable outputs.
Exact scope depends on the repository, product, integrations, and acceptance criteria. These are the working categories—not a promise that every project needs every item.
Performance diagnosis
LCP path, image and font delivery, JavaScript cost, layout shifts, long tasks, caching, rendering strategy, and third parties.
Priority fixes
Small, reviewable implementation changes ordered by access, indexing, conversion, and performance impact.
Regression controls
Build checks, route assertions, metadata scans, redirect tests, and a launch checklist that can run again after the engagement.
Questions resolved before the schedule is trusted.
Unanswered operating questions become implementation rework. They belong in the scope conversation, not at the end of QA.
- 01
Does every important URL return the intended status, canonical, and crawlable content?
Clarify the intended result and who can approve it.
- 02
Which asset or task actually controls LCP and interaction readiness?
Make system, data, and responsibility boundaries explicit.
- 03
Are route, locale, sitemap, and redirect rules generated from one source of truth?
Agree on evidence before calling a behavior complete.
- 04
Which findings can be reproduced in tests instead of remembered in a launch document?
Assign ownership for release and operation.
Working sequence
A visible path from uncertainty to handoff.
Each phase creates an artifact the buyer can inspect. The work does not depend on a final reveal.
- 01
Capture the baseline
Record routes, responses, rendered states, accessibility findings, lab performance, and configuration before changing behavior.
Output: Evidence-backed issue inventory - 02
Fix access and signals
Resolve status, redirect, canonical, robots, sitemap, initial HTML, and broken-link defects before decorative optimization.
Output: Stable crawl and indexability contract - 03
Reduce delivery cost
Address the measured LCP path, image and font handling, JavaScript, long tasks, and layout shifts.
Output: Measured implementation changes - 04
Lock the release
Turn critical assumptions into automated checks and record the remaining manual Search Console and field-data steps.
Output: Repeatable verification suite
Migration checks that can be rerun
The published migration note shows the kind of route, canonical, redirect, metadata, and accessibility controls used on this site's own release. Measurements are labeled by environment rather than presented as client gains.
Scope boundaries
A clear no is part of reliable delivery.
These boundaries prevent the service from implying proof, access, or outcomes the current public evidence does not support.
- Guaranteed rankings, traffic, or rich results
- Fabricated schema, reviews, locations, or doorway pages
- Performance scores quoted without the environment and measurement date
Questions to settle before kickoff.
Commercial terms, account access, confidentiality, ownership, communication cadence, and support are confirmed for the actual engagement rather than implied on a marketing page.
01Can you guarantee a Lighthouse score or ranking?
No. Lab scores vary by environment, and rankings depend on far more than implementation. The work can target agreed thresholds, document actual results, and explain remaining constraints.
02Is technical SEO only metadata?
No. Metadata matters, but so do status behavior, crawlable content, canonical ownership, redirects, internal links, rendering, structured data, assets, accessibility, and release controls.
03Do you need Search Console access?
Many defects can be reproduced without account access. Search Console becomes important for verified index coverage, queries, migrations, and post-launch monitoring; access should be provided only through an agreed secure process.
Performance and technical SEO / Fit conversation
Define the release before committing to the build.
A useful first conversation covers the current state, intended release, open decisions, evidence available, and the constraints that cannot move.