Technical SEO · Investigation / implementation

Technical SEO services that get to the cause.

Technical SEO services for teams that need more than another export. We connect crawl evidence, rendered pages and indexing signals to a decision your developers can implement and test.

Follow the evidence.

Missing from Google?
That is the beginning of the question.

“Not indexed” describes an observation. It does not identify whether the problem is discovery, retrieval, rendering, duplication or the usefulness of the page.

Discover

Can the URL be found?

Follow crawlable internal links from relevant entry points. Compare the sitemap with the intended public inventory. Search-only navigation and orphaned templates can leave important destinations poorly connected.

Retrieve

What does the response say?

Check the actual status, redirect destination and robots restrictions. A successful response that displays an error message can still be a poor destination. Review headers and page instructions together.

Interpret

What content and signals arrive?

Compare response HTML with the rendered page. Inspect main content, links, canonical output and relevant structured data. Use URL Inspection and log evidence where access is available.

Decide

Does this page deserve its own listing?

A near-duplicate collection may need consolidation. A genuinely distinct page may need clearer internal links or a corrected template. The goal is an intentional inventory, not an indexed copy of every URL.

We distinguish declared signals from Google’s selected canonical. A canonical is a consolidation signal, not a guaranteed instruction to select a page.

JavaScript and search

What a browser shows
is only part of the investigation.

A crawler must retrieve the page and understand the content and links. We investigate where a useful page depends on rendering or user interaction.

Response HTML · illustrative
<main id="catalogue">
  <div class="loading">Loading…</div>
</main>

Identify the dependency.

Check what arrives before scripts execute. An app shell is not automatically unindexable, but delayed content, blocked resources and script failures can change what is available for processing.

Useful output · implementation goal
<main>
  <h1>Desk lighting</h1>
  <a href="/products/task-lamp">
    Task lamp
  </a>
</main>

Test the intended result.

Make important content and destinations available reliably. Check crawlable links, client-side routing, status handling and metadata after navigation, not just the first page load.

We assess the existing stack before proposing server rendering, pre-rendering or a rebuild. Sometimes the right fix is a link or template change. A framework migration needs a broader business case and a release plan.

Useful prioritisation

Business relevance.
Evidence. Effort. Uncertainty.

A scanner’s severity label cannot tell you which development task deserves the next release. We separate the dimensions that affect that decision.

How technical findings become a prioritised backlog
FindingEvidence to collectDecision and verification
Unexpected canonical on a priority templateCompare affected and unaffected pages, declared output, internal links and inspection evidence.Correct the source if it is a template fault; consolidate if the destinations are duplicative. Recheck representative exceptions.
Faceted URL expansionMap parameter combinations, link generation and the useful search destinations in the range.Agree a stable indexable inventory and crawl rules. Avoid blocking a URL if a crawler still needs to read a changed page instruction.
Layout movement during purchase researchReview field data when available and reproduce shifts on representative mobile pages.Reserve dimensions for media and review late-loading app regions. Verify the actual journey after the change.
Conflicting product markupIdentify the generating theme or plugin and compare facts with visible product and market data.Assign ownership for overlapping facts; test multiple product states and public output after release.
Crawl-budget concernCheck size, change frequency, response health, duplicate inventory and available crawl/log evidence.Investigate allocation only where the evidence warrants it. Smaller sites often have a more direct discovery or quality issue.

Migrations & releases

Protect the destinations
your customers already use.

Before launch

Inventory and map.

  • Export existing public URLs and identify valuable landing pages using available evidence.
  • Map old pages to the closest useful new destination, including assets and market paths where relevant.
  • Preserve necessary content, metadata and internal connections.
  • Agree staging restrictions, responsibilities, backups and rollback conditions.
At release

Check the public response.

  • Verify representative redirects, status codes and canonical targets.
  • Confirm production crawling and indexing instructions.
  • Recheck navigation, forms, mobile interactions and rendered markup.
  • Update sitemaps and useful internal links to final destinations.
After release

Monitor the transition.

  • Compare observed crawling and indexing with the intended inventory.
  • Review redirected and newly published priority pages.
  • Investigate unexpected errors, redirect chains and landing-page losses.
  • Keep release dates and follow-up decisions in the change log.

No migration is made risk-free by a checklist. The checks make decisions visible and catch avoidable mistakes; they do not guarantee stable rankings.

The technical handover

A finding should survive
the journey to a developer.

A useful issue record includes the affected URLs or template, evidence of the current behaviour, the intended outcome and the reason to prioritise it. Impact and confidence are described separately from implementation effort.

We identify dependencies such as a plugin owner, routing rule, content decision or release freeze. Acceptance checks describe what someone can inspect immediately after the fix. A later improvement in search performance is monitored separately.

Your team can implement the work, or implementation can be scoped with Radian Ranks. We agree access, review ownership and deployment responsibility before changing production.

Evidence registerPrioritised backlogAcceptance checksRelease verification
Read a complete educational handover

Technical scoping questions

Before we inspect
the whole website.

A few practical questions to settle before choosing an SEO partner.

How is a technical SEO audit different from a crawl export?

The export is one source of observations. An audit tests what those observations mean for your intended pages, identifies the source of repeated symptoms and turns selected findings into decisions. Deliverables include evidence, ownership and acceptance checks rather than an unfiltered list of warnings.

Can you diagnose a JavaScript website without rebuilding it?

Yes. We can compare response and rendered content, links, navigation, status behaviour and metadata. The investigation may identify a limited template or routing fix. We only recommend a larger rendering or framework change when the evidence and business case support it.

Do you need server logs and Search Console?

They can materially improve a deeper investigation, but the first public review does not require account access. We identify which evidence is needed for the question, then agree read access or exports. Credentials should not be sent through an enquiry form.

Will better Core Web Vitals guarantee higher rankings?

No. Page-experience improvements can make the site more usable, but rankings depend on several systems and competing pages. We distinguish real-user metrics from lab diagnostics and test interaction paths as well as a score.

Can you work around a scheduled site migration?

A migration review needs the existing and proposed architecture, scope, release date and implementation owners. We can assess mapping, staging checks and launch verification within an agreed engagement. A last-minute request cannot substitute for the inventory and testing the change requires.

What if our audit finds that fewer URLs should be indexed?

That can be the right outcome. Duplicates, low-value filter combinations and overlapping pages may not need separate listings. We preserve useful customer navigation while defining which destinations should serve search intent.

Start with a useful conversation

Bring the technical question
your team needs answered.

Send your website and the question you need answered. We’ll review the public pages and discuss a sensible next step.

  • A focused public-site review. No passwords needed.
  • No paid engagement until scope and fees are agreed.
  • UK and Australian enquiries welcome.
Technical SEO reviewFree review

Find the technical blockers.

Share your website and the issue you are seeing. We’ll review the public pages and identify a useful next step.

Crawling & indexingPage performanceSite structure
Optional budget context

No payment details. No account login needed.
A focused review; implementation is scoped separately.