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.
Technical SEO · Investigation / implementation
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.
Evidence · ownership · acceptance checks
Illustrative planning view. No live website scan or ranking measurement is being performed.
Follow the evidence.
“Not indexed” describes an observation. It does not identify whether the problem is discovery, retrieval, rendering, duplication or the usefulness of the page.
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.
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.
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.
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
A crawler must retrieve the page and understand the content and links. We investigate where a useful page depends on rendering or user interaction.
<main id="catalogue">
<div class="loading">Loading…</div>
</main>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.
<main>
<h1>Desk lighting</h1>
<a href="/products/task-lamp">
Task lamp
</a>
</main>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
A scanner’s severity label cannot tell you which development task deserves the next release. We separate the dimensions that affect that decision.
| Finding | Evidence to collect | Decision and verification |
|---|---|---|
| Unexpected canonical on a priority template | Compare 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 expansion | Map 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 research | Review 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 markup | Identify 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 concern | Check 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
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 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.
Read a complete educational handoverTechnical scoping questions
A few practical questions to settle before choosing an SEO partner.
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.
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.
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.
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.
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.
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.
Related investigations
Start with a useful conversation
Send your website and the question you need answered. We’ll review the public pages and discuss a sensible next step.