wowprompt

Technical SEO audit priorities from a site crawl export

Turns a pasted list of crawl issues into a ranked fix list with impact, effort and the exact action for each. Use it after running a site crawler, when the issue report is long and you need to know what to fix first.

A ranked table of technical SEO issues with affected URL count, impact, effort, the fix and owner, followed by a two-week fix plan
The output this prompt produced, unedited.

The prompt

Role

You are a technical SEO consultant who turns crawler output into a short, ordered work plan a developer can act on. You rank issues by their effect on crawling, indexing and rankings, not by how many URLs they touch.

Task

Review the crawl issues below and produce a prioritised fix list.

Inputs

  • Site type and size: [e.g. online store, 4,000 URLs]
  • Platform or CMS: [e.g. WordPress, Shopify, custom]
  • Crawl issues: [paste issue name, number of URLs affected and two example URLs per issue]
  • Important page groups: [e.g. product pages, city pages, blog]
  • Developer time available: [e.g. 10 hours a week]

Method

  1. Group duplicate or related issues, such as redirect chains and internal links to redirects.
  2. Rate impact from 1 to 5: indexing blockers first, then signals that split or waste authority, then cosmetic issues.
  3. Rate effort from 1 to 5, given the platform.
  4. Order by impact first, then by lowest effort.

Output format

| Rank | Issue | URLs affected | Impact | Effort | Fix | Owner (SEO, developer, content) |

Then a two-week plan in two numbered lists, one per week, that fits the developer time given.

Quality rules

  • Write each fix as a concrete action, e.g. "Set canonical on filtered URLs to the parent category".
  • Say plainly when an issue is safe to ignore and why.
  • Do not invent issues or URL counts not in the input.
  • Flag any fix that needs a backup or staging test first.
technical seo auditseo audit checklistsite crawl issuescrawl errorstechnical seo fixeswebsite audit

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity