Crawling, rendering, indexation and site architecture — the layer that decides whether content is eligible to rank at all. Technical work is worth doing when something is actually blocked, and not otherwise. Technical SEO at Amrut Services.
Technical SEO decides whether your content is allowed to compete at all. Crawling, rendering, indexation and site architecture sit underneath everything else, and when one of them is broken no amount of content or link work will produce a result — you are optimising pages that were never in the race. The corollary matters just as much and is said far less often: when none of them is broken, further technical work produces very little. Technical effort should follow evidence of a technical constraint, not run as a default because it is the part that feels rigorous.
On JavaScript-heavy sites the document a crawler receives and the page you see in your browser are frequently different documents. Links that exist only after hydration may never be followed. Content injected client-side may never be indexed. Pagination implemented in the framework may present as a single page with no onward paths. None of this is theoretical and all of it is verifiable in minutes by comparing the raw response, the rendered DOM and what actually appears in the index. Where they diverge, that divergence is usually the whole story, and the fix belongs with your developers rather than your content team.
Large sites routinely spend most of their crawl on parameter URLs, filtered views, session artefacts and pagination that will never rank. Server log analysis shows precisely where it goes, which is a different and more reliable picture than a crawler simulation. Redirecting that attention toward the pages that earn revenue is often the fastest structural improvement available on a big site, and it is particularly acute in ecommerce, where faceted navigation can generate tens of thousands of URLs from a modest catalogue.
Site architecture is a technical concern and a relevance concern at the same time. How deep a page sits, how many internal links point at it and what those links say all affect whether it is crawled often and whether it is understood. A page four clicks from the homepage with two internal links pointing at it is telling a search engine something about its importance, whatever the sitemap claims. Restructuring is expensive; changing the internal link graph usually is not, and it is covered separately under internal linking.
Most large technical losses happen during a migration, and almost always for the same reasons: URL changes without a complete one-to-one redirect map, redirect chains that dilute signals, canonical or hreflang implementations that change without anyone noticing, or a new template that drops structured data and internal links. A migration handled properly is unremarkable. One handled badly can remove a year of accumulated authority in a fortnight, and if that has already happened the right response is recovery diagnostics rather than a general audit.
Technical work is the first stage of the sequence, and it is scoped from the findings in audit and diagnostics rather than assumed. Once pages are eligible, relevance work follows under on-page SEO, then authority through off-page work and earned links. Platform-specific constraints are covered under Shopify SEO, and multi-location businesses should read local search alongside this. Specifications are written with acceptance criteria so in-house developers can implement them directly, which is how consulting engagements usually run; agencies can have the same work delivered under their brand through white label. The full programme is under SEO services and the practice on the Amrut Services homepage.
The most useful technical metric on a large site is not a health score, it is the ratio of pages you want indexed to pages actually indexed and earning impressions. Most sites have never measured it. When you do, the shape of the problem usually appears immediately: a template excluded, a section behind a parameter, a product range that has never been crawled, or twenty thousand indexed URLs nobody intended to publish. That single number frames the entire technical brief and gives you something to measure progress against that a client can understand without a glossary.
Technical recommendations fail more often in delivery than in analysis. A list of issues emailed to an engineering team competes with the product roadmap and loses. Specifications with acceptance criteria, written in the vocabulary of the people implementing them, sized so they fit a sprint, get shipped. Where a fix is expensive, the cost is stated honestly alongside the expected return so the trade-off is visible and someone can decide against it on informed grounds. That is the same discipline applied in consulting engagements, where your team does all the building.
Related SEO services: SEO Services · SEO Audit & Diagnostics · SEO Recovery · Local SEO · Ecommerce SEO · Shopify SEO · On-Page SEO · Off-Page SEO · Link Building · Internal Linking Service · SEO Consulting · White Label SEO for Agencies.
Specialist work: Who I Work With · SEO for Criminal Defense Attorneys · SEO for Personal Injury Law Firms · SEO for Chiropractors · SEO for Roofers and HVAC Contractors.
More on Technical SEO: the full technical seo guide · PDF version · all Amrut Services documents.
Amrut Services — SEO consultant, Vadodara, Gujarat, India · +91 93769 10109 · mehuldedhiaa@gmail.com · amrutservices.com.