---
title: "Technical SEO"
description: "Technical SEO from ShoutRank: crawl, indexation, rendering, canonicals, and the HTML a bot receives. For sites that already have something to say."
canonical: https://shoutrank.com/technical-seo
markdown: https://shoutrank.com/technical-seo.md
---

# Technical SEO

Technical SEO from ShoutRank: crawl, indexation, rendering, canonicals, and the HTML a bot receives. For sites that already have something to say.
Technical SEO is the work of making the right URLs available, and keeping the wrong ones out of the index.

Teams call this a cleanup. It is closer to editing. Which templates can be crawled, which canonical is telling the truth, and whether the HTML a bot receives is the page a person sees.

ShoutRank does this before rewriting a library of posts. Advice that never ships to a crawlable URL does not change search.

ShoutRank does not guarantee a ranking or a citation.

## The problem

### The index is full of URLs nobody chose.

Filters, parameters, tag archives, and old campaigns sit beside the pages that make money. Google spends the crawl on the pile.

### The rendered page and the document disagree.

A client-side app, a consent banner, or a template bug hides the title, the links, or the main copy from the first HTML response.

### Canonicals point at the loser.

The URL you want is canonicalized to a thinner one, or several near-duplicates all claim to be the original.

## How ShoutRank approaches it

We start from the templates, not from a 400-line crawl export nobody will read. Revenue URLs first. Then the rules that create the rest.

Fixes are shipped with the people who own the repo or the CMS. After release we fetch the URL again and read the HTML, the same way the [free visibility audit](https://shoutrank.com/visibility-audit) does for a single page.

## What the work includes

### Indexation rules

What may be indexed, what should consolidate, and which parameters are noise.

### Template notes

Titles, canonicals, internal links, and status codes, checked on the templates that matter.

### Rendered HTML

A comparison of the document a bot receives and the page a person gets.

### Release checks

The same URLs fetched again after the change, so a deploy does not silently undo the fix.

## Process

### Discovery

List the templates that earn revenue queries, and the ones a migration or a plugin left behind.

### Audit

Crawl the host and read coverage, canonicals, and status codes against Search Console.

### Strategy

Decide which templates stay, which merge, and which rules change before any copy project starts.

### Implementation

Ship the crawl fixes with the team that owns the code, then refetch the HTML.

### Monitoring

Watch coverage and the assigned URLs, not a sitewide health score.

### Optimization

Reopen templates that still split one query across several URLs.

### Reporting

A fixed table: what was blocked, what was merged, and what Google did with those URLs.

## Why ShoutRank

### The HTML is the evidence

We read the document that was served. A screenshot of a dashboard is not a crawl.

### It sits under the rest of the practice

On-page work and AI citations both assume the URL can be retrieved. Technical SEO is how that stays true.

### English, beside your developers

ShoutRank was founded by Praneet Thakur. The technical work is done with your developers, in English, wherever the repo lives.

## How success is measured

Coverage of the URLs you meant to index, and the disappearance of the ones you did not.

Whether the canonical in the HTML matches the URL assigned to the query.

Fetch time and index status on the template set, read on a fixed day.

A named client result is published when that client clears the figure. Until then the report is the measurement.

## Questions

### Is technical SEO a one-time project?

The first pass is a project. Templates keep changing, so the rules need an owner after the project ends. Some teams keep us for that. Some take the rules in-house.

### Will you replace our developers?

No. We specify the change and check the HTML after it ships. Your team, or the agency that builds the site, writes the code.

### Does Core Web Vitals replace this?

Speed is one check. A fast page with the wrong canonical is still the wrong page.

## Related

- [SEO audit](https://shoutrank.com/seo-audit): The wider read, when the question is not only technical.
- [Enterprise SEO](https://shoutrank.com/enterprise-seo): The same rules, across many templates and owners.
- [A migration](https://shoutrank.com/seo-migration): When the technical risk is a new platform, not the current one.