Legacy SEO recovery

A practical 14‑step SEO playbook to recover and grow organic traffic

Turn the original '14 proven techniques' into an executable plan: prioritized fixes, content briefs, redirect and pruning guidance, structured-data snippets, and AI prompts your writers and engineers can run today.

Get the exportable checklist Browse SEO resources

Playbook overview

How to use this playbook

This guide converts the 14 techniques into immediate, owner-assigned work: a triage order for common problems, compact checklists you can export as CSV/Sheets, and prompt clusters for automated briefs, audits, and structured-data generation. Use the Quick Start checklist if you manage a site under 1,000 pages.

Triage first: address indexability and crawl errors, then Core Web Vitals, then content gaps.
Assign each task an owner: Engineering (performance, redirects), Content (briefs, pruning), SEO (priority, SERP features).
Export checklists and prompts to Google Sheets or your issue tracker for sprint planning.

Immediate 48–72 hour triage

Quick Start: Priority checklist for sites under 1,000 pages

If traffic is down or stagnant, run this compact triage. These steps reveal high-impact fixes you can complete quickly and schedule for follow-up.

Check Search Console → index coverage, mobile usability, and top-queries drop.
Run a crawl (Screaming Frog) for redirect chains, duplicate titles, and missing canonicals.
Identify top 20 pages by impressions and ensure they have focused, non-duplicate H1s and meta tags.
Flag pages with thin content (<300 words or low entity coverage) for refresh or consolidation.
Run PageSpeed Insights on representative templates to capture LCP/CLS errors.

Quick triage checklist (exportable)

CSV columns: issue,type,url,priority,fix,owner — ready for import into Sheets or Jira.

Indexability issues — SEO — example.com/page — High — Add canonical/resolve noindex — Engineering
LCP regressions — Performance — /product — Medium — optimize images/server timing — Engineering
Thin content — Content — /blog/post — Medium — merge + expand brief — Content

Content-first execution

On‑page & content operations

Convert keywords and gaps into production-ready content using tight briefs and internal linking plans. Each content task includes target intent, H1/H2 outlines, and SERP features to pursue.

Use content briefs with: title options, H1/H2 outlines, entities, related questions, internal link targets, and meta variants.
Prioritize pages with high impressions but low CTR — optimize SERP snippet and headings first.
Create a content-pruning plan for thin or cannibalized pages: consolidate duplicates into a merged brief.

Content brief generator (AI prompt)

Prompt to hand to an LLM or content tool that outputs a publishable brief.

Prompt: Create a detailed content brief for target keyword "[keyword]" (intent: commercial/informational/transactional). Include title options, H1/H2 outline, target entities, related FAQ, internal links, SERP features to target, suggested wordcount range, and meta description variants.

Meta & SERP optimization

6 title + description variations to A/B test for CTR lift.

Prompt: Produce 6 meta title variations (50–60 chars) and 6 meta descriptions (120–160 chars) optimized for CTR for [page URL] using primary and a supporting keyword.

Crawlability, Core Web Vitals, and render path

Technical & performance fixes

Address indexability and performance issues that block ranking. Provide concrete, code-level suggestions and Lighthouse budgets for common problems.

Resolve redirect chains, remove duplicate titles, and ensure canonical tags match indexable URLs.
Prioritize Core Web Vitals triage when LCP or CLS failures align with high-traffic pages.
Set Lighthouse budgets and instrument changes in staging; use synthetic and field data to verify improvements.

Technical audit prompt

Prompt to generate a CSV-style prioritized fix list for engineers and SEO.

Prompt: 'Perform a sitewide SEO technical audit for https://example.com — report indexability issues, duplicate titles, redirect chains, hreflang problems, missing canonical tags, sitemap inconsistencies, and a prioritized fix list with estimated effort (low/medium/high). Output as CSV rows: issue,type,url,priority,fix,owner.'

Core Web Vitals triage prompt

Turn CWV trends into a developer task list with budgets.

Prompt: 'Analyze Core Web Vitals trends for the last 90 days and return a prioritized task list to improve LCP, FID/INP, and CLS with specific code-level suggestions and suggested Lighthouse budgets.'

Preserve rankings during site changes

Migration, redirects and legacy URL recovery

Migrations and pruning failures cause ranking loss. Use a measured redirect plan, canonical cleanup, and a merged-content strategy for legacy pages.

Build a redirect map with source, target, HTTP status, and rationale; avoid redirect chains and unnecessary 302s.
When consolidating content, produce a merged-content brief and 301 source → canonical mapping.
Run pre- and post-migration crawls and compare index coverage and top queries.

Content pruning checklist

How to decide: prune vs update vs canonicalize.

Prune: low impressions, no backlinks, and no conversion signal.
Update: pages with impressions and partial rankings but thin content.
Canonicalize/redirect: duplicate intent pages where consolidation preserves backlinks.

Measure impact and avoid regressions

Monitoring, KPIs & reporting

Define a compact SEO dashboard and cadence to prove business impact and catch regressions early.

Track KPIs: impressions, clicks, top‑10 keyword count, organic conversions, pages with CWV failures, index coverage errors, and crawl anomalies.
Set monitoring cadence: weekly for performance and index status, monthly for content health and backlink trends.
Export alerts as CSV or integrate with Sheets to create automated sprint lists.

Monitoring & KPI prompt

Generate a dashboard definition and alert thresholds.

