---
name: blitz-seo
description: Runs a focused 30-day SEO sprint that concentrates search-intent alignment, internal link equity, first-hand proof, and targeted backlinks onto a single money page to push it into the Top 3. Use when a high-value page is stuck on Page 2, the user mentions "blitz seo" or a 30-day SEO sprint, or SEO effort is spread too thin across dozens of URLs.
metadata:
  version: 1.0.0
  author: illyism
  source: https://il.ly/skills/blitz-seo
title: blitz-seo
canonical_url: https://skilld.dev/gh/illyism/seo-skills/blitz-seo
last_updated: 2026-11-21T21:01:40.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install illyism/seo-skills/blitz-seo`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/blitz-seo`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/illyism/seo-skills/blitz-seo) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/blitz-seo`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/blitz-seo --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/blitz-seo --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Blitz SEO: a 30-day sprint to rank one page

Put 30 days of effort into ranking one page for one money keyword (3 at most). Most SEO work is spread across too many pages. Hundreds of pages past position 10 earn little; 1-3 money pages in the top 3 earn most of the revenue.

## Initial assessment

**Check for project context first:** if `.cursor/project-context.md` or `.claude/project-context.md` exists, read it for product, audience, and current rankings. Otherwise identify:

1. **Money keyword candidates**: high-intent, high-volume keywords tied to the core offering. Not blog keywords, not long-tails.
2. **Current position**: a page stuck at position 5-20 is the ideal Blitz target (already indexed, needs pressure).
3. **Revenue link**: would ranking top 3 for this keyword directly produce signups or sales?
4. **Available resources**: backlink budget, existing blog posts for internal links, social accounts for signals.

**The target test:** your Blitz keyword should be something that _hurts to lose_ to competitors.

## The sprint

### Step 1: Pick one keyword that matters

- High intent, tied to the core offering, with real revenue behind it
- Check the SERP: if competitors with weaker products outrank the user, that is the target
- Limit to 1 keyword (3 absolute max). Saying no to everything else is the strategy.

### Step 2: Choose one page to win with

Rewrite and optimize a single page to own that keyword:

- Tight H1 with the keyword
- Keyword in title tag, URL, and meta description
- LSI/related phrases in subheadings
- Fast load speed, mobile-optimized
- Visual trust: screenshots, logos, charts, testimonials
- Make it the hero of the domain: link to it from the homepage and main nav if possible

### Step 3: The daily optimization ritual (30 days)

Every day:

- [ ] Add internal links from older posts/pages to the target page
- [ ] Build 3-5 new backlinks pointing at the target page
- [ ] Make one on-page tweak based on competitor SERP analysis
- [ ] Re-submit the page in Google Search Console
- [ ] Share the page contextually (Reddit, Quora, X) where relevant
- [ ] Log every change and the daily rank position

Do not overthink any single change. Iterate fast, observe, adjust.

## Output

When the user invokes this skill, produce a concrete sprint plan:

1. Recommended target keyword (with reasoning) and target page
2. On-page rewrite checklist specific to that page
3. A 30-day calendar with the daily ritual filled in
4. A simple tracking log format (date, change made, position, notes)
5. Benchmarks: page-one movement expected around day 14-20 if pressure holds

## When to use it

Use Blitz SEO when:

- Stuck on page 2 for a keyword that brings revenue
- Launching something new that needs one page to win fast
- Weaker competitors outrank the user

Do not use it for brand-new domains with zero authority, or for keywords with no revenue attached.

## Reference result

Original sprint: position #11 to page one by day 17, position #3 by day 30. Organic traffic to the page up 720%, CTR 2.8x higher.

## Related

- Full article: https://il.ly/blog/blitz-seo
- Conversion copy for the winning page: [blitz-copy](https://il.ly/skills/blitz-copy)
