Technical SEO skill
The playbook Moonrank's SEO Agent uses to audit a site's technical foundations — crawlability, indexation, rendering, redirects, canonicals, and Core Web Vitals — and return fixes a developer can ship this sprint.
Download the methodology, see how the agent traces issues to their root cause, or run it live inside the SEO Agent.
- Category
- SEO
- Agent
- SEO Agent
- Format
- technical-seo.md
- Price
- Free to download
The skill file
What is the Technical SEO skill?
The Technical SEO skill is how Moonrank's SEO Agent inspects the layer under the content: whether Google can crawl the site, render its JavaScript, resolve its canonicals and redirects, and index the pages that matter — with every finding traced to the template or rule causing it.
It's written as a SKILL.md, a plain-language instruction format that people and AI agents can both follow. Read it to run the checks yourself, hand it to your developers as an audit scope, or let the SEO Agent run it end to end.
Downloading the playbook is free with a Moonrank account. Re-running it on every deploy and migration, before problems reach the index, is what the SEO Agent does continuously.
See it in action
“We moved to a new JavaScript framework and half our pages disappeared from Google. Help.”
Your product descriptions and internal links only exist in the rendered DOM — raw HTML ships an empty shell, and 2,300 URLs fell out of the index over six weeks. On top of that, the new router 307s every trailing-slash URL, adding a hop to 100% of internal links. Ship server-side rendering on the product template first, then flatten the redirect rule — the first fix alone recovers most of the loss.
From input to fix list
- 1
You provide the domain
Plus Search Console coverage and server logs if you have them — they sharpen the indexation diagnosis.
- 2
Moonrank crawls as Googlebot
Status codes, robots rules, redirect chains, and a diff of raw HTML against the rendered DOM.
- 3
It traces every gap to a cause
Each missing or dropped URL is explained — noindex, canonical, rendering, quality, or discovery.
- 4
It returns fixes by template
Findings grouped by root cause, written as changes a developer can ship, then verified by re-crawl.
Everything it checks
Googlebot crawl
Status codes, robots rules, crawl traps, and redirect chains across the whole site.
Render diff
Raw HTML against rendered DOM, catching content and links that only exist after JavaScript.
Indexation reconciliation
Every gap between crawlable and indexed, with the specific reason named.
Canonical and redirect tracing
Chains followed to the end; loops, long chains, and canonicals pointing at redirects flagged.
Core Web Vitals per template
Failures measured where users are, with the blocking resource named.
Template-level fix list
Root causes grouped so one change fixes hundreds of pages, verified by re-crawl.
When to reach for it
- Recover pages that dropped out of the index after a framework change.
- De-risk a migration or redesign before it ships.
- Explain why published pages never get indexed.
- Turn a Core Web Vitals failure into a named resource to fix.
- Give developers SEO tickets specific enough to estimate and ship.