Prompt: 'Define an SEO dashboard: list 10 KPIs (Search impressions, clicks, top-10 keyword count, organic conversions, pages with CWV failures, index coverage errors, crawl budget indicators) and provide a monitoring cadence and alert thresholds.'

Prompts and templates you can run

AI prompt toolkit & exportable artifacts

Turn strategy into artifacts: content briefs, audit CSVs, JSON-LD snippets, internal-link plans, and outreach templates. Each prompt produces an output that can be imported into CMS, Sheets, or an issue tracker.

Structured data generator to create Article, BreadcrumbList, and FAQPage JSON-LD for pages you update.
Internal linking plan prompt that outputs anchor text, source URL, target URL, and rationale as CSV.
PR and link outreach sequences to support content promotion and data-driven resources.

Structured data generator prompt

Create JSON-LD for enhanced results and rich snippets.

Prompt: 'Generate JSON-LD for Article, BreadcrumbList, and FAQPage for this article; include author, publishDate, mainEntityOfPage, and example FAQ Q&A pairs.'

Internal linking plan prompt

Boost pillar pages by inserting high-impact internal links.

Prompt: 'Audit top 50 pages by impressions and suggest 30 internal link insertions to boost link equity to target pillar pages. For each suggestion include anchor text, source URL, target URL, and rationale.'

PR & link acquisition brief

Turn research into outreach workflows for editorial links.

Prompt: 'Draft an outreach email sequence for earning editorial links for a data-driven resource: include subject lines, pitch hooks, value props, and follow-up schedule.'

Owner-ready artifacts

Execution templates and handoffs

Each technique maps to an artifact you can hand to an owner: CSV audit rows for engineers, content briefs for writers, and JSON-LD for publishing. Use the following owner model to structure sprints and responsibilities.

Engineering: performance fixes, redirect maps, canonical and sitemap updates.
Content: briefs, pruning decisions, meta optimization, internal linking changes.
SEO/PM: prioritization, monitoring, and cross-team coordination.

Hand-off CSV template

Columns recommended for issue trackers and Sheets.

columns: issue,id,type,source_url,target_url,priority,effort,owner,status,notes

Sprint planning sample

Sample 2-week sprint composition for mixed teams.

Week 1: crawl + top-20 page on-page fixes + 3 engineering performance tickets
Week 2: content refresh rollouts + redirect map fixes + monitoring verification

FAQ

Which of the 14 techniques should I do first on a site under 1,000 pages?

Start with indexability and crawl issues (Search Console coverage), then audit top pages by impressions and fix snippet/heading issues. Run a lightweight performance sweep (PageSpeed Insights) on representative templates. Use the Quick Start 48–72 hour triage checklist to convert findings into sprint tickets.

How do Core Web Vitals changes influence the priority of technical fixes?

Prioritize CWV work when failures affect high-impression or high-conversion pages. Use field data to confirm user impact, then apply a Core Web Vitals triage: reduce server response/LCP causes first, then address CLS and interactivity. Code-level fixes should be scoped with Lighthouse budgets and validated in staging.

What signals indicate a page should be pruned vs updated vs canonicalized?

Prune when a page shows low impressions, no backlinks, and no conversion signal. Update when it has impressions or partial rankings but thin content. Canonicalize or merge when multiple pages target the same intent—preserve backlinks by redirecting duplicates to the consolidated URL and provide a merged-content brief.

How to measure the business impact of content refreshes and technical work?

Map changes to KPIs: organic clicks, top-10 keyword count, and organic conversions. Use a measurement window (e.g., 4–12 weeks) and compare to a pre-change baseline; annotate deployments in analytics so you can attribute uplifts and regressions to specific fixes or content launches.

Are schema and structured data still worth implementing for organic traffic gains?

Structured data helps search engines understand content and can unlock SERP features (rich snippets). Implement Article, BreadcrumbList, and FAQPage where relevant. Use the structured-data generator prompt to produce JSON-LD and validate with the Rich Results Test before publishing.

How should I adapt this playbook for an e-commerce site vs a content site?

E-commerce: prioritize product schema, canonicalization for faceted navigation, and performance on category/product templates. Content sites: focus on entity coverage, topical authority, and content pruning/merging. Both need redirect discipline and monitoring for index coverage changes after edits.

What does a safe redirect and migration plan look like for preserving rankings?

A safe plan includes a comprehensive redirect map, pre- and post-migration crawls, preserved sitemap and robots checks, and a staged rollout with monitoring for traffic drops. Avoid redirect chains, use 301s for permanent moves, and keep a rollback plan. Annotate migrations in analytics for attribution.

How often should I re-run full-content and technical audits after fixes?

Schedule lightweight audits weekly for indexes and top pages, monthly for content health and backlink reviews, and a full technical crawl quarterly or after any major site change or migration.

How do I use internal linking to surface new pillar pages quickly?

Audit top pages by impressions, then add contextual links from high-impression sources into your pillar. Use an internal linking prompt to output anchor text, source URL, target URL, and rationale as CSV so editors can implement links at scale.

What team roles and time allocation are needed to execute this 14-point playbook?

A minimal team: 1 SEO lead to prioritize and monitor, 1–2 content owners for briefs and refreshes, and 1 engineering resource for technical and performance fixes. Time allocation varies by site health—initial triage may take 1–2 weeks, with ongoing cycles of content updates and monitoring.

BlogSEO insights and tutorials.
PricingPlans and export capabilities.
ComparisonHow Texta compares to other SEO tooling.
AboutCompany and mission.
IndustriesSector-specific SEO guidance.