Technical SEO3 min read
The technical SEO checklist for developers
Technical SEO is mostly engineering work: correct status codes, canonical URLs, crawlable HTML and fast pages. None of it requires a keyword tool.
A canonical URL tells search engines which version of duplicate or near-duplicate content should be indexed and receive ranking signals. Declared with rel=canonical or an HTTP header, it is treated as a strong hint rather than a directive, so consistency across sitemaps, internal links and redirects matters as much as the tag itself.
<!-- Self-referencing canonical on the page you want indexed -->
<link rel="canonical" href="https://rovqix.in/blog/canonical-urls-explained">It consolidates duplicate versions into one indexed URL and passes ranking signals to it. Google weighs it alongside internal links, sitemap entries, redirects and hreflang — if those disagree with your tag, it may pick a different canonical and report the discrepancy in Search Console.
| Situation | Canonical target |
|---|---|
| Same page reachable with and without parameters | The clean URL |
| Product in multiple categories | One primary product URL |
| Print or AMP variant | The main version |
| HTTP and HTTPS, www and apex | Redirect instead; canonical as backup |
| Syndicated content on another domain | Your original URL, set on their copy |
| Paginated series | Each page canonical to itself |
| Canonical | 301 redirect | |
|---|---|---|
| Both URLs remain accessible | Yes | No |
| Users can reach either version | Yes | No |
| Signal strength | Hint | Directive |
| Use for | Parameters, variants, syndication | Moved or merged pages |
If a user has no reason to see the duplicate, redirect. If both versions serve a purpose — a filtered view, a print page, a category path — keep them and canonicalise.
// Next.js: derive the canonical from the route, never hand-write it
export async function generateMetadata({ params }): Promise<Metadata> {
const { slug } = await params;
return {
alternates: { canonical: `https://rovqix.in/blog/${slug}` },
};
}No. It is one signal among several. If internal links, the sitemap and redirects point elsewhere, Google may select a different canonical and tell you so in Search Console.
Yes, and it is the correct approach for syndicated content — the republishing site sets a canonical to your original. Whether they will is a commercial question.
Canonicalise filtered views to the unfiltered URL when the filtered version should not rank. If a filtered view targets genuine demand, give it a self-canonical and unique content instead.
ROVQIX Growth
SEO & growth team, ROVQIX
The ROVQIX growth team handles technical SEO, Core Web Vitals and AI-search visibility for the sites we build. Recommendations here are the ones we apply to client projects and to rovqix.in itself.
ROVQIXdesigns and builds production web platforms — Next.js front ends, Node.js APIs and the infrastructure behind them. Tell us what you're building and we'll scope it with you.
Technical SEO is mostly engineering work: correct status codes, canonical URLs, crawlable HTML and fast pages. None of it requires a keyword tool.
Migrations lose traffic for one reason more than any other: a redirect map that was built quickly and never checked.
Hand-writing meta tags per page guarantees drift. Here is how we wire the Metadata API once so no page can ship without a canonical, an OG image and a description.
No spam. Just the occasional case study and craft breakdown.