What this prompt does
This prompt makes the model act as a senior technical SEO engineer and produce a sequenced WordPress SEO overhaul specified tightly enough to execute — concrete tasks and tools, not platitudes. Four placeholders shape it: [site_url] (the site being audited), [seo_plugin] (Rank Math or Yoast, used for on-page and schema), [timeline] (how long the plan spans), and [primary_goal] (the outcome everything is prioritized against).
The structure works because overhauls fail when they become a vague wishlist instead of an ordered plan. By demanding a week-by-week task list with the tool for each task and a measurable success metric, the prompt forces sequencing — fix indexation and Core Web Vitals before chasing new content. Anchoring the keyword and topic map to [primary_goal] keeps the content work pointed at a real objective rather than generic traffic. Scoping the plan to [timeline] decides how much can realistically fit, and naming [seo_plugin] keeps the schema and redirect tasks described in terms of features you actually have rather than a tool you would have to swap to.
When to use it
- You are running SEO recovery on a site whose traffic or indexing has dropped.
- You want a sequenced plan instead of a scattered list of SEO to-dos.
- You need a schema plan (Article, FAQ, Breadcrumb, Organization) implemented through
[seo_plugin]. - You are prioritizing technical fixes and want indexation and crawl issues handled before content.
- You need a Core Web Vitals and speed task list tied to specific fixes.
- You want each task mapped to a tool and a measurable success metric across
[timeline].
Example output
Expect a week-by-week plan structured as a task list. Each entry names the task, the tool or plugin to use, and a measurable success metric. It opens with a technical audit of [site_url] (indexation, duplicate content, thin pages, crawl issues), then a content gap and keyword map aligned to [primary_goal], a schema plan via [seo_plugin], Core Web Vitals fixes, internal linking and a redirects audit, and finally sitemap verification plus a Search Console monitoring plan.
Pro tips
- Set
[primary_goal]concretely (e.g. recover organic traffic and rank service pages) so the keyword map and priorities actually point somewhere. - Front-load deliverable one — you cannot rank pages Google cannot crawl or has flagged as thin, so let the audit drive the order.
- Match
[seo_plugin]to what the site already runs; Rank Math and Yoast configure schema and redirects differently. - Keep
[timeline]realistic; a compressed two-week plan should defer net-new content until technical issues are cleared. - Ask the model to make each success metric measurable (positions, indexed count, CWV thresholds) so you can tell whether a week's work landed.
- Have it tie the redirects audit to real data — fix chains, 404s, and orphan pages it can name on
[site_url]rather than hypothetical ones. - Pair the Search Console monitoring plan with the keyword map so you are tracking the exact queries
[primary_goal]depends on, not vanity terms.
