TechnicalCollectible prompt

Content inventory and audit before a website redesign

List every page on your current site and decide what to keep, rewrite, merge, cut or redirect.

ChatGPTClaudePerplexity

Curated by Nvoka

Nvoka wordmark logo
Nvoka wordmark logoTechnical

Content inventory and audit before a website redesign

Act as a content strategist preparing a website redesign. Build a content inventory and audit of {{website_url}}. The new site's goal: {{goal}}, for {{target_audience}}. Visit the site and its XML sitemap if you can. If you can't browse, say so and ask me to paste the sitemap or a list of URLs rather than guessing. Return a table with one row per page: URL, page title, content type, purpose, main call to action, last updated if shown, quality from 1 to 5 with a reason, and a decision: keep, rewrite, merge, cut or replace. For every cut or merged page, give the URL it should redirect to. Then: 1. Content that is outdated, duplicated or thin 2. Gaps: questions our audience asks that no page answers 3. Pages to handle carefully because they likely bring search traffic or links, with a reminder to confirm this in my analytics 4. A proposed page list for the new site 5. A redirect map to hand to the developer Mark anything you couldn't verify.
Technicalnvoka.com/library/nvoka-content-inventory-before-a-website-redesignScan to open
Technical

Content inventory and audit before a website redesign

List every page on your current site and decide what to keep, rewrite, merge, cut or redirect.

Nvoka logo

Curated by Nvoka

ChatGPTClaudePerplexity
Add to my library

Make it yours

Fill in the blanks and change any word. Only your copy changes, never the card.

Fill in the blanks

0 of 3 filled

Your prompt

Act as a content strategist preparing a website redesign. Build a content inventory and audit of {{website_url}}. The new site's goal: {{goal}}, for {{target_audience}}. Visit the site and its XML sitemap if you can. If you can't browse, say so and ask me to paste the sitemap or a list of URLs rather than guessing. Return a table with one row per page: URL, page title, content type, purpose, main call to action, last updated if shown, quality from 1 to 5 with a reason, and a decision: keep, rewrite, merge, cut or replace. For every cut or merged page, give the URL it should redirect to. Then: 1. Content that is outdated, duplicated or thin 2. Gaps: questions our audience asks that no page answers 3. Pages to handle carefully because they likely bring search traffic or links, with a reminder to confirm this in my analytics 4. A proposed page list for the new site 5. A redirect map to hand to the developer Mark anything you couldn't verify.
See all